Jump to content

pellelil

Members
  • Posts

    73
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    DCS
    MSFS
  • Location
    Denmark
  • Interests
    Software development, Flight sim, Music
  • Occupation
    Software Developer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks for the feed-back @Berto72 and glad to hear you got it working !!! I had planed to do some further investigation and in the weekend and make the version of vJoy I am using available for you, as it clearly appeared to be an issue between the version of vJoy driver and the version of the dll Joy2vJoy is using to communicate with the vJoy (however didn't have the time). As time allows I will look further into this, and again thanks for the feedback. Pelle
  2. Strange? From your screen-shot Jov2vJoy is behaving just as it should regarding the logic for the pinky-switch. So I am puzzled why DCS cannot see these changes. You CAN NOT run the vJoy Feeder application at the same time you run Joy2vJoy. However you can run the vJoy Monitor application alongside Joy2VJoy. So please run Joy2vJoy and the vJoy Monitor application at the same time. When you do, and you toggle the pinky-switch to its different positions, do you see button 13 changing in the vJoy Monitor application?
  3. 2: On my sim-PC I run an older version of the vJoy driver, so I don't see the driver mismatch warning on startup. However I do see it on my test-PC which runs a newer version of vJoy. But as you say yourself, the program is running fine nevertheless. As stated in a previous post, in the next version I have added a program-argument which will suppress this warning (will not display it) if this argument is added to the short-cut you use to start Joy2vJoy. 3: Its not necessary to enable "Update checkboxes" while running Joy2vJoy. This is just a "debug-thing", so you can visually see that Joy2vJoy is working as it should. Whether this checkbox is enabled or not, Joy2vJoy will "do its thing" as soon as it is running and it is activated. However if you think there is an issue where Joy2vJoy is not working as it should, you can use it to test that all is working. When you toggle the buttons, and switches on the physical throttle you should both see that the checkboxes on the left (representing the physical throttle) and the checkboxes on the right (representing the virtual device) should switch checked/unchecked. E.g putting the pinky-switch forward the Left (physical) "13" checkbox should be checked, while the Right (virtual) "13" checkbox will be unchecked. Putting the pinky-switch in the middle both the Left (physical) "13" and "14" checkbox should be unchecked, while the Right (virtual) "13" checkbox will become checked. Putting the pinky-switch aft the Left (physical) "14" checkbox should be checked, while the Right (virtual) "13" checkbox will be unchecked. DCS will always assign the axis for all of your devices (both the physical and virtual), so this is why you have to unassign your vJoy-device axis for pitch, roll, yaw and rudder, for each module (aircraft/helicopter) you fly in DCS, for each vJoy device you have created. This is also mentioned in the video (link below contains a time-specification to the place where this is mentioned): In the video I mention how you should map up actions to the off-positions using your vJoy device. DCS will have to see a change in order to map up a button, hence it has to switch from OFF to ON. So in order for DCS to see you are mapping up the virtual button 13, it has to be OFF before you try to map it up. So move your pinky-switch either forward or aft (and leave it forward/aft) so virtual button 13 is OFF, before you try to have DCS assign this button. Then in DCS you assign the virtual buttons, just as you assign physical buttons. If you have multiple vJoy devices you have to make sure you select the column for the correct device. As you can see in the video (link with time-code below), I search for "NVS" for the AH-64D Pilot, and then I first map up the two physical buttons (using the "Throttle" column) to map up physical buttons 13 and 14 (pinky forward/aft) to NVS-OFF and -FIXED. I then leave the pinky in the forward position (also mentioned in the video). Then I find the (correct) vJoy column, and double click the "PLT NVS MODE Switch - NORM" cell. When the window opens I simply moves the pinky-switch to the middle position (which will make the virtual button 13 going "ON). Hence DSC will automatically detect which button is switched from OFF to ON. In your screen-shot it appears you are trying to manually tell it which button to use. This is not necessary, DCS can detect this. For this to work, Joy2vJoy MUST be running while you run DCS, and it MUST be activated. Please verify as stated above that the (Left) virtual button "13" is ON (checked) when the pinky-switch is in the middle-position, and OFF (unchecked) when the pinky-switch is either forward or aft.
  4. When it's ready for release ... hopefully not before
  5. Affinity Photo can open PSB's. It's not freeware but still a lot cheaper than PhotoShop: https://affinity.serif.com/en-gb/photo/
  6. @Jokletox In next version I've added a program-argument (you can add to the short-cut) which will suppress this message. The message is displayed if there is a mismatch between the version of vJoy driver and the version of the vJoy dll.
  7. First of all I expect that you unzipped all files bundled with the Joy2vJoy program to the same folder (it's own folder). Did you create vJoy device #1 with 128 buttons? Did you test that this device is working using vJoy Feeder/Monitor?
  8. Depends how you want to use the 4 directional keys (those with the arrows). Do you plan to use them to slew the TADS or as cursor-keys (cursor on the MPDs)? If the latter then the "CURSOR ENTER" button makes sense, and you might might consider adding a "CURSOR DISPLAY SELECT" key (or what it's called) as well. This is the key that move the cursor to the other MPD. But I guess in this case keys to move the TADS would make more sense ... but then again ... if mapping up joystick/throttle keys up as a CP/G I'm guessing slewing TADS would be one of the first things that gets mapped up, and preferably to an axis for a more smooth experience.
  9. First time I had to rearm I had a hard time remembering what-was-what, so I made this Kneeboard-page to refresh my memory:
  10. Thanks a million Rudel ... it was an easy fix. Still weird they shifted around, but all is working again
  11. On my computer I have I have defined 6 vJoy devices (virtual joysticks) each with 128 buttons. The first I use with some software I have written (and used without any issues since 2019) what lets me assign actions to the off-positions of the 2/3-way buttons on the Thrustmaster Throttle. The other 5 vJoy devices I use with Stream Deck (SD), so that the buttons on the SD generates virtural joystick button-presses, in stead of sending keyboard-shortcuts. All this have worked fine until today where I retired my old trusty CH Products Pro-Pedals and replaced them with a pair of Trustmaster TPR pedals (and added 10 cm extension to my Warthog stick). When I started up DCS/AH64 none of my virtual joysticks seemed to work, and after some investigations I found out all of my vJoy deices had been "reordered", hence assignments in DCS that used to be assigned to the vJoy device which GUID was beginning with "B4" are now in stead assigned to the vJoy device which GUID begins with "37". Long-story-short: Is it possible to do a "search and replace" in some file (guess my control-mapping for the AH64 exists in some .lua file)? I would REALLY hate if I had to map +/- 128 virtual buttons for 6 devices, for both Pilot and CP/G ... it was a drag the first time So any suggestion of which file/location would be appreciated. Here as they were BEFORE replaceing my rudder pedals (37,68,B9 ... is the first 2 lettes of the GUID for each device): vJoy#1 B4 Joy2vJoy vJoy#2 F6 Stream Deck - DCS Module specific vJoy#3 37 Stream Deck - DCS Module specific vJoy#4 68 Stream Deck - DCS Module specific vJoy#5 B9 Stream Deck - DCS Module specific vJoy#6 C0 Stream Deck - General DCS Here as they are AFTER replacing my rudder pedals (now they seam to be sorted by GUID): vJoy#1 37 Joy2vJoy vJoy#2 68 Stream Deck - DCS Module specific vJoy#3 B9 Stream Deck - DCS Module specific vJoy#4 C0 Stream Deck - DCS Module specific vJoy#5 B4 Stream Deck - DCS Module specific vJoy#6 F6 Stream Deck - General DCS So basically I should replace "B4..." with "37...", "F6..." with "68..." and so on EDIT: Had swapped the before/after sets
  12. Stream Deck (SD) and the program you use with SD needs to run in the same way. So if the program "run as administrator" then SD have to "run as administrator" and vice versa. In the past I had to stop SD and then start it as with "run as administrator" to have et function with P3D.
  13. Been flying with CH Products (Fighterstick, Pro Throttle and Pro Pedals) for years, and never had any issues with them. However switched to Thurstmaster Warthog HOTAS in 2017 and haven't used the CH stick/throttle since that time (still using the Pro Pedals). I see no reason why you should not be able to invert the throttle input. You are sure its the correct axis you have mapped up in DCS (that you not by accident hit the mini-stick, so that is mapped up in stead?). Also check in DCS if axis of other controls are mapped up to collective, so you have multiple axis from different devices trying to control the the collective at the same time. Beyond the issues mentioned above I see no reason why you should not be able to invert the axis in DCS. However if you for some reason can't, you are able to invert it in CH Manager, so that DCS simply sees the axis you have already inverted in CH Manager. It's been too long since I last used CH-manager, but I remember it can run in 3 different modes (3 different buttons in the top). In direct-mode (AFIK) the buttons/presses are send directly to whatever program is reading the devices, however there is an indirect mode (perhaps called something else), where the programs (such as DCS) are not able to see the physical device input, but in stead see the virtual devices you create with CH Manager. As far as I remember you will have to map all axis/buttons from the physical devices to the virtual devices you create (in your case you would have to create 2 - 1 for throttle and 1 for stick). I think you are able to define curves and invert axis in the GUI. Otherwise you would have to resort to using a script that do it (I used to do all kind of <profanity> with scripts back them) ... but again ... this shouldn't be necessary ... but perhaps worth a try.
  14. Not easy to fit them all ... no WAS EDIT: There are 2 "IAT Aut/Mn". One of them should have been "OFS ret. TADS LOT"
  15. Mock-up version 2.0 Begins to get a bit crowded Not all. If this offer any inspirations, go with it
×
×
  • Create New...