nomdeplume

Related issue: IAS is always shown at the bottom left of the radar display, even when it's below the threshold for display on the HUD. Probably it should only appear at >= 30 knots?

I'm not sure what you're asking - 'radar up and down line'? The numbers on the radar cursor at the moment are the distance (in nautical miles, on the left) and the left/right offset (in degrees, on the right) for the cursor position relative to your aircraft.

It isn't implemented yet, but the cursor is supposed to show the min and max altitude being scanned at its position. So yes, for now you have to guess or calculate it yourself.

Two slight things: Barometric altitude display on the head should be rounded to nearest 10 feet as discussed elsewhere on the forum, and visible in HUD footage. Radar altitude is displayed on the bottom right of the radar screen when the radar altimeter is enabled, even if your altitude is > 5,000 feet AGL (see image). Radar altitude on radar screen is also shown in impossible flight regimes, e.g. when inverted. Here's some HUD footage that shows the altimeter on the HUD fairly clearly (skip to about 44 seconds):

I believe this is really an audio enable switch. That is, in the default position (down) it is off, so you won't hear any audio warnings. The middle position is on, so you'll hear warnings. The top position is I think the test position, but I'm not entirely sure what it does or if it's implemented yet. So for silence, leave the switch off (=down). At least, that's how it's worked for me since it was implemented.

How did you install it? That path looks a little weird. Anyway, the Start menu programs are by default under Eagle Dynamics -> DCS World OpenBeta (or DCS World 2 OpenAlpha). If you really can't find them, you can make your own shortcuts. The repair runs: "...DCS\bin\DCS_updater.exe" repair The force update runs: "...DCS\bin\DCS_updater.exe" update The regular game launch runs the same program with no parameters, which means it'll do an update check once per day. They all have their working directory set to the main DCS path (i.e. excluding the \bin\ folder). Attached a screenshot of my shortcut properties in case that's easier to understand. You can also check out SkateZilla's detailed posts: Using DCS Updater to Update, Revert, Repair, or Install Modules.

There should be a shortcut in the DCS program group in your start menu.

I just can't find that one It's listed as Stores 2 SELECT under the Armament Panel (PCA) category. The PCA has two rows of buttons, the top row is simply PCA Button 1 SELECT to PCA Button 5 SELECT, while the bottom row is Gun Mode SELECT, Magic II SELECT, and then Stores 2 SELECT through Stores 4 SELECT.

"As far as I can tell." i.e. looks to me like ...

The behaviour for mixed A-G loadouts is basically "undefined". I think the only guarantee Razbam are willing to make at this stage is that the game won't actually crash. So if you find a combination that results in a crash you can definitely report that as a bug, but anything else is beyond the specifications. Since the avionics don't support mixed A-G loads, it's impossible to say what the simulator should do if people do it anyway. At the moment it seems like Mk82 variants mask eachother so you can only select and release one type, but completely different wespons will be recognised and work normally. But I don't think the implementation is completely finalised yet, so things may change.

Yes, this is correct. The GBUs have two release solutions which can be configured via the DSMS profile page (see page 555 of the flight manual); the default is ORP for Optimal Release which will release the bomb such that its natural flight path will cause it to land beyond the target, so it has enough energy to maneuver once it picks up the laser reflection. The other mode is BAL for Ballistic, which will cause it to naturally land on the target (in theory, in practice mid- to high-level unguided bomb releases are not accurate enough for this to work) like a dumb Mk-8x bomb. This mode is not used by default for LGBs because if they pick up the laser reflection and start guiding, they will usually not have the energy to make it to the target and will therefore fall short. Currently, all bombs in the M-2000C seem to land beyond the aimpoint, but I think this is probalby due to it being an early WIP implementation and once other systems are more fully implemented it will be able to produce better solution cues. It would make sense for the LGB CCRP release profile to actually release the weapon so it'll go a bit long unless it picks up guidance, although at the moment it seems if you designate for release on the target it will fly so far it will often miss the laser reflection altogether.

VdK, your issue is different - LoneWolf is talking about the axis commands which simply aren't implemented yet. I've seen mention of the slew not working after updates, one fix may be to remove your old bindings so the game uses the new configuration with default values, and re-bind everything. I've been doing that with every update anyway, since the input configuration is receiving substantial changes. You can do that by removing the "M-2000C" folder from under your profile, "Saved Games" -> "DCS.openbeta" (or DCS.openalpha for 2.x) -> Config -> Input. You might want to just rename it or move it somewhere else (i.e. back it up) so you can easily restore it if it doesn't actually help. Also, you can look through this thread and this thread and see if anything there helps you.

