Jump to content

Joystick Diagrams - Automated DCS Joystick diagrams


rexehuk

Recommended Posts

I guess this does not work with TARGET and DCS or IL2. I try to export profiles and it does not work, I see absolutely nothing. Of course, I'm using DX SCRIPT commands in DCS, so I don't guess I will see anything, will I?... Shame....

Hoss.

Sempre Fortis

Link to comment
Share on other sites

  • 5 months later...
  • 4 weeks later...
37 minutes ago, _Hoss said:

Do you plan on including the TM Viper TQS and the Viper Panel templates?

Thanks,

Hoss

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.

  • Like 1
Link to comment
Share on other sites

Posted (edited)
On 2/29/2024 at 11:20 PM, Bvv.Fr said:

great software @rexehuk, thanks a lot!!!!!!!! 🤩

 

il will create MFD cougar templates

 

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/

 


Edited by rexehuk
  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

I'm having a problem understanding how it is supposed to be used. Any tutorial on this?

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Link to comment
Share on other sites

Yes I did and the profiles I tried to update I have yellow warnings and if I export them like that I get some very small svg files with unreadable text on the buttons and no pictures for the joystick or Throttle... The stick is a Virpil WarBRD and the throttle a Winwing Orion 2 F18.

here is an example:
f8171-RIGHT WarBRD-Mi-24p_pilot.svg


Edited by zaelu

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Link to comment
Share on other sites

24 minutes ago, zaelu said:

Yes I did and the profiles I tried to update I have yellow warnings and if I export them like that I get some very small svg files with unreadable text on the buttons and no pictures for the joystick or Throttle... The stick is a Virpil WarBRD and the throttle a Winwing Orion 2 F18.

here is an example:
f8171-RIGHT WarBRD-Mi-24p_pilot.svg

 

That works totally fine for me using Chrome and IE.

 

 

Screenshot_2024-03-18-21-31-54-11_40deb401b9ffe8e1df2f1cc5ba480b12.jpg

Link to comment
Share on other sites

11 hours ago, rexehuk said:

That works totally fine for me using Chrome and IE.

OK, I've managed to find the first problem. The images are OK but my viewer (Irfan View) doesn't display the picture just the rest... tables and text.
Then there are the next issues:
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.
2. The text spills over the boxes and looks bad or even hard to understand.
3. Sometimes the names of the buttons have gibberish words/letters
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 things that are 17 buttons unassigned.
In the second picture you can see how messy it loks and also I can tell you that buttons are misplaced. For example the left HAT (POV) is actually used for calling the Petrovich AI interface by pressing down then the directional buttons of that HAT are not assigned for Mi-24 Pilot and are used for Petrovich interface.
However when I create the AI interface file that one the buttons are correctly assigned to that HAD... still the text is completly messed up though. See picture 3.

image.jpeg

f8171-RIGHT WarBRD-Mi-24p_pilot.jpg

002a.jpg


Edited by zaelu

[sIGPIC][/sIGPIC]

I5 4670k, 32GB, GTX 1070, Thrustmaster TFRP, G940 Throttle extremely modded with Bodnar 0836X and Bu0836A,

Warthog Joystick with F-18 grip, Oculus Rift S - Almost all is made from gifts from friends, the most expensive parts at least

Link to comment
Share on other sites

2 minutes ago, zaelu said:

OK, I've managed to find the first problem. The images are OK but my viewer (Irfan View) doesn't display the picture just the rest... tables and text.
Then there are the next issues:
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.
2. The text spills over the boxes and looks bad or even hard to understand.
3. Sometimes the names of the buttons have gibberish words/letters
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 things that are 17 buttons unassigned.
nullnull

image.jpeg

f8171-RIGHT WarBRD-Mi-24p_pilot.jpg

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/
 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...