Bailey

FYI

Hello! I just stumbled onto this. I sure do wish the userfiles had a comment notification feature. If you are comfortable with github and code, here is the git. Feel free to edit at your leisure. https://github.com/asherao/DCS-Module-Hider-DMoHi I have used your mod and I am pretty excited. Not only does it work well, but it also seems to solve a requested feature from people that use DCS: DiCE. When I have time I'll gladly integrate your solution into DMoHi!

DCS Mi-24P Hind VoiceAttack is now live! https://www.digitalcombatsimulator.com/en/files/3318032/ First post has been updated.

Haha, ty. Would it be possible to have a set of presets? For example 5 sets of 20 that can be picked via the special options menu? For example if I want to play on Muiltiplayer ServerX I would pick the "X Radios" Preset. Presets could be defined via lua outside the game in a specific format. This would "simulate" the ground crew presetting the radios before a sortie or operation, which happens irl on some platforms. P.S. Now that I think of it, the presets could be the mission maker defined radios + the customs. So, if I have Preset 1 with 123.00, 124.00, and 125.00, the actual presets in the game would add those three to the 20 (or so) that were already defined by the ME. E.g, the users presets would always start at 21. Kinda complicated, but just throwing ideas out there.

Yea. Look at the post above yours.

You can't, but there is a Standard SD Profile in the download just for you.

This one for DCS-Interface. https://github.com/charlestytler/streamdeck-dcs-interface/releases/tag/v1.0.4 For DCS Bios / DCS Control the new version that includes the Hind isn’t officially out yet, but the individual Hind file is updated if you feel like getting them now. https://github.com/DCSFlightpanels/dcs-bios

You poor child, not using model Viewer! This must be addressed at once! Go to DcsInstallLocation/DCS/bin and you'll find something like modelviewer.exe. Launch it. Then Open a model. Navigate to DcsInstallLocation/DCS/aircraft/<pickAircraft>/cockpit/shapes/aircraftName.edm. The model of the cockpit should load. Now find the "show arguments list" button. Now while in the cockpit click the button on the toolbar with the running red stickman. You'll see everything animate. The trickiest part is knowing which one of the few hundred arguments go to which stwich, light, or guage. Trial and error is the main way of finding out unless someone else has written them down in DCS-ExportScripts, for example. I'm busy, so that's all I can say for now. Looking forward to diving into your posts later.

I appreciate the praise of my code. I try to write it so that the next week version of me knows what the heck the last week version was thinking, hahah. Your “auto-linerazation” functions sounds like a great idea. Idk what would be causing the pauses. You code logic is way over my head, but I’ll take a look from time to time to see if something clicks. one thing that I saw that may be an issue is that some of the gauges use the negative side of the value numbers too. A quick example would be the vertical velocity indicator where it’s kinda like {-1,0,1},{-30,0,30}. Would your “if current_value <= 0, return 0” prevent the VVI from being read correctly? The Hind radar altimeter gauge is quite linear before and after about 50 meters. Put some data points in Excel and you’ll see what I mean. In the right column put the number that you want to sample (such as 50) and then in the left column put the Value (such as 0.123). I sample the major representations and any that simply look like they could be a point in which the rate or linear-ness changes. So specifically for the Hind radar altimeter I sampled all of the numbered meters (0,20,40,60,etc). My result in excel was a line that had only 1 “elbow” in it, so that’s where I split the data and created the two equations. Sometimes either due to how the gauge is modeled or through sampling error the lines are not perfect. If that’s the case I choose the “best fit” for the range that the player will be in most of the time. You will notice this with the hind airspeed. Above 400 kmph the SD readout gets some huge errors. But honestly, if you are that fast and you are worried about your airspeed, you were about 50kmph too late due to VNE and you are currently in an uncontrolled right bank dive On the other hand, whoever did the Vipers airspeed gauge did us a favor. The gauge itself isn’t linear, but it is coded such that 0.100 is 100kts, 0.200 is 200kts, and so on. The result is that if you smoothly increase the argument at a steady rate in modelViewer, the gauge will visually start fast and then slow down. It made the conversion super easy because all I had to do was multiply by some factor of 10 and there was no “re-linerazation“ that had to be done.

I personally prefer one profile for everything. I feel like it makes life easier. I typically make my profiles at most 2 layers (1 layer deep), requiring a single back button press at any time. Then again, I am also thankful that I have an XL. That would be interesting to see a multi-button multi-state. How would you determine which state is "switched on"? In the F18 parking brake exercise we used a "multi-action switch" that switches between two "multi actions" automatically. The multi-action switch supports two image states, accordingly.

