@galoyo said in LAG: Syncing problems in Neko+Cpp Targets:
if after you optimize the code, there is still a delay in the speed of the game then you might give the option for the user to set the speed of the game by changing its framerate. this is not a bad idea as some users might like to play the game at a slower or faster framerate than others.
This^
Recently, a super nice youtuber willing to play my humble game stumbled upon this problem. Certain recording software can get the recording choppy, with uneven framerate, or slow to a crawl. We fixed this by adding an option to lock the game to 30 fps and enabling frameskip, with great results!
In case someone is wondering how that can be achieved, is simple:
FlxG.drawFramerate = 30;
FlxG.updateFramerate = 30;
FlxG.fixedTimestep = false;
BTW: sometimes is possible to have choppy, jumpy movement even tho you are having great performance. I can't yet understand why, but has something to do with super.update() call. For example, there might be sightly movement differences between this:
Update(elapsed)
{
movementCode();
super.update(elapsed) ;
}
... and this:
Update(elapsed)
{
super.update(elapsed) ;
movementCode();
}
Play test in game to see what gives you the best results!
