rongtw Posted August 18, 2017 Share Posted August 18, 2017 does this log look normal for my M65 pro ? 2017-08-18T08:52:57 I cue.init: CUE version: 2.15.83 2017-08-18T08:52:57 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V2/ 2017-08-18T08:52:57 I cue.init: Build type: Public Release 2017-08-18T08:52:57 I cue.init: Applicaiton ID: 6012 2017-08-18T08:52:57 W cue.locale: "Cannot load qt_en.qm translations" 2017-08-18T08:52:57 I cue.init.font: Using Regular text font family: "Open Sans" 2017-08-18T08:52:57 I cue.init.font: Using Title text font family: "Gotham Bold" 2017-08-18T08:52:57 I cue.session: Locked changed to false 2017-08-18T08:52:57 I cue.session.win: Will notify 'connected changed to' with delay 2017-08-18T08:52:57 I cue.session: Local changed to true 2017-08-18T08:52:57 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\sneeky\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder" 2017-08-18T08:52:57 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\sneeky\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder" 2017-08-18T08:52:57 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2017-08-18T08:52:57 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2017-08-18T08:52:57 W cue.library: Actions load failed: Could not detect cereal root node - likely due to empty or invalid input 2017-08-18T08:52:57 I cue.action.macro.win: Init time: 0.402422 (init: 0 reset: 0.00199415 ) 2017-08-18T08:52:58 I cue.session: Connected changed to true 2017-08-18T08:52:58 I cue.dev: Requesting working state enter because session connected. 2017-08-18T08:52:58 I cue.dev.enum.hid: Entering working state. 2017-08-18T08:52:58 I cue.sdk: Entering working state, session connected. 2017-08-18T08:52:58 I cue.sdk: Starting router. 2017-08-18T08:52:58 I cue.dev: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#7&2d3ff5b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 2017-08-18T08:52:58 I cue.dev: Created new device object: M65 PRO RGB; ready: 0 2017-08-18T08:52:58 I cue.dev: Attached to device object M65 PRO RGB: b=0 a=0 2017-08-18T08:52:58 I cue.dev: Attached to device object M65 PRO RGB: b=0 a=0 2017-08-18T08:52:58 C dev.manifest: Cannot find path for manifest key QPair(6940,6926) 2017-08-18T08:52:58 I cue.dev: Manifest for device vid=1b1c pid=1b0e not found. 2017-08-18T08:52:58 I cue.dev: Attached to device object M65 PRO RGB: b=0 a=1 2017-08-18T08:52:58 I cue.dev: Initializing M65 PRO RGB... 2017-08-18T08:52:58 C dev.manifest: Cannot find path for manifest key QPair(6940,6926) 2017-08-18T08:52:58 I cue.dev: Manifest for device vid=1b1c pid=1b0e not found. 2017-08-18T08:52:58 I cue.dev: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#7&37b3387b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 2017-08-18T08:52:58 C dev.manifest: Cannot find path for manifest key QPair(6940,7173) 2017-08-18T08:52:58 I cue.dev: Manifest for device vid=1b1c pid=1c05 not found. 2017-08-18T08:52:58 I cue.dev.nxp: M65 PRO RGB : trying to force P0 0 instead of P0 4 2017-08-18T08:52:58 C dev.manifest: Cannot find path for manifest key QPair(6940,6926) 2017-08-18T08:52:58 I cue.dev: Manifest for device vid=1b1c pid=1b0e not found. 2017-08-18T08:52:58 I cue.dev.nxp: M65 PRO RGB : success, continue initialization on P0 0 2017-08-18T08:53:00 I cue.dev: Initialized (st=1) M65 PRO RGB. 2017-08-18T08:53:00 I cue.lightings.player: Started lighting worker in 0x20b4 2017-08-18T08:53:01 I cue.dev: Device insertion processing complete for M65 PRO RGB. 2017-08-18T08:53:02 W QFSFileEngine::open: No file name specified 2017-08-18T08:53:02 C cue.download.fw: Aborting idle process not supported. 2017-08-18T08:53:02 W QFile::remove: Empty or null file name Link to comment Share on other sites More sharing options...
rongtw Posted August 18, 2017 Author Share Posted August 18, 2017 This a log from a few moments ago when the mouse failed to load totally i had to restart PC 2017-08-18T13:54:43 I cue.init: CUE version: 2.15.83 2017-08-18T13:54:43 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V2/ 2017-08-18T13:54:43 I cue.init: Build type: Public Release 2017-08-18T13:54:43 I cue.init: Applicaiton ID: 7040 2017-08-18T13:54:44 W cue.locale: "Cannot load qt_en.qm translations" 2017-08-18T13:54:44 I cue.init.font: Using Regular text font family: "Open Sans" 2017-08-18T13:54:44 I cue.init.font: Using Title text font family: "Gotham Bold" 2017-08-18T13:54:44 I cue.session: Locked changed to false 2017-08-18T13:54:44 I cue.session.win: Will notify 'connected changed to' with delay 2017-08-18T13:54:44 I cue.session: Local changed to true 2017-08-18T13:54:44 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\sneeky\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder" 2017-08-18T13:54:44 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\sneeky\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder" 2017-08-18T13:54:44 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2017-08-18T13:54:44 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input 2017-08-18T13:54:44 W cue.library: Actions load failed: Could not detect cereal root node - likely due to empty or invalid input 2017-08-18T13:54:44 I cue.action.macro.win: Init time: 0.402616 (init: 2.93e-07 reset: 0.0018993 ) 2017-08-18T13:54:45 I cue.session: Connected changed to true 2017-08-18T13:54:45 I cue.dev: Requesting working state enter because session connected. 2017-08-18T13:54:45 I cue.dev.enum.hid: Entering working state. 2017-08-18T13:54:45 I cue.sdk: Entering working state, session connected. 2017-08-18T13:54:45 I cue.sdk: Starting router. 2017-08-18T13:54:45 I cue.dev: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#7&2d3ff5b5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 2017-08-18T13:54:45 I cue.dev: Created new device object: M65 PRO RGB; ready: 0 2017-08-18T13:54:45 I cue.dev: Attached to device object M65 PRO RGB: b=0 a=0 2017-08-18T13:54:45 I cue.dev: Attached to device object M65 PRO RGB: b=0 a=0 2017-08-18T13:54:45 C dev.manifest: Cannot find path for manifest key QPair(6940,6926) 2017-08-18T13:54:45 I cue.dev: Manifest for device vid=1b1c pid=1b0e not found. 2017-08-18T13:54:45 I cue.dev: Attached to device object M65 PRO RGB: b=0 a=1 2017-08-18T13:54:45 I cue.dev: Initializing M65 PRO RGB... 2017-08-18T13:54:45 C dev.manifest: Cannot find path for manifest key QPair(6940,6926) 2017-08-18T13:54:45 I cue.dev: Manifest for device vid=1b1c pid=1b0e not found. 2017-08-18T13:54:45 I cue.dev: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#7&37b3387b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 2017-08-18T13:54:45 C dev.manifest: Cannot find path for manifest key QPair(6940,7173) 2017-08-18T13:54:45 I cue.dev: Manifest for device vid=1b1c pid=1c05 not found. 2017-08-18T13:54:45 C dev.manifest: Cannot find path for manifest key QPair(6940,6926) 2017-08-18T13:54:45 I cue.dev: Manifest for device vid=1b1c pid=1b0e not found. 2017-08-18T13:54:45 I cue.dev.nxp: M65 PRO RGB : trying to force P0 0 instead of P0 4 2017-08-18T13:54:45 I cue.dev.nxp: M65 PRO RGB : success, continue initialization on P0 0 2017-08-18T13:54:46 I cue.dev: Initialized (st=1) M65 PRO RGB. 2017-08-18T13:54:46 I cue.lightings.player: Started lighting worker in 0x170c 2017-08-18T13:54:48 I cue.dev: Device insertion processing complete for M65 PRO RGB. 2017-08-18T13:54:49 W QFSFileEngine::open: No file name specified 2017-08-18T13:54:49 C cue.download.fw: Aborting idle process not supported. 2017-08-18T13:54:49 W QFile::remove: Empty or null file name Link to comment Share on other sites More sharing options...
Toasted Posted August 18, 2017 Share Posted August 18, 2017 Logs are used by developers to see what the software is doing. While it could contain useful information, in most cases it does not. The log in your second post does not provide any hints as to why the mouse was not loaded correctly? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.