I thought a3 would fix this issue where double clicking on the [Game] tab to make it full screen woudn’t crash the editor ie it just locks up, and coming out of playmode would be instant, it seems coming out of playmode in both a2/a3 that I’ve tested result is an awfully long wait.. even longer if there was an error in the console imo.
wondering if this is just me/my test project or anyone else noticed the same with this 6.7alpha
is that on windows pc?
why yes it is… .
haven’t seen that issue myself.. (dx12)
well that’s not good, so just me then
Check if this also happens when you use the three-dots menu and choose “maximize”. I think that’s functionally the same behaviour. If this also freezes, try switching to a different Graphics API (Vulkan, DX11) in Player settings.
If it doesn’t crash, and this max size window is what you mean by “fullscreen”, then the crash may be due to the editor Windows - in that case Layouts => Reset All Layouts may fix the issue (like layouts themselves, any layout-specific issue carries over between Unity versions!). A less brutal tryfix is the Windows menu, I think there’s now a “Close hidden windows” feature which is used to clean up editor windows that have 0 size or moved off-screen but still technically exist.
If the graphics API fixes it, you have a system-specific issue with DX12 which can cause all sorts of issues and DX12 woes are all over the place. Updating graphics driver and resetting the driver to firmware defaults may help. There’s also Windows (11) settings that can affect this behaviour, specifically GPU task scheduling and Game enhancements (turn both off).
If the system is a Laptop that can dynamically switch between integrated and discrete GPUs, try forcing the editor to always use the discrete GPU - there’s a tendency towards crashes when those switches occur in demanding applications.
I had another look with another test project using rabbit demo project
Double clicking [Game] tab
And on the other test project, the same issue but the wait for game view enlarged to show anything takes even longer like 25seconds before it shows … originally this was the test project when I reported this issue crashing because if there was an error in console it would take ages to come out of playmode and I had seen crashes on a2, now in a3 it seems like it works just takes ages.
clearly something wrong as none of these issues happen on previous editor versions.
a4 still bad, going into full screen game window takes ages and coming out playmode takes ages, kinda broken really
Have you filed anything via the Bug Reporter? If so, can you share the incident number?
If you haven’t, please do so - the Bug Reporter will gather logs and system information that might help us diagnose the problem.
It is here: CASE IN-150997
I just tried 6.6b7 and that has the same problems reported here… only worse, going into fullscreen just takes even longer to complete, and 2mins later trying to end playmode and was just stuck.
Can’t remember the last 6.6 version I tried but it was an alpha/beta and don’t recall this happening.
And now I’ve tested 6.6a7 (the last alpha version before beta 6.6 and that works fine)
so somewhere between b1 and b7 on 6.6 +upto 6.7a4 this all got messed up.
upto 6.6a7 works
upgrading to 6.6b1 breaks, and then reverting back from 6.6b1 to 6.6a7, the manifest.json version differences
yet remains broken from reverting back, until I reset the UI Layout… then the issues reported here go away and its fine again.
Something at the start of 6.6.b1 broke things, resetting the UI layout in that version or 6.7a4 does nothing to fix it except mess up my layout.
So tested same test project on 6.7a4 on a macbook now and same issues 
seems like 6.6a7 is the last version things worked on
Worth pointing out: downgrading projects is not supported and may break things. At the very least you should delete all temporary files eg the Library and Obj folders at least to ensure there’s not going to be issues due to serialization format changes.
Upgrading may also update packages automatically but they may not get downgraded again, leaving the project with a different set of package versions as before and possibly incompatible package versions for the given Unity version. The manifest diff is telling.
Try creating a blank project in 6.6 beta, then export your existing project (select all scenes, this pulls in the dependencies) as .unitypackage and import that into the new project. That way you avoid carrying old baggage or misaligned package versions around. In principle, if all things are fine within the project it should continue to work after export/import and making any necessary settings adjustments (tags, layers, time, physics matrix, ..).
It would help to see if a blank version has the issue, and if not, if the issue appears after importing most of your project’s contents into the blank project.
yeah other than resetting the manifest.json version, the library wasn’t deleted, however the issue seems to only be apparent on 6.6b1 onward (I haven’t tested every editor version upto 6.7a4 but I have tested a number of them including other machines now)
I’m sure I could reset the library folder and results would be the same, 6.6a7 below would be fine, and every on from that would not.
No errors just very sluggish times taken to gointo full screen mode, and to come out of playmode (ironically if you go into fullscreen mode and then exit playmode it exits out without delay fine, but already waited like 30s or more for it to not be locked up before going into a fullscreen on my own test project, it’s all just very weird)
The blank project was tested with the 2d rabbit demo that came out recently on 6.7a3,
I’ve tested again with 6.6a7, with deep profiling and going into fullscreen no issue, like highest editor delay was like 130ms..
yet upgrading it (with deleted library folder, shouldn’t be an issue in upgrading)
and deep profiling going into fullscreen longer than 3 seconds imo and clearly showing high spike in the editor.
these lock up times are higher in the other test project.
so it is the new hierarchy causing all the problems… I can’t go back to previous one
going full screen with hierarchy attached triggers this problem, detaching the hierarchy and going fullscreen lets you go fullscreen without delay though, but coming out of playmode still triggers the same problem regardless.
just not having the hierarchy open at all ever also works.. if you can do anything without a hierarchy.
A new project made with 6.7a4 juts has bunny blitz imported no other imports/extensions
detached hierarchy and just coming out of playmode:
@sebastienlh I’m not sure how no one else has this issue at all, the more scene stuff in the hierarchy the slower it seems to be.
Hey @Player7, thanks for the thorough research going into your report. I’ve made the team aware and we will investigate this ASAP.
In the meantime, you can revert to the old hierarchy on a per-project basis from Project Settings > Editor at the bottom:
Edit: I am unable to repro locally (different project though, I wanted to do a quick sanity check with whatever non-trivial I had on hand). I’ve asked someone to come up with a repro, but we might have more questions for you.
Oh you can go back, for some reason I thought the option to go back was removed in these new versions, was only looking in the Preference>general though .. good to know, as indeed going back to the older one works without this slowness issue.
