F-16 cannon
-
+1
Realistic gun compensation should be turn no/off in the setup menu. -
nevermind
-
Well, the choice is correct avionics or correct flight modelling….
-
thought the commentry was that the old callback doesnt have the compensation and therefore always yaws…?
no the “bad” call back does not trigger GUN yawing NOR gun compensation and therefore shall not be used at all…
-
+1
Realistic gun compensation should be turn no/off in the setup menu.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
-
use DX for trigger
-
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
So maybe in some future update one of the callback commands should be removed/disabled/re-directed to the proper function. Otherwise, users will choose what they want to …. with or without understanding of the differences.
-
So maybe in some future update one of the callback commands should be removed/disabled/re-directed to the proper function. Otherwise, users will choose what they want to …. with or without understanding of the differences.
do you really think we missed that one ?
-
do you really think we missed that one ?
Missed or not, the choice (currently) remains. And proclamations or declarations by experts will not cause everyone to suddenly start using one callback over the other.
Also, BW’s last comment may still be relevant with regard to the ‘correct’ simtrigger callback:
Well, the choice is correct avionics or correct flight modelling….
-
do you really think we missed that one
up to 4.32 update 7 yes we did
Matter of fact, I’m still myself on secondtriggerdetent
-
use DX for trigger
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.
-
Missed or not, the choice (currently) remains. And proclamations or declarations by experts will not cause everyone to suddenly start using one callback over the other.
Also, BW’s last comment may still be relevant with regard to the ‘correct’ simtrigger callback:
and the correct answer is : USE DX1 for trigger !!!
-
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.
sorry but i dont get you….if you use DX1 you dont have to use a callback /…
-
and the correct answer is : USE DX1 for trigger !!!
….if you use DX1 you dont have to use a callback /…
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.
-
sorry but i dont get you….if you use DX1 you dont have to use a callback /…
well, DX1 is my first trigger detent. DX6 is my second trigger detent.
DX1 is set to SimTriggerFirstDetent, and DX6 is set to SimTrigger (was previously set to SimTriggerSecondDetent). Im probably going to set it back to the SimTriggerSecondDetent option so I have correct avionics. I dont want to accidentally fire in close trail formation while in NAV mode.
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
Ive avoided this unintentionally the entire time Ive flown BMS…
-
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.