Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
942282
Regression
Yes
Parts of mesh are always rendered on top when they shouldn't be when the Rendering Mode is set to Transparent in Standard shader
The issue seems to happen when you create a model that has parts of it that are not connected to the main mesh, but are still considered as part of the mesh (for example, when a primitive is created while being in edit mode in Blender).
To reproduce:
1. Open the project, attached by the tester (multiMeshRendering.zip)
2. Open the "scene" scene
3. Select cubeFBX game object in the Hierarchy
4. In the Inspector, in the Material section change Rendering Mode to Transparent
Expected: changing Rendering Mode to Transparent on a standard shader doesn't make parts of the mesh to always render on top of other parts of the mesh
Reproduced in 5.6.0a1, 5.6.3p3, 2017.1.0f3, 2017.1.1p1, 2017.2.0b11, 2017.3.0a7
Did not reproduce in 5.5.4p2
Regression introduced in 5.6.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "DateTime.Now" in the UK timezone does not adjust when the British Summer Time is active
- "Unsupported source texture format (7) in ComputeNextMipLevel" error is shown and the texture atlas is corrupted when the texture format "RGB Compressed ETC2 4bits" is selected
- HDRP Graphics "High Quality Line Rendering" is missing a documentation link
- HDRP Graphics "Screen Space Global Illumination" has a link to a wrong documentation
- OnParticleUpdateJobScheduled is never called when using ParticleSystem.Simulate() in FixedUpdate()
Add comment