nomdeplume

I don't think I've ever heard/seen any effect when I press the engine start button, but it's always worked fine for me. Could you maybe post a track of your startup? As I understand it, the tracks record user input so if there's an issue with your installation, a track where your jet fails to start might start when played back on another computer?

I don't see a gun arm binding in the keyboard or joystick input lua. Is there a command we can add manually? Edit: also, I would've expected there to be some kind of HUD indication when guns are selected, master arm is on, but gun arm is off. Probably the CAN symbology blinking, in the same way the other weapon symbology blinks when master arm is off?

Looks like this should be fixed in the just-released 1.5.3 update.

It would be nice if the controls configuration UI let you set this up. It'd be a bit silly for every switch to have to have two definitions to support both toggling-when-pressed and toggle-when-pressed-or-released behaviour. :( Anyway, you can (mostly) do it yourself fairly easily. I say "mostly" because not every control lets you specify the state you want it to be in; some of them (like the ones you're interested in) only seem capable of toggling. You can still do what you want, but it's easy to end up with them desynced (i.e. your physical switch is 'up', virtual control is 'down'). In SP you can fix that easily by pausing the game, flipping your switch, and then resuming. The bindings are configured in your DCS world installation folder under Mods\aircraft\M-2000C\Input\M-2000C\joystick. Make a backup of the default.lua (in case you break it) or even better, make a JSGME folder for your changes so they're easy to re-apply after updates (but the controls are often updated while the module is in development, so you'll want to check if anything useful has been added or changed instead of blindly replacing it with your customised version). You'll see the controls are generally defined as: {down = something, name = ..., category = ...}But some of them, especially the existing 3-pos switch abstractions, also have an "up = ..." parameter. This is the key to doing what you want: the "down = ..." command is performed when the button is pressed, and the "up = ..." is performed when the button is released. You'll also see quite a few have "value_up" and "value_down" parameters, which apply a particular value to the "up" or "down" command target. However, some controls just ignore the value_ parameters. This applies to the master arm and G-limiter switch. You can still make them toggle on button release by specifying the same command for the "up = ..." parameter. So for master arm, take the existing line: {down = iCommandSwitchMasterArm, name = _('Master Arm TOGGLE'), category = _('Weapons Management')},and duplicate it to your own custom control - I suggest putting it right at the start of the file, immediately on the line following "join(res.keyCommands,{": {down = iCommandSwitchMasterArm, name = _('Custom: Master Arm ON, else OFF'), category = _('Weapons Management')},and then adjust the logic to match what you want. Since this can only be toggled, it's pretty simple: just make it apply the same command when it is release ("up = ...") as it does when it is pressed ("down = ..."): {down = iCommandSwitchMasterArm, up = iCommandSwitchMasterArm, name = _('Custom: Master Arm ON, else OFF'), category = _('Weapons Management')},The G-limiter switch can be duplicated into something like: {down = iCommandPlaneCobra, up = iCommandPlaneCobra, name = _('Custom: FBW G-Limiter Mode A/A, else CHARGES'), category = _('Flight Control')}, You might also want to adjust the category to put them all together in the controls configuration dialog; maybe make a new Custom category by specifying "category = _('Custom')" for each of them.

Radar antenna elevation is on the back of the throttle grip. You'll need to use the keybinds or axis mapping control for it. Key binds are in the Sensors category, I believe. Edit: probably "azimuth button" is referring to the 3-pos azimuth setting switch.

How did you use the Saitek software to program this? Is it set up to send synthetic keypresses as substitutes for when you press the button? Or if not, what is the software doing? I used to have the TDC directly configured with buttons in-game using the TM Warthog (I don't use TARGET, so just DirectInput joystick buttons). I think I've used it recently, but not completely sure as I use the axis control now. The radar now needs to warm up and will only start warming up after takeoff (which seems strange to me, as other radars I've seen modeled in flight sims can warm up on the ground). It'll take two minutes if you have the switch set to 'P'. If it's on SIL or fully on, the warmup period will last three minutes. The P will disappear from the radar display once complete, so you know it's okay to switch it to SIL/on.

Yes, it can work. Often done by MiG-21 pilots in DCS who are outmatched by other flyables in head-to-head fights (plus their radar is borderline useless for search, anyway). Typical tactic is to fly very low so the terrain shields them from other aircraft's radars, and then hope to spot someone visually and get the jump on them. It's most effective when you have help from others - they can give you directions over the radio to help you get into a good position. Can be done formally with Ground Controlled Interception (GCI) or with airborne radars (AWACS in DCS), and informally with other players who are using their radars relaying information about contacts. Or, just someone looking at the F10 map or LotATC display and giving you vectors to intercept.

I'm think the logic is simply that anything with a weapon is capable of lasing. Any unit at all can be a JTAC but only those with weapons can lase, and probably smoke markers also require it to be armed, but I'm not 100%. They may need to be quite close to be in range for the laser, and they need a clear line of sight. You can use the advanced waypoint actions to set ROE -> WEAPON HOLD or RETURN FIRE to prevent the JTAC unit from fighting the enemy, and Perform Command 'Invisible' to make the enemy not fight the JTAC.

Just tried it with an air start, and no go. Are you using the latest open beta, 1.5.3.51870?

I can confirm, unable to select smokes. Only tried it on the ground so far, but I can select S530D and Magic on the ground. Occurs both with a mission editor loadout and after re-arming.

A lot of the discussion has moved to the new "DCS World" forums rather than module-specific. Aero Interface is the "new" shiny user interface introduced in Windows Vista, which allows windows to have transparent titlebars, amongst other features. Sometimes this causes problems (or just reduces performance) so some games automatically disable it when they launch; DCS gives you an option to have it automatically disable it. If you don't notice any problems then you don't need to worry about it. Vsync is a standard graphics option that makes the game wait until your monitor is about to start a new refresh cycle before updating the frame being output by the video card. This eliminates "tearing", which is the result of the video frame changing while it's being displayed - you see a line where above it is the content from one the previous frame, and below it is the content from the new frame. If you don't notice any tearing then leave vsync off. If you do notice it then it can be very hard to unnotice it, so you can turn vsync on. Vsync will effectively reduce your framerate to the closest even divisor of your monitor's refresh rate. So for a 60Hz monitor if your system can't sustain 60 FPS it'll drop to 30 FPS, then 20 FPS, etc. There are three autopilot modes, two of which will maintain your current altitude. They all have limits to their authority, so you should be trimmed out reasonably well before you activate it. To set AP mode, use the three-position switch underneath the Landing Gear Warning silence button (L/G WRN) on the throttle quadrant. To enable AP just press the ENGAGE/DISENGAGE button immediately to the left of the mode switch. The commands are in the "LASTE Control Panel" category. I'm going to make the wild assumption you don't have the TM Warthog HOTAS, so I'll provide the default key binding and the control name. The bottom mode, ALT ('4'; LAAP Altitude/Bank Hold), will maintain your current altitude, without trying to hold your heading. This is primarily useful when you want to orbit around a point (e.g. waiting for your push time) and you want to go heads-down for a while. To use this, trim yourself to roughly maintain altitude and the desired bank rate, then enable the AP. The middle mode, ALT/HDG ('3'; LAAP Altitude/Heading Hold) will hold your altitude and current heading. This is your 'cruise control' mode for transiting between waypoints when nothing's happening so you want to busy yourself with avionics, maps, etc. To use this, trim yourself out into straight and level flight, then enable the AP. The top mode, PATH hold ('2', LAAP Path Hold), will basically try to keep your Flight Path Marker in the same position. It's useful for when you're climbing to altitude; just trim yourself into a nice comfortable climb, then enable the AP in PATH mode and you can get busy setting up your systems, studying the briefing, etc. The default keybinding for the autopilot button is 'A' - listed as LAAP Engage/Disengage in the controls section. There are also two special bindings available, "LAAP Mode Selector (ALT)" and "LAAP Mode Selector (PATH)". These are used with switches and will enable the specified mode when pressed, and go back to ALT/HDG hold mode when released.

Used to work fine, apparently CCM has problems with this latest update: http://forums.eagle.ru/showthread.php?p=2730591#post2730591

I've noticed the 'ghost' contacts created by jammers will respond positively to IFF queries, even though I know full well the contact is actually hostile (and the other contacts closer to the target's actual location don't respond to IFF). I think the IFF logic is probably doing something like "if contact is not hostile then show the IFF response diamond", and ghost contacts are "fake" and therefore "not hostile".

It's not that mysterious. I mean if someone suggested to give the A-10C HARM and AIM-120 and afterburners (and variable-geometry wings so you don't rip them off the moment you light the burners), would you think that was perfectly reasonable, or kind of silly? Certainly it may increase sales. But it's not really a "simulation" of an "A-10" at that point, is it? Like you said, it's a question of where you draw the line. If you allow some fantasy, then that line becomes extremely contentious. It's therefore not at all surprising or hard to understand why many people end up taking this position: if you are simulating a particular aircraft, then limiting it to the weapons and systems it's actually operational capable of using and cleared to use in real life makes sense. Even though it can sometimes be hard to find authoritative data, it is at least an objective line: either an aircraft is operationally capable of using a specific weapon, or it isn't. If you can show evidence that a particular weapon system is or can be employed by the aircraft, you have a very strong case for its inclusion, and it's very hard for people who don't like (or just aren't interested in) that system to argue against it. If you decide to implement things just because they're useful to players or kind of cool and you can reasonably imagine how it would work if it had been on the real aircraft, then how do you argue that an A-10 "simulation" shouldn't have air-to-air radar and afterburners? Another important consideration is simply that if you start doing "fantasy" things like that, you remove (or at least reduce) a major aspect of what people find engaging about simulators, and that is working out how to employ a specific platform given its strengths and especially its limitations.

Number painted on the side of the airframe to aid with identifying the particular aircraft it is. A little bit of Googling (since I didn't already know, and had idly wondered) indicates that "bort" just means something along the lines of "side of body" or "side of ship" in Russian. So basically, "side of ship number". In some services it's related to the aircraft serial number or production number, but apparently in Russian service it's used only within subunits and prone to change, and has no relation to its serial number or other uniquely identifying information.

44 degrees would be pretty steep for an LGB release. Doable but certainly not necessary. Angels refers to (friendly) altitude in thousands of feet and makes more sense in context.

The carat doesn't indicate your waypoint, and I don't think at present is doing anything especially useful. This post by Azrayen is the best explanation I could find: http://forums.eagle.ru/showthread.php?p=2688815#post2688815

There is a command, something like "Special modes deselect", which will cancel the CCM and return to normal search mode. I think I did read that selecting S-530 is meant to automatically cancel CCM, though personally I prefer that it doesn't. :D

Regarding the oxygen issue, are you guys sealing the canopy? The P.CAB light should go off when you do. After closing the canopy you need to left-click the red bit of the lever, it should go into an "UP" position and the canopy will be sealed. Also: are you using any mods? I think there were issues with someone's mod to allow use of NVGs relating to hypoxia as it hadn't been updated.

You need to spin the INS knob (on the right side panel) to the NAV position. INS isn't implemented yet so you don't need to align it, but it does need to be in NAV mode in order to show your waypoints. It will automatically advance to the next waypoint when you get within 1.5 nm of it; or you can use the 'next waypoint' keyboard shortcut or the next waypoint button on the INS control panel (next to the keypad at the front edge of the right side panel). Auto-advance is disabled when you have your weapons armed (possibly on in air-to-ground mode, haven't verified). For the bombs, you're probably using a mixed payload? The avionics of the aircraft only support a single type of air-to-ground ordnance. In the current implementation in the sim, you can get away with mixed types but need to have the same type of weapons in the following groups of hardpoints: - mid-wing position (2 hardpoints) - wing root/fusealage (four hardpoints) - centreline (1 hardpoint)

I believe there's also missions that come with it, they're just not in the usual folders so the quick start options don't find them by default. I haven't used them so I'm not sure exactly where they are, but have a look around and you'll probably find them. e.g. check out this thread which says you can start them via the 'missions' tab.

My encounter with this bug had a bit of an uncommon ending which might indicate another bug; after running the tanks dry I got the vibration which I also discovered could be 'fixed' by switching to VRILLE. After refuelling, I switched it back to normal and the vibration was gone. Also after refuelling, I pulled back and to the right as hard as I could (okay, I wasn't completely full and a little bit frustrated), and my aircraft acquired a modest but annoying roll to the right. Checking the external view, I discovered my left wing tank had disappeared. Not sure if I'd managed to pull excessive G's or if perhaps I'd collided with the tanker. So, I decided to jettison the right wing tank to rebalance the aircraft, and that's when the aircraft went into a rapid and uncontrollable spin. Shouldn't the FBW bug have been triggered by the (uncommanded) loss of the left tank? Is it adjusting only based on expected aerodynamic changes or to actual changes?

Are you using 1.5.3 or 2.0 (Nevada)?

Ah of course! That makes sense. Thanks.

This makes sense, but may be problematic for people who use an axis to control the radar elevation. Unless they use a force-feedback axis, I guess. :) How does it work in real aircraft? Is the control a roller like a trackball or similar that has no limits to its movement, and only provides deltas rather than an absolute position?