Search Issue Tracker
By Design
Votes
0
Found in
2017.1.0f3
Issue ID
948147
Regression
Yes
RenderTexture gives wrong result when calculating area of the gameObject
Steps to reproduce:
1) Download attached project 'RenderTextureBug-5.6.0.zip' and open in Unity
2) Open scene 'Test' and press Play
3) Click on the Test button and check the Console window
Expected result: Value for the front should be 387 and for the back 6124 (check attached image 'expectedOutcome.png')
Actual result: Value for the front is 375 and for the back 6061 (check attached image 'actualOutcome.png')
Reproduced with:
5.6.0p4, 5.6.3p2, 2017.1.1f1, 2017.2.0b10, 2017.3.0a7
Not reproduced with:
5.6.0a1, 5.6.0p3
Regression since:
5.6.0p4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment