Azrayen

Agreed. This being said, memory could probably be lessened for STT signals: those have short period of recurrence, due to their very nature. Don't know what is doable in DCS on that topic, but seems a good idea "from the top of my head".

Answered here: http://forums.eagle.ru/showthread.php?t=169091 APP mode is still WIP. CP/PD not available yet.

Which actually could be even more than 8".

Obviously a broken bulb then :D

I guess engineers must have found useful to "free" a button on the stick; and I agree with them :) On an almost related topic: aircraft is invariant, no final "s" even when there is several of them.

altitude of TDC min / max or center beam

Indeed :) My comment about missile type remains valid though.

It could (should?) be powered already for in-flight start, like the RWR; didn't check.

No. D2M detects missile exhaust plume. It doesn't care what the seeker type is. And as said earlier, not implemented yet.

This is not a bug. Rather a fix for previous incorrect implementation ;)

What is missing is the salvo "hard" stop. If you click the trigger the let it go instantly => you get your salvo. If you maintain the trigger => salvo, salvo2, salvo3... until you're empty. So yes there is a bug, but you still can use salvo (ME setting + PAR mode + short trigger click)

Hi Saw the same thing last night. Plus another point, probably related: Look attached screenshot, I'm just about to overfly the waypoint (+/- correct coordinates) but the nav system tells me I'm 4.2NM from it. It looks like the drift doesn't impact the way the waypoint cross is displayed (or not "accordingly" at least).

NEVER move during alignment. Shorten alignment if you wish (as said by mvsgas), but never move the aircraft before you put the PSM left selector on "NAV".

Before answering I would like to know which alarm it is? The sound is to get your attention => done => then you should look at your alarm panel and see which one is lit? My money is on DECOL and my understanding is it's normal if you're not neutral trim. For now. There is a specific section for M-2000C topics...

It's done through the PCN (INS panel).

It's not outdated. VAD and BAD use the same "logic" (= offsetting) but, again, are different things. BAD = relates to a BUT. INS system. VAD = relates to a TACAN beacon. Independent from the INS. Not implemented yet. http://forums.eagle.ru/showthread.php?p=2691022#post2691022

No. Zeus said it's a whole new system, so you won't have the needed code in the current 1.5.3 stable; it's not about "just" swapping sound files. "Gear not down" alarm = no sound, just the lever blinking red. Triggered by low airspeed+RPM < 80%. "Gear not up" alarm = LIM (limit) sound + LIM light (WIP) + gear lever blinking red. Triggered by high airspeed.

Yes it is supposed to. Dunno if implemented yet, didn't try that. No. VAD and BAD are different things. VAD not implemented AFAIK (for now). To use BAD is like to use BUT, just a * should be displayed next to the BUT number in the HUD. I suppose you mean MRQ? Doesn't seem to work ATM.

http://forums.eagle.ru/showthread.php?t=156925 See first post, all changes are there. :)

^ this :)

OK then, if you know better than me what I think, I won't try more and will let you write your own answer. Enjoy :)

Uh oh... It's "late" but just in case: gospadin, you made a mistake. The switch you're referring to is not a radio selector. The radio selector is on the throttle (will be if not already fixed in DCS) with a 3-position combo selector+PTT. Positions are: (spring loaded) Select radio 1 & PTT / Standby / (spring loaded) Select radio 2 & PTT The switch you mentionned is to choose the audio amplifier. 1 is default, 2 is standby. Not very useful to simulate... What is "this" exactly? Refueling itself? Long time it works :) perhaps explains the silence ;)

I have no such recollection, npole.

This is a procedure only for those having problem with their throttle. Ususally a (physical) axis a bit wear-out, which DCS interprets as "not exactly at 0%" thus preventing start. Pushing the button enforces the "throttle = 0 exactly" situation.

Incorrect. Circle around target (HUD) = Magic lock. Already there. = = = = Later, we may get the triangle (when locks are "synchronised" radar (square) + magic (circle))