@scubapics that’s the problem, the tablet input is way skewed with BMS, you can get mouse movement but it’s way to sensitive to be useful. HTCC creator @fredemmott has discussed here and we have talked about it some on his Discord. He can explain it a little better, works for DCS because of the rare way it uses mouse input and makes devices like this have problems in other sims like BMs and MSFS:
@fredemmott said in PointCtrl in BMS:
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)