Sprool

Lol, i spend way too much time on the internet doing geek stuff! Seriously though, you look at how msfs and dcs has leapt forwards because of initiatives from members of the community, those who have the time and skills to be creative and contribute to the community, its one of the things that helps sort out the many bugs in complex software interactions. DCS_Volanta.lua

Good point First I must say Im not using it as a kneeboard at all but as a passthrough mask so I can see my real keyboard thru the mask when flying in VR, saves me trying to peer under the headset to see if my findgers are on the right keys. I'm assuming you already have the game and file pathways correct when installing OpenKneeboard. Im using a Quest 3 running Virtualdesktop as the streamer between headset and PC. Do not use SteamVR, do not use Meta Quest Airlink. For the Spitfire I drew a letterbox mask with colour R255, G0, B255 and a transparent background, saved as a phg file instide saved games/kneeboard/SputfireLFMkIX. It works same (I think) for any of the aircraft as long as you create a folder for them with full correct name inside the Kneeboards folder. I am sing the same mask in every plane. I called it something catchy like OK_Passthru.png, but the name is irrelevant. In OpenKneeboard Settings, Virtual Rality, I set size to 0.60m, height to 1.05m, then set a keybinding to recentre - same keypress as I use to recentre the VR view. Also set a keypress or control button press to toggle the kneeboard on/off. I set vertical distance from eye level as 0.55m, Left-to-Right position at 0.00 (so its centred) and forward position to 0.60m. You have to play around with this a bit to get the 'passthrough letterbox' to coincide with where the physical PC keyboard is sitting on your desktop. Pitch, Roll, Yaw I leave alone. In-Game UI Header, footer, bookmrks cropped - I set to off. Gaze Zoom set to Off. Opacity when looking at the kneeboard = maximum on the slider, when not looking at the kneeboard = also maximum. Click the Aircraft icon before starting DCS. (not sure if thats essential...) but you need it on Aircraft icon to show the passthrough mask in virtual cockpit. Now in VirtualDesktop app, go to Streaming option, VR passthrough, tick Environment, settings. Set passthrough configuration to Red: 255 Green : 0 Blue: 255 I set similarity to 10%, smoothness to 5% but I have no idea if these are optimal or not at this stage. Set Passthrough Opacity to 100%, show boundary = No. Now when you go into DCS in VR and select the Spitfire, you shoudl get a transparent letterbox with a magenta border inside your VR cockpit, and you shoudl be able to see your real desktop through the passthrough. Then its a case of manipulating the position within OpenKneeboard to get the desired position. If anyone knows how to get rid of the magenta border, please let me know. If anyone has better understanding of the smoothness and similarity do share!

Never mind - Ive had more time to play and got it working

Im really interested in trying to make this work in VR as a mixed reality magenta pass-through area, similar to the guy on the A-10 warthog project. Unfortunately I think I need a step-by-step walkthrough to make sure I have the correct opacity settings (in both VirtualDesktop and OpenKneeboard) as well as nudging the correct overlay area into the VR cockpit position - every time I switch out of DCS VR it tends to crash on me. Is there a step-through guide I could access? Ive scoured the youtube channels and the openkneeboard website but not found what im after.

Good luck identifying the issue, its really become a major block to my online play

i too find load times into missions really r e a l l y slow, and multiplayer missions even slower. Even clicking on a module in f10 map to go to f2 view seems to halt the game for 30 - 40 seconds.

ok cancel that, old keyboard also now playing up.

Update: Well I took out my current wireless keyboard and pugged back in my old USB cable one, and so far no repeats of the earlier problem. I have no idea if this has solved it or why a wifi keyboard might be the culprit?

OK no luck with that one, if I go to settings > controls > UI layer, search....Zoom, I only get options for toggle VR zoom, toggle VR spyglass zoom, none have any controls or keybinds mapped to them. If I try UI Layer > axis commands, ther'es no entries?

Well thats something to try, thanks for the input!

Still getting problems with this issue, testing a mission from the mission editor - not even multiplayer, esc key stops working, have to do a ctrl+alt+del to exit DCS. Tried a slow repair, no joy. Was trying to reset some snap views again (in the Harrier). Its really wierd, I jump into an instant action mission in the harrier, the snap views have ben reset after the last update, so I reset them, just mapping numkey buttons 7 and 9 to allow closer view of the left & right MFD's, then I find the ESC key no longer works.

Handover to and from Bob is a bit glitchy at the moment, if you do it at speed I get a big change in pitch

You'd hope the Chinook has more than enough room to pack a lot of ammo for the gunners, maybe tat feature is around the corner...

Dont forget the Bob button for cruising!

I'm struggling with a simple CTLD mission playing around with the CH-47. I want to be able to transport 40 troops in the CH-47 and 16 in the Mi-8. I created a new 40-strong unit "Platoon" which shows up in the F10 menu and I imposed the unit load limits but every time I load troops I get 40 into any helo, then the Mi-8 and Huey cant take off as they're too heavy. Lol. I also set ctld.numberOfTroops = 40, could that be the problem? If the number is < 40 then the Platoon option does not appear.

ваше здоровье vashe zdorov'ye

It may be quicker for me to start learning Russian

Are you running on the latest DLSS version?

Has anyone looked at resolving this bug yet?

I tried running these 2 modes in parallel with two ai Hueys, troop pick up and drop off, lik a timed assault course, combat on racing against combat off. sadly I cannot say I noticed any difference, they both landed back at virtually the same time and spilled thir troops out together. Maybe the distance from last waypoint to land or disembark poont is really critical to get this to work properly?

In further news, I managed to get keyboard emulation mapped to 2 of my little-used joystick buttons (VKB NXT Pro - the software that comes with this is amazing) so with one joystick button press it emulates L Ctrl + Lshift + W : i can store a waypoint, then move the map & store another, a different key press emulates Lctrl+Lshift+s and sends the waypints to the cockpit. Happy days

@Comrade Doge Thanks - this is a brilliant tool, it should be fully integrated into DCS at some stage. It would be good to find 2 really easily accessible keys to press for VR users. If I go to desktop view then the Quest 2 will crash and cause DCS to hang - this is due to me using Turbo Mode in the OpenXR tool, which really helps achieve good frame rate and smoothness, so I'd rather not have to turn it off!

New version with Kiowa support (big thanks!) works fine oon flat screen, but I cannot get it working in VR (Quest 2 headset). I tried the deault key bindings (ctrl+shift+s, ect.) and also tried changing settings to map my own keybinds but it will not pick up, store or transfer any thing. Its like my key presses are being ignored (in VR as well as flat screen). Did I miss a step? Is <numpad Enter> a reserved keypress? I guess I may have had ctrl+shift+s apready mapped to something different, if I change it to ctrl+shift+w then it works, I just wanted to avoid having to do ctrl+shift+anything in vr as I cannot see the keys.

THanks you Flappie I guess with (new) combat landing option ticked you have to make sure the helo has enough time to get low and come in horizontal, not a steep approach. that should be possible by placing th touchdown waypoint a sensible distance after the touchdown waypoint marker (does that make sense?)

i set up a new test mission with 3 hueys on the afghan map and now they are working fine! The only difference is ni MIST or CTLD script loaded up. I will do more testing to see if thats the issue, but I realise thats not a Huey bug then.