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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- 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
This is a duplicate of issue #1244629