Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
5
Found in
2022.2.0b3
Issue ID
UUM-2781
Regression
No
Unity Camera produces wrong pixel values in build when the Camera has a narrow Target texture
Reproduction steps:
1. Open the user's attached project
2. Open File > Build Settings
3. Add the open Scene to the build
4. Build and Run
5. Press Space
6. Open project directory > Build > SaveImage > "BlendTexture TestCameraTexture.png"
Expected result: Pixel colours in the saved image are correct
Actual result: Wrong pixel colours in the corner of the saved image
Reproduced with: 2019.4.36f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b5, 2022.2.0a3
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
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
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 (2022.2.X):
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.