rexehuk

We've just released support for the new Winwing URSA which can be found at https://www.digitalcombatsimulator.com/en/files/3337917/ https://www.digitalcombatsimulator.com/en/files/3337918/ Happy flying!

Great you got it working. 1. The SVG file now has to be opened with something, right? It can't be used by DCS directly as a kneeboard for example. Correct, you can convert the SVG to an image format to use in a DCS Kneeboard. The current plan it to provide post-processing plugin capability to fill this gap via Joystick Diagrams but for now you must do this yourself. The simplest would be just screenshotting the SVG in your browser and saving it to your relevant DCS kneeboard location. 2. The text spills over the boxes and looks bad or even hard to understand. This is purely down to the template provided not having large enough boxes by default. This was actually one of the first ever templates made (same stick I own) so this template needs a refresh with better standards (text size / capability to have 2 rows of text / min 140px width). 3. Sometimes the names of the buttons have gibberish words/letters This is down to DCS loving to use characters that are evil to SVG. The latest unreleased build fixes this, so should be solved in the next version. 4. My stick for example is set up in Virpil software differently that what the program finds as default(?) so as a result the buttons are misplaced all over the place and the program This is the nature of Virpil and others unfortunately. I cannot ship every possible variant of the stick, because they are infinitely configurable. Users can change BUTTON_1 to be BUTTON_99, a POV to become a 9 buttons etc. In this scenario you need to edit the template, which is very easy to do https://joystick-diagrams.com/templates/custom/ https://joystick-diagrams.com/templates/resources/

That works totally fine for me using Chrome and IE.

Hey, have you tried the setup guide? https://joystick-diagrams.com/setup/

Hey all, Some fixes went out yesterday, full changelog at - https://joystick-diagrams.com/changelog/version-2-0-9-release.html These directly impact DCS World, so recommend you upgrade Happy flying! Rob

Cougar MFDs are available in our discord actually! Have got the total controls MFDs coming. Creating templates is incredibly easy also, and we have a bunch of them in our discord too from the community. https://joystick-diagrams.com/templates/custom/

Hi Hoss, welcome to ask on the discord. I'm one human, and this is an open-source tool with all the documentation for people to make them. If you own the devices it would be fantastic if you could do it and share them back to others. Saying that, I will reach out to TM directly and see if they're willing to provide technical information now.

Version 2 is now live https://joystick-diagrams.com/changelog/version-2-release.html

Yeah, those are the simple cases, but without knowing the true ordering of the layering it's very hard to programmatically assert the end state given an input device of X name. Any information the community can help with will make it possible to add to https://joystick-diagrams.com/

I'm currently trying to understand exactly how DCS World is setting default binds for devices, and a bit stuck on trying to understand how it is done as the binds are not explicitly stored in the users saved games/config/input files but seemingly inferred at runtime. From initial looks, there are several "default" bindings defined in <MAIN INSTALL>\DCS World OpenBeta\Config\Input\Aircrafts base_joystick_binding.lua common_joystick_binding.lua common\joystick\default.lua I've also seen binds defined in <MAIN INSTALL>\DCS World OpenBeta\Mods\aircraft\*\Input\*\Joystick default.lua multiple lua files each which device names that are presumingly some level of default for a particular device (keyed off device name only?) What I'm trying to figure out here is how for a particular device DCS layers all of these on top of each other to produce the current bound state for a device, and if there are more files to consider to build this complete picture. Does anyone have knowledge in this area?

Update: https://www.joystick-diagrams.com/changelog/2024-update.html

Added frametimes

I did some tests people might find useful. To be clear this is not at VR, this is DCS at all HIGH at 3440x1440. NO MT = No Multi Thread GB Active = Game Bar set to "Remember Game" (and rebooted) GB OFF = Game Bar set to not game null

I saw that setting but didn't know what it does... remember this is a game... implies you need it open??

Just an observation as been testing the new MT patch against the normal version and noticed that core parking IS NOT working with DCS at all. Anyone able to verify this? I'm seeing all 16 cores used, in an ideal world should only see CCD0 and have game bar running.

Firstly let me apologise for being so quiet on development of Joystick Diagrams. It started out as a python script purely for a bit of fun, to do something I hadn’t seen done before - expanding it out to where it got to was a great challenge for me! Getting to 100 GitHub stars is great, as a non-professional developer I’m humbled Truth be told, I simply don’t have time to invest in the project anymore. I have some other projects I would like to pursue and don’t want to keep this open and unmaintained, as such I have decided to close it down; but hopefully pass the torch to other talented individuals to maybe get this where it could go. As such, I will plan to close the Application down at the end of 2022, unless someone wishes to continue it. As it stands, the license currently prevents anyone making commercial use of this even after the project is closed so I offer a simple route Fork the project and adhere to license obligations, and maintain a link back to this repository (which will remain archived) - Any forks I'll link out to from the repository If you wish to discuss altering the license, or taking on the name of the tool along with the domain then that will have to come in time with any repository that continues development. In any case, I will help you take on the project and explain the current design changes, vision and technical designs that exist for the next iteration. Thanks again for all the support on the Discord / Reddit - You’ve all been great.

Thanks. It's nothing personal, but there are multiple avenues for bug reports and I can't manage bugs via them all at once (I have no help). Far easier to talk on discord, past a few screenshots and not clog up this thread as it could go on for a while. Hopefully we'll get you sorted out quickly. Rob

If you read my post, you would have seen "I'm more than happy to help on Discord, bit hard over the forum to ask questions/share some data." There are many people who join and get instant help. I'm not doing it via a forum where the feedback loop is days.

We’re alive and incredibly excited to see the DCS World - Apache AH-64D released. With this release came some unexpected new characters in binding descriptions on the F16 and F18, which helpfully broke the tool. This release gets you back up and running. Features Fixes Fixed crashing when trying to generate diagrams for DCS World F16 Fixed crashing when trying to generate diagrams for DCS World F18 Get the latest version at https://joystick-diagrams.com/

Version 1.3 has been released New website is also up at https://joystick-diagrams.com/ - Hopefully can flesh this out with more information separately from the repository. 4/8 Way POV and AXIS Support The tool now supports POV and AXIS support, so if you have any custom templates you'll need to modify them to make this work. The format for templates is POV_NUMBER_DIRECTION (E.g. POV_1_D) Supported POV template directions _U _UR _R _DR _D _DL _L _UL DCS World Fully supports AXIS and POV hats Joystick Gremlin Only supports POV hats AXIS support will come with later versions once tool can read local devices Template Changes Changes to the T16000M template based on feedback Added X52 template Other features/fixes Hardware device names containing white space (VKB) will now work and find templates correctly You can now customise your "No Bind" text in the Config.cfg file When selecting your DCS directory, it should now auto navigate to the directory (if installed in default location) Added Discord link to application Added Donate link (Thanks to everyone who has donated) Some logging changes to capture fatals

Thanks for all this, I have no idea why I'm not being notified about these forum posts! Sorry for late replies everyone. POV hats not supported in current release, the main stick buttons not returning however is odd. This was a new template I made so could be mapping issue, I don't own the stick so had to make these based on public info. Can you confirm what button presses register for the top ones? I do spot an error with the template which is duplicate of button_4 No need to delete the "disabled.lua" as of 1.2.1. Also no other files should be placed in the directories, else the application will probably blow up. It'll ignore directories and stuff, but any files it finds it'll try parse.

Thanks, link didn't update right fixed. I'll double check tomorrow the templates, there could be a mix up in the template naming potentially as it was reworked.

Hotfix shipped for folder issue! @imackenbecause it's Virpil gear I cannot guarantee the mappings. Dependant on the firmware version and configuration by yourself the default button maps can alter. I'm more than happy to help on Discord, bit hard over the forum to ask questions/share some data.

Correct, known bug at the moment. https://github.com/Rexeh/joystick-diagrams/issues/40 Real life getting in the way of updates at the moment - sorry to disappoint you!

Hi, Exports should come out to /diagrams folder. Known issue with newest DCS world atm with them introducing disabled devices.