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

Choppy framerates with release 0.8.0 #422

Open
Gagert opened this issue Nov 10, 2024 · 4 comments
Open

Choppy framerates with release 0.8.0 #422

Gagert opened this issue Nov 10, 2024 · 4 comments

Comments

@Gagert
Copy link

Gagert commented Nov 10, 2024

Previously I used build 4200cfa (which I compiled from the source code) on Windows 11, and the framerates was decent using that build on Windows 11. With release 0.8.0 however, in both the windows-x64 & windows-x86 releases, the framerate is very choppy; it's like running the game in Dosbox.

The framerate seems to be choppy once you turn your car either left- or right. When driving straight forward or standing still, there does not seem to be any "choppyness" at all to the framerate.

My system specs are quite decent (not to brag), i7-12700KF, GTX 1080 Ti, only SSDs, 64gb DDR4 RAM. Can this have anything to do with the changes from June 2024 in the Changelog?

@Squall-Leonhart
Copy link

Squall-Leonhart commented Nov 21, 2024

--i don't experience this with far older specs, so its likely something specific to mixed capability cpu's such as the 12-14th gen parts.--

Correction, i do. It seems like theres jitter in the viewport that needs interpolating

@b-kurczynski
Copy link
Contributor

Hi, most likely the tear you see is due to the fact that physics frame-rate is different than rendering frame-rate. The physics frame-rate is also responsible for all the viewport transformations so you see it choppy.

Try to use this command-line arg:
--physics-step-time=10

It sets the physics engine to work at 100 frames per second. The default value is 40 which gives 25 frames per second.

@Squall-Leonhart
Copy link

--physics-step-time=20 seems more true to the feeling of carma95

@Gagert
Copy link
Author

Gagert commented Dec 18, 2024

The --physics-step-time=10 line inserted into to dethrace.bat file I made seems to do the trick. Maybe this could be the default setting going forward in newer commits of dethrace?

I could close this issue now, but would it for the community be more beneficial if I left this bug-report open, at least until this eventually becomes the default settings of dethrace?

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