F-16 cannon
-
Mav-JP, maybe you could post a copy of your keyfile (or the relevant lines) so we can see how to make DX1 the trigger without having need of a callback?
…. …if you use DX1 you dont have to use a callback /…
-
BTN TG1 /P KD(DX1) /R KU(DX1)
BTN TG2 /P KD(DX6) /R KU(DX6)
KEYSTROKE DOES NOT NEED ANY CHANGE, USE DX Functions that are native in BMS.key
-
I have the same as BW, how do you change the second trigger to be dx1?
Or is this misunderstanding caused by us using 4.32 and you are not?
sorry that was a mistake i edited my post
-
Is that from your key file?
-
-
**BTN TG1 /P KD(DX1) /R KU(DX1)
BTN TG2 /P KD(DX6) /R KU(DX6)**
KEYSTROKE DOES NOT NEED ANY CHANGE, USE DX Functions that are native in BMS.key
These lines of ‘code’ are not familiar to me. I assume they are inherent in the BMS code? If not, where do I find them?
-
BTN TG1 /P KD(DX1) /R KU(DX1)
BTN TG2 /P KD(DX6) /R KU(DX6)
KEYSTROKE DOES NOT NEED ANY CHANGE, USE DX Functions that are native in BMS.key
the bms.key ALSO uses the SimTriggerSecondDetent callback.
EDIT: and using the bms.key with no changes, I still get correct avionics but the old behavior of the gun, with NO yaw, and NO FLCS compensation.
These lines of ‘code’ are not familiar to me. I assume they are inherent in the BMS code? If not, where do I find them?
those are from Foxy.
-
These lines of ‘code’ are not familiar to me. I assume they are inherent in the BMS code? If not, where do I find them?
those are foxy lines…i am sure you can programm your saitek the same way (DX functions)
-
NEVERMIND
-
the bms.key ALSO uses the SimTriggerSecondDetent callback.
those are from Foxy.
mhh ok i understand what you mean now LOL …sorry i thought the DX callback was working fine in 4.32…
-
for the X52 it would be
BTN TG1 /P KD(DX2) /R KU(DX2)
BTN TG2 /P KD(DX14) /R KU(DX14)
Is that correct???
no idea about Saitek’s programming but i doubt command lines are similar to thrusmaster ?
-
i NEVER EVER touch my kesytroke, this is my falcon #1 rule
this comes from my foxy profile, and i am sure saitek can be programmed DX as well
Ah, ok, I just installed my cougar and the BMS.key fit like a glove. On the other hand I have a x65 and there I had to change the callbacks to fit the stick. I do not know if I can change the dx buttons in the saitek software, never seen that though.
-
those are foxy lines…i am sure you can programm your saitek the same way (DX functions)
no, saitek sticks cannot just change which buttons are which directX button. Foxy is a LOT more configurable than Saitek programming, its night and day.
-
i NEVER EVER touch my kesytroke, this is my falcon #1 rule
this comes from my foxy profile, and i am sure saitek can be programmed DX as well
Wait, what?
You’re talking about something exclusive to a Foxy/Cougar profile? I asked specifically about an X52/X52 Pro several posts ago.
Your ‘cougar-centric’ replies are useless to a large portion of the community. You really shouldn’t be wasting our time and mis-leading future readers of this post with drivel about "if you use DX1 you dont have to use a callback’ when it only applies in a LIMITED set of conditions.
Twice today:
-
the bms.key ALSO uses the SimTriggerSecondDetent callback.
EDIT: and using the bms.key with no changes, I still get correct avionics but the old behavior of the gun, with NO yaw, and NO FLCS compensation.
those are from Foxy.
SO, witch trigger callback is JP using?
-
sorry i was thinking saitek programming was possible…
jeez …
-
does your gun rock the a/c sideways below 200knt?
-
Okay, this is actually a problem in 4.32.
the old callback of SimTrigger has the FLCS compensation correctly.
However, the new callback of SimTriggerSecondDetent is the one that has correct Avionics integration - so using the old SimTrigger callback, you can fire the gun in any mode, whereas the SimTriggerSecondDetent will only fire in the correct modes (AA GUNS and DGFT OVRD).
I am, and using the SimTriggerSecondDetent callback, there is NO yaw recoil, and NO rudder movement.
using the SimTrigger callback, there IS yaw recoil, and IS rudder movement. There is very little recoil while at 0.8M, but at 0.3M its very noticeable.
using the SimTrigger callback just fires the gun without regard to avionics mode though.
the bms.key ALSO uses the SimTriggerSecondDetent callback.
EDIT: and using the bms.key with no changes, I still get correct avionics but the old behavior of the gun, with NO yaw, and NO FLCS compensation……
Instead of attempting to advise others on their keyfiles, perhaps these posts are better suited to you talents.
-
Instead of attempting to advise others on their keyfiles, perhaps these posts are better suited to you talents.
sorry to try to help, i will never do that again i promise.
and yes one of the two callback does not work as it should and there is nothing we can do about it…sorry again my fault…
use the other callback if you want to use AFM with full potential
-
Instead of attempting to advise others on their keyfiles, perhaps these posts are better suited to you talents.
Blu3wolf is on target.
witch callback is correct for x52.
the one that the gun fires in all modes and rocks the a/c to the sideways below 200knt and moves the rudder to right.
or
the one that fires only in the correct modes and the rudder does not move and the a/c does not rock sideways <200knt. (it’s like it;s on railroad track)