F-16 cannon
-
I was looking pretty close and couldnt see the rudder moving, and at 0.3 mach, I definitely had ZERO yaw while firing. HUD view, tracking a ground target, no yawing from firing at 0.3 mach.
I guess Ill try using the other callback and see if that fixes it.
use DX associated trigger
-
DX trigger…?
I dont know what I should be using :S
-
Hmm. I cant see the tail compensating, and I cant see any recoil when flying at Mach 0.3
SimTriggerSecondDetent is the callback being used.
IRRC there is a but in 4.32 where one of the two callback or DX input deos not trigger gun effect nor compensation…cant remember which one is not working…
I am pretty sure that the DX input works as it should
be aware that the tail compensation is very subtile movement , not huge deflection…
There are 2 ‘trigger’ commands for DX. One has the FLCS compensation, one does not. There’s a thread where it’s spelled out which one does which. It may the thread linked mid-thread above.
-
See, in the old thread it is asserted that the wpnfiregun callback is the old one, and the triggerseconddetent one is the new one with FLCS compensation.
But with the one I have, its just zero yaw.
-
See, in the old thread it is asserted that the wpnfiregun callback is the old one, and the triggerseconddetent one is the new one with FLCS compensation.
But with the one I have, its just zero yaw.
Depending which thread you read (there are a few) the callbacks get confused; which does what get’s swapped.
To be 100% sure, decide what you want …. FLCS compensation or not … then test your current call back (within the compensation speed/parameter). If it’s not what you want, change to the other then test to confirm you now have whichever ‘version’ you want.
-
Depending which thread you read (there are a few) the callbacks get confused; which does what get’s swapped.
To be 100% sure, decide what you want …. FLCS compensation or not … then test your current call back (within the compensation speed/parameter). If it’s not what you want, change to the other then test to confirm you now have whichever ‘version’ you want.
right, thats the problem.
My callback doesnt have a yaw when outside the compensation parameters.
-
right, thats the problem.
My callback doesnt have a yaw when outside the compensation parameters.
And the other callback does what … ?
-
thought the commentry was that the old callback doesnt have the compensation and therefore always yaws…?
-
-
I do not know if it is known (?) … anyway, thank you Caper for heads up!
-
It’s a cool feature that somebody put some time into it.
Use it or don’t use it. I like it. -
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).
-
thought the commentry was that the old callback doesnt have the compensation and therefore always yaws…?
oi …. :rolleyes: .
Change your callback if you don’t like the current functionality you have. It was a rhetorical question … your current callback does/doesn’t do something … what does the other callback do? IOW - change it and find out.
If you don’t like either, then live without guns or pick ‘the lesser of two evils’ and move on. Yeesh.
-
+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.