Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.37f1
2022.3.26f1
2023.2.20f1
6000.0.0f1
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-70711
Regression
No
GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
How to reproduce:
1. Open the “Deferred-Render-Target.zip“ project
2. Open the “DeferredViewportBug“ Scene
3. Open the Game View tab
4. Observe the image rendered on the Quad GameObject
Expected results: The image of the white GameObject projected onto the Quad is similar to the other GameObjects projected
Actual results: The image of the white GameObject projected onto the Quad is skewed
Reproducible in: 2021.3.37f1, 2022.3.26f1, 2023.2.20f1, 6000.0.0f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: macOS Sonoma 14.4.1, no other environment tested
Note: If the Render Queue of the Material “forward only“ is set to anything over 2500, it will be projected onto the Quad normally
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.
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.