Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.2.X
Votes
0
Found in
2018.2.0b8
2018.2.0b10
Issue ID
1054584
Regression
Yes
A default UFPS scene crashes Standalone player when an object is instantiated
To reproduce:
1. Download attached project from the link and open in Unity
2. Open "UFPS_CleanScene" scene
3. Enter Play mode
4. Wait till player drops on the ground and observe that Unity does not crash
5. Exit Play mode
6. Build and Run project
7. Wait till player drops on the ground
Expected result: After the player drops on the ground, Unity standalone does not crash
Actual result: After the player drops on the ground, Unity standalone crashes
Notes:
- This issue reproduces on both Windows and OSX standalone
- A stack trace is shared in Comments section
- Could not check on Unity 2018.3 because project becomes corrupted
Reproduced on Unity 2018.2.0b8 and 2018.2.0f1
Not reproduced on Unity 2018.1.7f1 and 2018.2.0b7
Regression on Unity 2018.2.0b8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment