-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Failed to set Nvidia threaded optimizations #30546
Comments
To help diagnose ppy#30546.
To help diagnose ppy#30546.
Extra logging shows
but I don't see why that would be the case. The only struct involved is this one and things look to check out to me. I wanted to try gpuview again but that tooling is apparently cobbled together using dreams and duct tape and I can't get it to work again. @smoogipoo you're the most likely the one that will know most / best person to ask; is there some secret pathway to nvidia people that we could use to debug this or something? |
Unfortunately I have nothing to help with here, can't see anything wrong in the code. Also don't have inroads to nvidia 😛 |
After bisecting, dda691b seems to be the culprit. |
I'm dumbfounded that bisecting did anything here, and that apparently it's that commit (haven't checked myself yet). For all intents and purposes, I'd expect that size spec to be correct as per https://docs.nvidia.com/gameworks/content/gameworkslibrary/coresdk/nvapi/struct__NVDRS__GPU__SUPPORT.html...? |
Nah, it's incorrect. Those are actually 1-bit fields 🙃, meaning this is a 32-bit flags enum. |
Type
Game behaviour
Bug description
Lazer has been failing to set threaded optimizations for some time on my machine, regardless of the current option of the setting, though i remember it working when it was added.
I reinstalled windows before making this post (for reasons unrelated to osu), installed the official nvidia driver, but the issue persists.
Screenshots or videos
No response
Version
2024.1009.1
Logs
1731054362.network.log
1731054362.performance.log
1731054362.runtime.log
1731054362.auth.log
1731054362.input.log
1731054362.nauth.log
The text was updated successfully, but these errors were encountered: