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
- White lighting artifact when a point light with a small emission range and "Hard Shadows" touches an object while a directional light with "Soft Shadows" and another point light are present
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
This is a duplicate of issue #616105