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
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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
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.