Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.5f1
Issue ID
1051448
Regression
No
Capsule Collider created in SpeedTree Editor differs in Unity Editor
When you import a Tree from SpeedTree Editor, the size of the Capsule Collider in Unity Editor does not match the size in the SpeedTree Editor
To reproduce:
1. Open SpeedTree Editor, create Tree and export it
2. Open Unity and create a new project
3. When the project loads up import created Tree
4. Compare created Tree Capsule Collider in SpeedTree and Unity
Expected results: The size of the Capsule Collider in Unity does match the size in the SpeedTree Editor
Actual results: The size of the Capsule Collider in Unity does not match the size in the SpeedTree Editor
Notes:
- This issue appears on both Windows and OSX
- The User has attached the patch to fix this issue
- Photos of Capsule Collider in SpeedTree Editor and Unity is shared in Comments section
- The Tree model is shared in Comments section
Reproduced on Unity 2017.2.3p3, 2017.3.2f1, 2017.4.8f1, 2018.1.9f1, 2018.2.2f1 and 2018.3.0a7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment