Cannon won't stop firing

[drtbkj]

I’ve been having a weird problem of late. When I fire the cannon it fires one long burst until it runs out of ammo. At first I thought it was a hardware failure on the stick(Saitek x-65). So, I unprogrammed the trigger completely in SST, and set my unused Hat 1 with second trigger detent. It worked for a bit, then it started doing the same thing!
As I have been working with my keyfile of late, I wondered if the callback had gotten messed up,even though it started before started working with the keyfile.
The second detent callback loaded is- SimTriggerSecondDetent -1 0 0x35 4 0 0 1 “STICK: SECOND TRIGGER DETENT” .That is directly from the 4.33 Full keyfile, and is in my keyfile as well.
Help!

[Stevie]

I had that problem with TARGET, and stopped using TARGET because of it…I never did figure out why. Only thing I can think of is that somehow the switch is being mapped into a press and hold state instead of momentary…check for that.

[Frederf]

How are you activating this callback exactly? Is it DX direct or joystick software that presses a virtual keyboard sequence?

[Stevie]

I ended up going directly to the BMS Config screen and assigning Trigger Detent 1 and 2 to my trigger from within BMS - I’m using a Warthog stick now, but the problem first appeared with my Cougar. That was the only way I could get things to work for a quick check.

Neither stick has any stuck switches - TARGET is junk…seriously needs an update. I’ve given up on it and will go to DX in the future…but I’m not there as of yet.

[Frederf]

TARGET is the best way to use the Warthog. You’re just not very good at it.

[Stevie]

TARGET sucks for the Cougar…plus it’s just one more chunk of processor overhead I don’t need in a full pit build. Not sorry in the least to be rid of it to make space for some that actually works - like DED Capture.

[drtbkj]

@Frederf:

How are you activating this callback exactly? Is it DX direct or joystick software that presses a virtual keyboard sequence?

Thx, Stevie and Frederf, and to answer your question, I kept trying both methods. I kept thinking stick issue as when I entered alt / via keyboard it worked properly. I ended up using the dx method, and suddenly it started working properly.
Stevie, I’m working with SST for Saitek, and am very rusty on Target, but I do wish these programs had more functionality. I, too wondered if the stick went to a hold state, but unfortunately SST doesn’t give a way to look at that.

[Stevie]

Yeah…and I must have gone over TARGET a thousand time to make sure I was using the correct momentary switch command - which I was, in several places. Only one giving me any problems was the trigger. Anyways, I’ve ditched TARGET completely and as I set up my pit build I plan to go DX for every button, switch, and command possible. I may even build my own stick and throttle input interfaces just because the basic Cougar PCB is outdated from an sampling rate standpoint…besides, I have a RealSim TUSBA for my TQS and it polls at 20 Hz vice 10, I think…big improvement. So I’d like to do the same for an FCC3 or Ribbstick…when I get that far.