Search Issue Tracker
Won't Fix
Votes
3
Found in
2018.3.6f1
2019.1.0b4
2019.2.0a6
Issue ID
1130496
Regression
Yes
[SpeedTree] Reference changes when upgrading to 2019.1.0b4 and later
Steps to reproduce:
1. Open original project "SpeedTreeRepro.zip" in 2018.3
2 Select the GameObject called "Model" from the Hierarchy view
3. Look at the Inspector and take note the "Model" property points to "TallAdler_01"
4. Open the project in 2019.1.0b4 and select the GameObject "Model" again
Expectes result: "Model" reference is "TallAdler_01"
Actual result: "Model" property points to "CollisionObject0"
Reproduced in: 2019.1.0b4, 2019.2.0b5, 2019.2.0a6
Not reproduced in: 2019.1.0b3, 2019.2.0a5
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
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
- Outdated documentation page is linked when clicking on the Help icon for "Virtual Texturing" Module in Profiler Window
- [Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
- Bounding Box Size of Light Probe Proxy Volume and Settings.Max Interaction Distance of Panel Input Configuration Components cannot be added as Properties in Animation window
Resolution Note (2020.2.X):
Unfortunately this is not fixable, without introducing other bugs in more recent versions. We think it would be better to just leave it as is.