-
Notifications
You must be signed in to change notification settings - Fork 207
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
Interlaced display modes aren't supported on lwjgl for linux #130
Comments
This should be fixed by the proposed change in: #112 (comment) |
Sounds good. On an almost-related note, does Java support non-capturing groups in regexes? It's been a long, long time since I used Java's particular flavour of regex, but in many dialects you could write it like this: |
Has this issue been fixed in LWJGL yet? This issue is still occuring in programs such as Minecraft. https://bugs.mojang.com/browse/MC-79573 (main bug page, there are also 11 duplicates). |
Custom resolution such as @ScoreUnder Yes they are supported: |
This is the output of
xrandr -q
The error encountered was an ArrayIndexOutOfBoundsException in XRandR.findPrimary.
This is a second-hand error report because my own monitors don't support interlaced display modes, but the person who I'm helping is testing this with Minecraft, which is notoriously hard to replace libraries in nowadays (due to integrity checks and automatic re-downloading). For that reason I can't really test a solution to this, but I suspect it may be as simple as:
I gave my friend an entirely different workaround, and one which is laughably hacky. I sent a tar.gz file containing a directory with these two scripts inside, then instructed them to run
./stupid-hack minecraft
in that directory. It worked.Probably related to:
(It is highly infuriating that even the moderators in that bug report point to the red herring error
~~ERROR~~ RuntimeException: No OpenGL context found in the current thread.
, which is caused byDisplay.<clinit>
failing and contains no useful information of its own.)The text was updated successfully, but these errors were encountered: