Search Issue Tracker
Fixed in 5.6.0f3
Fixed in 5.6.X
Votes
0
Found in
5.6.0f3
Issue ID
898302
Regression
Yes
Deferred camera throws an error with RenderTextures if the viewport is not set to default size
Steps to reproduce:
1. Open attached project
2. Open "test" scene
3. Notice the "Dimensions of color surface does not match dimensions of depth surface" in the error field
Expected result: Deferred camera should not throw a "Dimensions of color surface does not match dimensions of depth surface" when a RenderTexture is used
Note: This seems to happen only when rendering path is set to deferred and "viewport rect" values are changed
Reproduced in: 2017.1.0a6, 5.6.0f3, 5.6.0b1, 5.6.0a1
Not reproduced in: 5.5.3f1, 5.4.4p4
Regression since: 5.6.0a1
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
nielsdielen
Jun 18, 2020 13:53
I had the same error in Unity 2018.3.2f1 and it went away when I disabled some of the GVR prefabs I had in the scene from the Google Cardboard sdk. In particular I turned off the following:
- GvrBetaHeadset
- GvrControllerMain
- GvrInstantPreview
Hope this helps anybody,
Regards,
Niels
drcrck
Dec 23, 2018 18:57
It's NOT fixed + writing to disk every frame is not just annoying.
jite
Oct 09, 2018 15:32
Same in 2018.2.10f1
squirrelboy1225
Sep 21, 2018 05:56
Getting this on 2018.2.2f1 consistently. No issues, just annoying and fills the entire console continuously.
N1warhead
Jan 25, 2018 16:46
I am getting this error in 2017.3.0f3. Doesn't seem to be causing issues, just annoying.