Search Issue Tracker
Fixed in 5.2.0
Votes
16
Found in
5.0.0f4
Issue ID
681089
Regression
No
[Texture2D] Texture2D.ReadPixels() fails if RenderTexture has anti-aliasing set
There is a camera which renders to a RenderTexture. If this RenderTexture has anti-aliasing set Texture2D.ReadPixels results into an empty texture.
How to reproduce:
1. Open Main.scene in the attached project
2. Press buttons
One of the buttons uses an anti-aliased RenderTexture, another one uses a nonanti-aliased RenderTexture.
The first one fails to be captured into another Texture2D.
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
- "Custom Render Queue" field cannot be set above "2000" when changing it in the Inspector window using Debug mode
- "Preloaded Assets" list is empty when Player is built
- Input.GetKey() does not register key release when a specific key is pressed, and then released after opening a context menu
- Overlay Canvas is not visible when the Anti-aliasing field is set to FXAA and the Full Screen Pass Renderer Features’s Injection Point is set to “After Rendering Post Processing”
- The Particle System doesn't work when played through ContextMenu
KevKevOnFire
Sep 12, 2016 15:35
I am still seeing this issue in 5.4.0 when passing a the resulting texture2D into a shader
mpgholden
Aug 27, 2015 19:23
This happens in 4.6 as well, and is a pretty big issue for Gear VR developers. Gear VR games crash on 4.6 when running in GLES 3.0 unless all eye texture anti aliasing is disabled. Only current option is to run in GLES 2.0 mode, which forces us to texture compression that makes me cry :(
ngothanhtai
Apr 09, 2015 07:01
To me, this problem just happened with OS X, works fine on Windows.
PNordlund
Apr 02, 2015 06:11
Amazingly, I get this too.
leokrzewina
Apr 01, 2015 18:59
This happened in Unity 4 as well.