Hi,
Not sure if anyone else has this issue, i have read many posts but none of them suggest its the same issue, or i am not reading correctly.
Basically, when i enter VR, it displays my left and right eye on my normal monitor, and i also see two mouse pointers on each side, there is about a 3cm gap difference between the two however, is this normal?
Not sure if its related but my mouse just won’t work properly in VR, for a short period it will work fine but then it seems to just get stuck, like it cannot travel any further. It makes me think its because of this dual pointer issue and when one pointer his the edge of my screen display, in the VR it thinks i am at the edge or something?
Usually it works okay on the MCP or overhead but if i try to get it over the radios to set the transponder on the 737 it will have none of it, it will just travel around it or over certain parts of it.
I find the issue is made worse when i open something from the toolbar such as navicharts.
It makes it impossible to use the mouse in VR and its so frustrating because i find it easier to use than the controller.
Hopefully someone can help, if you need any further details let me know, its a bit hard to explain.
Having 2 (or even 3) mousepointers on your screen is normal. It reprojects the 2D mousepointer in the window into a VR space mousepointer in the 3D world.
That being said, the developer of the aircraft has to incorporate certain “VR planes” on which the mouse can move. Which 737 are you using? I might be that the developer hasn’t programmed VR capabilities and thus the plane will not work correctly in VR.
If it’s PMDG, all should be fine.
Thank you, glad to know at least that part is normal.
It is PMDG.
I found another post about PACX causing these types of issues, i have turned that off and will re-test but i am fairly sure i have had this issue when testing and tweaking the VR to which PACX is not open or used etc.
Glad you shared your experience as I too am having a similar issue. For me it’s almost like the mouse stalls when trying to move over specific locations.
At first I thought it was my mouse battery so I replaced it and ensured it is seated correctly and doesn’t come loose.
But the issue still happens. I haven’t identified any specific patterns yet, however, generally speaking the overhead panels seem to be ok.
I rarely fly the 737, let alone in VR, but I can take a look this afternoon to see I can see similar behaviour.
1 Like
Yeh, exactly, its a bit hard to explain but it just won’t go to the place you want it to go and you have to just keep faffing until it eventually goes there but its no good, if i use navicharts app and click in it, when i try to click back out of it or try to get the mouse to the FMC it starts again, its impossible to use the mouse, sometimes i just have to grab the controller because its just too much like hard work but i don’t like the controller because i find it difficult when it comes to turning knobs, it always ends up turning the way you don’t want etc.
Yep, I usually end up picking up my mouse and moving it on the table to try and get it to respond.
Next time it happens I’ll make a note of the aircraft I’m in and the specific location on the console, so I can try to repeat it.
Try to close one eye, you may be locating the mouse position with your dominant eye, while it was implemented for the other eye (with incorrect implementation of the plane on which the mouse cursor should be moving). This especially affects objects which are close due to bigger perspective difference between two eyes.
Following further testing it does indeed seem as though this issue relates to running PACX in the background. If anyone else faces this, hide the HUD in PACX by right clicking on the PACX app in toolbar.