DCS World: Handle DCS defaults for device that are not exposed in Saved Games configurations

[DracoLlasa]

When i run the program and select my saved games folder, select the A-10C and click export joystick profiles, it seems that it is only showing any custom updates i might have made. i have attached the results for the A-10C and my TM Warthog HOTAS.
You will see there are many bindings missing that should be there based on the stock config.
DCS - HOTAS Warthog_A-10C.zip

[Rexeh]

Thanks for reporting, are you able to send me your DCS config file for the stick/throttle under the A10-C/joysticks config folder?

[Rexeh]

Hey @DracoLlasa I've done some digging, and found a new scenario that is going to require some work.

Essentially this will affect anyone using default DCS binds, where they exist for your stick. Anyone using a fully customised profile will be ok.

From initial look, default configs are stored in C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft*

To fix this is going to require a pretty substantial rework to the parser, but probably something I need to handle to make it useful!

I will need to come up with a design/solution before I tackle this to ensure bases are covered.

[DracoLlasa]

Thank you for the update, i think this could be a very useful tool, especially why learning new modules.
i will follow the project and watch for updates that i can test out. Let me know if you need any testing related help

[nima3333]

Hi, I think this is not fixed in last website release (1.4.1). If it is not done, may I try to help ?

[Rexeh]

After further analysis, this is not trivial and requires more understanding of DCS behaviour.

https://forum.dcs.world/topic/344171-information-on-dcs-default-bind-allocation-logic/#comment-5387295

This will require

• Extension of plugin system to allow plugins to specify multiple setup items (current is one path expected)
• Parsing of new file types in order
• Dynamically handling the default device configuration and then layering on the existing parsed config

Welcome someone to take a look at the parsing/plugin integration piece and we can go from there with extending the plugin system to expose further settings to the client.