Telemetry data rate: make it faster?

Simulation_Player said:
200 hz would be a good start. ;)
Click to expand...

True :)

I think 400Hz would be good, and should be easy enough to do since that's what the physics comes down to for the FFB. Assuming making it available at the higher rate wouldn't in itself cause any performance issues, and then we'd have to be careful on how we access it to avoid causing more slowdowns. But would be good indeed.

@Erling Hugosson I should mention that tying to graphics rate isn't a great idea - rF1 did that until the FPS reached 90fps. Made writing a motec plugin a bit more challenging because interpolation was required. rF2 is nicely constant.

@Erling Hugosson actually, to explain a little more: rF1 the physics rate also dropped with FPS below 90. rF2 the physics rate is constant, which is a much better idea. It does mean the game actually goes into slow motion if your CPU can't keep up, which is a bit annoying, but the physics runs internally at 2400Hz at all times which is a very good thing for tyre interactions, suspension movement and stability. So from there, trying to sync it to framerate would be pretty messy. But 400Hz would be great for those suspension nuts out there.
 
Last edited:
Ok Lazza, wrote a little plugin that also measure the data rate... seems to be a limitation within the game at 100hz (just as you said).

Agreed 400hz should do it, with the more and more detailed road surface of the tracks and more running motion systems faster data is better ;)

And a stable at data rate is also good as you explained.

Any known work arounds to get higher hz?
 

Attachments

  • rfactor-hz.png
    rfactor-hz.png
    28.5 KB · Views: 140
Last edited:
You must log in or register to reply here.
Back
Top