nomdeplume

The F came before the D; F introduced in 1979, D 1988.

The new (ish?) "Restrict Air-to-Ground Attack" option is great! Except, it appears aircraft that are tasked to engage other aircraft will still attack aircraft that are on the ground, even with this enabled. They do not attack static aircraft, so it seems like maybe the "Restrict Air-to-Ground Attack" just stops the AI engaging ground units, statics and ships, but allows attacks against planes and helicopters. This is fine most of the time, but if you have e.g. a CAP near an enemy airbase, it will attack parked aircraft. Ideally it should require the aircraft to also be airborne if "Restrict A2G Attack" is enabled. Attached mission has an F-16 circling an airfield where there is a parked Su-27 (with "Uncontrolled" set so it doesn't start up). The F-16 has the normal "CAP" automatic enroute task, and "Set option Restrict Air-to-Ground Attack" enabled. The F-16 nevertheless engages the parked Su-27. Also, the Su-27 is parked in a hardened aircraft shelter, and the F-16 attacks the shelter with its cannon... and the Su-27 is destroyed, because some of the shots explode inside the shelter. restrict-ground-attack.miz

Throttle button? :huh: You need to assign something with an analog axis, like a slider. Buttons won't work. If you are assigning something appropriate, then make sure you're first clicking in the right grid so the game knows what controller you mean. So: Go to controls menu. Make sure M-2000C is selected. Select Axis Commands category next to it. Find "Thrust" in the menu. Click in the grid cell for your controller (you may need to scroll to the right, if you have many). Click ADD. Move the controller through its full range of motions until the "Key / Button" thing gets populated. Hit OK. If it doesn't detect it when doing that, you might want to quit out and go to the Windows devices & printers thing and check the controller is working properly.

I always find these threads very weird. If they wanted to (and could) make a 2000E or -D or -5 or something else, then that's what they would've made...

Don't forget about the doppler notch. The radar will filter out returns which are 'stationary' i.e. only approaching the jet as fast as it's flying. This is so your display is not covered in reflections from the ground. It's what enables the "look-down, shoot-down" capability - otherwise your radar looking down would see just a sea of returns. A side-effect of this is that if an aircraft manages to stay 'stationary' with regards to your jet, either by flying completely vertical or - more commonly - by flying perpendicular to your radar beam, it will also be filtered out as its speed is too low. Since this effect is common knowledge, the first thing to do when locked by an enemy pulse-doppler radar, is to put it "on the beam" (at 3 or 9 o'clock) and dive to get lower than the enemy, so as to force its radar into look-down mode, hence breaking the lock when you get filtered out. This may be what you're seeing.

Just assign it to "Throttle". Moving the controller will change the throttle position...

Another disconnect between damage model and graphics - tyres will throw out sparks and make grinding sounds when they're damaged, but will appear completely normal visually. The one in the attached screenshot is an AI that made it home without a wing, but obviously the flight model thinks it's still there (and that its gear was blown apart, so it's making sparks as well). The right main gear looks completely normal but is sparking and making noises like it's grinding on the runway. I've experienced the "sparking but tyre looks fine" issue myself, but didn't take a screenshot.

The mission editor is missing the default payloads, but you can create a new payload (button at the bottom of the screen) and set your loadout as desired.

The MICA missiles exist in the game (2000-5 can use them), but in the AI fights I've set up they haven't been impressive at all. In fact, I'm hesitantly of the opinion that they perform worse than the Magic 2 and Super 530D. Haven't tried to measure it though, and maybe the AI shoots them from different ranges or something which makes them appear worse than they really are. Still, you could probably modify the loadout configuration to allow the 2000C to carry them. They might even be fireable.

Are you turning the HUD on with one click or two? One click will it turn it on, two clicks puts it into test mode which (at least currently) shows most of the symbology as per normal, but some things don't work.

The frequencies for the pre-set channels are part of the mission file. It's not "admin-related" at all.

I wrote way too much about the radios in this post here, might help you.

What are you turning on prior to the starting engine? I (literally) just read a post that mentioned this: This is different to the procedure in the manual which I think assumes a ground power cart is being used. Maybe it makes a difference? I think I pretty much always turn TRN on at the very start.

Attached, for Black Sea map. (Don't have the NTTR alpha installed, sorry.) Has 4 client slots (selectable in single-player) - 2 are air start, 2 are ramp start. Radio channel 1 is preset for the airbase, Senaki. Briefing has the ILS and TACAN settings. M2000C-landing.miz

Trim works fine for me. What controls are you using for it? I have found it to be less.. sensitive, I guess, then most other DCS aircraft. That is, a single press will have a fairly small effect on the aircraft trim.

And have you used the correct mappings, i.e. "Thrust" rather than "Thrust Left/Right"? Also, gear up/down don't work (gear toggle does) and ditto for airbrakes.

I think I've only had this happen once; maybe it's dependent on weather? Cooler temperatures should result in more thrust, so maybe the initial surge can be enough to override the parking brake in some conditions? Are you using the DCS World 1.5 beta or 2.0 alpha?

See this thread. Personally I aerobrake until I (eventually) get down to around 60kn and then force the nose down and then try to brake carefully. I don't think the FBW should be able to keep the nose up at those speeds, though. You could also try using the keyboard command (W) to ensure the brakes are applied evenly, at least until you're at a more controllable speed.

You might be able to get around this by using a virtual joystick emulator like VJoy. Basically it should create a DirectX input device with axis you control via keyboard hotkeys. Then you can map the axis of the virtual device within DCS. Haven't actually used it so can't vouch for how well (if at all) it works, but might be worth trying if you're desperate.

Hit the "New payload" button at the bottom of the payload screen, then you can right-click the pylon spaces and select ordnance.

Should just be "D" (Special Modes Deselect on the HOTAS) but sometimes other bugs might play into it. Sometimes you might need to flick the radar scan azimuth back and forth to get it back to normal scanning.

The 3-position switches on the TM Warthog, like the flaps switch, are implemented as two DirectX buttons. So when you move the flaps to the up position this is seen as pressing (and holding) a particular button. When you move flaps to middle, that button is released. When you move it to the down position, a different button is pressd (and held). So with the standard mapping abilities exposed by most games and the DCS UI, you can only map the "flaps down" and "flaps up" positions, because the "flaps middle" isn't a button press, but a releasing of whichever button was previously being held down. Sometimes you'll have problems because the button is held down as well; but usually it works okay. In DCS, you can get a lot of controls working with these kinds of switches by manually editing the LUA files that are used for the input configuration, and specifying an action for "button up".

Also the bomb release quantity selection does not reset to 0 when starting a new mission if you changed it previously.

In the close combat modes yes, but not yet implemented. So no. ;) Also, the R-550 currently locks at the aircraft boresight/gun cross thing, not the seeker circle on the HUD.

It's on Dropbox: RAZBAM M-2000C Manual v 1.0.pdf From this thread. Keep in mind the manual is also in beta... :)