Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2019.1.0b2
2019.1.0b3
Issue ID
1127298
Regression
Yes
Lightmapper crash after runtime error pop up
Updating a project from 2018.3.5f1 to 2019.1.0b2 i get a crash when trying switching to CPU progressive lightmapper
Updated Repo
- Clone the project
- Open and upgrade to 2019.1.0b2.
- Open the scene Mainscene_DayLight
- Select Map_2 all the way down to Map_10_arounds and hide the geomtery.
- Once scene opens access the lighting palette.
- Enable Lighting Mode Shadowmask
- Enable mixed lighting Baked Global Illumination
- Switch lightmapper to CPU progressive
- A Run time error pop up will appear.
- Click OK
Notice issue >> Unity shuts down.
No crash reporter. I don't see anything in the log other than console warnings.
Video and log attached.
Tested:
Broken: 2019.1.0b2, 2019.1.0b3, 2019.1.0b4, 2019.2.0a3
Working: 2018.3.5f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
BradZoob
May 14, 2019 09:24
Jesus even the bug reporters bugged, LOL. stalls at 50%, stopped it compressed the projected, still stalls at 50% regardless. Nice.
BradZoob
May 14, 2019 08:50
Why is this resolved, this is not fixed? fresh project folder with large model on it's way in debug report.