Jenrick

Are any of those flyable right now? I'm not being flippant, the ability to actually use a module is a big issue. Screenshots can look amazing if they don't have to do anything besides look pretty.

As a kid we had a voice module for our Apple 2E, it sounded even worse than the APR-39, and it was considered state of the art back then. I have no doubt it's probably even harder to understand in real life. It's not a recording. It's using a very bad speaker and math to try and generate something that sounds like a human voice to say words. A very compact and low fidelity synthesizer.

The armament system does have keybinds for off, standby and armed. If you mean the ignition key, then I haven't looked that's a mouse thing for me.

It's a stored value, so set is and forget it in SP should work.

So long as you don't have the same keybinds in use on the copilot side for something different, they'll still work if bound on the pilot side controls. I have U and J bound to increment and decrement the radio channel in the pilot controls. They work just fine on the Co-pilot side so long as I don't bind the U and J keys to anything on that side.

You mean to move it? I just used active pause to set it up, and then left it.

Good to know, thank you!

You need to bind a key to the frequency change, clicking the button on the cyclic doesn't work right now. I don't think assigning a button works correctly right now either, but a keybind does the trick. Not sure on the PTT, might have the same issue with binding a controller button.

Just tested it, that is correct.

When you add a prepoint location it adds it to the list, and IIRC tapping the PPT button moves to the next one and you can add another.

I thought that was for hover only?

My understanding based on one of Casmo's videos is that that SCAS in the Kiowa doesn't do near the stuff the system does in the Apache's FMC/SCAS/SAS combo does, as it has no hold modes. The force trim in the Kiowa works similar to the Huey, it just holds the stick in the spot you leave it. Per Casmo most Kiowa pilots didn't even mess with it.

So far no, but that apparently is under consideration.

In the prepoint mode of the MMS hit the prepoint button (R2 I think, not in front of my PC). Type in the target number (for example 97T), hit enter, and slave to it. Just like you would waypoint.

I'm not having to "re-zero" every time I load up DCS, so I'm assuming they persist.

It's in the AI pilot options, default is LAlt+F I think.

I'll add a simple one, add an option for no tracers on the fifty, primarily for night operations.

I prefer the PC AI setup for telling my AI pilot where to go and how. I find Petrovich and George (PaG) both cumbersome in comparison to use with the combination of modes and short/long presses. If PaG used something akin to PC's controls for helo movement, and kept the combat control flow they have currently I think it would work nicely.

1 meter is approximately 3.3 feet, just multiply.

Mind posting the mission, see if we can replicate the issue?

The AI Kiowa will engage with their M4 depending on how you have them setup in the mission editor. Ironically I think Bombing with the weapon selection left on Auto resulted in them forgoing shooting APKWS and instead going rifle.

Turn off tht FFB under the misc tab in the general options.

Make sure you're in constraints (solid box), what usually gets me is the second missile defaults to B laser code.

Should be doable with the FAC script that came with the OV-10.

There is no chaff, and there are no CM programs. This is accurate to real life to my knowledge. Flares are 1 per press when on bypass.