Is anybody from iRacing aware that this low 60 Hz FFB is a problem? Maybe they should do something about it because more people are getting DD’s.
They are aware, and some things are being discussed. However they would need complete game engine rewrite to get much faster rate.
2 Likes
Thanks Mika !
Ok cool. It is almost perfectly clear. I understand. It seems very cool !
I have just a fews more questions to ask :
-“Slew Rate Limit” seems to solve a similar issue than the damping effect when I read the description (not exactly), Can you (please) explain a little more this effect and why everybody seems turning “off” this option (like “Static force Reduction” by the way). I have read the manual but I still doesn’t understand this effect…
- In “direct imput Effect Fine tuning” (game effect ?)
Damping and Fiction are set with lower values, there is a reason for that ?
In ACC for exemple, when the car is stopped, the torque on the wheel, the direction of the car is very light with the GD profil…So, I wondering why a lower values ?
Maybe for some games it’s better to use damping/friction in “Other filter” (section) ?
-" Audible notification" and “Torque clipping notification” is off but still the “bip” sound…?
@phillip.vanrensburg,
I’m just curious. I disagree, it’s important first, to understand each settings to set properly this device.
its similar end effect, but where as damping is proportional to the acceleration of the change, slew rate is more of a constant limiting of torque change.
in DD wheels, these have to be quite low to be at sensible rates. Everything would feel just wrong (too much) at 100%, as DirectInput was originally implemented for <2 Nm wheels.
Not many serious simulators use those effects in any sensible way.
Yes, the idle beep can not be turned off as it is a safety notification. The Audible Noficifications mainly affect the wireless wheel beeps at the moment. Next True Drive version will have a change to the beeps.
1 Like
Watching this Video will help you a lot , it explains all the setting in detail. In the end every one will tweak them to feel good for themselves. I have my own settings which i feel comfortable with, the more you use it the easier it will become to tune.
Common mistake I found was starting with too much torque, I use about 11Nm now on the Ultimate in iracing. in TD and iracing I have it set to 32 and wheel force is at 93. which calculates to abotu 11Nm, its plenty and the hard hits are not harsh and bumps etc. are not jerky, also my slew rate is low and static reduction is at 5. I get a lot of details without the negative. I am coming for a G920 at 2-3Nm. I do run high friction at 20-22% and high inertia at 18%
2 Likes
I do not use it “Simple mode”, but it is a really good idea !
I’m really happy with my SC2 Pro. Very good product.
1 Like
Software version 1.0.13 out today - surprisingly little feedback yet.
1 Like
I was just testing, I didn’t check the update. have a race tonight so may update before that otherwise after for sure.
I stay at 1.08 as there is still no improvement for me in the new release and i don’t like the new automatic torque off.
Will try to avoid that as long as i can and probably wait until the 360 bug is fixed
First impression - u have to change all buttons 
That sounds exactly as intended by this firmware update… It mentions it fixing some wireless rims not having the same button layout for sims as others so hot swapping was impossible. So you’d have the ones that didn’t match their “base” button layout.
In fact, it was totally our fault. We designed the system as per high level requirements we imposed. However, there were no real life test cases available so some tests were designed in a wrong way, and at the end, wireless wheels designed as per our recommendations didn’t work as expected when hot swapping wheels. This is now corrected and will also be corrected in an upcoming Simucube 1 firmware version.
2 Likes
1.0.13 no issues to report yet
Hi Mika,
While trying to install 1.0.13, an error msg appear as below,
“Simucube 2 True Drive.exe - System Error
The code execution cannot proceed because Qt5Core dll was not found. Reinstalling the program may fix this problem”
Any help will be appreciated.
Thanks…
That file is included in the .zip file. Are you extracting the zip into a new folder and not attempting to run from inside the zip?
Hi Mika,
I run the true drive application file from inside zip.
Did i missed any steps ?
Can you help to list the steps here to update to 1.0.13 ?
Thanks.
Tan, you have to extract the zip file into a directory of your personal choice.
Than, run the Exe… you can´t start the exe without extracting all files
1 Like
Thanks Jim. Upgraded to v1.0.13 successfully now.
Thanks again…cheers.
1 Like
Hi,
upgraded to R1.0.13 today, (SC2pro and Ascher F28 wireless, connection 100%).
Did some driving but noticed that shifts are not always detected. Checked in True Drive and indeed the button behavior is not one on one. It is the only thing that changed on my PC, did a restart but issue remains.
Can I go back to 1.0.10? Or what can I do to resolve this?
It seems as if the SC2 is doing something else, the speed of showing the button press also seems to be lagging when looking at the True Drive inputs UI.
I started DIView and there it seems to be OK, no lag. ???
A video , it is hardly to see due to the downsampling but you know where to look
By the way I took the wheel from the motor, hence the few X axis events.