X52 Pro - Assigning POV1 to TMS...
-
Hello.
Few specs…
OS Windows 10
Falcon: Falcon 4.37.3.1
Launcher: Falcon Launcher 2.4.1.5Joystick: Logitech X52 Professional
Driver: 8.0.121.0
Software: 8.0.213.0This is a fresh Windows/Falcon install. The issue I’m having is that in my previous Windows/Falcon (4.37.2) install, I had mapped out my joystick’s POV1.Up/Down… to the TMS functions. i.e. these keys:
Now, trying to map them out in the Alternative Launcher’s Keymapping just doesn’t recognize the key at all. It does nothing. i.e.
What did I miss here? How can I get Falcon/Launcher to see it as actual DX keys ? I already tried in the X52 software to set the POV 1 to be 4-way, fallback and Buttons (UNprogrammed!) and that didn’t work either.
I was however able to set them as 4-way Buttons, and setup New KeyPress in each 4 to send in the same keypress as within Falcon, i.e.
So in this way it is the X52 software that’ll send Shit+Home, etc to Falcon, BUT I never had to do this before. Seems like a dodgy way of having to do it. Wondering if it’s not a bug with The new Launcher maybe ?
Any clues, anyone ?
Much thanks.
Patrick -
I don’t have X52 and I’m not familiar with their software … but the Alt Launcher does (should) support 8-way POV hats.
Can you help me understand what the different X52 software modes mean… what does “Fall Back” mean?
And what does “Unprogrammed” mean? If that means, just let the pov-hat be an ordinary pov-hat (from a DirectInput perspective) that is probably what you want.
-
@ravenlost
I have a same problem with my Thrustmaster throttle.
For some reason game launcher cannot bind POV as a buttons.
I using Thrustmaster TARGET GUI with custom remapping POV to buttons. You can try this trick with vjoy / joystic gremlin setup to force bind POV to buttons. -
@airtex2019 Honestly, I do not know what is the difference between these. I couldn’t yet find clear documentation regarding this. Logitech’s documentation really suck if you ask me
I can say though that I tried all mode. All same results: nothing gets binded in Falcon Launcher.
The only way I was able to do it, is like what I think you are suggestion @QuantumDream with your VJoy / Gremlin software, well partially what you are saying (?). I dont know Gremlin soft at all… I’ve forced the behavior to be like 4 buttons in the X52’s software, and mapped out each of these 4 buttons to forcefully send in (as per previous screenshots):
- Shift+Home key
- Shift+End key
etc…
Not ideal, but not sure which other way…
-
@ravenlost Just try puting this in your key file who use from Falcon’s User/config, directory
Keep clear the profile from Logitech Stick programer.The POV hat has its own syntax.
We map TMS for the UNSHIFTED layer here.
SimTMSUp 19 -1 -2 0 0x0 -1
SimDoNothing 0 -1 -3 1 0x0 -1
SimTMSRight 20 -1 -2 0 0x0 -1
SimDoNothing 0 -1 -3 3 0x0 -1
SimTMSDown 21 -1 -2 0 0x0 -1
SimDoNothing 0 -1 -3 5 0x0 -1
SimTMSLeft 22 -1 -2 0 0x0 -1
SimDoNothing 0 -1 -3 7 0x0 -1 -
@QuantumDream I’d love it if you guys could help me understand what the gap is here. For the handful of devices I have, including game-controller d-pads, DirectInput pov-hats work ok in Alt Launcher and in game.
Can you run Joy.cpl and verify your device is actually presenting itself as a pov-hat, from a DirectInput perspective?
If that doesn’t work (because the OEM software hijacks the default Windows joy.cpl UI in an unhelpful way) maybe try VKB JoyTester or a similar tool to look at DirectInput events?
-
@airtex2019
Hmmm it is strange I tryed to rebind to show the problem, but it seems now works fine. Last time when I tryed to bind pov buttons, launcher did’t show in keybind POV buttons. -
@ravenlost
It is very simple software.
With Joystic Gremlin you assing buttons from real joystick to vjoy virtual joystick and system think that you have one more device. Also you can create additional curves and deadzones for axis. But you can try simple assign your Hat
-