spiddx

There is no update for 2.0 today so a new module won't work with it until it is updated.

Did you update your DCS first?

But... it worked so nicely in that one video! ;(

That's because you don't have Magics loaded in these missions. The sensors are mounted on the outer Magic pylons so no Magics => no D2M. S!

Fishbed 42:19 Miggen Fishbed 49:21 Miggen

As a workaround you can leave thew comms menu open for the time being and the mouse works again. Doing this there is the white dot for clicking the comms menu open as well which you have to ignore. Obviously not a perfect solution but not too bad until the issue is fixed.

Der "What are you doing" Spruch kommt, wenn man sich bewegt obwohl noch irgend was von der ground crew angeschlossen ist (electric power, air supply etc). Bein Reparaturvorgang wird ja das Flugzeug angehoben und denn wieder am Boden abgesetzt. Das interpretiert die Sim oft als Bewegung und schickt den Funkspruch. Hat aber keine weiteren Auswirkungen und kann somit getrost ignoriert werden. ;)

TDC slew is fixed in development according to devs, should be ok after the next update.

The Mirage 2000 does not have a VHF FM radio, so you won't be able to tune into these frequencies. 118.00 is the lowest frequency you can use. (VHF AM)

Agreed. And thank you for fixing the axis. Much appreciated.

Lima Charlie is fancy radio speak for 'loud & clear'.

Yeah the only advantage I see in A/A is if you lose sight in the merge and the bandit takes a SRAAM shot from behind and below you. Nice to have but not too much of a game changer.

Can confirm, first message is hard to hear because of the other plane starting up. A delay of 5-10 secs should probably solve this.

Probably magnetic deviation. Mission planer map uses true north, while aircraft HSI use magnetic. Deviation in Nevada should be about 12°, 6° in Black Sea map.

Just tested (1.5) and can confirm: rockets can't be used if only loaded on the external pylons (1 & 9). If I select RK3 only INT appears (active by default, can't be deselected) instead of EXT, rockets don't fire.

IMO the best solution would be to simply make two different variants of the Magic, one with and one without the D2M pylon. Then depending on your loadout the system is or isn't functional in the jet. That way multiplayer mission creators can restrict it's usage if they want to. And in SP, who really cares?

Climb to around 20k feet and you should keep line of sight to the TACAN station. Works for me that way at least. €dit: Alternatively just use a differnent station, someting like TPH (119X) 130 for 55 should get you there. Use the mission planer with the ruler tool before entering the mission to find out your wanted radials.

And here's another one for subtitles, at least in the fam flight mission. Catching radials and distances while setting TACAN and HSI course all while landmarks are called out was a bit much. Had to interrupt the flight several times to take a look at the briefing. (Yeah I know, I could just have written all down pre flight...) Nevertheless great campaign so far, I obviously have to learn a lot about BFM in the F-5. Already stuck at the F-4s. ;)

Really? If my (rather tongue in cheek) comment was perceived that way, then I apologize. That was definitely not what I was trying to say. We all know it's WIP and I'm sure the devs will get it tuned perfectly in time. On the other hand looking at your equation are we really only allowed to post enthusiastically about future features or we risk comm lines being cut? I know stuff has happened and your defensiveness doesn't come from nowhere but this seems rather... harsh. Whatever. Loving the new Nevada, spent my whole weekend there. The mission and mulitplayer possibilities now seem endless. :thumbup: Great update!

wags says in the comments to the video: I agree that the effect is overdone. In that video Nevada sparkles more than a modern vampire in the sun. ;)

Just tested on the VA server, IFF works fine. SRZO and Typ 81 switches have to be on (as it has always been). My Mig also shows 1.5.4 in the title screen, so that can't be the problem. They probably just forgot to change the label.

It's the one directly above the audio warnings switch. Auto-start puts it in the top position, it's supposed to be middle.

You are mistaken. From the latest newsletter: So Normandy will come before the merge according to current plans.

Well it has changed. Now upon flap extension the nose drops rather significantly instead of rising as it did before.

I have seen several AI issues (not specific to this campaign) since the update to 1.5.5: AI not starting up, holding short of the runway and not taking off, crashing into each other during taxi and so on... Probably all stuff for ED to figure out and fix.