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
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
- Standalone Profiler stays in Dark Theme after switching Editor theme to Light on Ubuntu
- Inconsistency in capitalisation and styling across various nodes and block in VFX Graph
- Package Manager Select all keyboard shortcut selects all packages even if they’re not visible to the user when the Package Manager has no search results and the shortcut is pressed
This is a duplicate of issue #1244629