OSX: Retina and F+11 FullScreen Broken

Just reporting the same issue, also on a retina screen, on 14w29b

Same here, with latest Java 8 and retina screen.

Same in 14w30a

Comfirmed in 14w30b as well. thats 6 different snapshots w/ this issue... whats the deal-e-o. playing in a window works fine and can be stretched out but w/ the new chunk loading (32) I would really love to experience it in full screen.

Yes, you should use the double arrows that OS X provides, it'll look better and allow you to switch between apps easier.

That's not a good long-term solution as it really ruins overall performance.

Can the title be changed? Something like: OS X: fullscreen on Retina display zooms to bottom left 1/16th. More descriptive and captures the absolute brokenness better. Right now it looks like a minor bug that affects 8 people. But it's totally broken for us, and if it's released in this state the floodgates will open.

@unknown: You can't decide for others what looks best. I even have a hard time deciding for myself. F11 interpolates pixels, ⤢ just doubles them and kills a few pixels in the corners. Both have pros and cons. But for the time being, definitely use the one that isn't broken.

@unknown: Performance is the same for me.

Yeah, I'm definitely with @unknown that performance isn't difference with the OS X fullscreen, However I do ask why you would prefer what to me looks blurry, over what is at least sharp.

Confirmed (for true MC fullscreen). I like @jonathan2520's suggestion to take advantage of the full-screen mode on 10.7+ (but that is a separate issue).

I tested with Oracle Java 1.8u11 and Apple's Java 1.6.

I can confirm on Java 7. To fix this, Just go to an earlier snapshot and exit full screen, then to go to fullscreen just use the mac fullscreen button, not minecrafts. Its still an issue though.

Same problem here... When in full screen mode on my MBP Retina, the screen only shows the lower 1/4th of the screen in minecraft. It is extremely annoying, and needs to be fixed.

John, have you tried using the native fullscreen with the double arrows?

This still has not been fixed in snapshot 14w31a.

Confirmed, this is still an issue in 14w32b
I am on Mac OS X 10.9.4 running Java 1.7.0_60
MacBook Pro Late-2013 with Retina display

I also test this in Java 1.6.0 and still had the same issue

Same bug for me. Still an issue in 14w32d running the latest versions of OSX and Java on a late 2013 MacBook Pro Retina.

Bug still there in 14w34a.

