Exiting Minecraft or using fullscreen mode changes refresh rate (from >60/120Hz) to auto (60Hz)

As this only happens with Minecraft and because Devin get's the same quirky behaviour with a complete different setup: No.

How many other java applications do you use? How many of them use LWJGL? Neither one is particularly common, so it's not that easy to be certain Minecraft itself is the cause.

Yes, I also suspect LWJGL to be the cause of this, as I can't see why Minecraft should do this by itself. Still, that's only a suspicion. And, no, I don't use any other LWJGL games. Still, the problem affects Minecraft, so I'm reporting it here. That's probably the best way as Grum is also involved in the LWJGL community, if this should be a LWJGL bug.

I testet this on some other Linux OSes now, same result.

The Open-source game Xonotic used to have similar problems on Linux OSes. Enabling NetWM fullscreen fixed this problem (http://forums.xonotic.org/showthread.php?tid=4369) and a fullscreen problem: https://mojang.atlassian.net/browse/MC-36747 I have no idea if I can help with this information, just mentioning it.

This could fix the fullscreen 60Hz problem that first appeared in 13w48b, but still doesn't explain the 60Hz switch when exiting minecraft.

Unfortunately, I couldn't find any other lwjgl applications to try, so I can't tell if this is a problem with minecraft itself of lwjgl.

If the fullscreen mode runs at 120Hz again, I'd be very happy. Always having to change the refresh rate when exiting isn't nice, but still better than not being able to play at 120Hz at all. This was possible in 1.6.4. Windowed mode never rendered more than 60fps anyway, even though there's 300 in the debug menu. This is the only thing I haven't tested on any other Linux OS than Kubuntu yet.

A borderless fullscreen mode with the possibility to manually set screen resolution would be nice! All of Valve's games for linux work like that and these are the best linux games so far.

affects 14w02b

Tried several versions now, alpha, beta and release versions. Found the problem in every version, 1.7 broke it completely.
Also updated to Kubuntu 13.10 and now I have to kill minecraft so that I don't kill lightdm. We NEED a fix now!

I've found a way to prevent resetting the refresh rate to auto. Go to /etc/X11/xorg.conf and delete everything in "Option "metamodes"" with the name nvidia*, this will disable nvidia's autoresolution. This is a workaround to fix some problems with minecraft, but it can cause other problems (new screens might not work at all because there is no autores anymore).

This fix only works for nVidia GPUs, not sure if there are similar problems with Intel and AMD.

This doesn't mean you don't have to fix it anymore 😉 Thanks so far.

//Sorry, this workaround doesn't work with Minecraft 1.7+, still broken. Seems to work just fine in 1.6.4, fullscreen doesn't reset the refresh rate and quitting the game works, too.
Fullscreen AND quitting the game is broken with 1.7, this will reset it.

Devin, do you have multiple monitors with different refresh rates? Maybe that's part of the problem?

me: 120hz main, 60hz 2nd

Yes, I do. I want a 120Hz one as I don't like 60, but why should I spend soo much money on a second one just for tweetdeck and some web browsing? A cheap 60Hz one is enough to do this.

As I said, it seems to work with 1.6.4- now, but whatever I do, 1.7 broke it.

I suppose this metamodes option is nvidia-exclusive (never heard of it)?
I'm running the game windowed (kind of borderless windowed) with awesomeWM and I'm not using a display manager. I only get the 60hz framerate reset (also with older versions, not just 1.7).

Maybe you should update the description of the bug report report to reflect that it only affects specific multi-monitor setups?

Haha, ok, if I use the ingame fullscreen option the game immediately sets the refresh rate to 60hz (I think it re-applies ( ? ) the settings to every monitor, as my 2nd one also flashes because of a resolution/refresh change) and then kind of crashes and leaves me with a minecraft window that doesn't render properly anymore. (1.6.4)

I just disconnected the second screen. 1.6.4- works just fine, no problems. Then I tried 1.7.4, didn't work. So 1.7 is completely broken on Every 120Hz setup. I think. When entering full screen mode, Minecraft tries to change the refresh rate on both screens, and on 1.7 it simply crashes lightdm (everything is just black, cursor still visible, need to restart to get it working again)

Hey, I just found this post on the minecraftforum about the issue. http://www.minecraftforum.net/topic/1780873-minecraft-resets-refresh-rate-to-60hz-upon-quit/
You should probably edit the title of the issue, as it not only affects 120hz monitors.

Also, I just tested it with Terasology , a open source minecraft clone also using lwjgl, and I get the same problem. So it's either a lwjgl bug or a jre/openjdk bug. I will try to talk with some of the lwjgl developers about it, since it seems like you can't expect ANY support from mojang.

First, this is a bug tracker, not a support system, so it should be no surprise if you don't get any support here. If you want support, go to the support site. Second, why should they be responsible for fixing bugs in other people's software, as it appears may be the case here?

Yes, the probably should, and may already have, communicated to the LWJGL team that there may be a problem. But if they don't experience the problem themselves, it's hard to provide the necessary information for them to track down the problem. You, on the other hand, can provide that information, so it makes the most sense for you to communicate directly with the LWJGL team, rather than expect Mojang to act as a go-between.

I'm sure this is a problem with minecraft. Minecraft's fullscreen has always done this, but using 1.6.4 and below, I got the game stopping correctly. I don't know why as I reset my xorg.conf, but it works. 13w48b and 1.7+ don't work. If these versions use a different version of LWJGL, this might not be a problem with minecraft itself, but mojang could fix it anyway.

I've tried several versions of OpenJDK and nVidia's X.Org driver, all ended up the same: 1.6.4 works, 1.7 doesn't.

And, as I said above, system's fullscreen doesn't work with 1.7+ anymore, and as Minecraft's doesn't work anyway, a >60Hz screen seems useless for this game.

I think the fullscreen 60Hz issue and the "quit game" 120->60Hz issue is the same, so I won't submit a new bug. But this needs to be fixed!

@Torabi guess what we are doing. We try to provide information about the problem so mojang can fix it. And, as I said, 1.7 made this much worse, isn't that enough information?

Signed up to comment on this one, I am the OP of the original minecraft forum thread.

I can confirm this is an issue with LWJGL. I'm working on a LibGDX game which uses LWJGL to launch a desktop version of the game, and it has this same issue.

Submitted the issue to LWJGL's Github.

Associated bug report can be found here: https://github.com/LWJGL/lwjgl/issues/64

Good to hear this! I tried talking to them on IRC, but sadly there wasn't much activity. I didn't just want to create a bug report, as I was not sure if it is definitively a LWJGL bug.

Resolved as invalid unless someone confirms its a Minecraft issue.

Seems like an lwjgl update could fix this, but this is still a minecraft problem; relacing the lwjgl.jar with a modified one doesn't work, minecraft downloads the old one everytime. There should be a way to use a custom lwjgl.jar file or something to fix this problem.