Just to clarify - this latest release has centering issues with SinCOS and requires that center point is manually reset most times?
If so, I’ll wait on the next update as 0.97 has been quite good to me.
Only thing that is still an issue with 0.97 is that I cannot allow my wheel to pass the index point (in my case about 25 degrees left of center) during phasing as this will result in misaligned wheel in relation to virtual wheel - I use manual index as auto is problematic.
I just make sure that my actual wheel is slightly right of center before powering on and phasing as that will always miss the index point and then I just manually turn the wheel left and find the index point. This works 100%
I can confirm when reverting to an old Win10 build, the issue goes away. So I guess Redmond changed something in the latest build. It was completely unusable.
Mika,
I am using the auto setup function you added in the last update. Is it my imagination or does it make the ffb feel more direct. No issues either so far with the update in AC,R3E AND P CARS2.
I haven’t tried disabling XHCI yet but what I did was enable Nvidia surround since I wasn’t using it at the time. Once I enabled Nvidia surround, the problem was resolved even while keeping GSync enabled and didn’t have to reboot.
With BiSS-C absolute encoder, one can now setup IONI so that phasing is not required at startup. However, SimuCUBE firmware does not yet take advantage of the absolute position, that is still under work.
Setup of the commutation sensors should not have any effect on the ffb feel.
Worked perfectly with 0.9.9 pre3 and open beta. Upgraded to 1803, had disconnects tried 0.9.9 pre3, still disconnects, then reverted to 1708 and ran fine with 0.9.9 open beta all yesterday, and now the disconnects are back.
What other USB devices do you have? Could you post a screenshot of the Device Manager. Select View -> Show Devices by Connection and find all your USB devices. I’ve attached an example image of my system here.
OK. Did 0.9.7 work any better, as it does not try to anything at all when USB gets stuck? 0.9.8 completely de-inited the USB stack, waited 1 second, and then re-inited it, with a noticeable Windows notification sounds.
0.9.9 now just tries to reset a flag in the USB state machine, and this should not result in anything that would result in sounds from Windows. However, I did not manage to induce this reset to trigger this time even when abusing an usb extension cable, so debugging is largely not yet performed.
In the Simucube is it possible to have button on each side of the “DirectInput Effects” to decrease or increase with precision each setting (Friction, damping, spring, …).
