Canard

Yes fixed. Thx

The Control Wizard in Wags 2.9 radio video. I must have missed that (and can't see it in my version of DCS). I put all my hope in that little button for now until the harsh reality kicks in and it will not solve my problem with to many modules and controllers. The control admin time will soon pass the flying time .

Really happy with my Aero (previous G2 and 8KX user). The DFR-modding recently was like a brand new headset from an already good experience. When I needed the Varjo support they were super helpful and quick .

Love the campaign, Baltic! I'm at mission 9 and will continue ahead even if you have teased quality of life improvements in the near future. I am really looking forward to a quicker, more immersive, way to interact with "a" or "b" responses.

Yes, still a problem with the same workaround fix.

Thx for all the tips regarding stutters and performance cores to you guys. On my new rig I had (or have) the same problem but have not installed process lasso yet on it (or ventured into the bios) . I was getting a little frustrated when moving my head it felt almost glitchy no matter what resolution or position of trackers I tried. I’m on a 13900,4090, Win11 and Varjo base 3.8 + OpenXR. A work around “fix” for me regarding stutters at this time seems to be change the priority in task manager for one of the Varjo processes to high (Varjo composer). On my system I can reproduce it with headset on in desktop mode and changing the priority from normal to high. In reverse it comes back. It practically eliminates both up/down and side to side “jumpiness” (Desktop, DCS and MSFS2020).

Sometimes I wish it was possible to just [modify-key] + click on a thing in the cockpit and a dialogue would pop-up “press a controller button”. Binding done and saved. It would not be suitable for everything like axis/hotas but I guess it would speed up the process and lessen the hassle of finding the control in the long list of commands to bind. I usually know visually where most of the “things” are that I want to bind.

I have added small clear bumper pads (from Amazon… 3M i think) on all my controller keys (including the Streamdeck). 1 or 2 on some strategic keys helps to navigate in the VR-darkness by feel.

Same/similar solution here. I used the last 5% of the max-min range of the front slider to trigger a button press/hold. Works fine.

This is only a comment based on my experience going from TM warthog and the Monstertech table mount to the full Virpil (insane spendapalooza) T-50CM2 with the 200mm extension and Virpils own mounts. So, I can’t answer your good question about the warBRD but: - For me, the long extension for the T-50CM2 really makes a difference. I can’t go back. I went from 100mm extension on the TM warthog and monstertech to 200mm Virpil. This is most def something that is a personal choice what works best (and the Virpil base itself probably stands for most of that improved feeling) - I was surprised by how much I like the Virpil mounts. Easy to mount, allows for better cable management, flexible + cool. I changed to them because of the 200mm extension (I think maybe 100mm is the sweet spot for the Monstertech mounts?). - I had the exact same idea to use my TM Hornet grip but only when flying the Hornet. This has not worked for me. The grip works fine but I am struggling with the VIrpil software when changing grips (It is probably a me-problem). If I was sticking with only one grip the Hornet grip works great on the base. I will keep the Hornet grip (I love it) and try to solve my swap-problem later.

I have experienced that problem a couple of times (when changing headset and computer) during my use of it. I can’t say exactly how it works but my fix as I remember it has been under options and the settings for compensating for standing or seated(?) (I am not in front of the app right now) . Maybe it is linked to how my VR-room setup is done and where the center is for the headset. After some trial and error I get it to stop floating me above the canopy after each turn.

I use this one https://totalcontrols.eu in VR and I personally love it. Not cheap at all but I’m using the F16 / F18 up front functionality much more. I find that the spacing and placement of the controls really works in VR (for me). The dobber was a real pain before and I hated trying to manipulate it.

Hi ChainsawAkimbo, I'll add my rules from Bome (for XTouch). They do the job but it is after some trial and error and can probably be a lot smarter. In short: I use Bome to clean and modify the Midi-signals to be used in Vjoy. I found that Vjoy was not able to react to all types of midi-signals so Bome converts the signals to something that can be used. So, My flow is: Xtouch sends signals in to Bome and I use Bome to send modified Midi-signals out in a virtual midi-channel as output. In vjoy I convert the virtual midi-channel to control-inputs as a controller would do. Some tinkering was necessary there also (like axis to button if I remember correctly). The slider-part should be the easy one. In VJoy just trap the MIDI signal Axis (midi) to Axis (virtual vjoy-controller). In Bome I just converted the CC-value for some conflict-reason that I had. Probably not necessary for sliders. The knobs increase/decrease-rule below is the most complicated and I have trouble reading it myself now . I wanted to convert movement to button presses for use in DCS. ------------------------------------- [x] Preset 0: X-touch All buttons [x] Translator 0.0: Button push Options: swallow Incoming: Note On on ch. 11 with any note set 'qq' to note with velocity:127 (0x7F), on port X-TOUCH MINI Rules: Outgoing: Control Change on ch. 12 with CC#:qq and value:127 (0x7F), to port Bome MIDI Translator 1 Virtual Out [x] Translator 0.1: Button push Options: swallow Incoming: Note Off on ch. 11 with any note set 'qq' to note with velocity:0 (0x00), on port X-TOUCH MINI Outgoing: Control Change on ch. 12 with CC#:qq and value:56 (0x38), to port Bome MIDI Translator 1 Virtual Out, delay:30 millisec _____________________________________________________________ (this one is for slider values - I use the slider and one volume knob as axis input, the rest of the knobs for ccw/cw values) [x] Preset 1: X-touch Slider 9 and Knob 8 [x] Translator 1.0: Slider 9 to passtrough Options: swallow Incoming: Control Change on ch. 11 with CC#:9 (0x09) set 'pp' to CC# with any value and 'oo' to value Outgoing: Use 99 instead of 9 to avoid conflict with button 9 [x] Translator 1.1: Knob 8 to passtrough Options: swallow Incoming: Control Change on ch. 11 with CC#:8 (0x08) set 'pp' to CC# with any value and 'oo' to value Outgoing: Use 98 instead of 8 to avoid conflict with button 8 _____________________________________________________________ (This on converts knobs to button presses ccw/cw) [x] Preset 2: X-touch Relative to simulated button on (1) [x] Translator 2.0: Knob CCW Options: swallow Incoming: Control Change on ch. 11 with any CC# set 'qq' to CC# with any value and 'x1' to value Rules: rr=qm qm=x1 if x1>=rr then exit rules, skip Outgoing Action qq=qq+50 Outgoing: Control Change on ch. 12 with CC#:qq and value:1 (0x01), to port Bome MIDI Translator 1 Virtual Out [x] Translator 2.1: Knob CW Options: swallow Incoming: Control Change on ch. 11 with any CC# set 'qq' to CC# with any value and 'x2' to value Rules: if qq==8 then exit rules, skip Outgoing Action if qq==9 then exit rules, skip Outgoing Action rs=qs qs=x2 if x2<=rs then exit rules, skip Outgoing Action qq=qq+50 Outgoing: Control Change on ch. 12 with CC#:qq and value:127 (0x7F), to port Bome MIDI Translator 1 Virtual Out [x] Translator 2.2: Clean up after 60ms Options: swallow Incoming: Control Change on ch. 11 with any CC# set 'uu' to CC# with any value and 'xj' to value, on port X-TOUCH MINI Rules: if qq==8 then exit rules, skip Outgoing Action if qq==9 then exit rules, skip Outgoing Action uu=uu+50 Outgoing: Control Change on ch. 12 with CC#:uu and value:62 (0x3E), delay:60 millisec

I have used my Pimax 8KX KDMAS for a couple of months now with 2 lighthouses and a 200g counterweight at the back of the headset and I like it a lot. The FOV is of course great but my main “plus” is that I am moving my eyes more and my head less than in the G2. One glance down and I can scan all or most of the instruments in one motion. Disclaimer: Based on my experience, nothing more or less. I liked the G2 also but I probably had an IPD-requirement (close to 70) that was pushing it and made my experience less good. I was in the beginning really missing the sound in the G2 but I have noticed that positioning the KDMAS perfectly over the ear makes a big difference and it is not an issue now. I use the beta firmware for 90hz and the Pimax experience-app for setup and launching DCS. No issues at all at the moment.

Old topic but I also use the X Touch Mini with a licensed copy of Bome Midi translator. I looked into using some of the helpful tips above but found them not for me by various reasons. I use vJoy to convert the output from Bomes rules/scripts to controller buttons and controller sliders instead of keystrokes. Kind of fidgety at first but works great with some work-arounds in both vJoy and Bome. I also got a Akai MPD218 pad controller. It looked great but I didn’t like the large and soft ”finger-drum-pads” in game . It is now replaced by Total Controls Multi function Box.