Skip to main content
gabriead
Up and Coming
October 21, 2014

Crosshair not displayed on Rift

Hi there,

i am pretty new to Unity and the rift. I would like to set up a crosshair so I used the following code, and added the script
to the OVRPlayerController:

Rect crosshairRect;
Texture crosshairTexture;
float crosshairSize;

// Use this for initialization
void Start () {

crosshairTexture=Resources.Load("Textures/Fadenkreuz2") as Texture;
crosshairSize = Screen.width * 0.1f;
crosshairRect = new Rect (Screen.width/2-crosshairSize/2, Screen.height/2-crosshairSize/2,
crosshairSize,crosshairSize);
}


void OnGUI()
{

GUI.DrawTexture (crosshairRect, crosshairTexture);
Debug.Log ("Building Crosshai");
}


The crosshair is displayed when I use a "normal" player camera.
But it is not displayed if I add the script to the OVRPlayerController.Any suggestions?

Thanks a lot!

Adrian
    This topic has been closed for replies.

    8 replies

    badgeir
    Participant
    October 21, 2014
    I think the problem is that you are drawing your crosshair in the middle of your screen. This will not be visible inside the rift, as the middle of your screen is hidden between the eyes. Done this way, your crosshair will be uncomfortably placed without depth in front of your eyes, which i doubt is the purpouse. I suggest rather making a transparent plane some distance in front of your ovrplayer, and adding your texture to this. This way the crosshair will have depth and be visible to both eyes (cameras).
    MikeF
    Inspiring
    October 21, 2014
    I'd have to agree with badgeir, i tried something similar to your code initially and ran into a bunch of issues related to depth and convergence between the two images. I ended up creating an Ngui sprite and attaching it as a child of the left camera, from there it was easy to adjust properly while running the application
    gabrieadAuthor
    Up and Coming
    October 22, 2014
    Thanks a lot for the super quick replies, creating a plane and adding it as a left child to the left camera fixed the problem!
    gabrieadAuthor
    Up and Coming
    October 22, 2014
    Another question that is not directly linked to the crosshair but just occured.
    What functions from the API do I use to detect certain objects in the scene that the player is currently looking at?
    For instance if the player is looking at items on a table?

    Thanks a lot in advance!
    cybereality
    Inspiring
    October 22, 2014
    @gabriead: I believe for that you can cast a ray from in-between the two cameras and see if it hit anything.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
    badgeir
    Participant
    October 22, 2014
    As cyber mentioned, look into Raycast. A good thing to do is probably taging the items you wish to let the player "look at" by using the "tag" pulldown menu in the inspector (you can create a new tag, e.g. "Lookable", and tag the lookable items with this. Then check if the tag of the object hit by your Raycast == "Lookable", and if so, do what you want to do to the object. (E.g. Change color or whatever). You should find examples of this online, i know i got it from an fps shooter tutorial.
    gabrieadAuthor
    Up and Coming
    October 23, 2014
    I haven't tried it so far but sounds like a very good approach. Is it possible to use GUIText with the rift? It doesn't display any text, so I am using a plane with a texture again. What is an elegant way of working with text with the rift?
    badgeir
    Participant
    October 24, 2014
    If you have pro version (which i guess you have since you're using the rift), you can use "3D Text" if you only want to display text: http://docs.unity3d.com/Manual/class-TextMesh.html . If you want other GUI elements, you can look into using RenderTexture to render GUI elements onto the texture of your plane. I'm unfamiliar with this myself, but it should put you on the right track (I think).
    Terms & ConditionsAccessibility statement