Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.6f1
2020.1.0a19
2020.1.0a21
Issue ID
1217364
Regression
Yes
"ReadPixels" errors appear when modifying a directional light with a realtime reflection probe
Steps to reproduce:
1. Open user-supplied project
2. Rotate the Directional Light
Expected: no errors in the Console window
Actual: "D3D11 unsupported ReadPixels destination texture format (6)" errors appear in the console
Reproduced in: 2020.1.0a19, 2020.1.0a21
Not reproduced in: 2018.4.17f1, 2019.2.21f1, 2019.3.1f1, 2020.1.0a1, 2020.1.0a18
Comments (8)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
UNDERHILL
Oct 18, 2020 05:24
I get this error in 2019.4.12f when using the nvidia flex water tutorial in my scene.
AydinDeveloper
May 22, 2020 14:43
HDRP is also OK. To bake a HDR reflection probe in URP, set the desktop graphics API to Vulkan.
onurerler
May 21, 2020 13:37
Same here. Still getting error 2019.3.14f1.
Emanx140
May 21, 2020 05:36
Still getting error 2019.3.14f1.
The workaround is to disable HDR on the probe.
user099
May 13, 2020 14:47
Still happening in 2019.3.13f1
Rafael_Costa
May 06, 2020 10:54
Same here, still happening in 2019.3.11f1.
jemca
May 01, 2020 03:27
"I get this error in 2019.3.11f1." same issue
AydinDeveloper
Apr 26, 2020 21:16
I get this error in 2019.3.11f1.