Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.6.X, 2017.1.X
Votes
0
Found in
2017.1.0f3
Issue ID
949574
Regression
Yes
[PLM] Progressive Lightmapper crashes with transparent shader (render queue = 3000)
Steps for reproduction:
1) Download project `AreaLightCrash` below
2) Open the scene `Skybox`
3) Generate the lighting
4) Observe the crash
Notes:
- Issue became noticeable when new light modes feature for Progressive Lightmapper is merged (introduced in 2017.3.0a5)
- Before 2017.3.0a5, editor didn't crash but baking process used to get stall for awhile but it always managed to finish baking successfully
- Re-authoring normals of the mesh in a DCC package resolves the issue
- Re-calculating the normals in Unity editor and changing `pushoff` parameter of the custom lightmap parameter resolves the issue (no more crash)
- Crash doesn't occur when standard shader is assigned to GameObject called "NightRoom_Skybox"
- Crash doesn't occur when another type of light is used in place of area light
- Crash only occurs when `Lightmap Resolution` is equal or higher than 19
- Crash is not related to `View Prioritization`, issue occurs regardless of this option
- Crash occurs regardless of supersampling
- Issue is not related to directional lightmaps
- Issue is not related to backface tolerance
- Workaround solution is to change the render queue of a transparent shader from 3000 to another value
Comments (1)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
BradZoob
May 16, 2019 03:30
Thanks immensely for this, by extending the standard shader in Unity 2019+ i was able to set the queue to 3100 for materials using transparent rendering and my lightmapper crashes ceased and finally it actually completes on those halted rendering jobs, no longer taking 6 hours to do nothing.