nomdeplume

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.

^ agreed, seems to happen with battery on, emergency hydraulic pump switch on. Park brake and wheel brakes both stop the shaking. Edit: although I'm unable to reproduce it now. May only occur with a fresh start or something?

I know I know, that darned clock again! The analog cockpit clock doesn't work prior to 4am local/mission time (midnight GMT). If the local time is between [0:00, 4:00) it'll just display 12 o'clock until it hits 4am. If you start the mission late in the night, the clock works fine until just before midnight local (when it shows one minute to 8), and then when the local time ticks over to midnight the hands jump to the 12 o'clock position and remain there until 4am. (Tested sitting on the ramp at Senaki, in case that matters.)

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

I've noticed it only with brakes (parking brake especially) off. When it's on the shaking stops. It doesn't always shake, but it seems to do it more often than not. I think putting the throttle up to get it to just start moving and then idling the throttle again is a good way to reproduce it. When I encountered it (stopped before turning onto the runway at Kutaisi) I put the parking brake on and off a few times and it reliably stopped/started shaking each time.

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.

Training missions and the like generally don't get implemented until the aircraft is like 99% implemented. For hopefully obvious reasons. There's a selection of skins already available, but most of them are only available for France (i.e. if you're making your own missions, add the aircraft as France to get all the current liveries).

Reproduced TACAN audio with Kutaisi (44X). I also noticed the thing that isn't an HSI but we call it that anyway does not provide direction in receive-only mode; i.e. OFF and REC mode both have the distance and direction indicator arrow disabled. VOR/TACAN stations should be able to provide bearing in REC mode.

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

I think you need to set the HUD's altimeter setting to the bottom position on the switch ("AG"?). This is from memory, but IIRC: - top setting shows just barometric altitude - middle setting adds the AGL using the radar altimeter - bottom setting also adds minimum altitude warning. This level can be adjusted by spinning the knob. I think you only got the pull-up warning arrow on the HUD when you have the HUD indication enabled.

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.

Sounds like this issue: Radar elevation wrong after unlock. When I was testing it initially I had the impression that banking the aircraft also caused the elevation to change, but when I was careful to not change pitch while rolling the effect was much lessened. So I came to the conclusion it's responding (weirdly) to aircraft pitch rather than roll. Might need to re-test that.

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.

Not common, but someone else has reported the same thing. Check out this thread: http://forums.eagle.ru/showthread.php?t=164504 I think it would probably be helpful for the developers to track down what's happening if they can get more information about the systems it's happening. So if it looks like the same problem you're having, could you post your system configuration, and results from any tests you're able to do.

What aircraft?

If you only want to spawn one or two groups of fighters, you can easily do this with the in-game triggers. If you want to spawn unlimited fighters, have a look at this recent thread. (Actually the mission the OP attached to this has an example of activating groups using triggers as well, so if the following is completely incomprehensible to you, you might want to take a look at it.) For your basic setup, add the AI fighter group as you normally would (waypoints etc.) and then make sure the "LATE ACTIVATION" checkbox in the group properties is ticked. This will prevent the group from appearing in the game until they're explicitly activated. Next, place a trigger zone of your desired size at the location you want to use to activate the AI group. Finally, in the triggers dialog, add a new 'Once' trigger with condition: PART OF GROUP IN ZONE Group: player group (or whatever group you want to use to activate the AIs) Zone: the zone you placed And then for the action, you want: GROUP ACTIVATE Group: your AI fighter group If you only want to have a particular aircraft activate the AI, you can use "UNIT IN ZONE" instead of "PART OF GROUP IN ZONE".

Yes it's been broken for the last few versions. You can use the HOTAS "Magic II SELECT" button instead of the PCA button (with the same name) as a workaround instead. This is a HOTAS switch similar to the dogfight override function on the F-16. Zeus has acknowledged the problem so hopefully it'll get fixed in the next few updates.

You can use the Spot functions in the scripting environment to do it manually. Also means players don't have to go through the repetitive FAC comms process to get targets.