nomdeplume

Nope, that it depends when you think the last update was. See here for a short checklist. Things that seem to be catching people out at the moment are the throttle may not be properly back in the shutoff position (click the little red button just to the right of the throttle to check), and you now need to switch off the Fuel cutoff switch (with the red safety cover near the engine start button).

I think so. Pretty sure I didn't have any bonus points before, and I have $12 now, so if they're enabled for NTTR you should be able to use them right away. Can't promise anything though. Well what we've been told is that the module was 'ready' for the normal standards of early access, but they decided they wanted to lift those standards and instead release with a full manual and training missions.

Not sure. I think at present it may be too precise, in that any change of trim at all results in the light going on, rather than there being an "acceptable region". i.e. if you've performed the FBW test and the DECOL light is off, then you tap say trim nose down, the warning will sound immediately. Tap trim nose up, and the warning will remain. CptSmiley suggests a FBW reset to remove any trim, but I don't currently know how to do that.

DECOL will also come on if trim is not neutral. So if you trimmed at all during the flight, DECOL will activate as soon as you have weight on wheels.

You'll probably want to add the Special Modes DESELECT to disable the CCM radar modes and return to normal search. The Close Air Combat Mode SELECT button will cycle the CCM radar modes. Currently that should be sufficient, as Magic II SELECT cycles Magic/A-A guns. This doesn't really match the actual aircraft controls so you might want to allocate 3 buttons for future use: Magic II Select, Cannon Select, and neutral (use PCA); for when/if Razbam implement this fully. Then again, Razbam may well implement an additional control to cycle through the 3 modes for those that can't or don't want to allocate 2-3 buttons for this.

Here you go.

With rockets on the outer pylons, the emergency jettison button does not discard them. Neither does selective jettison. Possibly the outer pylons are just excluded from emergency jettison since it's usually Magic out there? Also, maybe this is correct, maybe not, but once you've fired all rockets they're removed from the PCA, so it's impossible to jettison the empty pods unless you do it immediately.

BLG-66 is not yet implemented, in-game the Mk-20 Rockeye is used instead at present. You can use Mk-82 (or Mk-82S) for AI runway denial at present.

Just you, sounds are fine for me. Maybe check any mods in use? There was a mention of "RWR sounds fixed" or similar in the changelog, though I haven't noticed any difference. But, something under the hood may have changed that could've impacted mods.

I think there's fixes for most/all of these cases in the open beta, which was updated a couple days ago.

