Skip to content

Conversation

@Spodi
Copy link
Contributor

@Spodi Spodi commented Dec 15, 2025

This actually changes multiple things for the Directx renderer:

  • Graphic adapters (more or less "GPUs") aren't enumerated and checked until one can do at least feature level 10_0. Instead the first one (preferred) is used. This makes the checks easier (only one needs to be tried) and also always respects the "preferred GPU" setting from Windows10 (or driver control panel on older Windows versions).
  • Fallback to WARP (software renderer), if the primary adapter can't at least do feature level 10_0, can't do compute shaders / DirectCompute or fails for some other reason.
  • More granular error messages why the selected adapter isn't suitable/capable. Those will pop up each start, even when the fallback is successful.
  • More logging. Including adapter / GPU name.
  • Log when MSAA setting is ignored on old feature level 10_0 hardware. This was the case since some attempts for more compatibility where made, but was never logged. Also apparently there are not many GPUs out there that only support feature level 10_0, but with compute shaders. So this was and will be rarely noticed. But better save than sorry.

I feel like it's ready. Feel free to suggest better messages or anything else that can be improved.

Testbuilds:

@Spodi Spodi marked this pull request as draft December 22, 2025 23:00
@Spodi Spodi marked this pull request as ready for review December 23, 2025 22:46
That should never be shown. But who knows what broken Windows installs are out there.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant