Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error when windows goes to sleep and then wakes up (Error: WASAPI: Initialize failed with error 0xffffffff88890008) #84699

Open
Tracked by #76797
viksl opened this issue Nov 10, 2023 · 2 comments

Comments

@viksl
Copy link
Contributor

viksl commented Nov 10, 2023

Godot version

4.2 beta 5 - mono

System information

Windows 11 - Vulkan - Nvidia RTX 4070 - intel i5 13600KF

Issue description

I get this error as in the image:

image

~~My entire project drops from stable 60fps with vsync (without vsync the fps are in hundreds) down to ~20 fps due to something failing. It happens just once and since then the performance never gets back.~~
I'm not sure about he performance drop, it might have been a fluke, right now it gets back up after waking up the computer and give the game focus as usual.

This is apparently an audio driver from the error but I don't even use any audio stream or audio node, I also do not have any audio files in my project and never had. This has not been ahppening in beta 4, it started with beta 5 - potentially a regression maybe?

If it helps, I'm currently testing navigation (3D) in Godot.

Steps to reproduce

No idea, I haven't found a trigger, I have my project running for couple seconds/minute and then BAM.

Minimal reproduction project

No idea, at most I can provide my project if it's needed. Again I don't have and don't use audio at all at the moment or ever in this project, I'm testing navigation.

1 .Open a 3D project, doesn't matter what is in it, feel free to use an empty scene with just a single Node3D.
2. Let windows go to sleep.
3. Wake it up.
4. Observe the errors.

@Calinou
Copy link
Member

Calinou commented Nov 10, 2023

This audio error may be a red herring. Can you run the project with the Dummy audio driver (case-sensitive) by changing the audio driver name in the Project Settings?

Also, please upload a minimal reproduction project1 to make this easier to troubleshoot.

Footnotes

  1. A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).

    Drag and drop a ZIP archive to upload it. Do not select another field until the project is done uploading.

    Note for C# users: If your issue is not Mono-specific, please upload a minimal reproduction project written in GDScript or VisualScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a Mono setup available.

@viksl viksl changed the title Mssive drop in performance due to audo/threading error (Error: WASAPI: Initialize failed with error 0xffffffff88890008) Msssive drop in performance due to audo/threading error (Error: WASAPI: Initialize failed with error 0xffffffff88890008) Nov 10, 2023
@viksl
Copy link
Contributor Author

viksl commented Nov 10, 2023

Ok, so I figure out why it's happening. The peformance drop is also questionable whether that actually happens or not. When I reported this it did not recover but now when I can reproduce this the fps and performance does recover so I'm not sure if I missed something previously, if it was some Windows shenanigans or something else.

Anyway, when it comes to repro project, it doesn't matter. You can open an empty scene in 3D and run, it's not dependent on anything in the project itself as far as I can tell.

How to reproduce this. Run your empty 3d scene, let it keep playing and then let your computer go to sleep (on windows 11), then just wake your computer up and that's when it happens.

I did not notice this since my cats keep waking my computer up running around so it rarely gets to sleep mode so it surprised me, especially considering it does happen randomly but regularly. I feel stupid, I've been holding back on reporting this.

The same happens in previous version (latest 4.1.3).

I'm not sure what to do about this, should I close this? I can't tell if it catches back or not so not sure how much this could or could not affect exported games (or work in editor).

EDIT: I've changed the description and title to better reflect my findings. I'll close this if it's not a problem - I wish I figured this out sooner.

@viksl viksl changed the title Msssive drop in performance due to audo/threading error (Error: WASAPI: Initialize failed with error 0xffffffff88890008) Error when windows goes to sleep and then wakes up (Error: WASAPI: Initialize failed with error 0xffffffff88890008) Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants