@oakdesign As i suspected i had changed some config options trying to get it to work resulting in still not working with U6. Working now thanks

@CobaltUK unless they are in VR as well. I’m in 95% of the use cases am not using the chat window to chat with others but to send like config or .dot commands to the game, therefore my mention that the input is correctly recognized by the game

@rubbra when I run Falcon BMS from the Home Pimax desktop, it all works fine and when I exit a mission it takes me back to the BMS 2d enviroment. However, when exiting Falcon BMS, the Pimax desktop closes down too in the VR headset. I hope you understand what I mean here. Is this normal?

@crr_romero my personal preference is virtual desktop, using VDXR. But openxr is probably your best choice if going with link. You have to restart link after changing those settings in ODT or OTT. That’s how it works.

@oakdesign said in [OpenKneeBoard] WDP Converter Tool: @Icer not commenting on that in terms what BMS Team is doing, only on what I’m doing and that is working on a tool that aims in a similar direction as WDP but web based and open source Understood. In reality all I use MC for is to re-stock my squadron stores (and in the past to move objects erroneously placed in runways) and WDP to update my kneeboards, so please just be sure to include those functions…

Curious of the overall experience in BMS, especially if running in Steam OpenXR, and even more so if XRNS is working ok…

@TUAF-Ripper godlike and 3060 mobile that doesn’t fit, you wont get decent FPs in that setting [image: image.png] maybe with SSW you can get around with ultra

Hi, when I look at the specs of the Bigscreen beyond 2 (bb2), increased fov looks very nice. But … I can share you my perspective. As a quest 3 user (got into VR only last december) I like the pancake lenses of the quest 3 which should be comparable to the bb2 (at least when reading about bb2). With respect to micro OLED I cannot say anything, since I have no comparison. For sure bb2 has a nice formfactor, however with a headstrap I can wear the quest 3 (w/ cable) up to 3-5 hours in a row without problems which is a limit for me anyways. When I compare both money-wise, the investment would be too much for the (of course only anticipated!) difference. I personally would still get a quest 3 for less than half the price. I’d rather do this and wait until something reliable and small comes out with eyetracking and then invest the larger sum. I’ve read that an eyetracking version has been announced for some time this year. Please be aware that you need a decent rig for VR, eyetracking will enable you to use dynamic foveated rendering which decreases your GPU usage. And I guess it’s not bad to have some GPU capability to spare when 4.38 comes out … Best regards P.S.: I just recently started BMS in VR and use it 99% of the time. It is just another dimension of immersion! The BMS team got it right from the start Thank you for that!

Sounds like an Express train to Puke City.

There is a scale what starts at void and ends in reality. Every piece of software what tries to mimic real life are on this scale somewhere. No matter you call a software a simulator or a game.

@oakdesign thanks for clarifying !

@seagoat said in Minimum specs for VR in Falcon BMS 4.37.6: @crr_romero it’s desktop version. I installed 850w in my eGPU box for my future 4080 or 5080 or 5090 ^_^, so I’m not sure the really watts value. (I think 2070 should less than 250w) and I think bms graphic setting affects little, you can try high setting in BMS As you said, it seems that the performance of a 2070 eGPU is comparable to an internal 3060 mobile. As for the CPU, it seems that there is a lot of difference. Maybe in this aspect I do need more power… I still have many doubts about whether I’m going to waste my money buying the Quest3 because I can’t use them in VR.

@Wheelchock @rubbra thank you guys! I will look at those.

Thanks to all for the help! I will follow all of your suggestions.

Old posts on it: @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) @Snake122 said in PointCtrl in BMS: Update of a couple of posts from PointCTRL discord: Miles the PointCTRL creator: “Fired it up BMS and it looks like it’s not natively supporting absolute mouse coordinates. Its the exact same behavior as MSFS. I am going to try a few different things on the HID descriptors for MSFS and BMS,” Fred (I believe he’s @fredemmott here): "The way mouse support works in MSFS Until recently, it was pretty much entirely a no-go PointCTRL isn’t quite pretending to be a mouse: it’s pretending to be a graphics tablet/touch screen. A mouse sends “i moved 1cm in the last second” (movement, not position) A touch screen/tablet/pointctrl sends “My exact position is (x, y)” MSFS only supported relative movement (mice) until very recently. It’s now got some absolute position (tablets/touchscreen) supports, but it’s full of quirks, and not really usable." "HTCC right now uses OpenXR for: quest hand tracking (as an alternative to pointctrl). This is only possible with OpenXR. VirtualDesktop also does controller emulation with hand tracking, but that’s not usable for this - as far as anything on the PC can tell, it’s just a controller. automatic calibration (field of view, center point etc) VR controller emulation" I’m definitely not going to make it support steamvr as well. What I might do is make a separate ‘tablet mode’ program that comes as part of HTCC, with an enhanced calibration. That would allow HTCC to work both with DCS without opencomposite (but only in touch screen mode, not virtual controller mode), and BMS." HTCC and OpenComposite are his work with the OpenXR stuff and allows a work around for PointCTRL in MSFS but that’s about all the more I know and might not be 100% correct there.