DZ82

Yes, I've had it happen too. If I clench my fists and open my hands again, tracking seems to be fine again.

Thanks again. Looking forward to trying some of your suggestions

One more question for you - can you reach the fuel panel on the left, without bumping into your Hotas throttle?

Excellent idea. I'm definitely incorporating that into my setup, thanks!

Can you tell me a bit more about what exactly you did with the modified CMS switch? I'd like to try, that sounds awesome. I'll try the switches again, thanks for the advice!

Thanks, I had mine on the front as well, using the leap controller mount, but didn't have great success. Struggled flipping switches successfully on the first try. Moving it to the top greatly improved accuracy for me. Happy flying

Hi All, I posted recently asking for help because I was struggling quite a bit with Leap Motion in DCS and getting it to work, but after countless hours of fiddling, I have come up with a solution that works for me, perhaps someone else can benefit as well. It works really really well. I have attached some pictures of my rather crude setup. I was regretting the buy, not considering PointCntrl first, but not anymore! 1) So I use the Oculus Quest 2 and I run DCS from Steam VR 2) I have the latest version of the Gemini software 5.3.1. Under "Special" settings in DCS, I make sure that neither hand shows the pointer. The pointer does mess things up a bit. I make sure this is deselected every time I load DCS (by choosing anything else, then back to no pointers, to make sure it doesn't come up in game) 3) Make sure your DCS sim runs smoothly in VR before fiddling with this, it just makes the entire experience better 4) I experimented a lot with angles and placement of the leap motion controller on my headset - and what worked best? Mounting it on top of the headset! (It looks ridiculous, but I don't care, it works) 5) I mounted it with sticky velcro tape to the top of the headset, using 2 small plastic square brackets to stabilize it 6) You will see in the pictures that the motion controller is tilted back a bit, what this does in practise in DCS, is to render your hands at a lower position when you look at your cockpit (Tilting it forward will bring your hands up higher). You can play around with this a bit, but tilting it back really helped me to reach buttons like those on the NMSP 7) The next issue is bumping into stuff when you try to press a button, right? So yes, you need to make your environment as lean as you can, but what really helped me a lot was to use the "Recenter VR view function" (Can't exactly remember the correct name) in the control settings (under UI layer). What I do is to start by sitting comfortably, but moving my chair back - a bit further back than where I want to sit playing (maybe 3-6 inches) . I then recenter my VR cockpit view, and move my chair forward a bit after that. So this makes you move further forward in the cockpit, closer to the front panels. This brought the MFCDs and NMSP easily within reach, without hitting my surroundings 8)I can very easily reach and manipulate any button in the cockpit, without trying to flip a switch 15times before it works. First time, every time 9) You can also easily flip switches up, by turning your hand, palm facing up. (Like cycling the IFFCC switch to and from test) 10) I can rotate the course/heading knobs by basically touching the left side of the knob with my left index finger (keeping it there, so palm facing the switch), which rotates it counter clockwise, and by touching it on the right side with my right index finger (which rotates it clockwise, again palm facing the switch, so your index finger will be on top, and your little finger/pinky at the bottom) 11) I do struggle with rotary switches like on the AAP, still need to work on this, hopefully this will improve in DCS. Have the mouse handy as a backup 12) If your chair can swivel, use it. I sometimes swivel may chair slightly in different directions to avoid hitting things in my sourrounding and reaching buttons on the side panels. 13) Reach over or lean over a little if you need to. For example, reaching the APU switch next to the throttle can be difficult, as my chair armrest gets in the way. I just lean over it a little, and voila, easy 14) I use "double tap passthrough" on my Quest within the game. (https://support.oculus.com/articles/in-vr-experiences/oculus-features/what-is-passthrough/). By activating this and double tapping your headset, you can see your surroundings, like when you set your guardian boundaries. I use this to quickly look at my Hotas if I want to physically flip a switch, and double tap back into the game, no issues. 15) Make sure the cable running from your motion controller to your PC doesn't pass on front of the controller in any way. I had some issues with tracking my right hand, before realizing that the cable caused it. 16) Lastly, I use a mouse like the Redragon M908. I programme the side buttons for the kneeboard, pausing, F10 map etc, so no more keyboard near me when I play. Hope this is of help to someone, it's really enhanced the experience in DCS for me. 20220123_211111.zip

Hi All, I invested in the Leap Motion and the tracking using the software is pretty amazing, but I have not had the success as posted by some other members in DCS. I have attached a crude video to show you, I struggle flipping switches with my fingers, so figured maybe using the mouse pointer would work better. All in all, very hit and miss. Sometimes I manage it, mostly (as in the video) I have no success. I use Gemini 5.3, so there is no option to recalibrate etc. Dan from Leap said this is not a tracking issue, but an integration issue with DCS. A different user mentioned the importance of camera commands in VR to get this to work, but as far as my limited understanding goes, there is only a ZOOM toggle for VR - so I am not sure what this means Is this a question of "we're not quite there yet", or does someone have any advice? Not to keen on going on a pointctl waiting list for a year, by that time, Leap Motion will probably work great. Maybe Thanks LM DCS.mp4

That's a good suggestion, thanks! Should help with troubleshooting, Will report back and hopefully help someone else as well.

Hi Boltz, Thanks for your response. I still can't get it to work, but I will also troubleshoot this a bit, re-check all the wiring etc. When you do get around to trying it, please let me know how it goes. Yes, there are other ways, but for now I am determined to figure out (with lots of help) why this isn't working right now.

Thanks for this suggestion. It certainly is plan B, perhaps just easier to go with that. Would still be great to solve this, it's driving me nuts!

Hi all, I am trying to combine multiple CDU buttons for the A-10C to function off a single pin. I have connected 220ohm resistors between each button as voltage dividers, so my plan is to use the analog values that register with each button press to register each button on the CDU. The single button example below compiles in Arduino IDE (this is button2 in a series of 3 buttons connected to pin A0), but doesn't work in DCS. I know this is probably not correct, but I don't know how to fix it. I will try to fiddle around in the meantime, but would appreciate any input! Thanks! void loop() { DcsBios::loop(); buttonValue = analogRead(A0); if(buttonValue >= 678 && buttonValue <= 685){ DcsBios::Switch2Pos cduA("CDU_A", A0); } }

Thanks for the suggestion, will order and give it a go! This cockpit building thing is a dark, deep rabbit hole!

Out of desperation and frustration pehaps I can use 2 boards - an Arduino mega and Uno for example, and simply do one button one pin? I wanted to keep cost down by combining cdu and aap on one biard.

Brilliant! Thank you. I found this Arduino Sketch that communicates with LEDs, now I need help on how to communicate the button presses/ switch toggle with DCS. For a simple 2 position switch I would use, for example: DcsBios::Switch2Pos ahcpCicu("AHCP_CICU", PIN); But how do I incorporate this into an if loop (I am assuming this will be the best solution), I don't know what say instead of the pin number? void loop() { buttonValue = analogRead(A0); //Read analog value from A0 pin //For 1st button: if (buttonValue>=1010 && buttonValue<=1015){ digitalWrite(yellowLed, HIGH); } //For 2nd button: else if (buttonValue>=1000 && buttonValue<=1008){ digitalWrite(redLed, HIGH); } //For 3rd button: else if (buttonValue>=990 && buttonValue<=998){ digitalWrite(blueLed, HIGH); } //For 4th button: else if (buttonValue>=870 && buttonValue<=880){ digitalWrite(greenLed, HIGH); } //No button pressed, turn off LEDs else{ digitalWrite(yellowLed, LOW); digitalWrite(redLed, LOW); digitalWrite(blueLed, LOW); digitalWrite(greenLed, LOW); } delay(100); }