Hello there!
For some time now I've been noticing that if you activate the iRacing app.ini setting irsdkLog360Hz=1 most of the simvibe effects stop working.
Is this normal? Are there any fixes planned?
Best,
Welcome!
Welcome to our new question & answer style forum. We hope this new format will help you to rapidly find answers to common usage and configuration questions.
Please ask well formed questions and up vote answers that you find helpful. This forum is NOT for bug submissions or instances where customer support is required. Non-conforming posts will be rejected to preserve the integrity of this resource for future users.
This question has been flagged
1
Reply
1267
Views
Currently there are no plans to utilize the 360Hz option of iRacing because it doesn't add any actual value. It isn't a true 360Hz data stream. Instead it is a 60Hz stream and in each cycle it sends 6 samples. That's basically 1 current sample and 5 older ones per cycle. We only care about the current samples and that's exactly what we get with the normal 60Hz iRacing option. There is no point in sending 6x more data than is useful because that extra data represents what happened in the past, not at the moment.
If iRacing were to implement a true 360Hz output that aligned with true 360Hz physics such that each sample were meaningful, we would certainly give great consideration to supporting it.
Thanks for the info Bernard!