A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Discussion in 'Editor & General Support' started by badbod99, Nov 12, 2013.
Getting this error spammed on the console in Unity 4.3 on certain projects.
Same here. Spams the console with:
rect == rt->GetGLWidth() rect == rt->GetGLHeight()
UPDATE: Fixed this. It was to do with a saved layout I had. I changed my window layout to one of the defaults and the error stopped.
UPDATE UPDATE: Is actually when any layout contains a game view with the aspect ratio set to 16:9 or 16:10
Seems like you can now manually set specifc resolutions in this tab, tried setting one up for 1600x900 and it still gives me the error. Basically, you can't letterbox the active game portion of the game window without getting that error.
ADDITIONAL : OK, some more messing around and: I CAN have a 16:9 ratio without getting the error, but I can't maximise the game window if I do (else it throws the error).
Found it is coming from the AntiAliasingAsPostEffect Image Effect on an Orthographic camera. Will raise a bug.
EDIT: Actually, you're right BRShins, it was the Layout. Strange that disabling the post effect stopped the error too.
EDIT 2: Error still occurs with 16:9 or 16:10 aspect (not with free aspect) game views. Disabling the AntiAliasingAsPostEffect makes the error go away.
EDIT 3: Recreated in a simple project. Orthographic Depth-Only camera with AntiAliasingAsPostEffect.
Same here. The camera is Perspective in my case, the rest is the same (Depth-Only with FSAA effect). I already reported the bug. I made a small test-scene: http://t.co/E3WiaWC2qV - if the error doesn't appear, just resize the Game view dynamically.
Hi, I am also having this error. Using a default layout DID work, but the problem is that I am developing for the Oculus Rift, and when I put the Game window on my extended display (the rift) I get the same error
"rect == rt->GetGLWidth() rect == rt->GetGLHeight()"
Destroys performance. I am also getting this bizarre error message:
"fence == expectedFence"
If I discover any fixes I will post them here
Yeah I am getting this error as well. I hope it is limited to the Editor?
I am having the same error on my Android project running in 16:10.
Also get this error, I don't think it's related to the AAPost effect specifically though, get it every time that:
- game window is set to anything but Free aspect, 5:4, or 3:2,
- some active camera is Depth Only or No Clear,
- and the same camera has a script on it that listens to OnRenderImage (even if method block is empty or a straight blit)
it is an Editor GUI error. Always get new ones with the new versions . But the game keep running anyway
I'm getting same error.
Narrowed it down to JS Image effects on main camera.
If I turn them off spaming stops.
EDIT: Reported this as a bug.
Same error here.
Valyard, could post a link to the bug report please ?
Apparently they got a coupleof the same bug reports so they closed mine.
same bug here, very annoying.
I confirm it comes from post-process effect on the camera.
Currently using those from the Unity's Standard Assets.
if I unable them, the console stops spamming
Still occurring in 4.3.1
Using 4.3.1, getting the same error.
Removing post processing effects gets around the problem, but this isn't much of a solution...
Still occuring for me, too. I "fixed" it by disabling anti-aliasing in quality settings.
Just started getting this today and it's quite annoying! Does anyone know if it happens in a deployed game?
Really, really annoying.
Doesn't stop, just keeps rolling out thousands of errors.
Vote for it here: http://issuetracker.unity3d.com/iss...r-throws-error-when-image-effects-are-applied
Ran in to this at work today. 16:9 editor viewport on the vignetting effect, possibly other effects too, I didn't notice until I turned on the console to work on some code.
In the editor, it's causing a pretty severe performance drop. Because I am making use of some platform specific functionality I am not able to create a proper desktop/windows build where I can check if this also has a performance drop there or if it's just an editor thing.
Can anyone verify this?
I'm playing with my own (very simple) image effects and getting the error. I'm thinking it has to do with the graphics card, is anybody having the problem on a Windows machine?
I'm running OS X 10.9.1, ATI Radeon HD 5870
I'm also seeing this in the profiler when it happens:
Have the same error on a 680 GTX. Been like this for months, seems to be caused by many different image effects and I think it 1st showed up in 4.3.0. For the time being I'm taking my maximized window and shrinking it just enough for the error to stop complaining. It is definitely causing huge performance drops as it is printing tens of errors each second.
Same error here. It's annoying, I really need those effects. I tried different effects: bloom, fisheye, color correction. They all give the same error and when I deploy to my iPhone the screen is plain black (except for my ngui elements).
For the folks who are asking if this is only happening in the editor, I did a simple test. I used:
and an external text logging system (http://www.valion-game.com/295/use-log4net-for-efficient-logging-in-unity3d/).
Then I type control-B to build and run my application outside the Unity editor. Looking over the log, I quickly determined that:
1. This is an ASSERT error. This probably doesn't matter much, but I figured I'd mention it.
2. It does NOT happen in a normal build. It's just happening in the Unity editor. There were no instances of the "rect == rt->GetGLWidth() rect == rt->GetGLHeight()" problem in my log file. When I run in the Unity editor I get them instantly and pretty much continually.
This probably explains why UT isn't so concerned about it.
EDIT: I only tested on PC Standalone. I see that some people are having problems on mobile deployments. Those problems may be unrelated, but I can't speak to that.
Like others here, I'm running into this problem in Unity 4.3.3 whenever I run a 4:3 aspect ratio using a screen overlay. It's causing problems on iPad, forcing me to remove the effect.
Why does the issue tracker claim this problem is fixed?
Same problem here. It happens to me in every aspect except for free aspect...
Actually I noticed that it will always happen when the letter box is vertical. Horizontal bars doesn't cause any errors..
It doesn't matter which ratio is selected. Free aspect will never cause the error because it'll always fill the entire game view.
I hope they re-open the issue, it definitely hasn't been fixed
The issue has actually been fixed, however at this point our Issue Tracker cannot differentiate between Fixed in released Unity version and Fixed in an upcoming release, this causes some confusion. The bug should be fixed with next non-minor released version of Unity. If you can reproduce it please send a new bug report.
Unity QA Team
Interesting, it started happening to me when I added the WaterPro to my project.
It happends if your game view is being scaled down. Try to set the game view resolution correctly, the problem should stop.
Thought I'd give you guys some insight on the issue.
This is an EDITOR ONLY issue. As you can (or maybe can't ) tell from the error, it's a C++ error (meaning it's an editor error). Any built version of your projects will be unaffected by it.
Thank you, Captain Obvious.
But this doesn't make this issue less annoying.
This happened to me when changing game Quality to Beautiful. It was disabling the forced 2x Multi-sampling AA that fixed it.
that worked but i dont want to use a default setting. sigh
I just experienced this error and resolved it by switching layouts, then switching back to my custom layout and (re)saving the layout.
Nothing to do with any camera effect, etc.
Note: I also fixed the error by removing my Pro license and reverting back to free edition.
Also confirm it was when I added an effect to a camera. In my case, blur.
rect.width <= rt->GetGLWidth() && rect.height <= rt->GetGLHeight()
Please report this as a bug, but's probably cleared on restarting Unity. Do you change fov much?
Hi, not at all. I will see if I can track it down to a single object...
Seems to be camera related you are hinting. WIll check that out