In one map I deployed the FPSCharacter from Unity, and the camera renders to a texture.
I added another camera far away from the scene, that points to a mesh with a plane on which the rendered texture is shaded.
All was fine up to now, and for some reason now the vertical axis orientation of the camera is not working.
But it is working back again if I delete the second camera, or even only DISABLE IT!
I cannot understand what can cause this problem.
No script was edited, the second camera does not have any script on it.
The only thing I did before finding this problem was the following:
- I made another map, and worked on it
- I added a sphere and a camera and added FSM from PlayMaker
- Played with this stuff, with and without the render to texture thing
Then I got back to the first map, and I found the problem.
But I didn’t touch any script, and the two maps and prefabs are completely independent.
I’m getting mad.
The only thing that comes to my mind, is that the character controller script has some hard coded stuff that refers to a camera… any camera… and so it points to the second camera for the vertical movement, and the second camera is moving vertically, but of course nothing happens because the mesh with the texture on it is a child of it.
New data: apparently, having ANY PlayMaker FSM assigned to ANY prefab in the project, spawns this problem.
Can’t really imagine what it is.
None of the two cameras and their prefabs have ANYTHING to do with PlayMaker, they have no FSM appended at all.
Edit: seems that PlayMaker FSM take possess somehow of the mouse, because even removing the render to texture function now, doesn’t solve the problem: the Y axis of the mouse seems locked.
OK I don’t know if this is PlayMaker related, but I tracked down the problem to the second camera.
Despite the second camera having no script attached at all, and despite the fact that I didn’t modify the Unity character scripts at all, now this configuration with two cameras in the same scene won’t work.
I removed the second camera, and the mouselook works now, so the chances that PlayMaker is involved are thin now.