Bug Maximize on play not working

Hey! Thank you so much for fixing the Random Seed for Particle Systems in 5.4.1f1!

However, since I updated yesterday I the "maximize on play" feature of the Game tab isn't working anymore. It just stays like it is, no maximizing. Anyone experiencing the same issue? Can I do something to fix that?

 

So you are using 5.4.1f1? I don't experience that issue in 5.5.0b2.

 

Can confirm the issue on Ubuntu 16.04.1 with 5.5.0b2. The editor doesn't swap to a maximized view. Toggling it off and on again does nothing to get the desired behavior back either.

 

Maybe it's project-related? I don't experience the issue here either.
Could you submit a bug report with your project?

 

Can confirm this too on Ubuntu 16.04.1 64 Bit with 5.5.0b2. Just a simple basic 3d project. Nothing special, no additional assets

 

I can confirm it too, Ubuntu 16.04.1 64 bit with 5.4.1f1. The only way I can maximize is by pressing leftShift+Space when in play mode? (I don't know if leftShit+Space is a keyboard shortcut for maximizing the tab or not, but if it is, I think it should be disabled when in play session) . Also to add this behaviour happens sporadicly.

 

I am seeing this too on Ubuntu 16.04, latest Unity build. The editor has been running great overall these days, the effort is very much appreciated!

 

I found that it does it in both 5.5.0b2 &5.4.1f1 on Ubuntu 16.04. What fixed it for me was not using the maximize window button for the editor, instead resize it by dragging the window to fit the screen.

 

I was having the same problem but found if the Unity editor itself was not maximized then "Maximize on play" worked fine. If the Unity editor was maximized it didn't.
Mint 17 Cinn - unity 5.4.1f1

 

Can confirm what b-monkey says. Working fine when Editor is not maximized.

Arch 4.7.4-1 - Unity 5.4.1f1

 

Now I can confirm too the same issue when maximised.

 

Issue still exists in Unity 5.5.1f1.

 

Still have the issue in Unity 5.5.1xf1 - Ubuntu 16.04.2 LTS.

 

Also present in 5.5.3xf1 - Ubuntu 16.04.

 

I've got it on 2017.3.1f1 - Windows 10. The only custom change is I'm using the Experimental (.NET 4.6 Equivalent) Scripting Runtime Version (For the Azure SDK) but that shouldn't matter?

EDIT: Hum, seems to have fixed itself now. Was annoying whilst it was happening though.

 

Having this problem in 2019.4.19f1

Seems to work some of the time, haven't found a pattern yet.