VKB-SIM

Hi.

Been happy with my Gladiator stick last year so I’m eager to use the THQ in the sim.

Most of my flying is fast jet, and the Razbam and Wilco Harriers in particular. In the sim, the nozzle swivel is achieved by the cowl flaps action. So whatever button or lever has been programmed for “extend incremental cowl flaps” incrementally swivels the nozzles downward. On the Gladiator, I programmed that action to one of the vertical roll wheels on the base, and it worked fine.


On the THQ, I wanted to program that to one of the three lever axes, but the sim won’t accept that. Is there a way to have one of the levers act as the input for this type of action?

Many thanks.

dl

The THQ should be treated by game as any other joystick. The only difference I see is that on the Gladiator you were assigning that control to digital and on the THQ you’re trying analog, so maybe the game has a restriction to analog input for that control? If that’s the issue, you could assign that specific axis to buttons.

Thanks f9,

I was actually wrong - the action to which the Harrier's nozzles are supposed to be programmed is the propeller axis, so the good news, is I can temporarily program the #3 (right most) lever to make the nozzles swivel as they should.

The bad news is two items:

1) I don't have full "0 deg" / full aft deflection - the furthest up the lever will go is still 10 deg down, no matter how well I've configured/calibrated.
2) within a few minutes, that right lever will default to it's own seeming hardwired default of being an aileron axis, meaning the plane begins to roll.

I should note that in my NXT+THQ combo, all the configurator - and the P3D sim - see two controls the NXT+THQ1 and NXT+THQ2. #1 only accepts programming for the right most lever, and all the other buttons, levers, POV, etc. are entered as part of programming #2. So I've deleted all the axes associated with #1 except for the propeller axis, but as stated, within minutes, it all reverts back to a predetermined set of defaults for #1. #2 remains programmed, thankfully, including all the functions on the stick and all the buttons on the THQ.

I even did a "restore defaults" in P3D to start clean, but there is something about that #1 control that refuses to stay programmed.

I did the steps, including firewall off, bootloader, configurator, calibrate, etc. No idea. Running P3Dv4.5 on Win 7.

Any ideas?

thanks,

dl

Please post a screenshot taken from VKBDevCfg, with Profile/Axes/Logical and Physical Axes charts showing.