i started the True Drive 1.0.13 as every day.
after i turn on my SC 2 Pro and the Beeps the True Drive shut down and i can do nothing.
the LED’s on both power supplies and the base are blue.
it is the same with or without pressed e-stop
what can i do?
Windows Event Data
Version:1.0 StartHTML:000000226 EndHTML:000010120 StartFragment:000006109 EndFragment:000010082 StartSelection:000006109 EndSelection:000010082 SourceURL:file:///C:/Users/Mario%20Rudolph/AppData/Local/Temp/tmp723C.tmp
Simucube 2 True Drive.exe
0.0.0.0
5dcedbe1
Simucube 2 True Drive.exe
0.0.0.0
5dcedbe1
c0000005
0001a565
620
01d5b8c9c63c3c25
C:\Users\Mario Rudolph\Documents\Simucube 2 Pro\Simucube_2_true_drive_v1.0.13\Simucube 2 True Drive.exe
C:\Users\Mario Rudolph\Documents\Simucube 2 Pro\Simucube_2_true_drive_v1.0.13\Simucube 2 True Drive.exe
f0666c9b-79ab-4192-9fe9-aaaef2c2330e
how can i share the crash Dump file?
Crash dump file is not useful at all.
Does the software close down or crash? Neither should happen.
Make a shortcut that ends with …True Drive.exe" log
and it will generate a log.txt file that is actually useful.
the Software close down
here is the log:
19:33:05.764: Opened style file
19:33:05.998: Warning: QMetaObject::connectSlotsByName: No matching signal for on_wirelessbutton_clicked()
19:33:06.014: “C:/Users/GAMER/Documents/Simucube Pro 2/Simucube_2_true_drive_v1.0.13/simucubeprofiles.ini”
19:33:06.014: “C:/Users/GAMER/Documents/Simucube Pro 2/Simucube_2_true_drive_v1.0.13/profiles_autobackup.ini”
19:33:06.014: “C:/Users/GAMER/Documents/Simucube Pro 2/Simucube_2_true_drive_v1.0.13/profiles_autobackup.ini”
19:33:06.030: loadIncludedFirmwareVersion: included 1.0.13
19:33:07.018: EULA previously accepted.
19:33:07.018: Disconnected state
19:33:07.034: unable to open device, pid: 3423
19:33:07.034: Connected to SC2 Pro
19:33:07.034: reconnected
19:33:07.554: got a response
19:33:07.773: loadIncludedFirmwareVersion: included 1.0.13
19:33:07.773: shouldShowFirmwareUpdatePrompt: device reported 1.0.13
19:33:07.773: first connection done
19:33:07.773: no need to update
19:33:07.773: checked fw update need
19:33:07.866: got profiles
19:33:07.991: Configured in unexpected state
19:33:07.991: got hardware settings
19:33:09.089: got analog data and settings
does your GAMER username have admin rights or not? The next thing that the software would do after that point, is to write a temporary profiles file to your temp folder.
yes…GAMER is an Administrator and True Drive runs with Admin Rights
where can i find this Folder?
For me they look like this after the “got analog data and settings” message:
18:01:08.239: Consumed 19 bytes for part “TelemetryBufferer” at index 0
18:01:08.264: Consumed 612 bytes for part “powerHistogram” at index 1
18:01:08.285: profile export to “C:/Users/mikat/AppData/Local/Temp/Simucube 2 True Drive.XdwEmF” result QSettings::NoError
18:01:08.299: profile export to “C:/Users/mikat/AppData/Local/Temp/Simucube 2 True Drive.hjvinT” result QSettings::NoError
Unfortunately, I’m not in front of a PC that has access to our source code until after Christmas.
One thing that comes to my mind is that the telemetry download somehow crashes.
Can you try to remove from
HKEY_CURRENT_USER\Software\Granite Devices\Simucube2
keys TelemetryConsent and TelemetryConsentVersion
and then relaunch True Drive, and then answer NO to the telemetry consent question?
it’s the same
after init from the base the true drive shut down
OK, lets continue in PM.
Solved by resetting settings. There seems to be something strange going on with something making the Qt side of code crash for unknown reason. Unfortunately I won’t be even able to try to repeat it until January.
Dumb question:- I take it that after starting True Drive you reset settings before powering on the SC2?
If so, how would I do that exactly?
It requires a special tool to do it. Lets monitor the situation a bit before releasing it publicly. Would be best to fix the root cause instead.
