mondo

Yeah, it's pressed down as hard as it can be but there's some lateral movement where there shouldn't be. I've opened it up tightened everything down and got rid of some of the play but ultimately it's a poor design, especially with one part of it being plastic.

Fixed of a sort in that I'll just bite the bullet and buy the upgrade kit that deletes the three pin connectors. It's a terrible design choice that VKB themselves sorted between the Model 3 and 4. The other option was the much more expensive selling the grip and my old Gunfighter 3 and buying a Virpil Flanker which apparently is a direct mount onto the AB9.

Yeah, IRQs aren't something I've even thought about in decades. The adaptor on the VKB base doesn't have an connection to the AB9 base other than a screw fitment. Essentially windows sees them as two completely separate devices. However you got me thinking - there's some slight movement in the VKB adaptor and the signal is being created with the pins in the VKB stick by the looks of it. The terrible VKB 3 pin connector strikes again. Cheers buddy.

No, it's near the end of the travel. It's nothing physical as I can disconnect the stick and move the base and it still sends the signal. It's like the AB9 is sending a signal momentarily on the same channel or IRQ as the axis the lever on the stick is on. It's almost like they all need to be forced onto a different IRQ.

The problem is outside of DCS by the looks of it. If I rotate the AB9 I can see a momentary input in the VK software on the axis for the lever.

So I have weird problem I can't solve and I hope someone here may have some advice. I have a Moza AB9 with a VKB MCG I'm using a VPForce adaptor to connect the stick to the black box. The problem I have is the base is sending momentary inputs to the same channels as the axis on the stick. For example, if I move the AB9 on the X Axis it momentarily moves the axis the AP disconnect/brake lever is on - regardless of the settings I assign in the VKB software. It will also send signals to the virtual axis for the flip trigger but only if I'm in the F14 which is really weird. It doesn't do that in the Phantom. I've changed the port that the AB9 uses but it doesn't help. The only thing that seems to deal with this is to turn off the functions associated with the VKB Trigger and brake which is a bit crap. Neither device plays well with Windows Game Controller so that's a non starter. There's no actual physical or electronic connection between the stick and the base and I've had the stick previously on a Gunfighter III without issue. TL/DR Move axis on AB9, it moves both its own axis and that of the MCG. Halp.

It's entirely possible to beat the Mig 29 in the merge. As you merge keep on flying. The Mig 29 will run out of fuel catching you up. Manoeuver kill.

Imagine a Hip where all the switches and buttons are in logical locations. Like all the electrical systems being in the same place, the radios being in the same place, auto pilot and stability systems being in the same place etc. That's the Hind.

The problem with the Hip is someone designed the cockpit by loading a blunderbuss with switches. In contrast the Hind has all the same systems plus a few more and is very straightforward to start up.

This is the issue, my positioning is good. I'll record a track next time I can be essentially I'm flying a climbing intercept course towards 4 Mig 21s on the Afghanistan map, they are 30k ft and on a 45 degree course diagonally across my flight path. There's nothing behind them and the sun isnt a factor. Im nose onto them from outside the radars range until they are on top of me. I can see the Migs on the radar myself once they are within about 25 miles but jester is seemingly unable to see them. I can however hit them using the boresight but that's not the issue.

With a real WSO would can say to them "point the radar 1 o'clock angles 21" or similar. With jester I have to navigate menus and all that's involved in those.

Yeah, a look here is what I need. All too often I can get aircraft 10 miles in front with zero background but clear sky and the guy can't see anything. I'm aware of things like boresight mode but this is for visual targets outside of that range. As I understand that's limited to 5 miles. I'm aware of the various radar modes and uses but this is to simply tell jester to point the radar to a location, the same as I would say to a real WSO without having to go through a series of menus.

Could we get a feature like that in the Tomcat where you can use head tracking to direct jester to point the radar? I can get visuals.on targets from below and away from any background noise and the poor guy just can't seem to even see planes half the time. By the time I've managed to get him to move the radar I've gone passed the point of needing him.

There's some info on the ED discord and it. If you go to the bugs channel and search for shrikes there's a few issues and one of them has a table. But it's not something that ED has updated so the test information is just what players have figured out.

Shrikes are currently a bit buggy but they do work in same instances. Personally I take mavericks in most instances.