Trigger Delay...anyone else?

[Seeker]

Yes. Does it persist after you release too?

[Rattlehead]

I don't know what joysticks you guys are using, but on my X-52 pro I had the same effect, until I realised my main trigger was one of those 'dual' triggers (I don't know the right term, but I hope you know what I mean) where lightly squeezing it activates the first trigger, and squeezing it all the way down activates the second trigger, and I had mapped my machine guns to the second trigger, giving me a slight delay when firing.
Once I mapped it to the first trigger all was well.

[droz]

Originally Posted by Rattlehead

I don't know what joysticks you guys are using, but on my X-52 pro I had the same effect, until I realised my main trigger was one of those 'dual' triggers (I don't know the right term, but I hope you know what I mean) where lightly squeezing it activates the first trigger, and squeezing it all the way down activates the second trigger, and I had mapped my machine guns to the second trigger, giving me a slight delay when firing.
Once I mapped it to the first trigger all was well.

yeah, dual stage here, but i have the first stage selected.

[jimbop]

I get this but only when there are a lot of planes around so it seems like a processor-related delay to me. See this thread for discussion (but no fix):

http://forum.1cpublishing.eu/showthread.php?t=20232

[Psycho_Ch!cken]

It's the same old input lag that's been around since day 1. You just notice it more easily on the trigger.

[CharveL]

It's likely a performance related issue, I'm thinking video card or system memory, paired with the still unoptimized engine.

If you want to check if that's it just turn down the textures and effects and see if that helps it. Worth a shot.

For the record I had the same thing on release but one of the early patches has pretty much cured it for me, even with aggressive detail settings.