The PID/TWS mode is still buggy. The radar elevation change is dependent on the aircraft's pitch. So if you're 10 degrees nose-up and select a contact, the antenna elevation will go 10 degrees down. PIC/STT seems to work correctly at close range. I only did some brief testing in a tail-chase scenario, but the only time I lost lock was when my airspeed matched the targets very closely, and so would have been lost by the doppler filter. I was able to climb quite steeply and get quite a bit above the target, and also below it - no problem maintaining the lock. Look-down performance seems to degrade, maybe above 7 nm or so, though it's hard to really tell. I think this is to be expected, though. But, maybe something else is going on, especially if it's dropping it locks head-on. The weird behaviour is the min/max altitude readouts by the radar cursors. The cursors are still enabled in PIC, with the distance removed but the alt labels still there. e.g. I'm 3.8 nm behind my locked target. I'm at 1,600 feet, it's at 6,550. Next to the cursor it says 3, -0. After pulling to a nearly 45 degree climb (pitch is 49 degrees) I'm at 4,100 feet, target is 4.1 nm away (still at 6,550), cursors say 6, 2. This is below the target but I have no problem maintaining the lock, so it's clearly not where the antenna is currently pointing. It does seem to match fairly well with the altitude readout for the cursor at the same distance as the target when I drop the lock (when the antenna returns to the previously requested elevation). So I think what happens in PIC mode is: the altitude readout by the cursors will be correct for the radar's scan altitude range at the target's current range prior to entering PIC mode. It does not indicate where it's currently looking. If you drop the lock, the radar elevation returns to the previous position, i.e. if you have the cursor over the target and drop the lock, the area your radar starts scanning should match what the cursor indicated while you had the lock. I think I did actually find a bug with CCM: In certain situations, where the radar can't actually go into PIC/STT mode on a target, the CCM would act a bit weird. Basically I think it was locking a target (thereby removing the CCM scan mode symbology from the HUD) but not actually locking it so there was no target on the radar display or HUD. I could switch it into PID mode, though. Having difficulty reproducing it reliably, though. Having said that, I just immediately did. Situation: I am at 3,000, target (AI M-2000C) is at 6,500. Range is 8.2nm. Radar in CCM vertical search mode. Speeds are 368/419 ground, or 351/380 indicated (my speed first). First pair of attached images are with the target "locked". If I press the "TARGET LOCK" button it switches to PID mode, and the target is displayed (second pair of images). If I press it again to go to PIC mode, we lose the target display as if we don't have a target, but the HUD symbology for the scan mode is still missing (i.e. the radar acts like it's got a target locked). If I drop the lock ("TARGET CANCEL LOCK") the vertical search symbology reappears for an instance, and then disappears as the target is picked up. But the auto-lock puts it into PIC mode and the target information is not displayed, per the first pair of screenshots. So basically, if CCM picks up a target that can be tracked by the radar (PID/search mode), but can't be locked on to, it will still "select" the target and not display any information for it, but (presumably) prevent the radar from acquiring other targets that actually can be locked on to.

The POL appears on the HUD when you select fuel tanks ("RP") on the PCA. It blinks when master arm is disabled, just like for all other stores. If you jettison them "POL" will remain active (because the expended store is still selected, even though its light on the PCA will go off), just like for every other ordnance. (Sidenote: I don't know if this is correct behaviour or not, but I do find it both annoying and unexpected.) But you can exit this mode by either re-selecting the same button (even though it's now off), selecting a different store, selecting the gun, etc. The radar will ignore your attempts to designate an airborne target while you have air-to-ground stores selected on the PCA (I tried it with GBU-12s); and fuel tanks are treated as air-to-ground stores. If you select the cannon or missiles, then the radar controls work normally.

Radar is WIP and has some issues. You're probably experiencing this: http://forums.eagle.ru/showthread.php?t=165101

December 2010: http://forums.eagle.ru/showthread.php?t=64159 Also: http://forums.eagle.ru/showthread.php?t=53906 March 2011: http://forums.eagle.ru/showthread.php?t=70110 June 2012: http://forums.eagle.ru/showthread.php?t=90516 September 2012: http://forums.eagle.ru/showthread.php?t=94613

The manual states (page 60) that it's limited to ±3 degrees each side. I doubt they just made up that figure, so I'd assume it's correct unless someone finds good evidence to the contrary. IMHO, 20 degrees would make it way too hard to align accurately with it. For rough course corrections you've already got the HSI (or the aircraft commander IRL).

Might be related to this: http://forums.eagle.ru/showthread.php?t=156539&page=3 As far as I know no updates came to 1.5.3 open beta, so "next update" is still applicable.

They don't. It's the VTB export. Mostly intended for putting it on a second display, but can also overlay it on the main view.

Personally, I think the map has enough space that the UI could easily be designed to show km/m and nm/ft simultaneously. Same with L/L and UTM.

Airfields on the Black Sea map already change runway heading depending on the wind. They do have a 'preferred' direction, but if the wind is strong enough it will swap. Unless you're talking about the airfields with multiple runways, in which case the Black Sea incarnation of the engine only seems to support one runway per airfield. NTTR appears to be adding support for multiple runways in some limited manner, e.g. Nellis with separate runways for arrivals and departures. On the other hand, NTTR airfields don't appear to change direction and will happily have aircraft takeoff/land with strong tailwinds. But NTTR is still technically in alpha and hasn't been officially released, so it may not be the final intended state.

All modules are updated along with the base game when you run the updater utility. There should be a shortcut in your start menu, "Update DCS World 2 OpenAlpha". You could also try running a repair, with the "Repair DCS World 2 OpenAlpha" shortcut in the same location. When the main menu loads, the version in the bottom-right hand corner should read 2.0.2.52658 at present, for the latest version. If it's not updating, the usual culprit seems to be anti-virus software. If you're on the right version, then maybe post a track of you trying to do a cold start. That would allow other people to check your procedure, and try it themselves (you can take over control at any time during a track).

I think the radar has a hard time staying locked on to the helicopters, due to their slow speed. Basically they can notch you perfectly, almost without even trying. My experience tends to be the chopper will go evasive and my lock will drop shortly before the missile reaches the target, causing the missile to go stupid. From what I gather, the notch shouldn't be usable by helicopters since the rotors provide a strong return, but DCS has always allowed helicopters to hide from air-to-air radar by going slow, so...

Try reducing saturation and/or adding a curve for your rudder axis, it's very sensitive and you only need to use a fairly small portion of the total axis. You'll need a bit of right rudder when you first lift, but can let off as you pick up forward speed.

There are only training and quickstart (Instant Action) missions shipped with it at present. The campaign takes place on the Black Sea map so I wouldn't expect it to see it in 2.0.x.

Yes, AI units will fire ATGM at helicopters. They usually miss, especially if you have a little bit of sideslip - not easy to guide against an airborne target. Tanks used to fire their main guns at helicopters too, haven't observed it recently but may just not have had any units get close enough and not be maneuvering for long to get tagged.

There should be shortcuts in your start menu, to force update and repair. "Update DCS World OpenBeta" etc.