[4.34.1] [SOLVED] IdleDetentCutoff function for warthog
-
Hi folks,
I’ve now followed the changelog instructions to the letter and have the following lines in my keyfile:
SimThrottleIdleDetentCutOff 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF" SimThrottleRightIdleDetentCutOff 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF Right" SimThrottleIdleDetentCutOff 60 8 -2 0 0x0 -1 "TQS: Cutoff" SimThrottleRightIdleDetentCutOff 61 8 -2 0 0x0 -1 "TQS: Cutoff Right"
I’m happy to report the new U1 callbacks are now recognized but their behaviour seems backwards (at least on my rig).
o I enter the 3d cockpit for RAMP with my physical throttles (PT) set all the way back to cutoff (“over” the hump in the most backward position possible)
o the 3d cockpit throttle (3dT) is shown as all the way back in the correct position, so far, so good.
o once I move the PT throttle forward, the 3dT moves over the cutoff hump and forward along my PT.
o once I return the PT to the idle position (not “over” the hump, but simply to “idle”), the 3dT jumps all the way back to the CUTOFF position.
o If I now move the PT to the CUTOFF position over the cutoff, the 3dT jumps forward to the “idle” position.
o Moving the PT forward over the hump to the IDLE position will now make the 3dT jump backwards over the hump into the CUTOFF position.
Sorry for the lengthy discription, but I wanted to make sure I explained all the steps involved.
I’ve also tried entering 3d with the PT in the “IDLE” position, but that makes no difference. Entering the 3d cockpit I hear a distinct “click” each time but I can’t be sure it’s the 3dT changing position or something else.
No TARGET involved, simple DX programming only. My CUTOFF buttons register as 61& 62 in the BMS setup so I’m using 60 and 61 in the keyfile lines above. No other IdleXXX functions are mapped to DX buttons in the keyfile I’m using:
$ grep -i detent hoover20191221.key | grep Throt SimThrottleIdleDetent 314 0 0X17 4 0 0 1 "TQS: CUTOFF RELEASE - Idle Detent" SimThrottleIdleDetent 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Idle Deten t" SimThrottleIdleDetentForward 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Idl e Detent - Idle" SimThrottleIdleDetentBack 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF RELEASE - Idle D etent - Off" SimThrottleIdleDetent 279 8 -2 0 0x0 314 SimThrottleIdleDetentCutOff 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF" SimThrottleRightIdleDetentCutOff 314 0 0XFFFFFFFF 0 0 0 1 "TQS: CUTOFF Right" SimThrottleIdleDetentCutOff 60 8 -2 0 0x0 -1 "TQS: Cutoff" SimThrottleRightIdleDetentCutOff 61 8 -2 0 0x0 -1 "TQS: Cutoff Right"
I guess basically the problem boils down to the 3dT jumping to the CUTOFF position when the PT hits the IDLE position each time.
Thanks much in advance for any help!
Uwe
-
Judging by the number of views & replies, I’m assuming nobody has played with these two new callbacks yet?
I’d love to get them to work
All the best,
Uwe
-
Hi hoover,
Sorry for bit late reply. Just tested it in both development version and U1 released version and this two momentary cut-off keystrokes works for me without problem.Added this into my keyfile:
SimThrottleIdleDetentCutOff 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF”
SimThrottleRightIdleDetentCutOff 314 0 0XFFFFFFFF 0 0 0 1 “TQS: CUTOFF — Right”Mapped to Warthog Throttle Left and Right cut-off switches (DX62 and DX61) and tested in game for ramp start, taxi and in flight. All fine
Are you sure you don’t have any other cutoff controls concurrently mapped? Only this two new keystrokes are needed, nothing else for momentary cutoff operation that works out of box with Warthog throttle (There is also cutoff controls to going into and out of idle cutoff specifically).
Please make sure only this two mappings are there! (original idle detent keystroke toggle doesn’t matter)
SimThrottleIdleDetentCutOff
SimThrottleRightIdleDetentCutOffI simply can’t see anything bad. I was not needed to even move throttle during pie screen loading - all works. Of course sometime it can be necessary to cycle throttle if throttle position doesn’t match in-sim position. It is how falcon is done.
If you can’t find what’s wrong I will go back to you after new year and we will try find out. Marry Xmas and Happy New Year
-
Thanks very much for your reply, ataribaby.
I’ve now removed all lines pertaining to “detent” w/r to the throttle from the keyfile, only leaving those two that you mention above, and the behaviour is still the same.
When using the “game controller” application to check the WT throttle, I find that when my physical throttle (PT) is in the idle position, both buttons are lit continuously in the game controller display:
(see buttons 29 & 30 in the image above)
This is what I’m seeing with the throttles in the CUTOFF position (fully backward over the hump):
As you can see, the buttons 29 & 30 are no longer lit.
It would be my understanding that the “permanently pressed” position would be in the cutoff position, while the IDLE position should be the “momentary press” or do I have things backwards here?
thanks again for your support & let me know if there’s something I can provide to help debug the issue further.
the keyfile I’m working on can be found here:
All the best & happy holidays to you, too!
Uwe
-
Ooops? buttons 29 & 30 should be lit if you put WH throttles past guard into CUT-OFF position. Yours seems work opposite on controller HW level? They are soldered “backward” in your WH? Then all that behavior makes sense now and I am afraid there is no fix from Falcon side as your HW works differently than it should.
Is your WH newly bought or second hand (so previous owner modded this for some reason)? I will contact Thurstmaster support - I have nice experience with them.
Here is mine in CUT-OFF position:
-
That would indeed make sense. I bought my WT new a few years ago, so I’m afraid it’s out of warranty already
All the best,
Uwe
-
Just try contact TM support with your problem anyway. I have nice experience with their support.
-
Thanks, I’ll do that. It might be worth noting that I never installed any “Warthog drivers” or TARGET on my system (win7 / Linux Mint 19), as both devices worked OOTB from the start. The only thing I changed on the throttle was a new thumbstick, but I guess that wouldn’t have any effect.
All the best,
Uwe
-
hoover - You can get the same idle cutoff function without using those new call backs. I used Alternate Launcher to do mine and it works just fine. Been using it since 4.34. It’s just a matter of mapping it properly. The key is you will need to use the RELEASE feature of alternate launcher. If you need further assistance DM me and I can give you a hand with it.
https://github.com/chihirobelmo/FalconBMS-Alternative-Launcher
-
Hello wheelchock,
thanks for your comment & your kind offer!
I tried to implement the idle cutoff function before with what’s avaialble in 4.34… to no avail, probably because of the problem with my detent switches as outlined above which I only found out about today.
With my currently active keyfile (not the one I’m experimenting with) I can move the PT out of cutoff to IDLE by pushing it forward, but I cannot get it back to CUTOFF. I’ll contact you via PM and I’ll share the details.
All the best,
Uwe
-
I don’t understand something.
These callbacks have been known since 4.34 was out and have been working and in use (by just adding them to the key file).
So…what do the dev mean by introducing them in U1? -
Momentary SimThrottleIdleDetentCutOff and SimThrottleRightIdleDetentCutOff are new for U1.
-
Hi
Can anyone explain step by step the procedure to get a working warthog throttle cutoff when using TARGET?
Do I have to mark the thickbox idle cutoff in BMS config?
Thank you and best regards -
I’ve now received a reply from TM: they ask me to update / flash the WT firmware. I’m just wondering if any of our hardware experts here might expect this to fix the problem? To me it looks more like a wiring issue with the cutoff buttons as opposed to something than something that could be fixed by a new firmware version….
@Caldero: Sorry, I’m avoiding TARGET and use DX only.
All the best,
Uwe
-
Even though it is a switch that sends a signal it is not the component that sends the signal back to the PC. There’s a micro controller in there that does that. So its possible that a firmware update will fix your issue. There is also a calibration tool from TH that I’d use instead of the one that is included with MS Windows.
-
Looks like my throttle firmware is already at the latest version (v23), can some other kind WT owner please confirm this? Thanks!
I re-installed the firmware just to be on the safe side but the behaviour of the cutoff buttons hasn’t changed apparently (buttons 29 & 30 lit in IDLE position and off in CUTOFF position)
All the best,
Uwe
-
Yep you are latest for throttle - 23 and not latest for stick - mine says 12.
-
I was just thinking… I replaced the stock TM microstick on the throttle with a deltasim electronics one a while back, could this have anything to do with it? I’d rather think not, as the microstick came with its own little circuit board and it was a drop in replacement for the old one (with better haptics,though). I think I’ll ask around with others using the same microstick upgrade if they have experienced similar problems with the idle / cutoff switches.
Sadly I only started fiddling with the idle / cutoff stuff after the replacement, so I couldn’t even begin to tell if the throttle buttons 29 & 30 behaved as expected with the stock microstick.
Cheers, Uwe
-
Hoover, if I were you I would just do a complete recalibration of the throttle. This might solve your issue as it is not physical buttons, but “logical” ones based on throttle position value.
-
Hi folks,
thanks to Damien of “Deltasim Electronics” I was able to resolve the issue (see quote below). Apparently, I made a mistake during calibration of the throttle after installing his most excellent microstick upgrade a few months ago; I didn’t put the throttle in the CUTOFF position when I should have done so. Needless to say I feel utterly stupid and I’m quite sorry for wasting everyone’s time… OTOH I’m happy to say that everything works “as advertised” now.
I will also close the ticket over on the TM customer support site.
Again, thanks to everyone who helped to get to the bottom of this, the next beers are on me. :drink:
All the best,
Uwe
"The idle/off buttons on the throttle are not real buttons, they are purely virtual signals generated by the throttle controller when the throttle axis reaches a certain value. So I can’t see any way they could be physically faulty.
The most likely reason I can think is that the calibration was done backwards, when you ran the calibration tool after installing the upgrade it will ask you to set the throttle axis to OFF and IDLE. It does that to store the axis values to trigger the virtual buttons as above. I think if you move the throttle to the wrong position during the calibration weird things can happen.
I also know there are some parameters in the A10_Calibration.txt config file that effect it, but in not sure exactly which ones or what they do. I would recommend making sure you are using the file unchanged from my website."