3.2 error, can't use rendertexture

Unity Engine
1

I’ve updated to 3.2.0 and I get this error if the scene contains a rendertexture

screenviewcoord[1] < 0 || screenviewcoord[3] < 0

Assert in file: C:/BuildAgent/work/f724c1acfee760b6/Runtime/Camera/CameraUtil.cpp at line: 38

when i open a scene i get this error too

screenviewcoord[1] < 0 || screenviewcoord[3] < 0
UnityEditor.DockArea:OnGUI()

Assert in file: C:/BuildAgent/work/f724c1acfee760b6/Editor/MonoGenerated/Editor/AssetDatabase.cs at line: 106

the problem is due to the render texture height it has to be set <=256, any value above it will produce the error (no problems with the width).

several user are having this issue (please see http://forum.unity3d.com/threads/30545-screenviewcoord-1-lt-0-screenviewcoord-3-lt-0 ), for some of them the rendertexture works fine with height up to 512.

Just create an empty scene, create a new render texture with height >=512 and assign it to the camera and the error will show up in the console (just once in the editor, spammed continuosly during play).

I’ve reported this issue on that topic about a week ago and I haven’t had a single official answer, hope things will change here.

2

I saw this issue when game view/scene view is smaller then RenderTexture used

3

uhm yeah that could be the problem, my web game has a 720x450 resolution and I’m using a 1024x1024 render texture.
any way to fix this without resizing the game/rendertexture?

this is really blocking me from doing new builds.
it was working just fine with 3.1

4

No it is related to window size itself (ot is it manifested in game too?)
Anyway, if this is in game and is reproduced consistently - strip down your project to smallest size possible (though make sure that error is still here ;-)) and submit alongside bug report
If it is in editor - try to make (game view/scene view) window larger itself

5

I get it spammed continuosly (non-stop) in the console log when I hit play as my game window is 720x450, haven’t checked an actual build log, does it make any difference? (it’s a web game)

I’ve tested it in an empty scene with a brand-new render texture without adding any other object, just setting that render texture as target for the camera and it gives the error. do I really need to do a new project with an empty scene and send it?

and again, everything was just fine with 3.1 and previous version, never had this error, is something that appeared since my upgrade to 3.2

6

try making it larger as a workaround

7

I cannot make it larger, I work in a game company not on a personal/indie project and that’s the resolution the game window has to be.

since it was working on previous version should I expect a fix soon on this?
Otherwise I think I’ll have to revert on 3.1 if you can’t suggest anything else

I’m using the pro version, don’t know if it makes any difference for the bug

8

I’m talking about game view window in Editor - can you make window larger?

9

ok I’m using a 1024x1024 render texture and yes if I make the game window in the editor larger (something less then 1024, shouldn’t be >1024?) the error disappear but I don’t understand if when I’ll do the web build (720x450) the error will still be there or if it’s only an editor bug.

also I need to test the game at the build resolution, without considering that i cannot really work with a game window that takes the 80% of my screen; luckly I have a 1080p monitor and I can temporary resize it if it won’t cause problem in the final build, but what about the ones using a screen resolution where the height is <1024? they cannot use large render texture? (e.g. can’t work on this project on my macbook pro).

why the problem is only on the height and not on the width too?
and mainly, why it was working with all the pervious unity versions?

10

ok i’ve tried doing a web build and luckly there’s no error in the log so it’s only an editor bug.

I’ve already opened one last week but whit all those new infos should I open a new one or maybe is possible to edit the bug report in some way?

11

yes, this is editor-only bug
you can edit your bug - go by the link that was sent to you in the mail

12

can’t see any link/button to edit in the report

the ticket is: 391367_lqgfuach it was basically a copy&paste from the other topic, if you can give me a link to edit it I’ll do it

13

Any official word on where this stands? I’m in the same position as arioch, I need the render texture 1024x1024 and am continuously getting this error, and would rather not adjust the game window. If it’s just an editor error, I guess not that a big deal. But would be nice to know what the word is on this. It throws the non-programmers/artists on the team for a loop seeing this error continuously print out.

14

Guys, come on
Are seeing this in game build? No! Dammit, you will need to resize only game view window in Edtitor because not a single person have this error in built game

15

alexey I understand that as a temporary fix we can resize the unity game window but it’s not so nice to work with a window that takes most of the screen (with a 1024 on an full HD, height of 1280, it takes the 80% of it!) or anyway if you are working on a game (let’s say web or mobile) with a fixed resolution you have to test it at that resolution you cannot just resize the window using the free aspect.
and what about if you are using a 2048 render texture?

we can’t just use the console or any debug.log/warning/error as the error get spammed continuously on it.

what I think unityrookie was asking is: since it’s an editor only bug and it was working fine in 3.1 should we expect a fix/patch/whatever anytime soon?

also i’m reading of a lot of other issue here in the support forum with the 3.2, do you have any roadmap for a 3.2.1 to fix issues like this?

16

thank you arioch, that’s exactly what I meant with my question. I appreciate that its not a “critical” problem as I can still compile and build the program and there is a work around. But as Arioch suggests, the console gets spammed with the error during debugging, making it trickier to pick up the real problems, and I prefer not to ‘collapse all’. Same goes with wanting to work with a fixed resolution that actually represents the game, not a huge window taking up nearly all my screen. Again, these are not keeping me from working, but they are inconvenient and are new in the upgrade from 3.1 to 3.2, which is why I was wondering if they are being worked on.

17

Thanks for the heads up, will be fixed in next release real soon now.

18

thank you.

there’s any public roadmap on the releases?
just to understand if we’ll have to wait like months for a 3.3 or do you plan a 3.2.1 soon with this and other small fixes

19

ok it looks like this problem has been solved with 3.3 after htiting play in the editor with the game view but I still get it once in a while during a scene editing, i think it’s the same issue but with the scene view this time.
is it supposed to be fixed in 3.3? should I open a new bug / report an update to the old one?

20

same situation with me. It now works while playing the game, but pops up during editing. Much better this way though, at least I can run it without all the errors clogging up the console window while running.