Yes, you simply fire them. Make sure master arm is on, select Magic using the PCA (I don't think the button is labelled with smoke generators loaded, but it's the 2nd button on the bottom row, next to the cannon). Pay no attention to the seeker tone, WIP...

It's not implemented yet.

Oh, I get what you mean now - you're talking about the top of the display, where the antenna sweep indicator goes off the display? I think the only solution will be to use a longer range setting, and only switch to shorter range modes when you're investigating contacts that aren't so far off to the sides. Or possibly, switch to B-scope mode, which I think displays the entire search space. Edit: B-scope mode is probably best if you need the widest possible angle, as the ±60 will always have part of the search area beyond the display's physical area. Or you could use the 160NM mode since anything you can actually detect will be quite a bit closer than that, and probably within the display's limits.

This is correct, the standard scope is like looking down from above, your aircraft nose (where the radar is) is at the bottom edge of the screen, so you see the 60 degrees left/right the antenna can rotate; anything beyond that won't be visible to it. Vertically the same thing happens (with a narrower cone) but the overhead view cannot depict that and you need to use the altitude readouts on the cursor. In B-scope mode the display is stretched so the entire bottom edge represents the aircraft nose. This has the advantage of giving more lateral separation to contacts as they near the bottom of the display, and any contact moving straight down the display is on a collision course with you. The disadvantage is it's not as intuitive.

It's like other radars, you have configurable number of 'bars' of search: 1, 2, or 4. The radar cone is approximately 3 degrees, so a 1 bar search will cover 3 degrees, 2 bars covers about 6 degrees, and 4 bars covers about 12 degrees. What you're controlling with the antenna elevation control (and what is indicated by the marker in the display) is the amount the antenna is angled up or down in the middle of its scan zone. The min/max altitude this area encompasses depends on your own altitude, and the distance from your aircraft: 3 degrees covers a much wider area 40 miles away than it does 4 miles away. The images in this post might help visualise this.

Weird in the sense that no other aircraft in the game has this level of simulation, so either you make a special "super powerful ECM mode" for when you prioritise ECM over the radar, or a "super weak ECM mode" for when you prioritise radar over ECM, and no other aircraft in the game has this. But all aircraft in the game should be affected by their own jammers (and other jammers, of course) to some extent. So, it'd be some made-up stuff on top of a very very basic EW environment, and it would be weird for a third-party developer to either cripple or enhance their particular aircraft trying to simulate something the rest of the game world does not even think about.

Not implemented, you can see some discussion in this thread: http://forums.eagle.ru/showthread.php?p=2616263 Short version is nobody really knows exactly what it means, and ECM/EW modelling in DCS is so basic that it's largely meaningless and adding it only for the Mirage would be kind of weird.

Okay I understand you better now, but I think the 60 degrees each side is the limitations of the antenna, i.e. the radar cannot physically move further than that so it would not be able to give ±60 degrees with an offset. I don't see why they would artificially limit the maximum horizontal scan zone if the radar could actually swivel further than that. See also: http://forums.eagle.ru/showpost.php?p=2573013&postcount=2 To further clarify: if say you 'centre' the radar at +30°, then to provide ±60° scan the radar would have to traverse from -30° to +90° each sweep, but the radar can physically only move 60° in each direction.

That's what Azrayen said; if the scan width is < 60°, then it'll be centred on the TCD position (within the limits of the radar gimbal of course).

http://forums.eagle.ru/showpost.php?p=2692330&postcount=85

Refueling seems to generate start refuel/stop refuel events continuously (this is in 1.5.3, using an IL-76). I also find that exiting the simulator to the menu just hangs sometimes, not 100% sure it's related to this 'event spam'.

It looks like Georgia is supposed to have both Igla and Stinger MANPADS, but only the 'Stinger comm' unit is available for selection. The database scripts have a Stinger_manpad_GRG which is added in db_countries.lua: cnt_unit( units.Cars.Car, "Stinger manpad GRG");but this apparently doesn't work. Don't see any mention of 'stinger' in the logs so I guess whatever the error is, it isn't triggering any diagnostics. The Israel custom Stinger units both seem fine. Nothing that stood in the Georgian Stinger database files to me, only slightly suspicious thing is that the Georgian stinger uses 'StingerUSA_1' as one of its attributes, rather than having its own ID like the Israeli and USA Stinger units do, and the Georgian Igla units also have their own IDs (in wsTypes.lua). Not convinced that should actully cause any problems, though. DCS version: 1.5.3.50487

Could someone with this issue post a mission file where it occurs? Preferably as minimal as possible.