Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.3.2p1
Issue ID
766027
Regression
Yes
[Camera][VR]When near clipping plane is set to "0.01" camera does not render object in split-screen view
Steps to reproduce:
1. Open attached project.
2. Open scene named "main".
3. Press play button in the Editor.
4. Select game object "Main Camera".
5. Notice that camera's near clipping plane is set to "0.01" and game object named "Cube" is not rendered in the split-screen view.
6. Still in the play mode, in "Inspector" window increase the value of near clipping plane to "0.02".
7. Notice that game object named "Cube" appears in the split-scene view.
Expected result:
Setting near clipping plane to "0.01" (the minimum value) when using split-screen should not make game objects disappear.
Actual result:
When near clipping value is minimal, some visible game objects disappears from split-screen view.
Reproduced with:
5.2.4f1, 5.3.1f1, 5.3.2p1, 5.3.4f1, 5.3.4p3, 5.4.0b1.
Cannot reproduce with:
5.1.0f3.
5.4.0b14, because "VRDeviceType is deprecated".
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