Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.2.4f1
2023.3.0a19
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-59304
Regression
No
[HDRP][DynRes] Incorrect Shader Graph "Screen Position" node data when a Camera is using HDRP Dynamic Resolution
How to reproduce:
- Open the “UpsideDown.zip“ project
- Open the “OutdoorsScene“
- Observe the Game view
- Enable the “Main Camera“ in the Hierarchy window
- Observe the Game view
Expected results: When an HDRP Dynamic Resolution Camera is enabled the sample position is taken from the same position as a non-Dynamic Resolution Camera
Actual results: when an HDRP Dynamic Resolution Camera is enabled the sample position is taken from a different position than a non-Dynamic Resolution Camera
Reproducible in: 2023.2.4f1, 2023.3.0a19
Could not test in: 2021.3.33f1, 2022.3.16f1 (unsolvable missing material)
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
Note: When changing the size of the Game window, sometimes the Shader Graph output glitches out as well.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.
Resolution Note:
_