Hi, it’s been a while since I posted here. Can’t figure out how to indicate code or link, so it’s all in the same font. Sorry.
I am trying to modify the MouseLook script to force the mouse motion to stay strictly in the X or Y planes rather than be able to tilt. Here’s my code:
Of course this doesn’t work because Input.GetAxis returns a float and I need a boolean value. Is there any way to address Input.GetAxis to find out whether it is using Mouse X or Mouse Y at any given moment. Thanks.
I’m making a color cube (3D depiction of the RGB color space) that you can go into and move around in like a room. This works well if the MouseLook axis is set to either MouseX or MouseY, but if it is set to MouseXAndY, the view tilts which is not what I want. I’m trying to figure out a way to have the view move strictly as either in MouseX or MouseY but not tilt (see attached image). That’s why I’m trying to figure out how to access Input.GetAxis and have it tell me whether the mouse is moving in X or Y at any given moment so I can constrain the motion to only X or Y axes. If you or anyone has any idea on how to do this, I’d very much appreciate it. Thanks.
So I adapted your approach to using “transform.Rotate” which sort of works. It will keep the mouse traveling in either X or Y direction but it’s still easy to get things tilted because if the mouse is tilted when it starts rotating, of course, it will stay tilted. If only I could make the character controller/camera just stay upright all the time! Here’s my code. Any suggestions will be appreciated.
By the way, how did you get your code into a code box. I can’t find a button for that. Thanks.
I tryed a box (of 6 planes) with one camera inside: if i attach the mouselook script to the box i get the tilt you say, but if i attach the script to the camera it works ok.
Are you moving the box? And why not the camera?
Edit: for the code box use the “Insert…” button (near the films icon button)
If this is not the only problem you have with localEulerAngles, what else? Just curious, as I use localEulerAngles for my camera and I’m interested in knowing if there’s any problems with it I’m unaware of.
Moving the box on the mouse X axis (object Y axis) is good because then it sets transform.forward to the box’s forward vector and you can simply multiply transform.forward and transform.right by movement speed to get a movement vector.
In my FPS, I use a weird, hacky solution. I have my camera GameObject as a child of the player GameObject. My MouseLook script adjusts the mouse X (object Y) rotation of the PARENT (which in turn also rotates the camera), while the mouse Y (object X) rotates the camera. This is so my player objects is always upright, but also enables looking up and down.
With “box” I mean the room where the character controller is walking into. The camera setup you are talking about I think is the same of the standard 1st person character controller that works fine too in the room with no “tilting”.
So or Zaffer is moving the room or have a modified setup of the character controller that generates “tilt”.
I am using my own scripts for Character Controller and MouseLook, but I tried the default ones and got the same result, lots of tilting. I don’t know how you got your results of no tilting.
Thanks Cranky, I will try this and let you know if it works – sound like it might.
My other problem with localEulerAngles is that I am also planning to have a feature where the user can input two colors, like 204 153 153 and 0 0 0 by clicking on a palette of the 216 “Web Safe” colors which are the spheres in my model. The controller/camera will then snap to line up those two colors so the user can “surf” from one color to the other. You can see how this works by typing the “t” key in my running build at http://www.bitsong.com/forPosting/Unity/Color%20Cube_Build.html/Color%20Cube_Build.html
Here is the code for my FPSWalker script with the snapping code included at the bottom. It’s a very simplified controller script.
#pragma strict
var speed = 8.0;
private var moveDirection = Vector3.zero;
function FixedUpdate () {
moveDirection = new Vector3(Input.GetAxis("Horizontal"), 0, Input.GetAxis("Vertical"));
moveDirection = transform.TransformDirection(moveDirection);
moveDirection *= speed;
if(Input.GetButton("Test")){
PlaceFPC();
}
var controller : CharacterController = GetComponent(CharacterController);
var flags = controller.Move(moveDirection * Time.deltaTime);
}
function PlaceFPC (){
var obj2 = GameObject.Find ("204 153 153");
var obj1 = GameObject.Find ("0 0 0");
var dir : Vector3 = obj1.transform.position - obj2.transform.position;
Debug.Log ("dir: " + dir);
var midPoint : Vector3 = obj2.transform.position + dir / 2.0;
var endPoint : Vector3 = obj2.transform.position;
this.transform.position = endPoint;
var rot : Quaternion = Quaternion.LookRotation(dir);
this.transform.rotation = rot;
Debug.Log ("rot: " + rot);
}
@script RequireComponent(CharacterController)
This feature doesn’t work at all if I use the localEulerAngles code. Only works with the transform.Rotate code. I’m sorry, I’m not much of a coder and I haven’t stopped to figure out why this should be so, just went with what worked.
As for moving the box or cube, I also will have a feature that will rotate the box in three directions – haven’t decided whether to use buttons or keys yet. I want to have a lot of different kinds of user input, but don’t want it to be too complicated. That’s why I’m trying to get the mouse to do what I want, so I don’t have to add a keystroke to make the mouse move in either X or Y, though maybe I will have to do that.
Thanks for all you help and suggestions. If you have any more after trying out my actual color cube, please let know.
The eulerAngles did remove the problem of my “snapping” script not working. Thanks! But unfortunately, it works like the example I tried above, of using Mathf.clamp with transform.Rotate. It will keep the mouse traveling in either X or Y direction but it’s still easy to get things tilted because if the mouse is tilted when it starts rotating it will stay tilted.
Isn’t the camera object normally a child of the controller object?
How did you do this? Did you attach a MouseLook script to both the controller and the camera with one set to X Axis and one set to Y axis? That didn’t work for me. Thanks.
Do you intend to implement Player collision? Because if not, a Character Controller like that isn’t necessary. The code like I wrote above could easily cover movement. But if you intend to add collision, then perhaps a Character Controller is in your best interest.
Please note that you should disable your Character Controller component while testing this script, since it takes care of movement for you. You only need a single object with a camera attached for this script.
Sorry if this is confusing :S
Nope, I used one component and attached it to the camera and made the camera a child of the player GameObject. Here is what I did:
Hi Cranky, You’re a genius! Your MouseLookTest script works. There is still some tilting, but it’s controllable. I can use the mouse to straighten the image and get back to level. Whereas before, the scene would just spin out of control. I think my problem was that I didn’t realize you didn’t really need a controller script, that the MouseLook script alone would let you use the arrow keys to move. I had no idea. No, I don’t need any type of collision, the only thing I will need to do is get my “snapping” code working with this new setup – shouldn’t be too difficult. Thanks so much!
I think my problem was that I didn’t realize that I didn’t really need a character controller script at all – that the MouseLook script alone would move the object. Apparently the controller script was causing the tilt problem. With a modified MouseLook script using Mathf.clamp per Cranky’s code, I can get things working well. Sorry I didn’t realize your suggestion was a good one. Thanks.
Famous last words… I added my code for “snapping” – positioning the camera along a line determined by two of the color spheres it only “sort of” works. When I play the scene and press the “t” key (input for this), the camera goes to the correct position and rotation, but when I release the “t” key, the camera stays in its new position but returns to its last rotation before the “t” key was pressed – either the starting rotation or the last rotation determined by the user rotating the mouse (see attached). If you or anybody has a suggestion on how to fix this, I would greatly appreciate it. Thanks.
I lost my mind trying to understand why transform.eulerAngles reset the rotation. I also tryed to save and restoring old euler… I don’t know why but it doesn’t works.
The good news is I have an easy fix for this:
This is because the MouseLook script is setting the transform’s rotation to its own internal rotation value internally. The good news is this can be remedied pretty easily :).
