F-16 cannon
-
do you think the F16 pilot can chose to turn it off ??? this is not an OPTION ! this is build in FLCS and physics of gun can not be avoided
no, but I don’t think that more realistic yaw modeling is welcome in some parts of the BMS community. LOL
I use SimTrigger 14 8 -2 0 0x0 0
and the gun is useless below 200knt.
btw can you make the cockpit shake when gun is fired.
-
Are you serious? Even for a stick where the DX1 is not the second trigger detent. That works?
Case in point from, say, an X52 Pro profile: SimTrigger 14 -1 -2 0 0x0 0. You’re saying I can remove that while having a callback on my DX1 (my pickle button) AND the trigger will still work.
You guys f’kg ROCK!! I’m changing my keyfile posthaste. Thanks Mav-JP.
pickle button is DX S2 i think…
first is DX S1
second detent is DX S6 -
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?
-
pickle button is DX S2 i think…
first is DX S1
second detent is DX S5EDIT : NOT SURE , please check
Now I’m confused. Where is this info coming from? None of the X52/X52 Pro profiles/keyfiles I’ve seen are similar to this. Are you sure that DX1 ‘auto-magically’ makes the gun work?
-
Well I can change the directX number on my stick using Foxy.
That said, I have a marked preference to NOT do so, using as I currently do the unprogrammed mode for my Cougar.
Also, many other pilots are NOT able to do so, as they have a stick not as customisable as TM hardware is.
-
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?