Forcing a camera to be rendered when it's stubborn?

[Jessy]

I’m dynamically creating cameras in my game, and I’m using Depth Only to stack imagery. However, I can’t figure out how to “wake the new cameras up”. In the Editor, I have to go into the field for any property of the camera, as if to edit it, although I don’t actually need to edit anything, and then it renders. Otherwise, it isn’t rendering. I have no idea what to do to get it to show up on the iPhone - same result without any ability to Edit anything, obviously. Any tips?

[anon_85768832]

Bump. I don’t have an answer for ya man but thought I’d float this back to the top for (hopefully) extra eyeballs.

[Jessy]

Tom, thanks a lot. I reported this bug:

This is a bug in both Unity and Unity iPhone.

Each of the three scenes in this file include a Game Object with a camera attached, and a cube object with a tiny script attached. The cube can be seen by the camera in the Game View.

In “Start” and “On Became Visible”, the attached script adds a camera to the cube as soon as you hit Play. In “Start”, this happens in the Start() function. In “On Became Visible”, it happens in OnBecameVisible(). (The cube is visible at the start of the game, meaning that the camera is added immediately in both scenes.)

In “Start”, the behavior is as expected: the new camera renders a blue background where there had been a red one. However, in “On Became Visible”, the new camera does not render immediately. Instead, in Unity, you have to edit any property of the camera, in the Inspector, before it will render. In Unity iPhone, you only have to click in any of the editable fields, as if you were going to edit a property.

The problem only occurs when we explicitly set the depth of the camera. The default depth of a new camera is zero, and and even if we set the new camera’s depth to be zero, as shown in these scripts, the problem occurs.

A third scene, “Main Camera”, does not add a new camera, but simply sets the depth of the main camera to be what it already was. The same problem occurs.

I have listed it as a “Problem with the Editor”, but it is also an even more important problem for builds, because you can’t “wake up” the cameras.

The scripts that I use in this project consist of the line

(gameObject.AddComponent( typeof(Camera) ) as Camera).depth = 0;

When it’s in Start(), it works, but it breaks in OnBecameVisible(). Unfortunately, that’s where I need it. I’m going to experiment, trying to find a workaround. Again, if anyone has some advice, I’m all ears.

219244–7977–$onbecamevisible_depth_problem_163.zip (576 KB)

[Jessy]

I discovered that this is even more of a general problem than I thought. If you modify any camera’s depth based on an OnBecameVisible event, things break.

Example that is included in the latest project above:

void OnBecameVisible ()
{
	Camera.main.depth = 0;
}

[andeeeee]

Just to let you know, I’m running this by the dev team, but I think it will turn out that you’ve found a bug here.

[cherub]

its wrong for sure. this script was working just fine, then magically stopped working.

just keeps returning “seen” no matter what i look at.

function OnBecameInvisible  () {
//enabled = false;
//gameObject.tag = "null";
print ("gone");
}



function OnBecameVisible  () {
//enabled = true;
//gameObject.tag = "attract";
print ("seen");
}

[anon_41771069]

I’m having problems with visibility functions to.