spiddx

While I agree it's a nice addition I think you kinda opened a can of worms with that one. Now everytime someone demands a triple AIM-54 rack on their WW2 fighter the argument being made is: "But Leatherneck did it too with the Grom and nobody's complaining!!!" Just sayin'... ;)

Yeah there's someting pretty weird going on with the AP after the latest patch. We've talked about it here: http://forums.eagle.ru/showthread.php?t=159270

Where did you get that from?

Hmm, we are talking about 1.5, right? Because they work for me there while they don't in 2.0. Audio Warning switch in the middle position. (No idea, what the top one does) Main Battery switch on. I get the continous tone for red warnings and the short chime after 20 sec (and then every 20 sec) for amber warnings. Edit: It could be argued that the first chime should probably sound when the light comes on and not after 20 sec.

See post #17 of this thread.

So there's defintitly more to it... AP also automatically switched to standby over mountains when you are at very high altitudes (above ~48.000ft).

Can confirm this. I'm using those, they are very well sorted and easy to understand. Also they got rid of all the unused stuff from FC3. This is how a control setup should look like. :) Highly recommended.

The same issue exists in 2.0 Nevada by the way. It isn't a big problem there because most of the terrain is quite high above sea level, but if you fly for example over the Death Valley area, you get exactly the same behaviour from the AP.

After flying straight for two hours mashing the AP master button like a madman I think I've narrowed the problem down quite a bit: The AP seems to have a problem with the terrain elevation below the aircraft. It works in hilly or mountainous terrain. It doesn't work over the sea or near-sealevel flat terrain. To reproduce: - Start in the air over the sea - Turn on Autopilot Master (it goes to yellow/standby, no other modes functional) - leave it on standby and fly over the coastline (for example near Batumi, you have nice mountains there) - as soon as you come over the hills AP will turn on by itself (green), all other modes functional - fly back out over the sea => AP flips back to standby... Hope this helps.

visual

After the latest 1.5 update I get some strange behaviour of the autopilot. Take Instant actions for example: AP works in some of them (Free Flight, Intercept, Ground Attack) and not on others (Dogfight, Landing). ME generated missions are a no go too. When it works: AP master switches to active (green) immediatly, all other modes are available. When it doesn't work: AP master just toggles between standby (amber) and off. No other modes selectable. I haven't figured out yet why it works in some missions and not in others. Can somebody confirm?

Nah that one is to counteract the inertia from the spinning dish for sure. Seems pretty efficient to me! ;)

Ah i see, thanks. :)

Anyone else heard the new "Ding Dong" sound during startup? What does it actually indicate? :dunno:

Same here. Happens with GBU-16 and -24 as well.

There are two radios in the Mirage: Main (UVHF) and Aux (UHF). You have to select the correct one before opening the Comms Menu. Keybinds for both radios i think are in the HOTAS category. In general you contact your flight on the Auxiliary and ATC on the main radio.

...which is also fixed in the 2.0 update btw. :smartass: Chris: select "NEW" in the bottom left corner. :)

Jep there's an error in the mod, but you can correct it easily yourself. Just open the file, delete the AIM-9 line for pylon 8 and add it to pylon 9. Save and you're good to go.

Yeah i guess it can be stored upwards (the way it looks in 1.5 atm). Zeus mentioned that all this stuff will be interactive in the future.

Not yet. Wouldn't make too much sense now IMO since many of the systems aren't implemented at the moment. The developers said there will be training missions in the release version, and Baltic Dragon is working on a campaign.

Yeah 1.5 isn't updated yet.

In 2.0 with the panels on the right side open you can see another compass-like instrument below the screwdriver. (It isn't moving at the moment though)

Works already in 2.0.

I see, thx.

Maybe it's already fixed in the new 2.0. Anyone tried it yet?