Jump to content

makmanos

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by makmanos

  1. 7 hours ago, Corsair Notepad said:

    The MSI software is known for being aggressive in its ability to take exclusive control over third-party hardware such as our mice, and keyboards. If the issue is not able to be resolved by disabling the option in the MSI software then you should also be able to disable the SDK option in the iCUE software preventing the MSI software from being able to connect to and control those devices. Also may not hurt to reach out to MSI support and let them know that the option in their software to disable third-party hardware control does not seem to work properly as that is something they will need to resolve within their software.

    Thanks for your reply. I have shut down Mystic Light and disabled it from starting up for now. I may actually reach out to MSI support as well. I didn't realize you can disable iCUE's SDK for third party software. However, shouldn't your SDK also at the minimum warn the user that a third party app is trying to control lighting for your own hardware and let the user at least decide if they would like that and display a warning in iCUE? That's probably a worth while feature for iCUE because it seems it can be hi-jacked by others at the moment.

  2. Apparently it's a known issue I found this thread on these forums


    Wow this is totally messed up. I played a bit with it and although I have disabled the third party RGB override in Mystic Light (that's what MSI calls their software) if I nevertheless choose a profile for the mouse in Mystic Light it will immediately override iCue and apply it to the M65 Elite mouse, which it apparently recognizes and displays it in Mystic Light. I need to restart iCue for it to take control over again. I am not sure how this is possible, one would think that each company's software should have priority over the other for controlling their hardware (I have a MSI motherboard and liquid cooler that's where the MSI  Mystic Light comes from)
     

  3. Thanks again for your reply! 
    I found what the problem was. Apparently the MSI software that I have for controlling lighting schemes, overrode Corsair's. That's where the steady red light was coming from. I had forgotten about it, yet I got no notification in iCUE that there was a conflict with a different lighting software. I disabled the third party override function in MSI Center and at least now iCue controls the mouse lighting scheme.
    That was weird, thanks again.

  4. 45 minutes ago, c-attack said:

    Can you show us the lighting effects tab for the M65?  Make sure you did not activate one of the “scenes” on the main page. There is a red one and it will override all current lighting settings and sit on top like a blanket. 

    Thanks for your interest! So I am totally confused about what the scenes are supposed to be doing as well as what happens when I make a custom lighting effect under my own profile. At the same time, I am not sure which profile is selected at any given time. Anyway, on the Scenes page the only scenes I have selected to try them out are the Rainbow Wave and  a couple of others but not the static red ones. If you look in the screenshot I attach for example, I have chosen the Rainbow Wave Scene and yet nothing happens. I see a cyan static color scheme but my mouse is lit red. Now when I select "Lighting Effects" I get a screen that shows the mouse lit red and an info window that says that this device is controlled by Scenes, the Lighting effects tab is disabled. I don't get it. If it's controlled by Scenes why doesn't it show me the scene I choose? I haven't found a video or help page yet that describes how to use the iCue interface, that's why I made this post. image.thumb.png.4f2118d60bee20706671e6b642a93d26.png
    image.thumb.png.9ba353576f01287258401c0d1b2152de.png

×
×
  • Create New...