Fall back to Direct3D when dashboard OpenGL fails - #141
Merged
CodeZeno merged 1 commit intoSep 25, 2026
Merged
Conversation
CodeZeno
force-pushed
the
main
branch
2 times, most recently
from
September 25, 2026 02:25
dda0af4 to
814ff73
Compare
CodeZeno
force-pushed
the
fix/windows-365-dashboard-renderer
branch
from
September 25, 2026 05:36
36e6dbf to
bd00f00
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue: Running Claude-Code-Usage-Monitor on a windows that doesn't support opengl 2.0 fails.
This happens when I'm working on a Windows 365 machine, since its a simple Hyper-v virtual hardware, some stuff related to opengl doens't work properly.
The solution here is to try to load opengl backend, if it fails, we fallback to direct3d backend, if it fails, it shows the error just like it does for now.