-
Notifications
You must be signed in to change notification settings - Fork 334
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
DX11 crash when changing max frame latency #277
Comments
Can you try this on Windows 10? There have been quite a few issues reported on Windows 11 |
Yes. Just tested and indeed it's running fine on Win 10. But the Win 10 PC I tested on also had a different GPU (GTX 1070Ti) with a game ready driver (the Win 11 PC is running a studio driver), so OS was not the only difference. One more thing I noticed - when running on Windows 11, the V-Sync checkbox in both DX11 and DX12 seems to have no effect, the fps is permanently locked to my refresh rate. In Vulkan and OpenGL it works fine. And on Win 10 it works correctly in all 4 backends. |
This is unlikely the driver. Nobody has reported this issue on Win10.
Yes, somebody else has also reported this problem. There appears to be quite a few issues on Win11, they should be fixed eventually. |
I have a crash in every Diligent Sample when runnning the D3D11 backend. The crash happens when trying to change the "max frame latency" option to any value. DX12 does not crash when changing the latency (Vulkan and OGL don't have this option). Release/64 crashes, Debug/64 catches an assertion:
Call stack and variables:
Environment:
The text was updated successfully, but these errors were encountered: