DogsInTrousers

Sorry, didn't realise after every combat sortie we had to submit video to the MoD. Noted. "must be installed and running for every combat flight" I'm intrigued, source?

I think the KA-50 is the closest we'd ever get to an Mi-28 in DCS in our lifetime! Best we can hope for with (Redfor) FF is something that was exported from USSR/RF, then find a happy medium within the capabilities and variants. The SU-25A is a perfect candidate for that, exported to like 20+ different countries. A Mig-23/27 would be a great addition, for the same reasons as the SU-25A. ED could possibly lever in a FF SU-27 somewhere down the line, the US has apparently an SU-27P somewhere (sans ground attack capability) and an ex-Ukrainian SU-27UB trainer. I'm sure they could easily figure out the ground attack element. I would think an FF SU-27 could be a possibility within 5 or so years if we are lucky, if the new FF Mig-29 is anything to go by.

I would love to see the SU-25A as a FF module. It would be a perfect companion to the incoming Mig-29. While I understand the challenges faced by ED in developing "redfor" modules, redfor is severely lacking in FF modules to bring it to the later end of the Cold War era. I would have thought there would be enough export models hanging around in ex comm-bloc museums. Sure the heli's are nice (mind, the Mi-8 is screaming for a facelift) but we really need something else. I'm very excited for the Mig-29, but an SU-25 would open the door for awesome campaign building in Afghanistan! With the Mig-23 probably on ice for the immediate future, there's not much to go with and the "western" hardware just keeps rolling into DCS. The only dilemma I see with a FF SU-25 is how much should ED charge for it? If they offer the same visual fidelity in the incoming free SU-25 upgrade, what's the value that should be placed on full FF integration and PFM? $30? $40? $50? All I hope is with the incoming SU-25 upgrade, they give an option to remove the stupid HUD camera canister! Please ED!!

UPDATE Figured it out! I kept changing the iCommandPlaneLaserRangerOnOff to individual on and off lines. Need to be kept as a single on/off entry in each line of code, then the switch configured after that. Here's the correct code line. Now to work on the rest! {down = iCommandPlaneLaserRangerOnOff,value_up=1.0, name = _('Laser Designator On'), category = _('Sensors')}, {down = iCommandPlaneLaserRangerOnOff,value_down=0.0, name = _('Laser Designator Off'), category = _('Sensors')},

OK, Added the following to the code, {down = iCommandPlaneLaserRangerOn,value_up=1.0 name = _('Laser Designator On'), category = _('Jim')}, {down = iCommandPlaneLaserRangerOff,value_down=0.0 name = _('Laser Designator Off'), category = _('Jim')}, Both settings now appear in the menu and are bindable, problem.... they don't do anything. Doesn't turn the laser on/off.

Hi all, Trying to add additional keybinds to the SU25 using the following method, (https://github.com/Quaggles/dcs-input-command-injector) to make the most of my Virpil control panel. I have run into a hiccup and can't figure out why. I'm attempting to remap the SU25's Laser to be a 2 position on/off switch instead of default single button on/off. I have added these lines to a default.lua in the correct folder, however it only gives me the new keybind to "Laser On" (top code line) and not off, which I can't work out why. Is it because this switch for the laser is hardcoded to only be a single entry on/off configuration? DCS log isn't showing any coding errors. return { keyCommands = { -- Sensors {down = iCommandPlaneLaserRangerOn, name = _('Laser Designator On'), category = _('Jim')}, {down = iCommandPlaneLaserRangerOff, name = _('Laser Designator Off'), category = _('Jim')}, } } I successfully added controls to the Ka50 the same way with success (converting single on/off > 2 position on/off) but the SU25 won't have a bar of it. Any help is appreciated, I'm stumped. Jim