Stitcher
Caldari
J.I.T. Enterprises
Freelancer Alliance
   |
Posted - 2007.02.11 04:33:00 -
[1]
And the award for ignorant flamebait troll post of the week goes to....
 Originally by: ArtemisEntreri
This did not deserve a thread, there is no reason to post this on the forums, and lastly make a bug report u bob puppet.
THIS, on the other hand:
Originally by: Dark Shikari
Edited by: Dark Shikari on 11/02/2007 04:19:50
When you gate into a system in a large gang, every time someone uncloaks, everyone's client hangs for roughly a second. It hangs so completely that even the FPS graph stops, showing nothing but a single line representing however long the pause lasted.
If there's 100 ships that all decloak within 10 seconds of each other... everyone's screen hangs for minutes.
And the irony is that the cause of it is so mundane.
This lag doesn't exist if you're not in Fleet mode. Why? Its caused by the recalculation of gang bonuses. A new person joins the fleet, and the client code appears to be recalculating the entire gang bonus tree from scratch! Obviously I'm not 100% sure, but it seems pretty obvious. The strange thing about it is that the code isn't threaded; instead of simply having the gang screen be delayed by one second, it hangs the whole client.
Fixing this would be a very simple way to fix a huge amount of fleet lag and make tens of thousands of people happy.
On the way to Fountain to face off D2 today, our fleet probably wasted a good hour in this jump lag. Its pathetic.
Is a well-crafted, well-considered post that identifies the main cause of a fairly major performance issue and offers a neat solution, earning it a well-deserved:
/signed.
If re-calculating the gang bonus tree from scratch is the prime cause behind that particular source of lag, then it makes quite a lot of sense to alter the way the game handles gang bonus calculations - maybe with just a standard "If - then" system starting at the pilot in question and working as far up as the first instance of the "if" function not being met. Only re-calculate as much as necessary, and do the minimum possible calculations.
Oh, and delay it by ten seconds or so. Sounds like a neat solution.
***
|