Bailey

Your .lua should have comments for each of the numbered arguments. A Search/Find for “alt” would be my first try.

Post what you cant get working with what you think you need to do to get it working. Someone may be able to help you from there.

You might want to post on the new dcs-interface thread for the dcs bios implementation. The link is about 2 posts above your post.

I don’t think this explains the problem. Colons inside strings aren’t showing up. But, that link was a great read. I know more about lua now!

Where did you find that? I guess I need to polish up on my GoogleFu.

Hello, thanks for letting me know. It is nice to hear that it's still working. Np!

Restart the mission using LShift+R. I think DCS-ExportScripts uses ":" as some kind of important thing. I haven't found a way to use it in a display.

That look fine to me. Does it look good ingame? I am getting both normal and CW DCS Comms and outputs. You can attach your CW lua and I can compare.

Iirc the knob in the game is "continuous" and fluid. If that is the case, what you will need to do is make an equation that translate the position of the knob to the position of the radar (aka, what degree the knob is pointing to). That equation may take a bit to figure out. What I would likely do is, say for example the radar degrees go from -50 to +50. I dont like to think in negatives so I'll add 50 to make the new range 0 to +100. That makes it much easier because with a knob that is 0 to 1 the equation will be `knobPosition x 100 = radarAngle`. Doing that for knob that is half way (0.50) will give us 50 degrees. But wait, remember that 50 we added before? We need to take it back. So now our equation becomes `(knobPosition x 100) - 50 = radarAngle`. Which in the above scenario gives us 0 degrees. Done.

Darn. I likely used round()? you might be able to change that to math.floor() to fix it. That happened with another module recently, the UH-60L iirc. The issue being that the display of the graphic does not exactly match the parameters for the rounding for that specific number. Nope. Go for it. Let me know if it turns out well.

UH-60 has similar problems with their "EFM" switches. You'll need to use the spitfire .lua. https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/SpitfireLFMkIX.lua

That's quite a bit of stuff in one go. Have you tried to export each individually to see where the problem is? After you do that you can combine them and not have to worry about which one broke the Tile. You might also want to date out the stuff you aren't using like the Presets code (for testing).

1) Yes. https://www.digitalcombatsimulator.com/en/files/3313144/ 2) No.

Yes, those switches do not work correctly in the module with stream deck.

Now that I think of it, this stems from a problem that I found maybe over 2 years ago, reported, and ED never got around to fixing. Yesterday I tried to rebind by hand with no luck, unfortunately. If you can, maybe normal streamdeck hotkeys may work for you instead.

You aren't missing much. The UH-60L is still in development and therefore a number of things you would expect to work don't due to the state of the module itself. Your streamdeck is likely fine. The connection is likely fine. The only thing that I can say for sure (more or less) work is the exported data such as engine readings and HSI readings. The UH-60 devs are still working on switches and what not.

Also, please define "not to be controllable". I think I am seeing funny things too.

Iirc, inputs should be a “simple” formatted string that (iirc) terminates in \n? And with the A10 working, sounds even more odd. You are using the FlightPanels DCS-BIOS, correct? In the past I made a VoiceAttack profile that used dcs-bios instead of keybinds for the inputs (the L-39 one). I believe there is someone working on a partial DCS Bios VA for the A4 right now. I, and I know a few others, would be glad to take at look the early version of the app and try it out before “official” release.

Great work! I have noticed that many profiles lack animation arguments like that. I may do a sweep of a few to provide them now that there is an "unclickable" extract tool. Edit: Wow, F-14 does it quite differently. Thanks for the heads up!

Yes, you should be able to get the argument for the position of the levers as a decimal and convert it into a format you want, like percent.

Nope. I just did it the old school way. Copied your lua and pasted it in mine and reviewed the changes. Thank you, the Library has been updated! Surely we'll have another chance to try this Pull thing again in the future.

I see your fork, but I don't see your pull request..... wait, hahaha, you requested the wrong git. Request this one https://github.com/asherao/DCS-ExportScripts/pulls. You sent a pull for s-d-a's. You can cancel that pull by going to the request and near the bottom click close (I recently did something similar on accident too.)

did you see my technique? Look at this post closer. https://forums.eagle.ru/topic/283178-dcs-exportscripts-for-stream-deck-community-github-library/?do=findComment&comment=4873683

I honestly have no idea. My solution is a workaround. Anything more than that is uncharted territory. I'll keep an ear out for a solution though.

Now what you do, I think, is request a Pull using the most recent version of your fork. Git is still a mystery to me too. After having the issue, close DCS and check the Saved games/dcs/logs/dcs.log. there may be good info in there. thats how i determined that a usb hub was malfunctioning the other day, funny enough it gave similar symptoms as you. you can post the log here if you feel comfortable doing so.