• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS 2024 VR cockpit cursor/raycast API question for external pointing device

M

Mack11

Messages
1
Country
ca-britishcolumbia
Hi everyone — brief intro: I’m developing an external IR finger-tracking pointing device for VR cockpit interaction, mainly for flight sim users. The project is Talos: IR Finger Tracker by SimVRTech. There’s a basic overview here for context: https://simvrtech.com/


I’m not posting to promote it — I’m trying to better understand the correct technical approach for MSFS 2024 VR before going too far down the wrong path.


The issue I’m investigating is the MSFS VR cockpit cursor/raycast behavior. From testing, it does not seem to behave like a simple 2D Windows cursor at the center of the screen. It seems more like an internal VR ray/collision cursor that responds to relative mouse movement and may retain its last ray/cursor state.


What I’m looking for is guidance on the SDK/API side:


Is there any supported way in MSFS 2024 to query, reset, re-anchor, or influence the VR cockpit mouse/raycast cursor?


More specifically:


  • Does SimConnect expose anything useful for the VR mouse/raycast cursor position or origin?
  • Are any camera/view SimVars expected to reflect live VR headset movement?
  • Do camera reset events affect the VR mouse/raycast cursor, or only the camera/view?
  • Are Input Events a viable aircraft-specific workaround for interacting with cockpit controls without relying on the VR mouse ray?
  • Is MSFS VR cockpit interaction driven by normal Windows cursor position, relative/raw mouse input, internal raycast state, or some combination?

I’m not looking for general user troubleshooting. I’m trying to understand the supported architecture options: firmware-only relative mouse, Windows companion app, SimConnect, mouse injection, Input Events, or something else.


Any pointers to SDK docs, sample code, DevSupport threads, or known limitations would be appreciated.
 
You must log in or register to reply here.
Back
Top