nomdeplume

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.

Oops yes. Collective. :)

Seems there's an "auto cyclic control" which is enabled by default, C to disable.

Yes, I think the other thread describes it better. The dual-trim systems is pretty cool.

The slashes on the HUD or the sticky-up-bit which I assume houses the HUDcam/guncam? Slashes should go away after the radar is warmed up. I think they disappear in 'P' mode after the warm-up, but putting it to SIL should allow you to not have the slashes but also not have your radar active.

Are you adding the aircraft as country France? Most of the existing liveries are only available for that country. Not sure about the loadouts though. They're task-specific but not country-specific. What task is the aircraft set for? You can create a new loadout using the big "New Loadout" button at the bottom of the screen anyway, so that one's not such a problem.

All jammers do that to some extent, but AFAIK no EM jammers are so powerful they prevent IR missiles from locking on to a heat source. ;)

This bug is really hard to replicate. So I will appreciate that when you get it, you save both the mission and the track and send it to us so we can check and see what is happening. Please indicate at what time the bug occurs. Seems to happen for me pretty much every time, so that made it easy for me to reproduce! Here's some screenshots of when I saw it. It seems like it thinks the target is directly ahead at zero range when this occurs; so more like all the contact variables get zeroed out. First screenshot shows the contact just before I designate it again for PIC/STT. You can see it's being tracked normally. Second screenshot is immediately after designating to go to PIC. --- I've also attached a tiny track and mission for the Black Sea map which shows the issue. Air-start with an A-50 ahead. In the track I just lock the contact and bank left until it crosses the 30° azimuth marker and the lock gets locked. Sometimes the contact's data gets zeroed out and then the lock is completely lost immediately after; other times, it stays pegged at the bottom centre of the display for a good few seconds. --- Edit: Added a video of the relevant portions of the track: M2000C-radar-lock.miz m2000c-radar-lock.trk

Can you clarify - you mean if your own ECM is on it can't lock targets? And you're talking about R-550 Magic 2, not R-530D Super? Anyway, I just did a flight and destroyed two MiG-21 with my ECM on. One with two Magics (decoyed the first one), second with a single 530. Your own ECM could conceivably degrade your radar's performance, although I think Razbam chose not to try to model that since none of the other DCS aircraft do (or they might still be considering it). Obviously it should have no effect on the R-550. So: how did you test/determine the ECM was preventing R-550s from locking? And was it on 1.5 or 2.0? Keep in mind Magics currently only lock at the boresight cross, the radar slave functionality is not implemented yet.

I think the two most common causes are: 1) the flight you're in has a later start time than the mission time or 2) you don't have the required module activated/installed. For #1 most of the pre-packaged missions shouldn't have that issue, although apparently one of the M-2000C missions doesn't spawn the player until 2 minutes in. If you're using the mission editor, make sure you don't adjust the start time of your flight; use the briefing dialog to adjust the time the actual mission starts. For #2, you could go into the module manager and make sure everything looks right, and do a repair (shortcut in the start menu) to make sure it's installed properly. You could also potentially run the copy-protect programs manually. They mostly live under the DCS installation directory in Mods\aircraft\aircraft name\bin, though I think some modules use the dcs_protect.exe in the main bin\ directory.

Some useful info in this thread: http://forums.eagle.ru/showthread.php?t=161758

Yes, the OP's original question was never directly answered, so: no, there is no way to reduce the engagement range of SAMs/ground units. Unless you're willing to mod the game in which case you could probably the unit or weapon parameters to reduce its range.

Is "UH-1H 06 FARP London Cold Start" always occupied by a player when this script runs? If not, then the group would be empty and thus probably not returned by Group.getByName(), or if it is returned then getUnit() wouldn't return any units. From the error message it looks like the group doesn't exist at all, as far as the game is concerned. I do seem to recall some problem with getting multiplayer group names recently. Not sure if it's exactly this, or if it was ever fixed.

Using the UI tools, the only way to do this is to explicitly use the "GROUP IN/OUT OF ZONE" or "UNIT IN/OUT OF ZONE" conditions. Kind of a pain - would be really nice to at least have "COALITION UNIT TYPE IN/OUT OF ZONE" conditions at times. Sometimes you want to respond to aircraft entering an area but ignore the present of ground units, for example.

What aircraft?