Jump to content
Corsair Community

rongtw

Members
  • Posts

    49
  • Joined

Everything posted by rongtw

  1. Ticket #764378 is the ticket number , thanks
  2. Hi My M65 has just started sticking on left Mouse button ? when playing BF4 Is this a known problem ?
  3. What you need to do , as i found out Under the weight top right you will see a small button like a reset with a pin hold down a short time , reconnect the mouse remove the CRP disabled file . All should be fine then
  4. rongtw

    HX750i

    Hi the +5v jumps from 3.3 v to 5.4 v randomly , Link shows a constant +5 V running by itself . what happens is the Keyboard misses key strokes , and the mouse randomly slows down which is a pain while playing BF :(
  5. rongtw

    HX750i

    for some reason the screen grab dont work , try this link http://s1361.photobucket.com/user/ronwillsher/media/PSU_zpsgagbhxqv.png.html?o=0
  6. rongtw

    HX750i

    Hi , i have been having problems with my mouse and Keyboard , after trying several the problem persists . It has been suggested check my +5 volts on the PSU testing with HWINFO shows +5 v at 3.28 V ? is this considerd ok ? s1361.photobucket.com/user/ronwillsher/media/PSU_zpsgagbhxqv.png.html?sort=4&o=2
  7. Zotty , i have No problems with my Corsair HX750i or my Corsair H100i GTX , I do believe the Hardware is brilliant I had no problems with the Old M65 , But the M65Pro RGB :( The mouse is spot on its the CUE software that lets it down :( I have now got myself a Logitech G502 mouse which worked straight out the box
  8. They may have sold lots of hardware , but people who are new users will not know about the problems with software untill the try to use them
  9. Yes :( lots of post here Highlighting the fact that decent hardware is being let down by BAD software . No doubt Corsair will lose sales because if this
  10. TBH i have given up hope of CUE to fix this and work correctly
  11. I also see this now and again , BF1 and BF4 ? I have latest CUE , but i also saw it in previous cue offering :( have just tried the soft reset see what happens
  12. The USB unplug sound bug is back with this update
  13. Looks to have fixed the USB problem with my M65 Pro
  14. so it looks like i have to use my coolermaster mouse until they fix CUE . last month they said CUE 2.17 was getting released But nope :( Support say just try force firmware :( No help at all
  15. Allegedly according to Corsair James CUE is updated every month ? well last update was 21/08/17 so its now 21/09/2017 and NO updates
  16. I had this problem with my M65 ,,,, i scrapped it :( mouse is great , CUE is crap software
  17. So eventually i found a fix for CUE problem with my m65 pro RGB ! UNPLUG AND PUT IN RUBBISH BIN Plugged in my old CM sentinel 2 and YES works 100% no errors
  18. Yes they need to release 2.17 urgently ,, as they do update every month mmmmmm this one was a week overdue , because of buggs
  19. snapper69 ,, dont ya read ? http://forum.corsair.com/v3/showthread.php?t=161278 Uninstall CUE mouse starts correctly except wrong profile and cant change dpi
  20. Oh dear :roll: still has not fixed my m65 USB disconect sound 30- 60 sec after start , before CUE loads .:eek:
  21. On the 25/7/17 Corsair stated a new update next week :(: Then they said we found some bugs in it :eek: since then its been very quiet :evil: "Originally Posted by Corsair James We release updates every month, which is more frequent than most other gaming software. In fact, I'll be releasing 2.16 next week." Originally Posted by Corsair James View Post I do have 2.16 but its been delayed and Im going to wait until 2.17 to deploy. My ETA for 2.17 is 8/22.
  22. 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
  23. My Corsair PSU and AIO are working perfectly because it uses Link not CUE , so the problem is not the Hardware its fecking CUE software is Pants :(
×
×
  • Create New...