Yep, thanx Mika.
From my many years in Simucube, that 2nd digit resolution in trimming settings is a waste of time. Nobody needs that, irrespective of what they claim
1 decimal point resolution more than sufficient.
Yep, thanx Mika.
From my many years in Simucube, that 2nd digit resolution in trimming settings is a waste of time. Nobody needs that, irrespective of what they claim
1 decimal point resolution more than sufficient.
A scale of 1 to 100%, where over 75% of that scale is unused, thats really a waste of resources! Lots of processing power for nothing, a waste of money for someā¦
Give us better granularity where it matters, anybody wants the chance to waste his time on whatever they needs
EDIT
In True Drive we can export profiles, edit on Windows and then load them again, Best part is that we have that granularity hidden, but its there and the software can read those decimals. I can feel the diference and I want that tuning granularity In True Drive.
honestly, will you be able to feel any difference between, for example, a 2% and 2.05% value for D,F,I filters?
Not that scale, better from 2 to 2.5% (True Drive scales) and Yes, sure I can feel it.
And is more noticeable when playing with only 15 steps (from 0 to 15%, more than that is useless for me).
I did effectively found myself playing in the zone of 0.00 to 3.50 for ioni filters in SC1, which seems to translate for 0% to 35% in SC2 scale. It would most probably not be useful to test and find the differences between 10% and 10.1%. But between 10% and 10.5% and 11%, yes absolutely and you can feel the difference. Anyway that possibility of fine tuning would be missed for some, thatās the point.
This make me remember why some people prefer so much the older audio amplifiers for example. The new amps mostly went with incremental encoder that would change the volume in range of +/-0.5db, where the more vintage dual-gang potentiometer give you more precision and without hearing the steps, etc
Just wanted to let you know I finally got the upgrade completed! I wiped the settings using DFUse but couldnāt get it to do the firmware update in 1.23 (it would just show the update window but not do anything) so I installed 0.11 and it upgraded the firmware and then I installed 1.23 and everything works fine.
I love having my wheels be wireless which is what forced me finally to upgrade. Thanks for the hard work and support.
Ah thanks for the clear up. I had mis-understood the scaling then.
Thanks Mika!
So if my old profiles showed a value of 1.50 then I would just choose 15% in the new software?
But if they were 1.57 then I choose between 15 or 16%?
If so, then that is fine.
I was under the impression we were losing the mid values between numbers.
In that case this is fine, and than you to @phillip.vanrensburg for helping clarify this.
Is it normal for the desktop spring effect not to work anymore in this new FW version?
Hasnāt worked in any of the betas so far.
Not a big problem really if thatās the case.
hmm, i think I was supposed to have fixed a bug that prevented it from working. Iāll have a second look.
One other thing I noticed is that I have never had to perform the āConfigure Motor, encoder and Center Pointā with any of these FW iterations recently.
The wheel is always perfectly in line.
Sorry if thatās normal behavior with Biss-C, but itās nice to not have to keep doing this!
If thereās a valid reason for doing it regardless of everything just working, please advise.
There is no valid reason to re-do the wizard. Its just needed to get information about the encoder & indexing mode to the firmware, in addition to user friendly way to calibrate the center point.
On the topic of the Granularity of the filtersā¦ I am one that in the current SC1 Software use essentially .05% increments to fine tune (I donāt go to .01 as as Beano mentioned it is a waste of time) but .05 has allowed me to enhance smoothness transitions from filter to filter mainly over the center point of the steering that was not possible at .1ā¦ So as I have mentioned before I would suggest that all TrueDrive be bumped to have .5% (.05% in SC1) increments this way there is still no difference between the two versionsā¦ SC1 users keep their finite control of the filters and SC2 users Rejoice in seeing that Granite is giving them additional featuresā¦
You would think?
So far, only 4 people have indicated to actually need more granular setting fidelity.
We might make the setting range altogether more usable by example halving the range from 0.100 to 0.50% and then make that be 0ā¦100%. But that runs the risk of users having to second-guess the parameters when gettings settings from various forums.
Also, bug fixing of 1.0.23 is ongoing. Centering spring, missing re-enable torque function from wireless wheel automatic idle timeout, and going back to having only āconnect to previously paired wheelsā and āno automatic wheel connectionā is done.
I have added a Poll on iRacing to see how people feel about granular setting fidelity.
https://members.iracing.com/jforum/posts/list/3749027.page
Lets see what people think?
I have noticed that the inputs from my Ascher B16L-SC are different since i updated to 1.0.22/1.0.23 (button numbers are different compared to 0.50.4d). I donāt see anything related to this in the changelogs. The strange thing is I also have an F28-SC and that seems to be unaffected. Anyone else with a wireless B16 encounter this?
Seems like the button numbers on the B16 now more closely resemble the F28, so it might actually be possible to hot-swap without having completely nonsensical keybinds.
Oh yes, that was one of the fixes we did for Simucube 2. I didnāt remember to mention it in the changelog.
The next and hopefully last bugfix release for Simucube 1 is coming soon. Let me know if Iāve missed something.
Bug fixes