FunkinCrew / Funkin

A rhythm game made with HaxeFlixel
https://www.newgrounds.com/portal/view/770371
Other
2.99k stars 2.3k forks source link

Bug Report: Levels doesn't work when changing Audio Output Device #2285

Open Repertix opened 6 months ago

Repertix commented 6 months ago

Please check for duplicates or similar issues, as well performing simple troubleshooting steps (such as clearing cookies, clearing AppData, trying another browser) before submitting an issue.

If you are playing the game in a browser, what site are you playing it from?

If you are playing the game in a browser, what browser are you using?

What version of the game are you using? Look in the bottom left corner of the main menu. (ex: 0.2.7, 0.2.1, shit like that)

0.3.2

Have you identified any steps to reproduce the bug? If so, please describe them below in as much detail as possible. Use images if possible.

Please describe your issue. Provide extensive detail and images if possible.

So, I was playing Week 6 when my earbuds ran out of battery so I quickly paused the game, and changed the earbuds for another pair I have, when I connected back, I noticed the game was muted so I restarted the level, after restarting, the first notes appeared but stopped moving upwards, if you try to restart the level this won't work as the notes will behave just like in the first time.

After checking a bit further, when entering other levels, the level starts fine but in the moment the Enemy or Boyfriend hits the first note, the notes stop moving again and level freezes.

My Epic Evidence:

https://github.com/FunkinCrew/Funkin/assets/43357489/480f8cf6-7a18-42b0-8cd9-122d802a6856

If you're game is FROZEN and you're playing a web version, press F12 to open up browser dev window, and go to console, and copy-paste whatever red error you're getting

EliteMasterEric commented 6 months ago

I believe this is an issue with the Lime library, where it does not include functionality to detect a change in audio device and reinitialize the playback module. As a result, all audio stops.

As a side effect, the Conductor does not change its position since it relies on the current timestamp of the audio (which isn't currently playing!) and therefore the notes (which rely on the Conductor position) don't move!

We will look into fixing it but it's not easy.

AbnormalPoof commented 1 month ago

Does this still occur in v0.5.1?

NotHyper-474 commented 1 month ago

Does this still occur in v0.5.1?

Yes