Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.39f1
6000.0.12f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-77381
Regression
No
Incorrect ZTest when using a Custom Shader for non-Standalone Target Platforms
Reproduction steps:
1. Open the attached “RimLightBug.zip“ project
2. Make sure that a non-Standalone platform is selected (File > Build Settings…)
3. Enter Play mode and observe the Game window
Expected result: Nothing of note happens
Actual result: Rim Light of a cabinet GameObject is visible on the table GameObject
Reproducible with: 2022.3.39f1, 6000.0.12f1
Could not test with: 2021.3.41f1 (Due to cabinet GameObject not being fully rendered after fixing errors in the Console)
Reproduced on: macOS Sonoma 14.5 (Intel), Windows 10 (by the user)
Notes:
- Issue is reproducible on Android, iOS and WebGL platforms in the Editor and in Player
- Issue is not reproducible on Standalone platform
Comments (1)
-
jennie258fitz
Aug 05, 2024 06:42
Thanks for sharing this useful information
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
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.
In this specific case we are pleased to confirm the workaround was able to resolve the issue.
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.