Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.0f2
Issue ID
1048024
Regression
No
HandleUtility.ApplyWireMaterial(); does not contain Handles.zTest in DotHandleCap method(source code)
To reproduce:
1. Open users attached project "zTest.zip"
2. Open "SampleScene.unity" scene
3. Move the blue cube around
4. Observe as one of the white points is visible through the cube
Expected result: both points are not visible through the cube
Actual result: the point that is using Handles.DotCap function which is obsolete is not visible (correct), but the one with the new function Handles.DotHandleCap can be seen through the cube (incorrect)
Reproduced on:
2017.2.3p1 2017.3.2f1 2017.4.6f1 2018.1.7f1 2018.2.0b11 2018.3.0a3
Notes:
The user has found in the source code that DotCap uses the zTest : HandleUtility.ApplyWireMaterial(Handles.zTest);
And DotHandleCap does not use the zTest: HandleUtility.ApplyWireMaterial();
More info: https://forum.unity.com/threads/handles-dothandlecap-ztest-issue.535437/
---
Fixed in 20018.3a06.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash after the “State comes from an incompatible keyword space“ log when opening the project
- [Android] GameObject are not rendered at all or rendered black when in the custom shader “multi_compile_instancing“ is enabled with two “float4” instance properties are present on older devices
- LineRenderer.BakeMesh generates a box-shaped MeshCollider when the camera's Y-axis rotation is in a specific range
- Different build sizes between Editor build and command-line build when "Static Batching" is enabled
- Particle System "Start Rotation" property affects a different axis when upgrading to newer Editor versions
Add comment