Thank you. You can see the code here https://github.com/asherao/DCS-ExportScripts/blob/master/ExportsModules/Mi-24P.lua, lines 1107 to 1276. The "universal" IDs are 44224 - 44231. I have used the same structure on the F16 too (https://github.com/asherao/DCS-ExportScripts). Take/copy what you want for other modules and improve on what I had. In the "extras" section you will see that there is support for image changes, for example, if you are about to hit 350 kmph in the hind, the background will turn red. A readme may be needed, but it's all there. The reason for the km is specifically for the Viggen. That's it. "How did you "re-linearize" radalt on this plane?" Which plane? Can you show the code? I am currently having trouble getting radalt for the F16 due to a specific condition where if the thousands number is not present in the export, the system kinda freezes. I dont have this problem with the Hind or any other analog guage. For the non-linear guages I get some samples into excel and have excel make a function via a line graph. From there I decide if I need to break up the equation into two or three parts. It takes a little bit to get used to doing, but it is more simple than trying to make some 4th order differential equation or something. You can cee an example of this in the Hind lua around line 1235, here: https://github.com/asherao/DCS-ExportScripts/blob/master/ExportsModules/Mi-24P.lua#L1235 So yes, you do need to make it linear, but it is still approximating the entire range of values. Kind of like drawing a square from a circle. The more lines you draw, the more it becomes more of a circle.

Possible first step https://github.com/asherao/DCS-ExportScripts

I think this guy solved it https://forums.eagle.ru/topic/276992-streamdeck-emergency-brake-issue/?tab=comments#comment-4724051

Making progress. Don't mind the colors and typos. WIP. I am working with a few other folks to get some aircraft conditions exported and read for some special treats.

Take a look here ‘DCS World OpenBeta\Mods\aircraft\<PickAircraft>\Cockpit\Scripts\Macro_sequencies.lua’ and this post

I went by the Bar Raiders discord (it's not what you initially think! BarRaider is a Stream Deck app creator) and asked a similar question. They replied with Super Macro: https://github.com/BarRaider/streamdeck-supermacro/releases/tag/v2.1 It works well. In "Short Press" put {{RALT}{a}} Change the "L" to "R" if you want the other one. You can also do something like: {{RALT}{RSHIFT}{a}} if you wanted to. It is working for me in DCS. Oddly enough I sometimes have to keybind it "by hand" in the DCS Options Controls menu, but it works fine in-game. Here is the keyboard list for the modifier keys: https://github.com/BarRaider/streamdeck-supermacro/wiki/Keyboard-Commands Oh, and change {{a}} to whatever letter you want. I'll need to dig into Super Macro more bc it looks a lot more useful than I initially thought. Thanks!

Hahaha, I didnt see you wanted the emergency brake. That's pretty funny that you got it on your own in the end. Nice work!

No.

This is a nice idea. I think I might go through some the different modules and make some kind of “universal unit conversion panel”. An airspeed square. A pressure square. A QNH/QFE square. An altitude square. Etc. hopefully I can find some super unique export IDs so that the same buttons could be used for all modules. The math and compatibility would be done in the individual luas.

I use US keyboard and language. The issue is still there for me.

That was the first time I have used any multi actions in that way. I can see it opening possibilities with macro sequences like completing a personalized autostart or having a single button to dial a specific frequency or a handful of other things.

Keep flying.

Keep flying and the paper map will change automatically. There is no "manual" way to change it.

Here is a SD profile with this command as the only thing. DCS F18 Parking Brake.rar

Got it. ED didn't exactly make this easy. Thankfully Elgato themselves saved the day with the Multi Action Switch that no-one uses I think that the stow commands can be optimized by about 50%. The way that I successfully found out the right sequence was by looking at the autostart lua and matching the devices and their respective values. Enjoy! Oh, I almost forgot that there is a condition where the wrong action may fire after you hop in a new plane. It's fine, noticeable, and does not cause any problems. The next press of the Command resyncs everything. You can also set a custom pic AND text for each state of the "switch" to make it more fun and informative. Also, my F-18.lua had two [240] entries. I personally commented out the "[240] = "%.4f", -- EmergParkBrakeHandle" one by making it "-- [240] = "%.4f", -- EmergParkBrakeHandle".