-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ball "jittering out of sight" when moving upwards #29
Comments
That is a known quirk of v1.x. I don’t know for sure, but I think it is caused be mismatch between screen refresh rate and game FPS (>120). I am not sure if there is a fix for this. |
If it's gone by the next version anyway I think there's no need for a fix. Otherwise being able to turn on an FPS limiter in the options would be an option I guess? |
Unfortunately it is not as simple as limiting FPS. This game uses a retained render model, each frame only stuff that changed is updated. There is a workaround – discard partial render and update whole screen at desired FPS. I am hesitating to use this workaround because of my wish to keep v1 code authentic to the original. |
Available under new option Window->Alternative Rendering. Issue #29.
I decided to add the option anyway. |
I feel you with staying true to the original. |
Issue resolved with a workaround. |
Whenever the ball moves too fast upwards, it becomes close to untracable with the human eye. It seems to have something to do with the FPS and building each frame from top to bottom, but I'm not 100% sure.
The text was updated successfully, but these errors were encountered: