MVAMS, Spad.Next (or not) and Saitek Throttle Quadrant

[johnh]

Hi, I have tried and tried to get this working but nothing seems to work

I have P3Dv4.5 HF3, Win 10 Pro, Spad.Next, 2 x Saitek TQ and Honeycomb Yoke (amongst many other things!).

I have tried:

With Spad.Next
Mapping all Axis via Spad and Disabling in P3D|Options|Other|Enable Controllers (this is my default setup and ALL aircraft work with this including FSLabs A320. MJC Q400, PMDG 737/777/747, TFDi 717, Maddog MD80, etc). I can get the Prop and Condition levers to work but not the Power

Without Spad.Next
P3D|Options|Other|Enable Controllers is set to Enabled and all Axis are set on both TQ's.

I have configured everything in the MVAMS including Enable Hardware Mapping. Again the Prop and Condition levers work but not the Power

If anybody has this working in Spad.Next I would love to hear from you. Even if you don't use Spad.Next but have two Saitek TQ's I would love to hear from you too! I simply cannot fly and after waiting soooo long (I was one of the Early Access people) I would love to get this bird flying.

My axis.cfg looks like this:

[GENERAL]
enabled=1
[THROTTLE]
reverse=-16383
beta=-8192
idle=896
max=16383
invert=1
[THROTTLE1]
reverse=-16383
beta=-7671
idle=640
max=16383
invert=1
[THROTTLE2]
reverse=-16383
beta=-9362
idle=128
max=16383
invert=1
[PROP]
feather=-16383
min=-4587
max=16383
invert=1
[PROP1]
feather=-16383
min=-390
max=16383
invert=1
[PROP2]
feather=-16383
min=-9492
max=16383
invert=1
[CONDITION]
off=-16383
lowidle=-4587
highidle=16383
invert=1
[CONDITION1]
off=-16383
lowidle=-1171
highidle=16383
invert=1
[CONDITION2]
off=-16383
lowidle=-130
highidle=16383
invert=1

[Slayer]

If you are just using P3D mappings, no Spad Next and no hardware mapping in MVAMS do the throttles do anything? That would be a good starting point.

[johnh]

I am heading away overnight for work so will test this when I get back. Thanks for your reply.

[Slayer]

You may want to also have a look at this file if you do not have it , even though it doesn't say spad.Next the same ideas apply.
viewtopic.php?f=105&p=100092#p100092

[johnh]

Hi Steve, I have tried with just P3D control settings. Unfortunately the result remains the same. I also tried assigning the Throttle levers on different Axis. Again the results are the same. I decided NOT to continue with the MVAMS instructions as it seems pointless (unless you tell me otherwise!) configuring MVAMS if there is NO success at the first step

Interestingly, when assigning Throttles to other Axis the Condition Lever moves instead of the Throttle. This only happens to ONE Axis

[Taguilo]

Hi,

Questions:

- Mapping with Spad.Next, P3D option must be disabled, right? In this case, checking P3D controller's calibration shows nothing, no movement on the sliders.
- Mapping with Spad means NOT mapping with FSUIPC, right?
- If using Spad, does it allow to set different calibrations for each lever? (ie idle, beta, reverse for Throttle). I guess Spad brings its own calibration procedure?
- If the last one is true, then MVAMS MUST NOT be used to calibrate. Spad should be enough. in MVAMS the checkbox "enable hardware mapping" must be left unchecked. If checked, remove it and SAVE, then quit MVAMS.
- If using Spad only (No P3D, No FSUIPC) rest of aircraft work fine with the levers, then the KA should as well.

I don't have experience with Spad, that's why I'm asking.

Thanks

Tomas

EDIT: if when physically moving one controller is another which moves in the VC, you have a hardware mapping conflict. Please revise that there are not crossed mappings between Spad and P3D.

[johnh]

Hi Thomas,
Thanks for replying!

1. Yes, if I use Spad.Next then Controllers are disabled in P3D and if I use the P3D controls I do NOT start Spad.Next
2. Correct, FSUIPC is NOT used
3. Yes. There are two different modes you can use for mapping an Axis in Spad.Next.
a. Standard Axis: This is the same as the standard P3D mode
b. Custom Axis: Here we have range definition, rescaling, Invert, and choose to use Raw Data or Axis Data
I have been using the Standard mode but even setting up Custom mode there is still no movement of the Power Levers
4. It does not matter whether MVAMS is set with "enable hardware mapping" or not. I still get no response from the Power Levers. I have also tried setting different Axis on the two TQ's as the Power Levers as well as my MadCatz F.L.Y 5 joystick (which has dual Axis controls). I have turned off "enable hardware mapping" and clicked Save Defaults
5. Agreed! ALL other aircraft work fine as do the Condition and Prop Levers. That's why I am so confused!

I am wondering if I should Uninstall and Reinstall both the KA350i and MVAMS? If so, once the they have been uninstalled are there any other pieces/directories/registry entries (I am very familiar with the Registry) that I need to hunt down for a complete uninstall?

PS. I know you're probably too busy but if you have any Saitek/Logitech/Honeycomb gear Spad.Next has a free 14 day trial and it is very very good (in my top three add-ons along with Track-IR and Chaseplane!)

[Slayer]

When you tried P3D for the axis, Im curious did you use Raw input or Directinput? Default is raw input.

input.JPG (75.35 KiB) Viewed 1838 times

I would try to use directinput and see if that works. Also go through ALL your other controllers and make sure nothing has any throttle assignment. This has caught me a few times.

[johnh]

Sorry about the delay but I had to go out of town again and it looks as though I'll be doing this a couple of times a week for some time to come. So please don't take silence from me as a sign that I have given up. I REALLY want to solve this issue and with your assistance remain hopeful.

OK, So without Spad.Next and with Controllers enabled in P3D I have tried both Direct Input and Raw Input and no change. So today I disabled (unplugged) ALL controllers except for 1 TQ and the Honeycomb Yoke.

Using Engine 1 Throttle Axis for the X Axis still no throttle. So I thought I would try Throttle Axis and this seems to work to a degree. I have movement from Idle to Full Power. I then configured MVAMS and the throttles work! BUT I can only use the throttles as a pair and NOT as individual levers.

So now my question is how to get them to work as individual levers?

PS. Tried Spad.Next again but still no luck

[Slayer]

It's been a long time since I used Saitek but i vaguely remember something about trying to use 2 USB TQ's seems like you had to have the PS2 one that plugged into the yoke and if you want the second set those were USB? Also very finniky about being plugged into USB3 ports , had to use USB2? They also made it so you could swap the heads to diff colors so that if you needed 6 axis you could for instance have the throttles side by side instead of split across 2 controllers.

Just some thoughts, I'm sure you know this but I'm running out of ideas.

[johnh]

I do indeed have two USB TQ's. And these work with all other aircraft without issue. Unfortunately my PS2 TQ is broken so I can't plug it back in to see if that would work.

All my Saitek controllers are plugged into powered USB2 hubs which in turn are plugged into USB2 ports on my computer. You are correct in remembering that there are major issues using USB3 ports.

And Yes, you can swap the coloured handles so that you can have throttles side by side.

My issue appears to be that the sim is not recognising the "Engine <n> Throttle Axis" but IS recognising "Throttle Axis"