Works for phones, what could be simpler.
May be quick poll on this?
- BT Auto Scan
- Manual BT Pair
- Disable Auto Scan option
0 voters
Our internal plan / adjustment for this is to always automatically pair to a wheel if that wheel has not been paired before. This would be enabled as default, as the 99% use case for the wheels is that users are at their home, and all wireless wheels are theirs. Then, a game hall / LAN mode would be an option with manual pairing (like it is now).
What about an undocumented config file setting like āTMC=xxxā (torquemodecheck) that someone finds you can set to zero and that stops the torque mode check. Surely that is an end user doing something they should not be doing and their fault if they hurt themselves as a result of high torque mode.
You know a user either had to click yes or āhackā the software so company is covered.
I do not understand why high torque mode is treated as something abnormal, use at your own risk, life threatening feature.
It is the main reason we bought these wheels.
We have not analyzed it yet. Mostly we are interested in technical data (how much power is actually used) and whether or not people use interesting settings or just defaults. Also, there will be more telemetry stuff done in the background in the future.
sin, it would have been useful!
@Mika, looks like Overview page with wheel animation suffers the same problem as BT scan gauge, it hogs CPU even more when this tab is active.
If this is the problem with all these fancy graphics components just dump them, you can use something simple and effective like what MMos used
So why donāt you just not close the GUI when youāre racing? I always leave mine open without Iāll effect, but if it bothers you, just close it.
Modern CPUās have significant enough overhead capacity to deal with the minor loading this, if any other, GUI might imposeā¦
Indeed, just close the UI when not needed. Thatās what I do, I just open it to switch to High Torque and then just close the app again.
Although, reading about a few snags in both 1.0.12 & 1.0.13 I didnāt updated to any of those versions but decided to wait untill 1.0.14. Still running 1.0.10. 
Doctor, it hurts when I touch it.
Then stop touching it.
āMinorā loading is 5.5% on i9-9900K, this is not small and can cause stuttering if the same core is shared by sim rendering or physics thread.
But the real question is why incur that unneeded overhead due to some fancy useless animation.
Hope it does not use hardware accelerated rendering, that would make situation much worse by loading GPU.
And having app on second screen is quite handy when tuning params, observing which DirectInput effects game utilizes, or if you want quickly flip to different profile for specific car.
And why defensive position, if anything team should thank for all reported bugs and observed issues, not shutting people down for that.
May be you did not mean it, but it sounded that way.
5 Likes
I am an end-user too, just like you are 
I just think there is to much spoon-in-the-mouth stuff requested at this point. There are more important matters to focus on first, eye-candy can come later.
For now, simply close the app if it is of concern to you.
2 Likes
Ironically this is eye candy that is causing issues in two places already, wireless scan and overview tab.
Anyway, the issue is reported, hopefully GD official staff will take this into consideration.
5 Likes
Yea True drive should not use 5% CPU on a good CPU. I donāt think I am going to update to the latest version for a while. And for the love of god, donāt give advice to just close it 
1 Like
Sorry, I forgot, for some, it might be to much effort.
6 Likes
Closed software is no good for tuning or changing profiles, it has nothing to do with too much effort to close it.
Sometimes you need to have it running, in case of multiple profiles for different cars, all the time.
Itās nice that you can close it to avoid CPU overhead, but it would be much nicer if we didnāt have that overhead with app running, especially as it has nothing to do with the functionality, just some fancy nobody cares about animations.
I expect next reply from Mika on that.
2 Likes
The update rate on the overview tab is already reduced when the application is not the foreground application, so it does not hurt performance when gaming.
The situation has been the same in all released software versions.
1 Like
Itās a shame to see good suggestions that will ultimately improve TD performance being discouraged.
For those of us that use VR, keeping the loading on individual threads is critical and can make a big difference to the experience.
All input thatās given in a polite manner should be encouraged, not condescended.
3 Likes
All feedback is indeed encouraged, but Iām just saying that some CPU consumption is unavoidable at the moment, and that there are already mitigations in place.