Aurora doesn't work

[vicdilou]

Actual behavior:

Aurora start up but don't work

How often does this problem occur?

This problem occurs everytime

What is the version of Aurora you are experiencing this issue with?

My version is beta v0.6.3-516

Does the previous version of Aurora have this issue?

Some previous version have this issue.

I have a G910 with the last update of Ghub and the assistant.

[olokos]

I can confirm this. Upon bootup it refuses to work and requires closing aurora and starting it again

[BrN027]

I have exactly the same issue. Actually, i've untick start with Windows and i lauch Aurora manually.

[olokos]

@vicdilou can you reopen the issue?

[simon-wh]

Have you tried with the latest build and experienced the same issue?

[olokos]

@simon-wh with 0.6.3-532-cnttkfsy on pc start aurora does start, but I need to go into device manager and START corsair, usually this doesn't work and I need to turn off aurora, then turn it on again, START in device manager and it works flawlessly until the next PC reboot.

(I'm talking about device manager within aurora, not windows)

I just downloaded .537 and I'll update this issue once I'm done working.

I'm also running Razer Mamba (the first one with 16k DPI) along with Corsair K70 LUX RGB, if that matters. I tend to plug DS4 aswell, but I'm using DS4Windows by Ryochan7 for DS4 handling so I disabled it within aurora.

[olokos]

https://gyazo.com/1986394e1de16932e05ea0b616b8b51c

exactly the same thing with new version

[simon-wh]

@olokos Could you post your log file for a launch where Corsair doesn't start up when Aurora does? It should hopefully give us some insight into why it doesn't connect when Aurora starts. I take it Razer connects successfully when Aurora starts?

[olokos]

@simon-wh C:\Program Files\Aurora\log.txt is completely empty
Corsair's iCue does start and provides its effects
Razer does connect successfully each time, that's correct.

[simon-wh]

@olokos You need to look in %appdata%/Aurora/logs for the log files, or in Aurora go to Settings -> Debug -> Show Logs folder

[olokos]

@simon-wh
Here it is:
https://pastebin.com/3D4A6Xtb

[simon-wh]

@olokos From what it looks like, it seems that Aurora is starting up earlier than iCUE so is not able to connect immediately and expends all retries before iCUE starts.
Could you try adding a delay to the startup task of Aurora?

1. Open Task Scheduler (Either through searching for it in the start menu or WIN+R and type in taskschd.msc and press Enter)
2. Click on "Task Scheduler Library" on the left
3. Find "AuroraStartup"
4. Right click that entry and click Properties
5. Click on the "Triggers" tab
6. Click on the "At log on" entry, then click "Edit" at the bottom of the box
7. Under Advanced Settings check the "Delay task for" and put in a time, you can try experimenting with this, you can type in an exact number, so try maybe 2/3 minutes initially. Then click Ok for everything
   The screens should look like below
   

Could you let me know how you get on with trying that?

[olokos]

That's exactly what I also thought, but I didn't know a way to delay launching of Aurora, back in the days there were Registry keys, msconfig and such. I wasn't really expecting it to be within tasks.

I think the best solution would be to implement some sort of check if corsair sdk service is running before launching aurora corsair profile.

It does work perfectly fine with this solution though, thanks! 😄

[simon-wh]

@olokos Yeah, I'm planning to do checks and stuff, but I also think what probably didn't help was that it only had 3 retry attempts set, so it wasn't trying very hard get it setup. I think I'll probably set it to do more retries with a bigger gap between them which should hopefully help with other cases.

[olokos]

That sounds even better than what I came up with! My suggestion would be 5 checks with 1 minute delay inbetween 🗡
I mean, people with RGB everything won't be running a slow PC so that should be enough.