fullscreen mode in LWJGL2 on Linux crashes during startup

[RossComputerGuy]

I get this exception while trying to put my game into any fullscreen resolution. Is there any way to go into fullscreen from the dialog that doesn't have this problem?

java.lang.RuntimeException: Unable to find fullscreen display mode matching settings
	at com.jme3.system.lwjgl.LwjglDisplay.createContext(LwjglDisplay.java:79)
	at com.jme3.system.lwjgl.LwjglAbstractDisplay.initInThread(LwjglAbstractDisplay.java:113)
	at com.jme3.system.lwjgl.LwjglAbstractDisplay.run(LwjglAbstractDisplay.java:211)
	at java.lang.Thread.run(Thread.java:748)

[stephengold]

This appears to be a troubleshooting question. Such questions are best answered at the Forum:
https://hub.jmonkeyengine.org/

[MeFisto94]

I guess Linux and lwjgl3?
Then it's something we should really take care of. The Clue was that the settings dialog is falsely setting the frequency (setFrequency) as it's somehow differently reported by AWT/whatever we use to get the resolutions

[rsubtil]

I had this problem too some time ago and reported it here. It has not yet been fixed AFAIK but for anyone willing to dig deeper, here's what I found out:

• As @MeFisto94 said, this problem happens because LWJGL and AWT are reporting different refresh rates for the same resolution. Forcing the refresh rate to 60Hz in my case makes jMonkey apps able to go fullscreen.
• This problem is happening with the nvidia proprietary driver for linux, in my case. Switching to nouveau fixed these problems to me, so I encourage other people to test this as well. Back then I had a legacy driver (340.X), but even with the latest driver (415.X) this problem persists.

[louhy]

I see these strange refresh rates coming from AWT too. Linux, NVidia proprietary drivers. I don't know if there's a fix, maybe a workaround, but that workaround (ex. force 60Hz on Linux) may just create a problem for someone else, no?

[riccardobl]

If this happens on linux with lwjgl2, it might be related to this https://hub.jmonkeyengine.org/t/fix-for-unable-to-find-fullscreen-display-mode-matching-settings-for-multimonitor-configurations-in-linux/41510 .
LWJGL2 is unmaintained so i don't think we will get an official patch.

[louhy]

Does anyone even use 2 anymore? I noticed a two year old comment (I think) from shadowislord about looking forward to removing it once 3 is stable, or something along those lines.

Also I'm pretty sure I was using 3 and seeing this issue. Isn't the issue related to AWT (or AWT interaction with NVidia drivers), though?

[riccardobl]

I use 2. It's a generic error, it might be caused by several things.

[stephengold]

I've encountered this issue on Linux Mint. Substituting the jme3-lwjgl3 library for jme3-lwjgl works around the issue.

[louhy]

Yeah, confirmed (also Linux Mint).
To be clear, I still see the strange Hz options in the settings dialog, but instead of crashing, it just works.
I guess can't be fixed and probably not worth it anyway.

[stephengold]

Does anyone even use 2 anymore?

LWJGL2 is still used by default in jme3-examples and the SDK. Also, Issue #942 might discourage some people from upgrading to LWJGL3.

[louhy]

Yeah, I wasn't suggesting removal of 2 unless the answer was "nope", and clearly it's not.

[RossComputerGuy]

I use jme3

[louhy]

I use jme3

We all do :) This is about LWJGL2/3, a dependency which lets JME3 talk to OpenGL.
Or do you actually mean lwjgl3?