Idea how to figure out the leak
WhiteWolf22
Join Date: 2009-08-21 Member: 68559Members, Reinforced - Shadow
Join Date: 2009-08-21 Member: 68559Members, Reinforced - Shadow
I just read that you guys are going crazy while trying to find that leak/crash...
My first thought is this:
Let us beta-testers record lots of detailed 'realworld' data for you about the performance - client- and of course server-sided. And that while recording a replay/demo-thingy, so you might develop a little tool that shows the performance as peaks while watching a recorded replay - and you might see exactly, what action causes the highest peaks in memory / cpu usage. Developing that little tool might take some time, but I am sure, it will pay off through reduced time to figure out the sweet spots to finetune. (what will result in a smooth game experience)
If you think now "WHOA, DUDE! thats gonna be too much of data!" then you might make it stop after 10 mins or so automatically. ^.^
What I want to say is: I am sure almost all of us preorderers are willing to support you with whatever we can do, so let us give you some real data instead of guessing and trial & error.
My first thought is this:
Let us beta-testers record lots of detailed 'realworld' data for you about the performance - client- and of course server-sided. And that while recording a replay/demo-thingy, so you might develop a little tool that shows the performance as peaks while watching a recorded replay - and you might see exactly, what action causes the highest peaks in memory / cpu usage. Developing that little tool might take some time, but I am sure, it will pay off through reduced time to figure out the sweet spots to finetune. (what will result in a smooth game experience)
If you think now "WHOA, DUDE! thats gonna be too much of data!" then you might make it stop after 10 mins or so automatically. ^.^
What I want to say is: I am sure almost all of us preorderers are willing to support you with whatever we can do, so let us give you some real data instead of guessing and trial & error.
Comments
EDIT: I agree your signature, Linux port ftw :)
D:
D:<!--QuoteEnd--></div><!--QuoteEEnd-->
ymmd :D
Debugger is not what I think of. I mean a visualisation of those things, as a graph.
If you watch a replay, imagine you have graphs for CPU, MEM and FPS - you can watch what happens ingame from any angle, and look how it affects these values - oooor: you recognize "whoa, look at that peak!" and look what happened right at that moment.
That is more intuitive than reading logs and code, I think.
It cannot replace a debugger, but it surely can help to find problems and memory-eaters.