Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
2022.3.64f1
6000.0.53f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
6000.5.0a1
Issue ID
UUM-111061
Regression
No
Crash when reimporting fbx asset used as tree by specific Terrain component
How to reproduce:
1. Open the attached “IN-103806.zip” project
2. Open the “SampleScene”
3. Move the Scene View camera closer to the “Terrain” GameObject so that trees are visible
4. Reimport “Objects/Trees/tree01_LOD.fbx”
5. Observe the crash
Reproducible in: 2022.2.0a1, 2022.3.64f1, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
First few lines of stacktrace:
{noformat}UnityEngine.Rendering.ScriptableRenderContext:Internal_Cull_Injected <0x00097>
UnityEngine.Rendering.ScriptableRenderContext:Internal_Cull <0x0002a>
UnityEngine.Rendering.ScriptableRenderContext:Cull <0x0009a>
UnityEngine.Rendering.Universal.UniversalRenderPipeline:RenderSingleCamera <0x0089a>{noformat}
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.