tanr

Still only 14 flares in most instant action or missions in 2.5.6.59398. For example, F/A-18C Mission: "Weapons Qualification - Air to Air Gun and AIM-9 Sidewinder" has only 14 flares.

Ah, I missed that! Thanks!

Yes, that one.

Still only 14 flares for missions (like Sidewinder Practice) and instant action in Open Beta 2.5.6.58125. EDIT: Should I post this in the Bugs forum instead?

Are the specifics of missions broken in 2.5.6 already reported as bugs? I can't easily downgrade but would like to go through the campaign.

Important button bindings missing from joystick\default.lua (though can get them from clickabledata.lua 3467 Engine Shutdown Button Important axis bindings missing from joystick\default.lua (though can get them from clickabledata.lua): {action = 3209, cockpit_device_id = 5, name = _('Target Wingspan')}, {action = 3192, cockpit_device_id = 5, name = _('Minimum Altitude Selector')}, {action = 3703, cockpit_device_id = 16, name = _('MAGIC Tone Volume')}, {action = 3705, cockpit_device_id = 16, name = _('Marker and SERVAL Volume')}, {action = 3706, cockpit_device_id = 16, name = _('UHF Radio Volume')}, {action = 3707, cockpit_device_id = 16, name = _('V/UHF Radio Volume')}, Mappings that are/were incorrect in joystick\default.lua: --RADALT - This is RADAR ALTIMETER POWER, not MODE, and mappings were to incorrect toggle positions -- Below are corrected mappings and names {down = 3205, up = 3205, cockpit_device_id = 5, value_down = 0, name = _('Radar Altimeter Power OFF'), category = _('Sensors')}, {down = 3205, up = 3205, cockpit_device_id = 5, value_down = 0.5, name = _('Radar Altimeter Power ON'), category = _('Sensors')}, {down = 3205, up = 3205, cockpit_device_id = 5, value_down = 1, name = _('Radar Altimeter Power TEST'), category = _('Sensors')}, --Subsystems -- Electrical -- Names were HUD Altimeter Power Switch, but this is Altimeter VTH Mode -- Below are corrected mappings and names {down = 3204, up = 3204, cockpit_device_id = 5, value_down = 0, name = _('Altimeter Mode Barometric'), category = _('Electrical')}, {down = 3204, up = 3204, cockpit_device_id = 5, value_down = 0.5, name = _('Altimeter Mode Radar'), category = _('Electrical')}, {down = 3204, up = 3204, cockpit_device_id = 5, value_down = 1, name = _('Altimeter Mode Minimum'), category = _('Electrical')},

@jaguara5, your link doesn't work anymore after the forum rebuild, and I couldn't find it with a search. If you're able to find that thread, could you post the updated link? Boresight after vertical scan being positioned incorrectly is still an issue in 2.5.6.58125.

Just ran into this myself.

The Mirage maps its PCN mode knob to 11 separate buttons, instead of exposing a clockwise/counterclockwise method, so you can't map it to a standard encoder knob. Could you please add a clockwise / counterclockwise mapping for the PCN mode knob?

@RAZBAM_ELMO, should I change title to show track files are attached?

Still only 14 flares for missions (and Instant Action) in Open Beta 2.5.6.57949.

In case it's related to the radar / fps issue, for anybody tracking this, I've got a different (but maybe related) repro case. For me FPS is decent in the MiG-21 with radar on, until I go to the F10 map. Once I've pressed F10 and then returned to the F1 view, FPS goes from the 70-120 range down to about 10 fps. NVidea Quadro RTX 5000 with current studio drivers. I can record a track if that's helpful.

Still only 14 flares for the missions in Open Beta 2.5.6.57530.

With the newest DCS Open Beta 2.5.6.57264 (Steam), the number of flares for most of the F/A-18C missions (such as the combat certification missions for IR Missiles) has been greatly reduced, down to 14. Per other comments from ED, the plan had been to increase, not decrease, the number of flares for the Hornet, so this seems to be a mistake? Currently if will be hard to successfully complete a number of the missions with such a small number of flares.

I've attached two tracks, which both show similar situations. The example tracks show how I lock a target, reposition so that target is off the HUD, unlock with CMD PRESS, then try CMD FWD to turn on boresight. IF I have another target centered under the boresight BEFORE I turn on the boresight with CMD FWD I can lock the new target. Otherwise, with no target right under the boresight when you turn it on, and even though the previously locked target is pretty far off the HUD the lock will revert to the previous target. Hope this helps. And BTW, the Mirage is a blast to fly. Cheers. M2000-StaysLocked2.trk M2000-StaysLocked1.trk

Issue: With the newest DCS Open Beta 2.5.6.57264 the M-2000C Mirage can't seem to truly release a radar lock and is blocked from locking new targets unless you turn off the radar system then turn it back on. Repro steps: Air start, armed with 530s, with multiple possible targets Master Arm ON Select 530 missile with PCA . CMD FWD for boresite mode to lock one of the targets. Result: You will see the lock on HUD and radar. CMD Depress to unlock target. Result: HUD lock symbol (square around target) goes away. CMD FWD for boresight (or any radar mode) to try to lock any other target. Expected Result: Should be able to lock another target. Actual Result: Can't lock any other target. Instead lock jumps back to previously locked target, even if that target is outside boresight. So, once you have locked one target, after unlocking it you can't lock any other targets. Hope this isn't a duplicate report. I couldn't find any other mention of this besides discussion on reddit ( ). If you need a video of this I can try to put one together.

Where are the ranges actually located? Don't see any nav points for them. And hey, thanks for making this -- it's just what I was looking for as I try to make my Mk-82 CCIP use not suck.

You were right with your last comment there. I changed my mapping over to use the APU Start (instead of the ENG L Fuel) toggle for the fuel booster and now it doesn't automatically put it out of sync if I start with the switch in the ON position. So there looks to be a definite bug with only some of the HOTAS buttons being synchronized. That's really too bad, as it makes syncing up control panels (I'm planning to build some soon, though mostly for the A-10C) kind of a nightmare, especially as different missions or instant action have you start with different toggle settings. I'll try to add another bug report, and will post if I come up with useful mappings or other solutions. And thanks!

Thanks for the profile. I've already created something similar, with a bit of lua editing as well, but I'm happy to use some of your setup! However, my real question is how to figure out in the lua files which of the planes toggle switches or rotary dials can be properly mapped to their multiple states, meaning that they have either multiple Command values, or different value_down and value_up settings, or both. Examples of this working: The A-10C EAC Arm/Off toggle has two separate command values. So you can map your physical (single-throw) toggle switch in the lua with: down = iCommandPlane_EAC_ARM, up = iCommandPlane_EAC_OFF, The A-10C Anti-Collicion Lights switch has both different command values and different value_up and value_down: down = 3010, up = 3011, value_down = 1, value_up = -1, As I said, with some experimentation, I determined that the P-51D Rear Warning Radar also works like this, with: down = 3002, up = 3001, value_down = 1, value_up = 0, This means, that even if my toggle is out of sync with the plane's toggle, going back and forth with it will get it in sync. Note that neither the up= or the value_up= were documented. The problem is that some things, like the P-51D Fuel Booster, seem to only have a single iCommand value, and though I can set value_down = 1 and value_up = 0 for it, setting EITHER value just toggles the state of plane's toggle to it's opposite state. Thus, if my toggle switch is set to OFF, and the planes starts out as ON, then turning my toggle ON turns the plane's toggle OFF... The "Synchronize with HOTAS" option doesn't fix this. Instead, it (sometimes, but not always??) will see that my physical toggle switch is ON, and will take that to mean that it should turn the plane's toggles switch OFF! The best way I could work with this would be if there was a list of the controls per plane that specified if the control could only work as a toggle (like the Fuel Booster) and if it could work as more than that, specified the valid values (and their function) for: up down value_up value_down Note that the A-10C lua files seem to be pretty fully specified, with actual iCommand names for most up and down values, making this much easier. It's the P-51D and UH-1H that are, um, rather difficult to interpret. These have got to be documented somewhere. Here's hoping the documentation comes to light!

Hi All, I've mapped a few toggle switches from my Thrustmaster Warthog throttle for the P-51D. In general, this works fine. I edit the lua file and with some experimentation find the proper commands and values for up and down positions of the switches. For example, the Rear Warning Radar is mapped to the RDR ALTM toggle like so: {combos = {{key = "JOY_BTN25"}, }, down = 3002, up = 3001, cockpit_device_id = 25, value_down = 1, value_up = 0, name = "Rear warning radar Power", category = "Rear Warning Radar"}, In the example above I experimented to discover that I needed up set to a different number than down. Don't know for sure if I really need the value_up set to 0, but this is what works. The nice thing about the above setup is that regardless of my toggle switch position at startup, toggling it will get it in sync with the sim. My question/problem. I'd like to do the same thing for the Fuel Booster toggle switch. However, it looks like it doesn't have a separate command ID, and it seems to ignore the value set, so it functions as an ON/OFF toggle, REGARDLESS of what I set for value_up and value_down to. For example, my current attempt at it: {combos = {{key = "JOY_BTN16"}, }, down = 3006, up = 3006, cockpit_device_id = 15, value_down = 1, value_up = 0, name = "Fuel Booster", category = "Engine Control Panel"}, The problem with this two-fold. If it is out of sync at the start, then it won't go back into sync (so turning the toggle off turns the Fuel Booster on, etc.) Worse, SOMETIMES if I have the toggle switch ON at the start (meaning in the down state), the P-51D seems to read it at startup and toggles the Fuel Booster off. This is kind of bad when you do an instant action, start in mid air, and have your fuel booster turn off and your engine die... So, is there some other way I can do this with a toggle switch? Some undocumented ID I can use for "up?" A different set of numbers to plug into value_up and value_down? Thanks in advance for any suggestions.