Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.31f1
2022.3.12f1
2023.1.18f1
2023.2.0b15
2023.3.0a11
6000.0.0b11
Issue ID
UUM-54436
Regression
No
GameObject that has a material with Alpha Clipping and Virtual Texturing becomes invisible when restarting the Editor
How to reproduce:
1. Open the attached “vt minimal repo.zip“ project
2. Open the “OutdoorsScene“ Scene
Expected result: The “MetalFence“ GameObject is visible
Actual result: The “MetalFence“ GameObject is invisible
Reproducible with: 2021.3.31f1, 2022.3.12f1, 2023.1.18f1, 2023.2.0b15, 2023.3.0a11
Reproducible on: macOS 14.0 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- The “MetalFence“ GameObject becomes visible again if the “AlphaClipping“ value of the GameObject’s material is updated (the value needs to be 1 or less for the GameObject to be visible)
- GameObject is also invisible in Builds
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
As a reminder, Streaming Virtual Texturing is currently marked as an experimental feature in documentation, but we greatly appreciate the feedback you provided. As a result of your feedback, we made plans to document this limitation more clearly in the user manual page for Streaming Virtual Texturing.
While investigating your report, we verified a potential workaround for this use case may give the behavior that is intended: using Streaming Virtual Texturing textures in materials that use alpha-clipping. The potential workaround is to create a custom MonoBehaviour that uses the (experimental) Streaming.RequestRegion API, then add this component on those object(s) using alpha-clipping with Streaming Virtual Texturing. Some sample code is already provided in the Scripting API documentation for that experimental C# API and can be used as a starting point to create your own script. For more info, see: https://docs.unity3d.com/ScriptReference/Rendering.VirtualTexturing.Streaming.RequestRegion.html
A different approach - where a monobehaviour toggles the Alpha Clip OFF to trigger texture streaming initially, then later toggles alpha clip ON for rendering - proved to have significant limitations when we tested it.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.