Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Add Support for IL2 CoD, IL2 GB #79

Open
Rexeh opened this issue Jan 20, 2024 · 3 comments
Open

Feature Request: Add Support for IL2 CoD, IL2 GB #79

Rexeh opened this issue Jan 20, 2024 · 3 comments
Labels
New Game/Tool Support Feature that will enable additional games or programs to be supported

Comments

@Rexeh
Copy link
Owner

Rexeh commented Jan 20, 2024

Copied from #69

  • Add support for IL2 series games
@Rexeh Rexeh added the New Game/Tool Support Feature that will enable additional games or programs to be supported label Jan 20, 2024
@Rexeh Rexeh changed the title Add Support for IL2 CoD, IL2 GB Feature Request: Add Support for IL2 CoD, IL2 GB Jan 20, 2024
@edwardwbarber
Copy link

Hi! I'm just scratching the surface of the code structure for joystick diagrams, but I wanted to offer up two scripts that could be adapted for this issue:

  1. Importer for IL2 GB
  2. Importer for IL2 CLoD

Amongst other things, respectively, they parse GB .actions files and CLoD .ini config files for devices, button/axis id's, bindings, and descriptions - which all get returned as a dict. They're for my fork of joystick gremlin, so there's some extra logic around it that would have to be re-worked... but the core logic for how to parse each line of those config files should be reusable here.

@Rexeh
Copy link
Owner Author

Rexeh commented Mar 20, 2024

Hi! I'm just scratching the surface of the code structure for joystick diagrams, but I wanted to offer up two scripts that could be adapted for this issue:

  1. Importer for IL2 GB
  2. Importer for IL2 CLoD

Amongst other things, respectively, they parse GB .actions files and CLoD .ini config files for devices, button/axis id's, bindings, and descriptions - which all get returned as a dict. They're for my fork of joystick gremlin, so there's some extra logic around it that would have to be re-worked... but the core logic for how to parse each line of those config files should be reusable here.

Hey @HaddocktheHorrible,

Thanks for posting these up, they look pretty much there for being able to use with Joystick Diagrams. As of version 2.0 I opened it up to a plugin system so if you're up for it you could convert these to plugins without much effort.

The only mechanism you really need to adapt it to is the input library

https://github.com/Rexeh/joystick-diagrams/blob/master/docs/plugins.md
https://github.com/Rexeh/joystick-diagrams/blob/master/docs/profiles.md

I've been waiting for the first plugin from the community before adding in the install capability, and very happy to work with you if you want to take this on! Might be worth hopping into Discord and can cover questions there, and can update documentation alongside questions you have.

@edwardwbarber
Copy link

Thanks! I'll see if I can take a look at the plugin system when I can - and probably have follow-on questions for the Discord. Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Game/Tool Support Feature that will enable additional games or programs to be supported
Projects
None yet
Development

No branches or pull requests

2 participants