Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.1.0a12
2019.1.0b3
Issue ID
1127310
Regression
No
B10G11R11 cannot be used a source for async readback
please ignore initial repro project and use TestReadback.zip attached later
*somewhere deep inside LWRP we decide to use this format for metal - this does not make this issue metal specific
Steps to reproduce:
1. open TestReadback scene and press play
Actual Result:
there may/will be asserts and errors. The most important part is that script attached to camera shows texture copy of RT - they will be very different (to make sure script make sense you can tweak it to use "saner" format)
*please note that you can freely ignore ValidateFormat error if that happens - it is simply logged (not an exception) and it happens because c#-side SystemInfo.IsFormatSupported is very weird
THE reason:
on all platforms AsyncReadback reads data from texture as is and then use ImageReference to do on-CPU conversion. ImageReference works strictly with TextureFormat and not all GraphicsFormat/RenderTextureFormat can be mapped to TextureFormat
please note that repro uses GraphicsFormat.B10G11R11_UFloatPack32 but it will be reproduced with RenderTextureFormat.RGB111110Float
hence i removed regression flag but i keep "first affected version" as i didnt bother to check that way back
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
- UI Toolkit 'background-size' property is not fully animatable
- Moving the Scrollbar via clicking no longer works after the first-click when page size is too small
- Elements in UI Builder Viewport are displayed incorrectly when Editor UI Scaling is set to 125%
- Prefab referencing a script is not shown in the Search window's Project tab when using "Find References In Project"
- Scroll view sensitivity remains unchanged when modifying the "--unity-metrics-single_line-height" value
Resolution Note (fix version 2019.2):
readback from RG11B10 is not supported. There is exception added in 2017.2 about that