MTakala wrote:
Just to add, that our wheelbases are not using any custom drivers; we are using the default Microsoft Human Interface Device driver that has all the required functionalities. But as the issue does not seem to happen with wheels that have bespoke drivers, then it also might be a driver bug - for example if you create the effect to the driver but not set any parameters to it, we do not actually know if it leaves the effect variables to strange values that could cause that -10000 torque.
I will be happy to test any debug/test/beta versions.
Hi Mika. Can you send me some your direct contacts in PM? Email, or some social networks profile maybe. In order to have an option to get in touch with you directly by our development team.