Search Issue Tracker
Fixed in 4.5.X
Votes
79
Found in
4.3.0f4
Issue ID
574965
Regression
Yes
Camera with image effects throws error when certain game view aspect ratios are used
To reproduce:
1. Create a camera with Clear Flags set to "Depth Only" or "Don't Clear"
2. Attach an image effect to the camera
3. Set the game window scale to 16:9
4. Enter game mode. Try resizing the game window
5. "rect[2] == rt->GetGLWidth() && rect[3] == rt->GetGLHeight()" appears in the console
Does not occur with version 4.2.2f1
Seems to be related mostly to the aspect ration of the game view and the image effects.
does not occur if game view is undocked
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
pojoih
Jan 05, 2014 17:06
same Problem here (16:9 gameview and active "Bloom" effect on Camera in Unity 4.3.2)
SkaredCreations
Jan 04, 2014 14:18
Please it's very annoying, it happens to me each second when the game window resolution is 16:9 or 4:3 probably depending on what post process effects attached to the camera. Having both game and editor windows displayed on the screen, this continuous print of debug info is making me crazy.
kylekaturn
Jan 03, 2014 08:27
Please fix this isuue.
John-Citizen
Jan 03, 2014 03:03
Getting the same issue.
masterprompt
Dec 04, 2013 22:11
The workaround doesn't work, please fix this
Mikkel-Gjoel990
Nov 27, 2013 14:39
So, my previous suggestion breaks the view when using the search-functionality that grays out the scene.
Saving the old rendertarget (RenderTexture prev_rt = RenderTexture.active; ) and restoring it after the final blit (RenderTexture.active = prev_rt; ) appears to be a functional workaround.
Mikkel-Gjoel990
Nov 26, 2013 17:54
Appears to be cause by Graphics.Blit() leaking state for rendertexture.active back to null.
Workaround: add RenderTexture.active = null;