Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
Issue ID
1054313
Regression
No
[MacOS] Standalone Player crashes at launch when the width / height is set to 0.
When the Standalone Player width / height is set to 0, the Player crashes at launch.
Due to the Screenmanager info is saved in the file named in Bundle Identifier, and the setting does not update automatically when create new project. Several projects can end up sharing the same .plist file.
If one of them set the Player height/width to 0, it affects all other projects with the default Bundle Identifier settings, creating the illusion that "all projects crash at launch."
Repro step:
1. Open 2018.2.0b11 Unity Build with an existing project or create a new one.
2. Build the standalone player with height/width set to 0.
3. Launch the built Player.
It seems the crash has nothing to do with the Player Settings.
Though it crashes for both Metal and OpenGL Graphic APIs, it crashes for different reasons.
More information will be in the comment sections for better separation.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment