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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
- [Editor] Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
Add comment