Search Issue Tracker
Duplicate
Votes
0
Found in
4.1.1f1
Issue ID
532208
Regression
No
CameraDepthNormalsTexture filtering changes, causing decoding issues
Steps to reproduce :
- import the project
- set the game view at 1024x768
- open the scene "DebugDepthNormals"
- note that Camera0 renders to the left half of the screen, Camera1 to the other
- verify that the rightmost half of the screen looks like ProjectFolder/Screenshots/step1.PNG
- select Camera1 and click "Raw Depth". Verify that the rightmost half looks like step2.PNG, uncheck "Raw Depth" after this.
- select Camera0 and click "Get Temp RT". Verify rightmost half against step3.PNG. Scary part is changing settings on Camera0 affects Camera1
- select Camera1 and check "Raw Depth". Verify rightmost half against step4.PNG -notice the bilinear-filtering thing horizontally.
- re-open scene without saving. Select Camera0 and verify that checking the "HDR"-checkbox on Camera0 will have the same effect on Camera1.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #616105