No Corsair Devices Detecting

[jordandavies98]

Expected Behaviour

Corsair devices to either show or be automatically picked up (like logitech mouse with overwatch).

Actual Behaviour

Nothing (corsair SDK Is enabled) .

Reproduction steps

i havent found any workaround, so no steps on how to re-create (using QL series fans).

Frequency

every time

Aurora Version:

most recent version as of writing

Previously an Issue?

Don't know

Further notes:

The corsair service wont let me manually start it either. All other services are okay. 2020-11-09 17.55.28.log

[Chroch1]

Same here, i reinstall both icue and aurora and nothing, i have void pro wireless headset and TS100 headsetholder

[gitmacer]

You can try to use the dev build. https://ci.appveyor.com/project/antonpup/aurora/branch/dev/artifacts Please report if it works.

[jordandavies98]

You can try to use the dev build. https://ci.appveyor.com/project/antonpup/aurora/branch/dev/artifacts Please report if it works.

so i tried this, and on my GF's right with LL Series fans, it works like a dream. On mine with QL series fans no joy, still doesnt even start the SDK :/

[zejjnt]

Still no stable release with this fix implemented? It's kind of a bother to choose either stable without half of my RGB or all RGB and Aurora crashes once an hour :/

[gitmacer]

Still no stable release with this fix implemented? It's kind of a bother to choose either stable without half of my RGB or all RGB and Aurora crashes once an hour :/

The dev version is crashing after 1 hour for you? You are the first one reporting that can you please send a log? %appdata%\Aurora\Logs For fast answers it is recommended to write to use over discord.

[zejjnt]

I haven't got all the stuff I previously had so this is a new machine, maybe the OS was a culprit but I'm also using around 8 less RGB related products so I might (hopefully?) not run into that problem again. It seemed to relate to that I had like 12 Corsair products (mixed with Logitech, Razer and Steelseries) and couldn't see the full name string with the window fully stretched across 3 1080p screens :D I'll be in touch if I have anything useful to give you.

But still, are you waiting for something major to be done before you push anything as stable, because it's been a while?

[zejjnt]

@gitmacer Well how about this. Second time I start this version I get an error dialog, keyboard starts to flicker until all Razer services are restarted (Razer Central Service, Razer Synapse Service, Razer Chroma SDK Server, Razer Chroma SDK Service & Razer Game Manager), then the keyboard goes into slow rainbow fade mode. Sometimes the apps quit automatically and sometimes I have to force quit all the Razer applications (Razer Synapse 3.exe, Razer Synapse Service Process.exe, Razer Synapse Service.exe, RazerCentralService.exe) via taskkill or Task Manager, then restart them; first Synapse & Control Center from the Start Menu, then sometimes Synapse again but then via the Control Center tray icon menu in order to get your custom Chroma settings enabled again.

My Corsair & Logitech products DGAF about all of this and continue working as if nothing happened, and the SteelSeries hasn't worked in over a year, so long ago that I forget to point it out (and no one seems to care anyway).

Attaching SS of error dialog and two log files from the folder you mentioned; one has a couple almost duplicated (all are 8 KB) but one is 28 KB and I suspect that may contain some info of what caused this to happen. 2021-02-22 14.42.40.log 2021-02-22 14.45.50.log

[gitmacer]

That is the first time someone reporting that and I wasn't expecting to see your audio setup is making problems. Do you have any special audio setup on your pc? Software? Devices?

Also I see another issue with Razer. Even though there are few reports of the error "Call to native Chroma SDK function QueryDevice failed with error: Unknown: Unknown. (1167)" on other projects sadly I wasn't able to find the reason why razer's SDK isn't working correctly for them and you. To me it seems like that is an issue on razer's and not aurora's side.

[zejjnt]

That is the first time someone reporting that and I wasn't expecting to see your audio setup is making problems. Do you have any special audio setup on your pc? Software? Devices?

Also I see another issue with Razer. Even though there are few reports of the error "Call to native Chroma SDK function QueryDevice failed with error: Unknown: Unknown. (1167)" on other projects sadly I wasn't able to find the reason why razer's SDK isn't working correctly for them and you. To me it seems like that is an issue on razer's and not aurora's side.

But in the latest stable there are never problems with my Razer products, only Corsair, so along the way something has been changed which has fixed that problem.

Relevant setup should be Sounds: Steelseries Arctic 5 via USB to motherboard. 2 x Audio Pro C5 used with 3.5 phono and/or RCA, via Corsair ST100, via USB. Occationally Sennheiser M2 via BT. The devices that are not used currently are all disabled. I am almost always using the Arctis 5. Windows, relevant software and drivers are updated (or checked for updates) almost every day and I always use stables, no previews, alphas, betas, nightlys or anything other than stable versions are used at all times. Playing through Chrome or a Chromium based application 99% of the time, foobar2000 is used when listening to locally stored material.

Devices that are relevant I really don't know. Corsair MM100 (that is both an RGB unit (pairs with the mouse pad light settings), and a USB soundcard,, Corsair Commander Pro, Corsair Lightning Node, 3 Corsair iCue LS100, a bunch of Corsair QL120 & 140, some ML120/140, might be an SL120 in there as well. I used to have the fan setup continuous but my computer caught fire lol. Aurora is set to QL for the fans but that has never been an issue at any time. The only Razer Product is the Razer Blackwidow Elite. Logitech G903 Lightspeed on Logitech Powerplay, on top that pad there is a Corsair MM800. Sometimes a NAD D3020 is plugged in via USB, using NADs own recommended drivers. All sound enhancements, surround emulation and such nuisances have been disabled and the sound output for all units have been setup for 48000 KHz, 16 bits, 2 channels.

Again, the functionality of these devices never fail with the beta version, but Aurora crashes instead.