Newcomer / Intro TARGET - buttons not working?

[johntarr]

@Clicker - TARGET = v3.0.18.328, Joystick = v12, throttle = v23

So somehow, despite running TARGET, your machine is still interpretting the buttons coming from "ThrustmasterWarthogJoystick" etc. (not being intercepted despite being MapKey'd).

I think what you're describing is how TARGET normally behaves, but not how it behaves in MODE_FILTERED. In filtered, the joystick and throttle still do their own thing. It just creates a virtual device in addition to them.

 

[johntarr]

@Clicker

I got a chance to mess with the scripts.
I'm pretty sure it's nothing to do with conflicting DX commands.
In this latest version I excluded the Joystick, and I'm still not able to use the grey slider on the throttle.

 

[Clicker]

@Clicker - TARGET = v3.0.18.328, Joystick = v12, throttle = v23

I think what you're describing is how TARGET normally behaves, but not how it behaves in MODE_FILTERED. In filtered, the joystick and throttle still do their own thing. It just creates a virtual device in addition to them.

Nope, I was describing my understanding of MODE_FILTERED which was evidenced by my tests yesterday...on my machine.
(that doesn't make it PROOF that I'm right or wrong...just how it is on my machine)

I can confirm that I still have 3 controllers available when running the script in MODE_FILTERED.
The bit that is tripping both of us up it seems is in relation to Mapkey(...0);
You believe it allows passthrough.
I believe it is meant to block the button.
I further believe leaving a button without a MapKey allows it to be passed through.

The difference between what you are seeing on your PC and what I'm seeing on mine is...

For me the fed-through button appears to come from the Combined device.​

For you the fed through appears to come from the independent device.​

Seems MODE_FILTERED behaves differently on your machine ... this is the bit that I do not currently understand.

Look at it this way...I think we are both correct based on what we are seeing on our own machines.

This must be immensely frustrating for you, but for what it's worth, I'll keep thinking and playing with this because I want to understand this stuff more...I find this fun.

Cheers
Clicker

 

[Clicker]

@Clicker

I got a chance to mess with the scripts.
I'm pretty sure it's nothing to do with conflicting DX commands.
In this latest version I excluded the Joystick, and I'm still not able to use the grey slider on the throttle.

You are right, not conflicting DX commands....that was the rabbit hole I went down yesterday which caused a lot of confusion.
I assumed you were using...

MapList(&Joystick,&JoystickMap1);
MapList(&Throttle,&ThrottleMap1);

...to map your DX, when you were in fact using...

MapList(&Joystick,&JoystickMap0);
MapList(&Throttle,&ThrottleMap0);

Again, my bad...and sorry.

 

[johntarr]

@Clicker - Found something you may find interesting. Check out a post by Thermal on this thread.

He explains that you can exclude buttons from the original device using "magic" in the event handler.

I believe that if statement is the piece that says "ignore this button on the physical device"

Not sure if this helps us or not, but found it interesting.

Also, I'm on discord in the HOTAS server if you want to be able to communicate a bit quicker.

 

[Clicker]

Flip! Wish you told me you were talking to sYfte, and I'd have given up yesterday!
He certainly knows this stuff way better than me!

 

[Clicker]

@Clicker - Found something you may find interesting. Check out a post by Thermal on this thread.

He explains that you can exclude buttons from the original device using "magic" in the event handler.

I believe that if statement is the piece that says "ignore this button on the physical device"

Not sure if this helps us or not, but found it interesting.

Also, I'm on discord in the HOTAS server if you want to be able to communicate a bit quicker.

The "magic", he's referring to is TARGET causing Windows to hide the original controllers and replace them with the Combined one.
Further "magic", when you use MODE_FILTERED...TARGET doesn't hide the original controllers, but does al create the Combined one.

Have you run joy.cpl on you machine and watch what happens when you run the script and stop it again?

Clicker

 

[johntarr]

@Clicker - hit me up on Discord if you get a chance, sent you a friend request.

I keep the controller screen up and when I use mode_filtered, it keeps the original devices and creates a new one called "Thrustmaster Virtual Game Controller".

I think you and I are reading Thermal's post differently. He says that by default it will hide the original devices and create a "Thrustmaster Combined" device. However, he then goes on to explain that MODE_FILTERED allows you to keep the original devices. He further explains that you can exclude specific buttons from the original devices, not exclude the original devices entirely. If that was the goal, you wouldn't need MODE_FILTERED at all, right?

 

[Clicker]

@Clicker
In this latest version I excluded the Joystick, and I'm still not able to use the grey slider on the throttle.

Try adding...

MapAxis(&Throttle, THR_FC, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);

... directly underneath your "KeyAxis(...)"; statement at line 335 in your script.

You'll need to get in a rebind this in game, but you should then be good to go.

Clicker

 

[Clicker]

@Clicker - hit me up on Discord if you get a chance, sent you a friend request.

I keep the controller screen up and when I use mode_filtered, it keeps the original devices and creates a new one called "Thrustmaster Virtual Game Controller".

I think you and I are reading Thermal's post differently. He says that by default it will hide the original devices and create a "Thrustmaster Combined" device. However, he then goes on to explain that MODE_FILTERED allows you to keep the original devices. He further explains that you can exclude specific buttons from the original devices, not exclude the original devices entirely. If that was the goal, you wouldn't need MODE_FILTERED at all, right?

Yes, that's what I've been saying...above.

It hides the whole device when you are NOT using MODE_FILTERED

Clicker