Mordants

By far the easiest solution! I was looking at lua file alterations and all sorts before I stumbled across this. Don't know why I didn't think of this initially but cheers anyway.

The number string next to CSAR_1_ is not useable in game. I fly the Mi-8 and use the ARK-UD system to home in on a SAR rescue, on channel 4. The Distance and Bearing co-ordinates I put in the doppler system to aid navigation. When within range you may see a flare deployed and within 2k smoke blue/red will be deployed. The equivalent SAR system in the Hind is the ARK-U2. Chucks guide should be able to help you use it.

I wonder if anyone can help me with an issue I have regarding the DCS interface. If I open a web page before connecting to DCS my stream deck will not communicate. Works ok from hotkeys etc. The only solution so far I have found is to restart the computer. I wonder if there is a setting somewhere I could fix. Thanks in advance.

.......I did this from a copy/paste into my mods folder for OvGME so it doesn't have to be done manually after every update, but do what floats your boat. What structure did you use to do this?

Ah I see what you did there, clever. That's why you used Incremental Input (Text Above) because of the two states. Whereas the button I used had just the one state. Brill well I'll alter mine then I'll have the perfect set up for the weapons states. Thanks for explaining that bit. This looks amazing, if I just wanted solely the compass heading, so that I could make the font bigger to read at a glance what tweak would I do in the lua?

Bailey and Bones, this all works fine now, so not sure what went on with the other Lua. Just need to set up the colour change for the stream deck button now. I've also noticed when you fire the guns/grenades the Armed line changes to safe, when you let go the trigger it goes back to armed. Cool. Once again thank for your efforts it's all fantastic stuff and I am humbled by your generosity in giving me and the community your valuable time. Makes an old man happy!

Bailey & Bones1014, wow thanks I'll put it in now. Thanks again for your time. I really don't know how you do all this so quick. Takes me longer to read it I'm sure lol.

I inserted the file you created, whilst the doppler keys still worked the gunnery ones didn't. I use momentary button display for these outputs but tried your suggestion of Incremental Input (Text Above), again to ensure a readout I swapped the doppler number 1003 for 1004 and tried the others to no effect. The individual DCS ID numbers work as I have them mapped individually on other keys. So I'm not sure what's going on.

Not sure why, but I can't get this to show up on the stream deck. I've done exactly the same thing as the Doppler readings you did but the buttons remain stubbornly blank. As a side note and unrelated, does anyone know the solution to this re-occurring problem I have. When starting the computer if a web browser is opened before the stream deck and DCS are running, the two do not communicate. I have to restart the computer and ensure the stream deck and DCS are running first to enable communication. Not the end of the world but if there is a solution, or just a work around that I could do without having to restart the computer that would be great. Cheers.

Never mind, thanks for the swift reply. Guns and ammo indicators brill by the way, I'm saving all the revised lua's just in case of any mishaps in the future lol.

Here it is from the module viewer, left side Pilot

Super effort, you're so good at this. Thanks very much! Could I be cheeky and ask you to look at digitising the compass? I think that would be super cool especially for these old eyes lol.

I'll have a look for a "degree " font character, thanks for the update.

