Search Issue Tracker
Duplicate
Votes
0
Found in
2019.3.0a12
2019.4.4f1
2020.1
2020.2
Issue ID
1265258
Regression
No
Old additive scene Light Probe data is used after calling LightProbes.Tetrahedralize in a new additive Scene
How to reproduce:
1. Open user-submitted project (FailureToTetrahedralizeProbesCausesStickRepro.zip)
2. Open the Boot scene and enter Play Mode
3. Click 'Load Setup 1' button
4. Click 'Unload Setup' button
5. Click 'Load Setup 2' button
Expected result: Light Probe data from Setup 2 is used
Actual result: Light Probe data from Setup 1 is used
Reproducible with: 2019.3.0a12, 2019.4.5f1, 2020.1.0f1, 2020.2.0a19
Could not test with: 2018.4.25f1, 2019.3.0a11(Light Probes do not contain a definition for Tetrahedralize)
Notes:
Tetrahedralize is automatically called by the scene loading code once the scene has loaded
Workaround: click the 'Tetrahedralize' button before step 5, after unloading the first setup
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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
This is a duplicate of issue #1244629