Well i guess you have alot more popping up then me then because i power it on open TD enable high torque and im done.
-
Telemetry consent will be fixed in next release
-
Simucube Wireless Wheel scanning does not cause background overhead unless you have the Wireless Wheels tab open, so your concern there is not valid.
-
Periodic telemetry collection does not break bumbstop when actually driving, so no real concern there.
I really donât understand why someone should be so bothered of dragging a bar and click âenable torqueâ and stop the wirless scan on every startup. how much does it take, 3 seconds in all? come on guys, letâs be serious.
It is a concern coming from the user, you as a software engineer may see it your own way but it doesnât make it less valid.
- You automatically exercise function that end user do not need, providing manual option to turn it off but no permanent disable, requiring user following same steps on every startup.
- Animation and perhaps scanning itself causing CPU load. Now user needs to make sure that this tab is not active as well as the Generic setting tab with animated wheel that is also causing unneeded CPU load. What tab is safe to have active on that app to not cause that CPU drag?
On telemetry torqueOff. First off, I did not consent to telemetry collection, by collecting it you violate userâs privacy.
Second, it already caused issues with wheel going past bumpstop, stucking in wrong orientation and going crazy after that, requiring full reboot. And related or not, same happened in R3E few times after wall crashes. The symptoms were the same. So no, it is very valid and safety related concern.
Do you have some sort of internal issues tracking system, like JIRA, where all these issues can be submitted by users with ability to track the progress.
Seems like we are rehashing over the same stuff over and over again, making it public entertainment for others instead of more productive feedback collection.
I believe some of us, especially those with software development background, can and want to be helpful, try to use that to your advantage.
Happy holidays!
Come on now, you donât know his wife.
Thereâs plenty of people it could affect, like my mother who canât handle most shopping placesâs music, or ads on telly and plenty of other things due to stress âafter effectsâ
I didnât know a âbeepâ could act as a trigger for stress youâre quite right.
I am starting to appreciate the fragility of the modern day human thanks to SC2 owners experiences, itâs a dangerous world out there, stay safe.
it is stated the data collection is anonymous
If there is no consent to collect telemetry,then it is never downloaded from the Simucube 2 to the PC. The collection you see is technical data collection from the servo drive to the USB interface firmware, which does not violate any privacy in itself.
What is the purpose of that collection if data is never uploaded to GD?
Can we turn it off please, I donât need it, itâs just hazard waiting to happen, already happened a few times.
Iâm glad you are having fun, so Iâll just go ahead and be a little bit of an arse.
Interesting how you talk about fragility when what is being requested is the ability to disable the very thing that is âprotectingâ my âfragilityâ.
Bottom line is I have a 20,000$ rig and I just canât be bothered clicking and repeating things every time I fire up the PC and have an hour or two to do some laps. I just need things to work at home because I solve problems at work all day.
You know, I have a busy life, a wife and my free time is limited.
Might be hard for some to grasp, but yes, annoying beeps, constant confirmations and just minor annoyances can very off putting.
And I do have to wonder what purpose it serves for you to come hear and argue against something that people are requesting. What purpose does that serve? What do you get out of this?
With that being said, Iâm not quite sure why I wasted my time on this.
And to GraniteDevices, thanks for a great product, hopefully with a few more updates to the software it will be even better.
Iâm willing to bet most here have spent a sizeable amount on their rig, have a job/girlfriend/wife/family and a lot less spare time than theyâd like.
The difference is most of us realise a computer game accessory that has to be turned on and that beeps occasionally isnât the end of the world, especially knowing that GD have updates for those issues in the works
Nothing is a âproblemâ per se, rather a nuisance that can and should be avoided.
Those who care about software and product to get better provide feedback, and despite back and forth arguments seems like sometimes GD listens.
This is how user friendly with usability in mind software is developed.
What you accomplish by talking down other users, I have no idea.
When I heard of the new true drive versions collecting telemetry, I thought they meant vehicle telemetry in order to start basic testing of vehicle physics/telemetry based filters (like a âsteering-return-to-centreâ or âanti-centering-springâ filter just for example). I totally misunderstood what GD meant when they mentioned collecting telemetry data. I just realized this today, lol! (I still havenât updated from TD v1.0.10 and itâs FW).
Happy Valentineâs Day everyone!
https://granitedevices.com/wiki/Simucube_2_True_Drive_releases
Thanks Mika!
Still the âstandby modeâ to unlock the âHighTorque modeâ or do we have the new system ?
standby mode and automatic high torque mode changes/features will be in the next release.
Ok ! So right now, itâs the old system with the slide bar ?
Yes, no changes has been made to that.
Thanks !
I will check GD profil on this new TD, but is it always possible to use the old one (V1.0.10) ?
EDIT: I guess that the answer is yes.
Old versions are possible to use until we make a change to device <-> True Drive communications interface (feature changes, effect parameter changes, etc). At that point, if there is new firmware flashed on the device, the old True Drive will refuse to start (and notifies the user of this).