TED

Yeah 20cm is a bit too long. I'm just gonna go for 10cm. Basically I need to mount the base a bit lower so it fors better with my NLR rig and add a little more precision for rotary stuff.

Has anyone tried using an mh16 grip with a warthog extension or virpil and the cables used for a them? This would be an ideal solution as well, as I could use the mh16. Unfortunately seems like moza doesn't sell any kind of cables themselves. The virpil extension with cable is only 25 Euros and seems pretty decent. If it works might be even worth buying the curved version.

I want to add an extension and already have a winwing stick with extension, so would save having to buy the moza z-axis one. I do have the mh16 and it works great so I may just use a warthog extension if that works.

I recently picked up a new moza ab9 base and the mh16 stick and I have to say I’m really impressed with it. It is a huge improvement to general immersion and feeling. I honestly could not go back to using a traditional base again. I am trying to use some different grips and picked up the vpforce rhino winwing adapter and the vkb adapter. Both connect ok. The vkb is the simplest as you still use the black box, so all buttons are controlled through vkb software. However using this solution I lose the ability to control mechanical trimming of the base as well as force trim release, which is a bit of a non-starter for me. With the winwing, it connects ok however the ww16 stick selection in moza cockpit does not work at all. If I select another grip from the dropdown it does work! So I select the Virgil alpha grip and it will sense some of the buttons but not all. Very weird. Has anyone managed to use a winwing grip on the ab9 and get full functionality of all the buttons?

I get the same with a 9800x3d and never fully understood why.

Has anyone else built this yet? I made the original with the button matrix a few years back and now have a PCB but my design abilities are not great, so I haven’t been able to modify the original design to encompass the PCB. Has anyone else managed to do this and use the PCB?

I'm using a 7900xtx and 9800x3d and it's been stellar. I get a solid 90fps with my quest pro and VD low level in f16 in Afghanistan. Most dcs settings maxed except shadpws. PD 1.1 and VD godlike. It looks great, clear and sharp with no stutters. If u are having issues with this setup then look at your tuning.

Master arm was on. I'd just dropped jdams previously. All the indications showed they'd dropped, which wouldn't have if not armed, so a real mystery! I did another run yesterday and this time they dropped although the impact point was well off as was the 200' interval I'd set.

I’m not sure if this is a bug or user error and these days the user base seems to be posting less and less. Anyway, I’ve been away from the f15 for a while and the last days getting back into it to see how it is. I was trying to use blu 107 on an airfield runway. Set to CDIP, R.SGL, N/T. I am carrying 12 bombs and dropping 6 at a time with intervals of 150’ set in the PACS. As far as I can see I’m following the manual and used to do this quite a bit. I fly a low level pass, pipper on the runway, it designates and appears to release. I see on the armament page 6 bombs have gone, I get the relevant hud release symbology and get a little kick in the haptic seat. As I bank around and check there are no explosions. I then checked the f2 view and lo and behold all bombs are still on the rack! I checked the track replay and see that they don’t actually drop. I don’t have the track file at hand right now so can’t attach it. Just wondering if anyone else has seen this, if it’s any known issue or if I’m missing something in the setup?

This just happened to me today. Also Afghanistan map. Straight and level trimmed out transiting back to Kandahar, a sudden nose down. Short finals to landing sudden pitch up. I've flown hundreds of hours on the a10, albeit not many in Afghanistan, and this is the first time I've experienced this. Quite noticeable.

To be perfectly honest, I just don't understand anymore why people use quest link when virtual desktop is so good. In my experience its just better in every way. Certainly worth a little effort to get it all running, then just uninstall all meta rubbish. Its a constant lottery with every new meta update as to what it will have broken this time. I've had almost non issues since i started using VD a couple of years ago. Any issues i have had, have been due to my own configuration mistakes. Once it's working, it just works. It seen like the developers actually test it thoroughly with multiple headsets and multiple games, including dcs, before they release updates. Its pretty rare if ever an update breaks anything and it just keeps getting better and better.

I’d love to get metalink to work properly just to see if it really compares, but alas - meta says no!

I gave up on Link almost immediately after I got my quest pro and stuck with VD. No matter what I do with link it looks like a mess and none of the settings seem to adjust the graphics and resolution. No idea why. I reinstalled last week and tried again out of interest and its still a blocky mess compared to VD. The difference is huge. I know it’s not supposed to be like this, but to be honest when VD just works, I can’t be bothered messing with link trying to work out which bizarre setting is conflicting with what and why none of the sliders make any difference whatsoever. For such a big company Meta really have messed up on the software side for vr.

Managed to get hold of a globular cluster for the QP. Totally different experience now and solved all comfort issues. Very comfy to use now, so thanks to all those who suggested this as the solution.

Yep. Forgot to check other Amazon stores. Ordered now and hopefully that makes it a bit better.