Chewmann, Thank you for your generous offer, it's really great that people help each other out in this community. Whilst I have the Hornet I don't fly fixed wing that often but working out how the buttons work and writing the lua files is generic to the DCS interface I think. For me at the moment it is the lua file script development. As I said earlier modifying an existing one is relatively easy now (After about a year of experimentation), the script generation another. But it's fun trying and you can't break anything. Thanks again for your offer! Bones did the additional bit below for me for the MI-8 doppler, I reckon it would have taken a million years for me to get to the first couple of lines! Truly inspirational. function ExportScript.diss15_panel_drift_angle(mainPanelDevice) local drift_angle_100s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(799) * 10, 0) local drift_angle_10s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(800) * 10, 0) local drift_angle_1s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(801) * 10, 0) local drift_angle_direction if mainPanelDevice:get_argument_value(802) > 0 then drift_angle_direction = "RIGHT" else drift_angle_direction = "LEFT" end local drift_angle_readout = drift_angle_direction .. "\n" .. drift_angle_100s .. drift_angle_10s .. drift_angle_1s ExportScript.Tools.SendData(1000, drift_angle_readout) end function ExportScript.diss15_panel_flight_path(mainPanelDevice) local flight_path_100s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(806) * 10, 0) local flight_path_10s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(807) * 10, 0) local flight_path_1s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(808) * 10, 0) local flight_path_direction if mainPanelDevice:get_argument_value(805) > 0 then flight_path_direction = "BACK" else flight_path_direction = "FORWARD" end local flight_path_readout = flight_path_direction .. "\n".. flight_path_100s .. flight_path_10s .. flight_path_1s ExportScript.Tools.SendData(1001, flight_path_readout) end function ExportScript.diss15_panel_map_angle(mainPanelDevice) local map_angle_100s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(811) * 10, 0) local map_angle_10s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(812) * 10, 0) local map_angle_1s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(813) * 10, 0) if map_angle_1s > 9 then map_angle_1s = 0 end local map_angle_minutes if mainPanelDevice:get_argument_value(814) < 0.05 then map_angle_minutes = "0" elseif mainPanelDevice:get_argument_value(814) > 0.05 and mainPanelDevice:get_argument_value(814) < 0.18 then map_angle_minutes = "06" elseif mainPanelDevice:get_argument_value(814) > 0.18 and mainPanelDevice:get_argument_value(814) < 0.28 then map_angle_minutes = "12" elseif mainPanelDevice:get_argument_value(814) > 0.28 and mainPanelDevice:get_argument_value(814) < 0.38 then map_angle_minutes = "18" elseif mainPanelDevice:get_argument_value(814) > 0.38 and mainPanelDevice:get_argument_value(814) < 0.48 then map_angle_minutes = "24" elseif mainPanelDevice:get_argument_value(814) > 0.48 and mainPanelDevice:get_argument_value(814) < 0.58 then map_angle_minutes = "30" elseif mainPanelDevice:get_argument_value(814) > 0.58 and mainPanelDevice:get_argument_value(814) < 0.68 then map_angle_minutes = "36" elseif mainPanelDevice:get_argument_value(814) >= 0.68 and mainPanelDevice:get_argument_value(814) < 0.78 then map_angle_minutes = "42" elseif mainPanelDevice:get_argument_value(814) >= 0.78 and mainPanelDevice:get_argument_value(814) < 0.88 then map_angle_minutes = "48" else--if mainPanelDevice:get_argument_value(814) >= 0.9 --and (mainPanelDevice:get_argument_value(814) < .81 then map_angle_minutes = "54" end local desired_course = "MAP ANGLE" .. "\n" .. map_angle_100s .. map_angle_10s .. map_angle_1s .. "." .. map_angle_minutes ExportScript.Tools.SendData(1002, desired_course) end function ExportScript.GrndSpeed_and_Drift(mainPanelDevice) local ground_speed_100s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(792) * 10, 0) local ground_speed_10s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(793) * 10, 0) local ground_speed_1s = ExportScript.Tools.round(mainPanelDevice:get_argument_value(794) * 10, 0) local drift_angle_needle = string.format("%.0f",(mainPanelDevice:get_argument_value(791) / 2) * 100 ) .. "ยบ" --[[local drift_angle_needle if mainPanelDevice:get_argument_value(791) <= 0.001 and mainPanelDevice:get_argument_value(791) >= -0.999 then drift_angle_needle = "0ยบ" end]] local ground_speed_and_drift if mainPanelDevice:get_argument_value(795) > 0 then ground_speed_and_drift = "GRN SPD" .. "\n" .. "///" else ground_speed_and_drift = "GRND SPD" .. "\n" .. ground_speed_100s .. ground_speed_10s .. ground_speed_1s .. "\n".. drift_angle_needle end ExportScript.Tools.SendData(1003, ground_speed_and_drift) end

Wow, thanks for your efforts in this. I thought it might take me some months to work it out using Charles Tytler vids. Though I have watched them many times over its still magical to me! I'm going to test this this afternoon. I'll report back later. Really, really appreciate you doing this. I look forward to the gun counters result. Bones works an absolute treat, you are a super star! . What you have done in four buttons I did individually in 12 lol. Not sure what "ยบ" is though. Thanks very much.

Wow you're so clever, I would love to see a series on Youtube that shows step by step how to do this stuff. I can modify existing lua's scripts to show stuff on my streamdeck, took a while to get the hang of it and the model viewer is a really handy tool to show values etc. But I can't do the clever stuff. I would like to get the Mi-8 Ground speed and drift indicator "ground speed" value on to one key, at present it's on 3 keys hundreds, tens and units. You and Bailey are the stars of lua editing it seems and all hail to Charles Tytler for the DCS Interface!

It happened to me also a while ago, found the "Synchronize cockpit controls with HOTAS controls at mission start" and it sorted my problem with the Mi-8 hurling itself around on a hot start mission. With having to trim on take off it was better for the controls to be at neutral for me anyway.

Regards the hovering, I've done that earlier so it's already implemented. Just hover tree top level for about 5 seconds and the pilot hops on board.

Phew that's a relief, not so dumb after all!

Re we added a csar menu in F10 radio menu to help you find people. Thanks for that but. I'm not too bright though, how do I interpret the first bit of the code I've highlighted in red CSAR_1_7089.721: 299 for 271.5 kilometres I read through a copy of a CSAR lua script and found the line below, but couldn't see a relationship with those co-ordinates. csar.coordtype = 3 -- Use Lat/Long DDM (0), Lat/Long DMS (1), MGRS (2), Bullseye imperial (3) or Bullseye metric (4) for coordinates Sorry in advance if its a dumbass question.

CSAR Operations I had a similar scenario where in I took of in a Huey from the most western side of the map far from the frontline. My FM Homing took me all the way to the frontline a good twenty divisions with no deviations for any other downed pilots on my route. FM Homing gives bearing only not range for downed pilots. I just wondered if there is a way of determining, via the map maybe or F10 menu, the rough co-ords of the downed pilots. Unless others can enlighten me of a different way to search for the downed aircrew?

I did the same one about a month ago, works a treat! I found the assembly a little tricky though, very tight specs and I was worried I might strip the threads on the 3dprinted parts. But went super careful and it was fine.

For your helo re- supply missions in an MP server then I could definitely recommend Cold War 1947 - 1991, many scenarios with most containing the Mi-8.

I'll take them off you. I'm in the UK

You are definitely the man! I've downloaded and installed the profile and works a treat, love it. Now I'm just going to analyse how you did it to see where I went wrong. Though I'm sure I tried all permutations of negative numbers. Obviously not otherwise we wouldn't be having this dialogue! Once again thanks for your generous help, I am indebted.