Feedback was positive. And I got just now some feedback on the white screen issue, looks like it is worth to also put a solution to that in the final release.
2 Likes
Just a thought on the white screen problem…
I’ve never once seen it, but I’ve seen numerous different programs over the years not handle multi monitor setups correctly, especially if the configuration changes.
Since mine’s been fine, I wonder if it’s related to configuration.
My monitors are setup with Monitor 1 being my primary.
Windows lets you pick a different monitor to be the primary.
I wonder if there’s any relationship there.
If a fix is still needed, it would be great to know the configuration for users having the white screen problem
Actually, I have one of our OEM partners that can reproduce the issue in a reliable way on his rig. He has the 2nd display on top of the first one as (“data display”).
We managed to solve this by having the application use software OpenGL rendering for now.
Nice, was the white out part only from the web rendering portion of true drive?
I wonder what engine QT uses under the hood, a few years back I had a problem with Chrome rendering weird - the first ‘fix’ was to use the software renderer - the second fix was to do a full nvidia driver reinstall (I am probably not giving it the correct name, but when new drivers are available, there’s an ‘express’ option, I had to skip the express and do the regular one)
On something like truedrive, you shouldn’t see a big performance hit in using the software renderer.
But it might be nice closure to see if the OEM partner has an nvidia card and can do a full driver install and see if that also solves the issue.
It seemed to block the whole software from running, i.e. a total freeze. Not just the web portion.
Qt Webengine is based on Chromium.
1 Like
2021.9 still resets Resonance Reduction to enabled on update disregarding previous user’s settings.
With 2021.9 the trayminimized option is not working anymore. True Drive starts but closes itself within a few seconds. The tray option is fine.
Edit: Last entry I get in the log file when I start it with trayminimized log is
Warning: Release of profile requested but WebEnginePage still not deleted. Expect troubles !
Thanks for report. This is for the Paddock application, right?
It seems to be closing for some reason, and appears that the framework closes its dialogs in some order that the WebEnginePage is not happy about. Profile in this regard is not the settings profile in the device, but the operating profile of a web engine page.
Nothing to worry about, as it is not going to be used any further anyway when app is closed.
I do not think that setting even has an effect anymore. We would like to keep it enabled as much as possible to lessen the support requests for buzzing devices when users have not rigid enough steering wheels / QRs.
Strange this one. It seems to work fine in debug build, but not in release build.
I’ll investigate this for next release.
It used to buzz more with it ENABLED for many. (link)
If user makes conscious decision to disable it, SW should respect that choice and not shove its own down user’s throat.
1 Like
Almost like paddock? 
1 Like
Those are quite old posts, and the frequency the resonance reduction affects, was also changed since then.
I must have missed this in release notes.
But this is not the point.
- If user does not experience resonance as some users with “not rigid enough steering wheels / QRs”, why would he needs extra filter doing god knows what. Besides adding extra resonance it was affecting quality of FFB in ACC, was it fixed too, who tested for that?
- As you provide this as an option after all, please be consistent and retain its value during FW reflash, same as all other settings. It’s very user unfriendly when SW makes decision on its own and changing settings without user’s acknowledgment.
@Mika Regarding the problem with initialize the wheel base.
I made some tests and noticed when I release the E-Stop before switched the wheel base on it is able to initialize without any issue.
Can confirm 4 starts without any issue so far. I keep you updated about it :).
1 Like
I’ve just downloaded 2021.9 and get multiple .DLL errors when running the paddock version - I can see the supposed missing DLL files in the directory. Classic boots up fine. Downloaded the file from troubleshooting.txt and still the same. Any ideas?
Ignore me, redownloaded it and all good.
3 Likes
I’m about to upgrade from 2021.4_3. How does everyone like the latest version?
Have the SimBin DirectFilter issues been fixed or improved?
2021.9 is pretty good, at least Classic version, no issues.
1 Like
Ya, it does seem to be. Just played GTR2 for a bit so far…just tested DirectInput Effects, still buggy 
1 Like