Unity Cursor Locking & mouse delta issues
I'm trying to build a simple FPS with a mouse connected via the USB port to control the crosshair using unity but I'm finding that the mouse values I receive get clamped. I initialize cursor controller like so: void Start () { UnityEngine.Cursor.lockState = CursorLockMode.Locked; } And retrieve the cursor delta with this line var delta = new Vector2 (Input.GetAxis("Mouse X"), Input.GetAxis("Mouse Y")); The behavior I'm seeing is that the delta is returned fine to begin until I hit the edge of an invisible wall At that point the delta values become zero in the axis of the wall I hit. When I log UnityEngine.Cursor.lockState out on a device build it says that it's no longer locked. It seems to me that two things could be going on - The cursor is not being locked, and the feature is not supported - Something is unlocking the cursor lock Can anybody shed any light on what's going on here?
ScreenPointToRay and ViewportPointToRay not working with VR camera
X-posting from the Unity VR forums: https://forum.unity3d.com/threads/screenpointtoray-and-viewportpointtoray-not-working-with-vr.471440/ Environment: - Unity 5.6 - VR is active and rendering to the HMD My goal is to raycast from the mouse into the scene, with a VR camera. When using ScreenPointToRay on a VR camera the ray's direction is way off. Here's an image when my cursor was in the center: When using ViewportPointToRay the ray's direction is much better but still not perfect. Here's an image showing the difference (sorry for mouse pic, my screen capturer wasn't picking up the mouse): Here's the test code to reproduce in a clean Unity 5.6 project and scene: using UnityEngine; public class Raycaster : MonoBehaviour { public Camera sourceCamera; public bool useScreenPoint; public bool useViewport; public Transform viewportSphere; public float sphereDistance; private void Update () { Vector3 mousePos = Input.mousePosition; Ray ray = new Ray(); if (useScreenPoint) { ray = sourceCamera.ScreenPointToRay(mousePos); } else if (useViewport) { float normalWidth = mousePos.x / sourceCamera.pixelWidth; float normalHeight = mousePos.y / sourceCamera.pixelHeight; Vector3 viewMousePos = new Vector3(normalWidth, normalHeight, 0); ray = sourceCamera.ViewportPointToRay(viewMousePos); if (viewportSphere != null) { viewportSphere.transform.position = ray.origin + ray.direction * sphereDistance; } } Debug.DrawRay(ray.origin, ray.direction, Color.red); } } In these screenshots I'm using a single camera set to both eyes. However, I have repro'd the same problem when I switch to left and right eyes too (that's the setup in the actual project I'm working on). To visualize the use case: there is one person in VR and one person not in VR but on the PC using the mouse to click on things the VR person is looking at. The simple solution to this would be to use another camera that displays just to the monitor, however the project is very performance restricted and the new camera would be displaying exactly the same thing as the existing VR camera. Has anybody had to tackle this or have any ideas on how to solve this without an extra camera?
[SOLVED] OVRCameraRig & Use Per Eye Cameras: Turning on and off cursor problem
Hi, I want to turn on/off the OVRCameraRig property Use per eye cameras to display stereoscopic or monoscopic video. I want to use a single camera for both eyes in the menu and then turn on/off the Use per eye cameras option as needed. If I enable this option in runtime, the gaze cursor's (OVRGazePointer) position is not in the center anymore, but half a way between the center and top border. If I enable this option in the object inspector, then the cursor works fine until disabling and re-enabling per eye cameras. Do I need to switch OVRInputModule's Ray Transform object? If so, which one? At the moment I'm having it set to CenterEyeAnchor.
Unity 5.4 b13 World Space canvas cursor registration
We have encountered an issue where our World Space Canvas no longer registers the cursor correctly (for mouse over etc). For context, we use a centred (faked/gaze) cursor to interact with canvas-based menus. However, the behaviour occurs both with a standard mouse cursor and a faked/gaze cursor. 1. It looks like this has to do with the new way in which unity is handling the game window scale/resolution 2. The cursor acts as though it's offset by an amount proportional to the current resolution set on the game window (mucking around with the resolution, we can almost correct it). At 1024x768, the button registers events above and to the right, at 1200x1600 it's centred but somewhat below 3. This only happens when the rift is plugged in 4. The behaviour can be reproduced in a brand new project 5. We are using Oculus runtime 1.3, Oculus unity plugin 1.3, Unity 5.4.0.b13 EDIT : A sample project can be downloaded here, run the test scene on the top level of the assets folder. https://www.dropbox.com/s/pgmfiuvk6rnoxdy/Cursor%20Test.zip?dl=0
