Can you try a good quality USB cable directly connected to an on-chip usb2 port. Avoid connecting to USB3 ports, especially those AsMedia 3rd party chipsets, often found on Asus boards.
I generally use only on-chip (native) usb2 ports for my wheels/pedals et al.
i did a test, Just to see if usb 3 is a problem i don’t know which chipset i have( i wil look it up later its a asus board dough), but i have been running my simucube on usb 3.0 for months now, never a single problem.
Congratz on that find Mika, I’m not a programmer, but it seems you found the needle in the haystack
It would be awesome if I could race in F1 2017 again.
Glad to hear that it you found a good solution ML & MR values are quite robust to different values and as long as torque response is good, the values are ok. So no worries using larger values there when needed.
The issue is the interface or direct communication… and even older 1x/4x systems as they will not work either… Basically the firmware cannot talk to the Argon the same way it can the IONI and with the 1x/4x systems there is no link for communication between the firmware and the IONI so that doesn’t work either. Hence why it is only SimuCUBE board compatible.
The FFB effect creation bug is successfully fixed. I also managed, somehow, to drive F1 2017 for 1.5 laps (Melbourne Time Attack) until it froze. It has never happened before. And on re-trying it froze right away.
I’ve added a good amount of sliders and scalers for effects for user customizations.
Side effect of this is that we are close to having more data in the profile settings than is possible to put into a single USB HID packet as it is now used. I already implemented things so that user settings won’t break as saved on flash when the profile data is enlarged, i.e. saving and loading of data does work.
Now I’m also setting up the protocol to implement the saving and loading of the data in suitable packets. This is to make this future proof when people start to add even more configuration parameters some time in the future.
Also, I’ve upped version number to 0.9.0 so that this new Configuration Tool with slightly tweaked communications won’t try to do things with older firmware - there might be unforeseen consequences when doing that.