Aurora Bug Reports Discussion

In the settings you can change the volume of the trainer's voice. I have it set to maximum, which was fine at first, but every time I start the Aurora process, the volume is reduced. This is fixed if I go into the settings, lower the volume, click the "Test" button, then raise it back up again and click "Test" again (though I'm unsure if clicking it a second time is necessary, I just do it to make sure the volume is applied).

Easiest way to test it:
1. Go into Aurora settings
2. Increase audio volume to the maximum
3. Click "Test" to make sure it's at max volume
4. Exit Aurora and restart it
5. Go into settings again
6. Click "Test" and notice the volume's been lowered
7. Decrease the slider by any amount.
8. Click "Test"
9. Increase the slider back to maximum
10. Click "Test" to make sure it's now at max volume

It's like it's not actually saving my volume settings even though the slider stays where I set it to.

[Edited by mrwallace888, 10/2/2024 12:49:12 PM]

I was only able to reproduce it once and even then the volume is correct in Aurora settings so I don't know why it played the audio with lower volume. But now I can no longer reproduce it. If I max the volume or even set volume close to max, restart Aurora and hit the test button it plays the audio with full volume.

It's kind of hard to capture but luckily OBS's volume meter helped show it.
streamable.com/kb5fyf

🤷‍♂️ You can check the Global Settings.json file in %appdata%\Cheat Happens\Aurora if the value of the "Volume" entry is 1.

The volume is set every time before it plays the audio file. If the value from the setting file is 1 (maximum) then Aurora sets the volume also to 1 and plays the audio. At this point if the volume level is not correct, it's not the fault of Aurora or something I could address.

Yeah it's still changing that. This problem disappears if it's at any other volume, though. Only when it's set to 1 on startup does it make it go quiet until I do the aforementioned steps.

A sort of "solution" is to set the volume in the config file to "0.99" but any higher than that (even like 0.991, 0.992, etc.) and this bug happens.

This is... extremely weird.

[Edited by mrwallace888, 10/2/2024 5:03:26 PM]

Set it to 0.99 if it only happens on 1. I wish I could constantly reproduce that but I cannot. Although even if I would like I said before there is low chance for me to fix it. Whatever causes it it's not within my code.

It's quite alright, it's just such a weird and... rather oddly specific bug. I'd try it on multiple rigs if I could, but I've only got one.