Jump to content
Corsair Community

CUE exits immediately


Bane2087

Recommended Posts

Hi guys, as far as I'm aware nothing has changed recently on my system however CUE now fails to start - or rather it starts, shows system tray icon and then exits after about 10 seconds. The GUI never appears. I found the log file:

 

2017-05-25T23:13:54 I cue.init: CUE version: 2.13.80
2017-05-25T23:13:54 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V2/
2017-05-25T23:13:54 I cue.init: Build type: Public Release
2017-05-25T23:13:54 I cue.init: Applicaiton ID: 9512
2017-05-25T23:13:54 W cue.locale: "Cannot load qt_en.qm translations"
2017-05-25T23:13:54 I cue.init.font: Using Regular text font family: "Open Sans"
2017-05-25T23:13:54 I cue.init.font: Using Title text font family: "Gotham Bold"
2017-05-25T23:13:54 I cue.session: Locked changed to false
2017-05-25T23:13:54 I cue.session.win: Will notify 'connected changed to' with delay
2017-05-25T23:13:54 I cue.session: Local changed to true
2017-05-25T23:13:54 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\Chris\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder"
2017-05-25T23:13:54 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\Chris\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder"
2017-05-25T23:13:54 W cue.library: Lightings load failed:  Could not detect cereal root node - likely due to empty or invalid input
2017-05-25T23:13:54 W cue.library: Lightings load failed:  Could not detect cereal root node - likely due to empty or invalid input
2017-05-25T23:13:54 W cue.library: Actions load failed:  Could not detect cereal root node - likely due to empty or invalid input
2017-05-25T23:13:54 W cue.dpi_manager: "C:\\Users\\Chris\\AppData\\Roaming/Corsair/CUE/dpi" Could not detect cereal root node - likely due to empty or invalid input
2017-05-25T23:13:55 I cue.lightings.player: Started lighting worker in 0x2554
2017-05-25T23:13:55 I cue.action.macro.win: Init time: 0.404455 (init: 0 reset: 0.00129695 )
2017-05-25T23:13:56 I cue.dev: Device insertion processing complete for Scimitar Demo.
2017-05-25T23:13:56 I cue.lightings.player: Started lighting worker in 0x25ac
2017-05-25T23:13:56 I cue.dev: Device insertion processing complete for K95 RGB Demo.
2017-05-25T23:13:56 I cue.lightings.player: Started lighting worker in 0x2570
2017-05-25T23:13:56 W cue.devbehavior: Not implemented for current device.
2017-05-25T23:13:56 I cue.dev: Device insertion processing complete for VOID Wireless Demo.
2017-05-25T23:13:56 I cue.lightings.player: Started lighting worker in 0x257c
2017-05-25T23:13:56 I cue.dev: Device insertion processing complete for MM800RGB Demo.
2017-05-25T23:13:56 I cue.init.ui: Starting UI.
2017-05-25T23:13:56 W cue.thread: Can't rename main thread.
2017-05-25T23:13:56 I cue.session: Connected changed to true
2017-05-25T23:13:56 I cue.dev: Requesting working state enter because session connected.
2017-05-25T23:13:56 I cue.dev.enum.hid: Entering working state.
2017-05-25T23:13:56 I cue.sdk: Entering working state, session connected.
2017-05-25T23:13:56 I cue.sdk: Starting router.
2017-05-25T23:13:56 W MainWindow_QMLTYPE_338(0x8341b88) must be a top level window.
2017-05-25T23:13:56 W MainWindow_QMLTYPE_338(0x8341b88) must be a top level window.
2017-05-25T23:13:56 W qrc:/qml/ui/accordion/LibraryPropertyViewsAccordionItem.qml:453:12: QML LibraryPropertyViewsAccordionItemToolbar: Binding loop detected for property "applyFromLibraryEnabled"

 

Ends after that last same line every time. Things I have already tried:

 

Updating to latest version of CUE.

Uninstall, remove all settings, reinstall.

Repair installation.

Reboot many times.

Update ASMedia USB drivers from ASUS (Z170 Pro Gaming mobo).

Closing all other applications before running CUE.

Running CUE as admin.

Pausing Kaspersky protection.

 

Please help, I can't use my Scimitar!

Link to comment
Share on other sites

OK I have solved my own problem. The issue seemed to be having a custom scaling factor set in windows display properties - I think I had it set to a non-standard value like 110%. I hope this helps someone in future.
Link to comment
Share on other sites

OK I have solved my own problem. The issue seemed to be having a custom scaling factor set in windows display properties - I think I had it set to a non-standard value like 110%. I hope this helps someone in future.

 

Thank you so much Bane2087, you have given me the answer to my problem from this thread.:D: I can now open CUE2 with no crash.

 

I don't know if this fix will work for the others who were having the qt5gui.dll error but at least for me this has really helped, so thank you for posting what fixed your problem.

Link to comment
Share on other sites

  • 4 weeks later...
OK I have solved my own problem. The issue seemed to be having a custom scaling factor set in windows display properties - I think I had it set to a non-standard value like 110%. I hope this helps someone in future.

 

After 2 hours testing and endless search, this solution works for me, Thank You.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...