Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0b6
Issue ID
838184
Regression
Yes
SpeedTree mesh is not properly created through a script when importing a project from 5.4 into 5.5+
Reproduction steps:
1. Download and and open the latest attached project (fogfiles link).
2. Open scene "TreeScene"
3. Look at the Gameobjects "DrawSpeedTree_LOD1" in the scene view, drawn with with DrawSpeedTree
4. Open the same project with 5.5+
5. Look at the same objects.
6. Notice how Meshes look
Added video of the problem in the last edit
Expected result: tree mesh is drawn normally
Actual result: the selected mesh is not drawn normally
Reproduced invalid import from 5.4.1p3 to 5.5.0b7, 5.4.1p3 to 5,6.0a1
Not reproduced when importing back and forth on versions 5.4.1p3-->5.3.6f1, 5.4.1p3-->5.2.3f1
Note: new project added from 838946
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment