Ok, so went to start minecraft today been a while since I last played but never had the issue in the past. My second display went out when the game went to game mode. So I closed the game and it didn't come back up. Checked the display settings. The system no longer seen the second display at all. In fact it didn't come up with a reboot. So powered back down. Checked the bios settings and then removed power from the display. This time on rebooting it came back up.
I develop software using Opengl, DirectX and vulkan. And I've never EVER created such problem. I don't even want to guess what you did but whatever the hell it was its wrong.
Full screen game mode doesn't require the second display being shut down. In testing it only makes about a 3fps drop leaving it open across games. If you are worrying about a 3fps issue you are focused on the wrong issue in your game engine. Suggest you learn to properly profile your game engine even if it is threaded it can still be done. Hell I can profile the game engine i have which uses a task manger to grand central dispatch. With all your expertise there you sure as heck should be doing better than this.
You might want to put the option back in to run in borderless window mode. I'm pretty sure most of your players/ customers would prefer having that option over this type of garbage.
Comments 6
I only got the one option under the menu. So that was what I selected. If it gave me the option to select 1.13.1 I would have.
Cannot reproduce. The game enters/exits fullscreen just fine without any other monitors being affected. Tested with two monitor setup and going fullscreen with both monitors
It does it every time for me. The only way I can play the game safely is to put the game in window mode.
Where you using the same hardware? My guess is no. My bet even though I mentioned in the complaint I am using a radeon R7 370 you probably tested with an Nvidia card in your system. No I don't expect you to have every hardware on hand to test. But at least knowing something like this causes issues for some cards would be a good reason to avoid it.
It appears to be an on going issue with AMD display drivers when they aren't shut down properly they crash all the way. Which means the system needs to see the hardware again as new hardware thus the unplug and plug back in. It's not like this is some secret you can find discussions on the issue on pretty much every board out there that talks about hardware to the tune of 27 million references.
Going fullscreen game mode doesn't require shutting off the other monitor. So why do it over a 3fps max gain when you can create issues like this. Unless the person is playing a movie or some video in the other screen you aren't going to see a significant frame drop leaving it up. If the user is stupid enough to play a movie while gaming that's on them not on you.
To be clear the difference this version of minecraft gets between windowed for me and fullscreen amount to less than 1 fps. The reason being is the second display is essentially a static image and doesn't need reloading unless something changes.
Please do not mark unreleased versions as affected.
You don't have access to them yet.