Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
4.2.0b5
Issue ID
547988
Regression
No
[LOD] Confusing renderer preview on LOD group if multiple renderer components are assigned to same GO
- Create a Cube and add a Particle System and a Line Renderer component to it.
- Add this Cube as a Renderer in a LOD Group. Notice that3 previews show up and all of them show a cube mesh preview
- Add a Particle System or a Line Renderer component to an Empty GO and add that to the LOD Group. Notice instead of a preview you get a text saying Line Renderer or ParticleSystem Renderer, etc.
I think that when adding an object that has more than one type of renderer component attached to it to a LOD group, we should display a graphical representation of what is on the MeshRenderer and for all the other kinds of Renderer components we should get the textual info in the preview box.
See attached screenshot for LOD Group setup like I just described
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
Add comment