Last night I was testing the Building State fix and some client-side performance tweaks (compiler settings that might affect performance). I needed someone to help me so I roped merlin51, ptxl, etain and jizzyjaz into assisting me.
Some of the tests were pretty interesting – we were flying over Flamierge where there was an intense ground and air battle going on (great to see so many people flying now). My frame rate was hitting 110fps, and as I dove down on the town, not a single chug. Then I got close and suddenly lots of small, sharp, stutters. Overall, probably the same total amount of pause but spread out so I was able to avoid hitting the ground. The same build, however, gave merlin51 a completely smooth ride. He was turning and weaving over the town before bugging out and RTBing.
There was one build gave me 138fps taking off and flying to town, but the stutters approaching the town were hideous. That one might be worth persuing, I was messing with the /heap and /stack arguments in the compiler, but I’m the host coder and I really haven’t had enough time to fully grok all the relevant aspects: just enough to known and validate its a worthwhile avenue of persuit. (Right now we just use the defaults for all of those linker values).
Unfortunately, I needed to do the test as Axis. Merlin51 was playing Allied but volunteered to take one for the team and switch Axis.
Apparently it got him booted from BKB :(
Anyway, the builds are looking good but I think we’ll go with a minimal set of these changes, the ones that didn’t cause any negative impact on any of the tests, but don’t expect double the FPS.