F-16 cannon
-
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) -
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)the first one is giving correct FM and wrong Avionics
second is giving wrong FM and right avionics
that’s all 4.32 can offer
-
did you write the first one? what was the source of the effect?
-
did you write the first one? what was the source of the effect?
what ?
the problem is that falcon’s code uses two different callbacks for what is supposed to be the same function (TRIGGER).
as i missed that fact during AFM development, i missed the second possible callback, and unfortunalty, that is the other one (the one i missed) that is used in avionics code …
classic F4 code…a big mess
-
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
Both callbacks do not work as they should, one works correctly with the Flight model, one works correctly with the Avionics…
And if I had to hazard a guess based on your responses, its just gonna be a case of waiting for 4.33 to get it fixed.
Kinda tempted to screw with my Cougar to see if I cant get it working correctly the way you describe, but I dont really see that as a solution for two reasons. One, not everyone uses a cougar, and two, I have invested a lot of time and effort into not needing a Foxy profile.
Based on difficulty level of solution, I think Im likely just going to leave my setup as it is. For one thing, its gonna make learning to shoot accurately much easier to start with.
EDIT: wow, lots of replies. Okay, waiting for 4.33 MORE THAN EVER… :roll:
-
@Blu3wolf
F4AF gun fired in Nav mode. I use spacebar for Masterarm On because it was easy to press. When my lead told me to fencein, I never went Masterarm ON until we broke formation. -
nevermind. Already asnwered.