Anyone else experiencing the “Blank Game View” feature in 5.4? Only happens when the new scale slider is set above 1x. It generally doesn’t happen when first running the game, but just randomly blanks out while running. If you un-maximize and re-maximize the Game window, it comes back again.
Also getting lots of weird stuff like this happening in the interface quite frequently.
The first issue you’re seeing is known and we’re working on a fix now.
The second issue is different, I believe. We don’t have any reports of this, but like @orb mentioned, interesting to know if you’re on a Sierra build of macOS.
I too am experiencing the first issue – often times it seems I’m able to get the game display to work again by switching from Game view to Scene View (or even Asset Store) and back again. I have not experienced the second issue at all.
I’m on OSX 10.11.6 (El Capitan). Definitely looking forward to a fix for the first issue, though!
Any idea when this might be fixed? Or perhaps any idea what’s causing it – if it’s certain/specific code that’s triggering it I’d be more than happy to work around it in the meantime if that’s possible?
Accidentally started a duplicate thread on this issue (even searched for similar threads first—oh well).
To add to the descriptions of the problem, I’ve noticed that some time after refreshing the window to get the Game view back, graphical glitches appear all over the Editor, and I will sometimes have problems selecting objects in the Hierarchy. The only real solution is to quit and reopen Unity, which I do multiple times per day.
I have the same problem sometimes black game view sometimes graphical glitches (on OSX 10.11.04), could be in conjunction with the Unity remote 5 , but that is just a guess.
Yeah, I’m getting it to on OSX 10.11 and I just happened to be doing a screencast when the last one happened http://xiotex-studios.com/UnityBug822112.mp4 my slider is set exactly at 1x.
I have reported in other threads, since this one seems to be the main one now, Yes I experienced issue #1 about once a day at random times and it seems thats its now being worked on. I have experienced issue #2 but only during a build process, my game window (which is on a 2nd monitor and viewable a100% of the time) will glitch out like this, but when the build process ends, it fixes itself. This one I don’t worry about as it never hits me during gameplay. MacOS 10.11.6 Late 2013 iMac i7.
Any chance that you’ve (Unity Technologies) perhaps at least dialed in on what might be causing this? I’d be more than happy to spend some time trying to change our code a bit to work around it if I had a decent lead on where to perhaps begin looking.
As much as I love (truly couldn’t be more pleased with) the high-DPI support that 5.4 brings, this bug is really driving me up the wall. I’m currently restarting Unity >10 times per day because of it (often just switching views fixes it; but in some cases I even lose the view buttons which requires me to fully restart Unity).
My lead engineer, running same project & same version of Unity, but via a new iMac (vs my Mac Pro) – is reporting that he’s rarely getting the issue, reportedly <1x per day – I’m jealous of him… Frustrating! Keeping my fingers crossed though!
I made a custom layout with the windows all like I want them. When my Game window goes blank while in Play mode, I just reset my layout to that custom layout and it resets my blank window back to normal, even if Im in Play Mode I don’t have to stop the game. I don’t like it either, yesterday I had it go blank every 20 min or so. Very frustrating. But I didn’t have to reboot Unity.
Unfortunately, still nothing to report. We’re actively trying to isolate the bug, but it isn’t straightforward. We’re only very rarely able to reproduce it, which is significantly slowing things down. If anyone happens to find a more reliable way to reproduce this, it would be a big help.
I tried many things and its just so random I haven’t been able to see any cause and effect situation yet. Is this related to the old OpenGL issue coming back for certain video cards?
I wrote an Automator script that booted up Unity with an older version of OpenGL, I will run that again and see if it stays away. Im now running on OpenGL 2.1 depreciated. That was the last work around.
Thanks for your help people! As the bug seems to be very rarely reproducing on our end, it’ll be very helpful to hear if it still happens when running on old OpenGL. Another thing that would give us some hints is if you could start the editor with -force-gfx-direct flag and tell us if that affects the issue.