Closed zahnatom closed 2 months ago
So one thing I'll mention is that the format by which these are exported is not uniform across all modules. All modules name their data differently - so I don't know that there's a uniform solution we could use here, other than something like every module exports items 1-100 of each display but I don't see that being a very useful solution.
This is something we could consider in a limited scope on a module-by-module basis.
i'm not entirely sure what the best option is but an acceptable solution i think would be to have it work like with ExportScripts where you write some lua code and only export the stuff that you want. My point of reference here is this https://www.youtube.com/watch?v=XqUi-plg2K0.
Bios isn't really designed in a manner that would be extensible like that. I mean you could technically go in and edit the lua to export whatever you want, but I don't know that there are any additional tools I can provide to make that easier.
Version
Aircraft
Any
Control
MFDs, HUDs, etc
Description
In the lua console(and lua in general) it's possible to get strings from MFDs, the HUD, etc through "list_indication(N)". It would be great to have this be exportable to arduinos to replicate certain texts without having to export the entire screen. Here's an example: on aircraft that have MFDs, the buttons have some text associated with them, which is displayed on the screen. which i'd like to export to make interactive touch buttons instead of hardware buttons. end goal is to have this work for the Eurofighter Typhoon which has those buttons with screens but thats not here yet :p
Screenshots
Additional context
i put some code snippits for the f-15e in the discord https://discord.com/channels/533342958712258572/1287518951709999287