I did a testing cycle with biss-c commutation sensors, 2500ppr encoder with automatic indexing, and index point indexing.
This uses the new fastupdatecycle mode.
Anyone up for a 0.9.11 experimental test version? Only those that have a BiSS-C Absolute Encoder are potential testers this time.
I also maybe found the DRC file upload bug; it only manifested itself on new systems. The fix will be in 0.9.11, and we already have someone testing that soon.
I m up for testing it.
Also, there is a new feature plan that has to be done for future development, but it will change the status packet format. For this reason, the version number will be 0.10.0 (or something else) quite soon.
I never had problems with the different versions, but today after the computer resumed from sleep and with version 0.9.10 and starting iracing and leaving the pitbox my steering wheel started moving from left to right and back like it was searching for the center. It is also happening in Assetto Corsa as soon as I start driving. Can this have anything to do with latest bugfix?
Can you show the profile you are using and also the debug log? Thanks.
Simucube says disconnected, should I restart and try to repeat this situation?
Edit: it says connected now, weird
Try to see if disconnecting and reconnecting the usb cable has any effect.
USB stack was reset due to being stuck busy : 2
USB stack was reset due to being stuck busy : 2
USB stack was reset due to being stuck busy : 2
USB stack was reset due to being stuck busy : 2
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 3
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 3
Command: Request profile data is for 55 byte set index : 1
Command: Set calibrated analog axis mode : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 0
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 1
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 2
Command: Request profile data is for 55 byte set index : 1
Command: Request Profile number : 3
Command: Request profile data is for 55 byte set index : 0
Command: Request Profile number : 3
Command: Request profile data is for 55 byte set index : 1
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Event log download request : 0
there were like 100 messages: USB stack was reset due to being stuck busy : 2
And it is working again without me changing anything?
So this was with 0.9.10?
Yes, it was with the latest 0.9.10 version
I guess it changed after opening Simucube software
hmm, that might have something to do with it, maybe its a Windows issue, not liking the reports continuing at that point. Iāll compile a test version for you to test.
Sorry for the delay getting back. Ive been using this in r3e,ac and pcars with no problems that im aware of. There is an issue in r3e with the ffb getting stuck and pulling to one side after a collision but im pretty sure thats game related because it didnāt do that before the latest r3e patch.
Status update: Bug fixing the 0.9.11 release is continuing.
Also, BiSS B Absolute encoders as found on many Kollmorgen motors are also going to be supported to use Absolute Indexing.
Just thought Iād let you know that the phasing issue is indeed gone as far as I can tell.
The virtual wheel is always where the real one is - I use automatic again.
Thanks for all your continued work.
As a side question, will there ever be a better solution to the bump stop issues - far too violent and the option to lower the strength creates itās own issues where the wheel goes beyond the bump stop and feels like you are pulling on a heavy stretching band!
I accept of course that this could be a problem on the game developerās side!
Yeah, would need to know what game you are talking about regarding bumbstops.
Both iRacing and AC.
AC is much worse and the soft lock must be disabled - no amount of adjusting in Simucube can change the brutal bounce off the bump stop.
iRacing is much better and I have found settings that mostly work, but thereās still that bouncing off the bump stop that makes driving very difficult - although by that point the cars is usually un-saveable anyway!
Yeah, both of these titles have their own bumpstops that have nothing to do with the simulated hardware bumpstops that can be set up in SimuCUBE.
Can we assume you are working with those developers to try to fix these issues in future releases?
