PointCtrl in BMS
-
@Snake122 said in PointCtrl in BMS:
Update of a couple of posts from PointCTRL discord:
Thanks @Snake122 , I put myself on the PointCTRL “pre-order” list last week, hope he gets this sorted (or someone gets OpenXR integrated). Do you have an Invite URL for the Discord?
-
@Atlas current V2s have a nicer blue plastic body. Original V2s FCUs (finger buttons) that are black are a little slimmer and the HMU usually doesn’t have the white reset button towards the back. V1 FCUs have a little reset style button under the LED.
@Icer the wait will be brutal but they are well worth it! https://discord.gg/vxESrKuG
-
FWIW, if using RawInput, this should show up as WM_INPUT with a RAWMOUSE with MOUSE_MOVE_ABSOLUTE set. If using classic WM_MOUSEMOVE, data should already be good - but those (x, y) need to be treated as an absolute rotation to project, not as an offset
It doesn’t look like there’s true absolute mouse support in DirectInput - while the axis can be set to absolute mode, this just makes DirectInput emulate it by keeping a count.
If y’all have a wacom/huion/similar tablet, that works essentially the same way as a PointCTRL as far as the game is concerned - if absolute mode is working correctly, there should be a rectangular region that maps to your FOV, which isn’t the case in BMS.
As a side note, the mouse shouldn’t necessarily map to one eye buffer; while DCS shows one eye in the mirror window, the ‘input FOV’ for the mouse/tablet over that window is the combined FOV - so 2* max(abs(leftfov), abs(rightfov)). This lets you use the mouse over your full FOV for both eyes, not just the one currently in the mirror window. This means that the windows cursor doesn’t match up with the in-game cursor if you move it from the outside the window to in the window, but gives a better in-game experience (regardless of if mouse or tablet)
-
@Snake122 thanks!
With 4.37 now out, how does PointCTRL work with BMS?
-
@Atlas It doesn’t Currently.
-
@SOBO-87 is it something that the BMS have to work at to incorporate it? Or the PointCTRL dev?
-
This post is deleted! -
@Atlas I think it’s something in the way BMS maps the mouse as discussed above that needs to be adjusted. Or at least an alternate option set-up for…
-
Yeah, word from Miles is that it will take some work like MSFS does because of how it as looser mouse area sl to speak. Fred is the creator of OpenComposite and OpenKneeboard and has made it work in MSFS but via OpenXR, not SteamVR. So we are waiting.
-
-
Yea I also had a quick chat with Miles (PointCTRL dev) he said that BMS guys are going to contact him.
So far I like BMS VR a lot, got the VR world scale and Voice Attack sorted, now I only need the PointCTRL to work to make the full switch from DCS for single player experience. -
@Metzger in the mean time, I’m hoping that @SemlerPDX mouse lock to center program will let me at least use the click functions.
-
@Snake122 do let me know if it works.
-
So it is this from BMS technical manual that causes PointCTRL not to work currently:
"
4.2 Touchscreen Use for Cockpit Interaction
Correct touchscreen usage is currently not possible in BMS as the input system uses relative mouse input only.
Touchscreens need absolute coordinates for proper handling. If used as a secondary monitor to simulate
cockpit panels you risk invoking functions in the 3d pit by accident.
To prevent this, new keystrokes have been added to enable/disable mouse buttons in the 3D cockpit entirely.
This offers the possibility to avoid unwanted mouse clicks in non-exclusive mouse capture mode, e.g. for
touchscreen users. The new keystroke names are:
"As far as I understand, PointCTRL works like a tablet, so I guess it is up to BMS devs to make it work.
-
@Metzger said in PointCtrl in BMS:
So it is this from BMS technical manual that causes PointCTRL not to work currently:
"
4.2 Touchscreen Use for Cockpit Interaction
Correct touchscreen usage is currently not possible in BMS as the input system uses relative mouse input only.
Touchscreens need absolute coordinates for proper handling. If used as a secondary monitor to simulate
cockpit panels you risk invoking functions in the 3d pit by accident.
To prevent this, new keystrokes have been added to enable/disable mouse buttons in the 3D cockpit entirely.
This offers the possibility to avoid unwanted mouse clicks in non-exclusive mouse capture mode, e.g. for
touchscreen users. The new keystroke names are:
"As far as I understand, PointCTRL works like a tablet, so I guess it is up to BMS devs to make it work.
Yep. That’s my understanding also
-
Hi,
I am pointctrl v1 user in DCS and I am in the process to revisit BMS after 10+ years. Mainly due to the VR option . To use pointctrl in BMS would be awesome. I am going to check this topic here very closely. Thank you for sharing here! Much appreciated.
Best flex -
Hopefully @SemlerPDX will come out with his full cursor locking app soon. It won’t be completely what we want since it seems like it will take some kind of BMS magic, but it will at least allow us to look at a switch and use the PointCTRL to send the mouse click since we are used to that in a way.
-
@Snake122 Hm, if cursor is locked in the center of the screen, then good luck in looking back at the test panel or avionics panel. Not sure if this would work
-
@Metzger I know, it’s a stretch, quite literally, but maybe the option for awhile. PointCtrl will definitely send the mouse clicks in 3d, I have confirmed that. EDIT: It’s also seems like there might possibly be a way calibrate it to be usable in a more mouse like fashion, just the not 1:1 movement we are used to and for those of you that fly DCS would require the recalibration for that. But there may not actually be enough cursor limits and such for that, but down the list for me to try. Just now getting used to calibrating my V2 without the voice over app.
-
U1 still has the same overall issues with PointCTRL and the mouse overlay. However, with the new lock mouse to VR and also a mapping to allow toggling this on and off, you can at least use the mouse clicks on PointCTRL to press switches without your hand being tracked. Now I see why @SemlerPDX stopped working on his app!