Weta43

Make sure you're not in route following mode too.

As QuiGon said, I wrote "E.D. will have released..."

& as you were told, it never was, that's not your problem.

It's the best way to get a few thousand testers checking features as they're added. If you think you might be one of those people that buy an E.A. module having been told it's not feature complete, has bugs & will continue to have bugs appear as features are added, then be unhappy that it's not feature complete, still has bugs and that new ones appear as features are added, and are likely to spend the next however many months clogging up the forums complaining that the early access module isn't feature complete and has bugs, or isn't progressing as fast as they expected, please do yourself and the rest of us a favour and wait till you read it's feature complete.

Think of it this way: When we do get the Mi-24 E.D. will have released 3 Russian helicopters, of which 2 are attack helicopters, and only 1 Western helicopter and zero Western attack helicopters

Twist stick is fine - that's all I used for years (& that was with the Mi-8 and Huey) until the twist started getting spikey

They may be flying, but do they have original engines / weight distribution, and is someone prepared to let E.D. put one in a wind tunnel / fly one hard to get some performance data. If not - it makes the model & textures easy, but not much more...

What (I think) he means is : You put enough forward cyclic in to get the aircraft 10 degrees down, and as it passes through 5 degrees you let go of the trimmer. The joystick stays where it's trimmed, and the control authority of the AP takes the aircraft back to 5 degrees (the nose rises after you let go of the trim). But although the aircraft is flying at 5 degrees, the stick's deflection would generate 10 degrees if the AP weren't countering it. At the point that you push the trimmer in, the AP stops fighting the stick, and the aircraft moves from 5 degrees nose down to 10. To make sure that this isn't part of the problem, you'd have to make sure that the aircraft was stable in both pitch and airspeed before releasing the trimmer. I use an FFB stick and the FFB trimming method, and if I do make sure the aircraft is stable before releasing the trimmer, I get the result I mentioned above.

& to date, they have been doing that, and they haven't said they won't continue to. They have said they're having trouble getting detailed enough data to work with - that's a good reason. Also - personally - I wouldn't expect them to put the highest possible priority developing modules that a significant part of the full price early adopters market will get for free...

Maybe - it doesn't drop with a jerk though, it just slowly starts to drift down if I hold the trim in for more than a second. No curves - Good (in that at least it eliminates something), but using curves does make a difference if you're actually using FFB, as the FFB is set to always assume no curves for providing the FFB for the trimmed position (the FFB assumes a linear relationship between real stick position and SIM stick position, but with curves that doesn't exist), and so the trimmed position & reported position of the stick end up misaligned if FFB is on and there are curves set on the pitch and roll axis. That would mean there was a tension between the point the aircraft's AP was trying to align to and where the stick was trying to fly the aircraft to, and one side of that tension would be relaxed every time the trimmer was pushed... There are threads about it and E.D.'s advice is no curves with FFB sticks...

Just tried it with the MSFFBII - no pitchup at all. At a stable altitude and 240km/h, actually a very slow slight nose drop if the trimmer's held in, nothing else. Do you have curves set on your controllers ?

Paid money for - but to a company that no longer exists, not to E.D...

No, because it's people not understanding what they are doing when they use the OB that causes so much angst in the community. People don't read what they're signing up for, then complain endlessly when what they signed up for comes to pass. Rather than pretending the OB is not an OB, what they should do is put in f*ck off big letters on the OB splash screen a message reminding people that it is an OB, will have bugs, may occasionally introduce bugs with new features, and make them click an "OK, I understand" button every time the OB launches. A message to the effect of: "If I find a bug, I agree to report it, not complain about it" wouldn't be a bad idea either.

As you said - they need them "when occupying a side door Gunner (and hopefully in future the rear gunner) and you can't be in controls". An autopilot that could fly an indicated path & maybe jink / avoid fire / use CM would make behind the Kord a reasonable place to sit...

In my bizarre alternate universe, I thought there might be people that were interested in either the AH-1, or the F-4, but not both, and so might not read both threads (personally I could care less about the AH-1 (waiting eagerly for the Hind ;-), and only posted in this thread by accident, but there you go...). Ridiculous thought I know - obviously every reader of the Forums reads every post in every thread....

Wrote this in the AH-1 thread & it's just speculation on my part, but it's possible that Belsimtek got pretty close with the F4 (As Belsimtek said, they had it flying internally), and were working on getting their Autopilot AI to work (that much we know), but that while the new AI was a step forward from the Autopilots of the Huey and Mi-8, it was still in that vein. Then when they came back in-house - & with the F-14 out - it was decided that the Autopilot AI & interface wasn't going to compare well with other products as it was then conceived, so they have put aircraft that need that functionality (aircraft that need a full RIO / WSO) on hold until E.D. have their own version of that kind of WSO AI that will compare favourably with the Jester. Edit: Not sure how that fits with the M-24, but maybe that was too close to ready & too anticipated to make sense to sit on it, & maybe they figure we can get by with a better autopilot. Maybe we'll see how the new AP came out.

Speculation on my part - It's possible that Belsimtek got pretty close with the F4, and were working on getting their AI to work (that much we know), but that while the new AI was a step forward from the Autopilots of the Huey and Mi-8, it was still in that vein. Then when they came back in-house - & with the F-14 out - it was decided that the AI & interface wasn't going to compare well as it was then concieved, so they have put aircraft that need that functionality (aircraft that need a full RIO / WSO) on hold until E.D. have a version of that kind of AI that will compare favourably with the Jester. Edit: Not sure how that fits with the M-24, but maybe that was too close to ready & too anticipated to make sense to sit on it, & maybe they figure we can get by with a better autopilot. Maybe we'll see how the new AP came out.

Work the radar at night ?

Definitely sitting in the "glass half empty" camp today eh ? :) Seeing as the Huey came out first, meaning early adopters have been waiting for longer than Mi-8 owners, adding the new tech to that first seems both sensible and fair.

But obviously not using E.D.'s TWS code (otherwise E.D. wouldn't have to delay implementation until the code is finished …)

WTH ? After years of complaining & asking for the ability to have both a human pilot and co-pilot in MP, the moment it's announced it's about to arrive, people don't even wait till they've said 'great' before complaining that they just want MORE!!!!

Either G.55 only 350 delivered, but still a production aircraft... or Macchi MC. 205 :)

The F-16 was released in a much less developed state, and E.D. are making amends to the purchasers ? Seems a reasonable goodwill effort....

I've only had the throttle connected from my X-52 for ages (that + MSFFBII), but I did use the mode switch to get different functions. At the very least DCS recognises modifiers - can't you make the mode switch cause the output to be CTRL + Key / ALT + Key / SHIFT + Key ?

There are already some published if you use the search function