Thanks Mika.
As a wild thought, may be we don’t even need that “Reconstruction Filter”, as there is little to nothing to “reconstruct” with already high resolution to begin with.
And some primitive smoothing filter over n-number of samples, like the one in MMOs, could produce more desirable output.
All window-based averaging filters add lag to the end result. It is much less desirable than interpolation/extrapolation or a frequency based bandwidth limiter.
Could be less critical for higher res signal.
360 hz each sample is 2.7ms. With average of 3 it’s 8.1ms delay.
But may be mythical Recon 2.0 will solve this better.
My base has been randomly going back and forth between the PERFECT setting (there’s good detail and it doesn’t feel too noisy and is totally quiet) and “sand in the base” and I can’t figure out to make it stop doing that lol. Sometimes I turn it on and it feels like sand, sometimes it feels perfect.
dont forget to click on your profile ( even if you have set your profile to default one )
This issue has popped up since the 360hz true drive update. sometimes its not reading the default profile correctly. I have to switch between profiles to properly ‘activate’ my profile.
Hello, one of the latest iRacing patches says:
Fixed an issue where Force Feedback was not being properly enabled when the setting: “enable360HzInterpolated=0” for Simucube wheels.
Has anyone managed to find out what exactly this setting does?
And what value we shoud use 1 or 0?
I think it controls some values that show up in the iracing telemetry memory map. It should be =1 at default, and I don’t see a reason why you would want to turn off. For certain it does not affect FFB at all, but there was an issue where if it was at =0 then there was no FFB at all.
1 Like