I cannot replicate this unless I force fullscreen while a world is loading (and that is not something we're about to fix).

Seems to touch only Macbook pro late 2013, and it's doing even i i don't force full screen and go to the option

I have the same issue, MacPro from early 2013.
I have windows 8 installed on a partition and the problem is not present there.

I also have the bug MC-62484, where my FPS goes bellow 10 when viewing the potions creative tab. But when I switch to the windows partition I get constant 60fps

Continues in 14w34a as well, to go full screen from the pause menu forces a zoomed resolution. if you use the machines full screen from the window its fine, its in game that forces the resolution zoom.

OSX 10.10 MBP Retina, 13inch Late 2013, java 8 update 20

I don't know if it's linked, but when I use the two arrow button to make it full screen I have two light blue banner appearing on the top and on the right. Don't know if you want a screen of that or not.

add 14w34b as well.

In reply to: [Mojang] Grum (Erik Broes)

As far as replicating the issue goes, no one has reported that specific scenario in order to encounter the issue, I encounter the issue as soon as I select full screen from the options menu. Zooming in while forcing full screen on world loading may be a separate bug. I'd advise trying on a retina macbook since the pixel density is different to what would be expected for that screen size. Specifically I am using the late 2013 15" model, but it does not appear to be limited to that machine according to the comments.

Grum, do you have a retina macbook or a normal macbook?

Retina mode is really crucial to this.

You don't need Retina hardware, though. You can also use Quartz Debug (install Xcode Graphics Tools) and enable HiDPI modes under the Window → UI Resolution menu. Log out and back in and select one of the HiDPI modes in System Preferences. It's annoying to work with on a non-Retina display (my 23" 1920x1200 monitor only offers 960x600 HiDPI which is rather crammed) but you can use it for testing. I have reproduced it this way on a machine that's otherwise totally non-Retina; only pixel densities that make it sensible are a hardware thing.

Note that Minecraft doesn't seem to keep track of resolution changes very well. To be safe, switch to the desired mode before starting Minecraft.

Reference: Enable High-Resolution Options on a Standard-Resolution Display

Grum, thanks for looking into this. This is not a trivial bug. You cannot play the snapshots in fullscreen, period.

To expand on my hardware; I have the 15" late 2013 MacBook Pro Retina with the dedicated GeForce GT 750M graphics card.

Johan, use the system fullscreen. It works fine.

Ok, that actually works. I might have to downgrade this to a trivial bug now. 🙂

Thanks!

The purpose of the following is to state the severity of the bug; not to blame, offend or be hostile to anyone mentioned, I appreciate your work on minecraft:

The 'final' snapshot has been released for 1.8 and this is still unresolved. It seems that now Grum has had a quick look into (unsuccessfully) replicating the bug, it will now go unresolved into the main release. Of course it's not difficult to work around the bug using the native fullscreen, however many users will have fullscreen enabled in-game. As a result, when they are auto-updated to the latest (1.8) release (provided they have a retina macbook), the game will launch directly into fullscreen and will appear unusable (once past the title screen, which for some reason this bug does not effect).

Since my snapshot resides in a different folder to the officially released minecraft (and I expect this applies to most users who reported this bug); it was easy to link the issue to fullscreen straight away, because it was not enabled before starting the game. (As explained) it's unlikely non-snapshot users will link the bug to fullscreen, and thus makes this a game breaking bug for such users.

To reiterate my point: any users who (have payed for the game), have a retina macbook and full screen enabled in-game will be unable to play after the official release, because the zooming makes the game completely unusable. This bug has a trivial fix, but is not a trivial bug.

and it continues in 14w34d.

It is a trivial bug. Just use the native fullscreen button.

I already know how to fix it, but unless you put that on the release notes there are going to be a lot of unhappy users.

Aidan, I agree with your statement that many who don't use the snapshots probably will encounter this bug as soon as 1.8 is released if it's not fixed before that. And they won't necessary link it to the fullscreen option.

@Ezekiel, it is not going to be clear to people just getting the 1.8 update that fullscreen is the issue and that native fullscreen is a viable option. Currently using Mac OS X native fullscreen is most likely not the common method for going fullscreen and is not clear in the interface how to use it. Using the F11 or custom hotkey is the more obvious and discussed method. That makes this bug nontrivial. New 1.8 users with retina displays, especially those who default to fullscreen as most do, will immediately encounter the bug and feel helpless in remedying the situation.

Spex, I'm working with Grum to find a solution, but fullscreen isn't unavailable, just getting to it by old methods doesn't work. Therefor trivial, so long as people are informed by some means.

@Ezekiel, sure, trivial if and only if users are clearly informed. Thank you.

Ezekiel, that is the first confirmation that the bug is actually being worked on that we've had. All other previous feedback from Mojang, and current information at the top of the page, indicates that the bug was not going to be fixed (including Grum's own comment). No one is complaining about the current situation, understandably it's a snapshot and things go wrong; however, up until that last comment it appeared no one was working on fixing this.

The fact no one appeared to be working, or gave indication of intent to work on it, was the main concern. Not the existence of the bug, we're all very well aware of how to use native fullscreen.

Thanks for the updated information 🙂

Fixed on 1.8 pre-release 1

Not fixed in 1.8-pre1.

well that's weird, first time I launched it, it was "fixed". After seeing your message I tried to relaunch the game to see, and the problem appear again :/

Are you sure you didn't just check the main menu or something? Was the display not in Retina mode? (although you'd think those who change it would know)

Couldn't figure out to reproduce the thing, but I'm sure it was working :/ I went into game, generate a few world, tried to enable/disable full screen, by F+11, menu and the native full screen and everything was working fine :/

1.8-pre1 the main title screen works nicely with the built-in fullscreen on a retina display, but all other menus and the game itself still have the resolution bug for me on a MacBook Pro late-2013 with retina display.

This includes trying to open the video options to get out of built-in fullscreen. Users who have this issue will not know what is causing the problem and may have trouble exiting the built-in fullscreen if they are not accustomed to hotkeys.

Behaviour unchanged in 1.8-pre2:
Full screen zooming/cropping still rendering game unusable throughout the game, with the exception of the title screen.

Bug still present in 1.8-pre 2 and also present on OS X 10.10 developer preview 6 (as well as on 10.9.x).

Can also confirm issue: 10.9.4, 1.8-pre2. Using the native fullscreen button does work, but I wasted quite a bit of time figuring that out.

Mojang: It would be great if you could DISABLE or REMAP the fullscreen button in the meantime on OSX retina until this bug is fixed.

I'm unconvinced that this could be considered trivial since it is an introduced behavior. Unless, in the end, this introduced behavior is completely transparent to the end user.
If it requires the same kind of discovery > work around path on release day you'll have an additional support burden. Simple making this invisible would be the prudent course of action.

It's seems to me that Mojang was able to make this work on retina displays before and therefor should be able to again.

Evan, take a look at LWJGL issue #83: https://github.com/LWJGL/lwjgl/issues/83