bones1014

Button type is a Momentary button/Display (UFC) with the 3010 in the Title Text Change on DCS Update Settings

I use this for flare and chaff. Didn't make one for gun count since that's displayed on your HUD anyway. function ExportScript.Chaff_Counter(mainPanelDevice) --export RIO Chaff Counter local chaff_10 = string.format("%.f",mainPanelDevice:get_argument_value(392) * 10) local chaff_1 = string.format("%.f",mainPanelDevice:get_argument_value(393) * 10) ExportScript.Tools.SendData(3009, "CHAFF" .. "\n" .. chaff_10 .. chaff_1) end function ExportScript.Flare_Counter(mainPanelDevice) --export RIO Flare Counter local flare_10 = string.format("%.f",mainPanelDevice:get_argument_value(394) * 10) local flare_1 = string.format("%.f",mainPanelDevice:get_argument_value(395) * 10) ExportScript.Tools.SendData(3010, "FLARE" .. "\n" .. flare_10 .. flare_1) end

They say it's available on the 20th. does that mean on the store only or on the store and download after purchase?

Not a bad idea. I'd also like that. [emoji106] Sent from my SM-G781U using Tapatalk

Well that is fantastic

I'm having exactly this problem right now except it's the right MFD that's doing it. Do you know which module keybind is causing the problem? EDIT I just removed the key binds like you did and it fixed it. Now I guess I'll put one folder back at a time and see which one is the problem. EDIT Looks like it's the binding for the NS430.

In the Harrier I am able to assign the bright, gain, etc inputs in the key bindings to the appropriate buttons on the left device. When I go back to the game they don't work. The same bindings work on different devices like my HOTAS. The right side MFD works fine. When I do the same in the F-16 both sides work fine. Sent from my SM-G781U using Tapatalk

Still having trouble with this. I can get other inputs, like buttons on my HOTAS, to work in game but the thrustmaster buttons don't. Any ideas? They work in other modules just fine like the f-16.

Those buttons with on the right MPCD but the left they don't except in the key binding options Sent from my SM-G781U using Tapatalk

No I don't have any double bindings.

I have the thrustmaster MFCD frames with buttons mapped to the MPCD corner buttons for Gain, Cont, etc. DCS world recognizes the button presses in the controls menu but in game they don't do anything and I have manually click the corner buttons to adjust them. What could the cause possibly be?

Thanks for the tip. The == fixed it. stupid little stuff ruins everything! lol Sent from my SM-G781U using Tapatalk

Working on a flap mode and angle readout for the harrier. For some reason in my function when I add this if/then/else it crashes the export. I don't know why. I THINK I'm doing it correctly. If I change the local flap_mode variable to equal a constant it works just fine. function ExportScript.FlapAngleMode(mainPanelDevice) --Flap Mode local flap_mode if mainPanelDevice:get_argument_value(454) = 1 then flap_mode = "CRUISE" elseif mainPanelDevice:get_argument_value(454) = 0.5 then flap_mode = "AUTO" elseif mainPanelDevice:get_argument_value(454) = 0 then flap_mode = "STOL" end --Flap Angle local flap1 = string.format("%1.0f",mainPanelDevice:get_argument_value(455) * 10) local flap2 = string.format("%1.0f",mainPanelDevice:get_argument_value(456) * 10) ExportScript.Tools.SendData(5000, "FLP ANGL" .. "\n" .. flap1 .. flap2 .. "\n" .. flap_mode ) end

Thanks for verifying

Not that I've noticed. The Viggen has the worst mach tuck. The F-16 doesn't but that could be due to the fly by wire compensating.

While in the backseat of the F14 I am able to use my pilot bindings to move the weapon selector on the pilot stick. The input isn't bound to anything as in the RIO control set.

Not the case for me. It's the same image from the same monitor. Gotta be a filter. Sent from my SM-G781U using Tapatalk

The thing is there ISN'T a brightness rotary for that screen in the front of the F-14 because that screen doesn't exist. It's definitely some kind of filter. The brightness is all the way up when I move to the back by pressing 2. Sent from my SM-G781U using Tapatalk

I have my RIO seat screens exported to external monitors. When I jump in a plane in instant action and am sitting in the front seat the exported monitor screen is nice and bright. When I move to the back it dims considerably. How do I keep the bright image in the back seat? See the screenshot for examples. Left is the unfiltered front seat image and the right is what it dims to in the RIO seat.

A friend of mine and I are having some trouble with F-14 multicrew and I'd like to see if maybe my new Virpil stick and software are the cause. Just today I was in the RIO position and some of the controls I have mapped as a pilot were working in the back seat. Specifically the flap lever on the CM3 throttle which is mapped in the pilot position as an axis and the pilot weapon selector witch is using the Constellation analog thumb stick which has been mapped from an axis to a button input in the Virpil software. If anyone has the time to test and get back to me I'd greatly appreciate it. I'll even sit front seat to help test if we can line up schedules

A friend of mine and I are having all kinds of controls from the RIO seat affecting the Pilot seat and vice versa. For example I can control the weapon selector from the RIO seat and the RIO ICS PTT activates the pilot PTT.

do you have the correct path listed in the top box when looking up an ID?

What is Igla? Inbound ground launched something?

Have you finished with building this profile and is it available?

I use them for engine start switches or canopy switches in one mode. Could also be fire extinguisher switches. Sent from my SM-G781U using Tapatalk