Skip to content
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

Physics update rate causes you to get caught up more often. #8

Open
NiamhHyx opened this issue Jul 28, 2022 · 3 comments
Open

Physics update rate causes you to get caught up more often. #8

NiamhHyx opened this issue Jul 28, 2022 · 3 comments

Comments

@NiamhHyx
Copy link

I have noticed that while it really helps with the camera jitter, it also causes some small issues.

If its around 60-120, its rare, but you can get stuck on little step ups in the game, and above 240 its happens almost every time.

Is this something that is possible for the mod to fix with in its self or something we have to wait for the developers to deal with?

@alliepet
Copy link

I am also experiencing this issue, not sure if I should revert to the version I updated from (0.5) until this is fixed.

@Lyall
Copy link
Owner

Lyall commented Jul 28, 2022

This does make sense given that increasing the update rate is essentially a band-aid fix. It definitely is something the developers could and should fix.

There is the potential to add some kind of interpolation to the camera movement to smooth out the default 50hz update rate. There's a really good writeup by @SuiMachine on adding interpolation to character movement in Dead Premonition 2 with Sui's Hack. Doing that kind of thing is probably beyond my meagre ability however.

I think what I could do for now is to change the default of 240 to be set to your current screen refresh rate. This should make the update rate not be set far higher than it should be. For example if you play at 60fps you really only need the camera movement updating at 60hz from the default 50hz anyway.

I am also experiencing this issue, not sure if I should revert to the version I updated from (0.5) until this is fixed.

Reverting wouldn't fix anything since it is directly related to the physics update rate as @NiamhHyx mentioned, which has been in RF5Fix since the start.

Lyall added a commit that referenced this issue Jul 28, 2022
@NiamhHyx
Copy link
Author

Makes sense to run it at your refresh rate, I did test 120 fps with 120 update rate and getting caught up felt about as uncommon as 60fps with 60 is. Cant test any higher than that though because my monitor is only 120hz.

Maybe I'll start spamming xseeds discord and hope they see it so it doesn't end up having to be everyone else's problem for a long long time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants