So we did a lan last weekend with 22 players in this new 434 POH theatre. We encountered some issues wich might be important here.
For the lan itself, i always setup a test mission, to see if players are able to join the server and test their hardware, before the actual lan missions begin. We found out that this mission itself crashed each time after about 25 minutes. The crashlogs from different players all showed the same error:
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
00000000400E020A Falcon BMS.exe, PrimitiveCollectionClass::GetBSPTexture()+10 byte(s), e:\wip\bms\svn\source\rel-4.34\graphics\bsplib\bspmeshbuilder.cpp, line 535+10 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 0000000000000000 caused an access violation.
Bytes at CS:RIP: 8B 14 88 81 FA 0F 27 00 00 75 0D 48 8B 05 FC 34
We went looking for this error on the forums and found that the balkans theatre has had a similar problem. Further deduction we’ve cautiously concluded that there could be a problem with the mig21 model or texture. The test mission was the only mission that actually had a mig21 in it, so we went ahead and tested with one of the actual prepared missions.
The actual lan missions themselves seemed much more stable. However not without problems of spontanious crashes to desktop without actual notifications of the crash itself. You just switch to desktop and BMS is nowhere to be found anymore.
Also had lots and lots of people unable to move their throttle, but i believe this is an 434 mulitplayer issue and not really a theatre issue.
Another thing i also noticed: I like to use the VMT tool a lot for briefings on the lan. There is an early, early version that is able to load 434 mission files. However on the POH theater it fails. Not sure where the fault is, POH or VMT, but i thought you should be aware of it none the less.
I would like to stress that we aren’t actually able to tell if the issues are 434 or POH related. However we did test the lan network by flying in KTO for an hour with 22 people and encountered no problems. When doing the same in the POH theater with the simplest mission we could think of resulted in crashes around the 30 mins mark.
The network was setup using direct connections to a gigabyte switch, with serverhostall set to 1, and all object density set to max on all players.
server computer has a 9900k proccessor, 2080 RTX TI card, 32GB memory. it didnt even break a sweat.
to be sure we also tested with serverhostall set to 0, made no difference.
bandwith on clients was set to 4096 for up and down. Using the alt-O key in game allowed the server computer to display all the network connections. No client ever came close to 1000kbs, and the slowest ping we ever saw was 2ms. Most were at 0ms. No blue letters with desyncing were encountered. We saw a warp once, but only for a few seconds and was probably related to the client computer that saw it.
We used the exact same setup we used 6 months ago. We had a lan in 433 then, and used the POH the too. (i believe i posted about it). That ran rock solid, no problems at all.
Our squadron really loves your theatre. It is fantastic and we are going to fly more of it. I hope we can help solve this stability issue we encountered. Depending on it being a POH issue or BMS.