Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
1
Found in
6000.0.54f1
6000.1.13f1
6000.2.0b11
6000.3.0a3
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-112554
Regression
Yes
GameObject becomes invisible when using Built-in Render Pipeline with DirectX12
Reproduction steps:
1. Open the attached project “ReproProject“
2. Open the scene “Report“
3. Connect the VR headset to the PC (for example, connect Meta Quest Headset using Link)
4. Enter into the Play Mode with the headset on
5. Observe the result in the headset
Expected result: A cube in the front can be seen
Actual result: A cube can’t be seen
NOTE: The issue is reproducible via MockHMD (no Quest3 required). You only need to put MockHMD in single-pass instanced mode and you're good to go. This also means it's no longer a DX12+Linked mode issue, it's a DX12+single-pass instanced issue. It also makes it more likely that it's a problem with the DX12 code itself, and not related to Oculus/Quest specific code.
Reproducible in: 6000.0.50f1, 6000.0.54f1, 6000.1.13f1, 6000.2.0b11, 6000.3.0a3
Could not test with: 2023.2.0a12, 6000.0.49f1 (the view is corrupted and it is not possible to visually confirm that the issue reproduces)
Not reproducible in: 2023.2.0a11
Reproducible on: Windows 11
Not reproducible in: No other environments tested
Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
- The issue is reproducible in Player for Windows and Meta Quest as well
- The issue is reproducible with OpenXR and Oculus plugins
- When trying to reproduce with Vulkan, the view becomes corrupted and it is not possible to visually confirm that the issue reproduces on any version of the editor
- The issue is not reproducible with DirectX11
- The issue is not reproducible with Universal Render Pipeline
- The issue is not limited to a cube. The issue is also reproducible with different shapes of 3D objects, light sources, terrain
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment