Bind X and Y AXES TO WASD keys

[Ron61]

Do as shown in my screenshot and the buttons will work when you move the handle along the X and Y axes.

[wildwolf]

If I reset joystick to default, and turn on virtual keyboard, set POV screen to this:

The joystick has no input from pushing left, right, forward, or backwards. Nothing. To confirm, you stated earlier I do not need the older settings at all?
(setting wasd to 76, 75, 74, & 73 as someone stated earlier, with the additional changes to Axes2Buttons tab? Those are not needed? I get SOME input if I keep/put those settings back. But when using JUST the screenshot above, there is zero input from the joystick's axes.

[wildwolf]

Finally! Thank you! Thank you! Thank you!

I finally did the right combination of reset/calibration, and settings and it appears to be working. When I got it working after the reset, instead of losing that and trying to fix what was wrong with my old configuration (saved to a file), I went ahead and mapped all my buttons again, so hopefully it will all work correctly when I game again tonight. IF I game, been up ALL night.

[Ron61]

Well, that's great.
You can assign any button that will switch the X, Y or WASD axis mode and also hang up a mode indicator.
Instead of Always, set On/Off and select the priority.

[wildwolf]

Thanks, but I only use the joystick for 1 game (or 1 type of game) and it's always FPS games. Thus, I always/only need X/Y as WASD.

I do have one other item I still haven't been able to figure out.

On that same screen as your last screenshot, there's the POV1 DOWN, UP, LEFT, RIGHT - on my stick they are the POV stick. I'd like to be able to bind 4 keys to those buttons, but that doesn't seem to work for me.
This is original, unmodified:

Trying these settings on it:

I also tried similar to how the axes were modified for WASD, but using the arrows (though bummed that it MUST be the arrows). That didn't seem to work right either, but I will try again - it doesn't work right in the test tab. It seems to not release correctly during the test and is either way too sensitive or designed that way - as it shows UpArrow LeftArrow if I try to push the ministick.

I have someone coming to swap out that mini stick for the hat switch that was included as I'm sure that's the best solution for me. Another thread I started said I would lose an axis - and I'm not sure which axis I lose - if JUST an axis for the ministick, I'm perfectly fine with that as I don't need another axis, I need more buttons that are easier to program/less likely of hitting other buttons.

Suggestions?

[Ron61]

Which specific POV (its marking on the grip) should the keys be bound to? And which keyboard keys?

[scryber]

I'm so glad someone has asked how to get this working. I don't know if the person that started this thread is still checking, but I too started with a MadCatz Panther XL and have been using joystick/trackball for FPS gaming for 25 years now.

To this point I have been using Joy2Key for almost everything. The last few years I was using a Logitech X52 but I wanted something with better build quality that also had a button layout that was similar enough to what I was accustomed to, and that led me to the VKB NXT.

Anyway, Joy2Key works pretty well. The one downside, as mentioned in this thread, is getting the dead zone set up. I'm totally new to the VKB software so I haven't fully understood some of the parameters discussed. Please forgive me if these questions are rudimentary:

- Is there a way to set the dead zone for the x/y axis?
- In Joy2Key I just load up a config file for each game that I have created (for example some games use F to activate things, some use E), I presume with the VKB software you can set up customized profiles for each game in similar fashion.
- This might be a topic for a different thread, but some games (for instance: Once Human, Delta Force) simply do not allow external input from anything other than a keyboard/mouse. Any device that mimics keyboard input is ignored. This includes joystick input from Joy2Key and even something like a StreamDeck. I think this is because of the anti-cheat system they use. Anyway does the method shown here that uses the VKB software (not Joy2Key) get around this issue?

[fallout9]

The moment you use J2K or something similar an extra layer is used between hardware and game. Programming through VKBDevCfg writes directly into the joystick's memory; after applying the changes there's no need for any software to run in the background, so the game will read the direct input from the joystick as coming from keyboard and mouse.

[Victorus]

- Is there a way to set the dead zone for the x/y axis?

Yes. Custom dead zones for all axes including virtual (encoder or keys set as axis).

- In Joy2Key I just load up a config file for each game that I have created (for example some games use F to activate things, some use E), I presume with the VKB software you can set up customized profiles for each game in similar fashion.

VKB SW allows to save and load as many custom profiles as you want.

- This might be a topic for a different thread, but some games (for instance: Once Human, Delta Force) simply do not allow external input from anything other than a keyboard/mouse. Any device that mimics keyboard input is ignored. This includes joystick input from Joy2Key and even something like a StreamDeck. I think this is because of the anti-cheat system they use. Anyway does the method shown here that uses the VKB software (not Joy2Key) get around this issue?

My own experience and advice. I don't use joystick buttons "as is" at all. Keystrokes mapping only. Different simulators but plane controls are the same. Throttle, RPM, gear, flaps etc. So if I map button to G it will control gear retracting in the same way in any game. VKB SW allows to map buttons to any keystroke, including Shift, Ctrl, Win etc. Also macro allowed. Enjoy)))

[scryber]

Which specific POV (its marking on the grip) should the keys be bound to? And which keyboard keys?

I wasn't the one to first ask about setting the POV hat to keys, but I'd like to follow up about it.

I have the EVO Premium so the A1 ministick has the POV setting. I can't get it to bind any buttons. As for which keyboard keys, it kind of varies based on the game. It could be up=G, down=C, right=5, left=F, or it could be up=C, down=6, right=5, left=P.

[Ron61]

We turn on the keyboard, configure the HAT and assign the first button of the row (41) and only after that we assign the necessary keys to them.