Is it JUST ME?

[Goilveig]

Hmm, I wonder if it's a joystick/driver/profile glitch rather than a direct game issue then? Someone did tell me elsewhere that the X52 can sometimes suffer from power problems - it draws all it needs from the USB port after all. So, if your motherboard isn't quite up to scratch (or indeed, the joystick draws slightly more than spec) then you could run into issues potentially. I have additional RED USB ports on my motherboard that provide extra power, notably for charging devices, but possible this could be something to test the controller on?

Oh, I only bought the X52 for ED and don't use it in any other games.

Scoob.

My X52 is kind of flakey too. I would be really happy with it if it were only a little more reliable.

Thankfully for me, the main glitching is on button 16 (the mouse button on the throttle which I use for toggle UI mode) so it's not SO bad when it screws up. Also occasionally the throttle will randomly not zero, it idles at about 15% until I unplug and replug it. That one actually got me killed, albeit indirectly when I accidentally hit boost instead of reverse throttle .

 

[Werewolf13]

Frankly for multi-cannons i always thought that they wouldn't fire in the first seconds because the guns had to start spinning and get to firing speed, If you take that into account it all looks perfectly normal to me. Unless it happens to your lasers as well of course...

The only time I've ever equipped them was on a viper and I had the same issue. Completely random too, sometimes they would work and sometimes not.

My X52 is kind of flakey too. I would be really happy with it if it were only a little more reliable.

Thankfully for me, the main glitching is on button 16 (the mouse button on the throttle which I use for toggle UI mode) so it's not SO bad when it screws up. Also occasionally the throttle will randomly not zero, it idles at about 15% until I unplug and replug it. That one actually got me killed, albeit indirectly when I accidentally hit boost instead of reverse throttle .

OKAY Guys!

Y'all have solved the problem. IMO - not firing is not a bug - at least not on the viper.

Whatever is mounted on the medium HP's will not fire until the target is in the bottom half of the canopy view. With gimbal mounts the center dot and the target dots must line up at least once to achieve lock. After that the weapon(s) will fire and track until lock is lost (target went outside of gimbal move range).

I switched the Beam laser to the medium HP to see if it would behave the same as the MC's and before it would fire I had to do the above. With target in top of canopy view could not achieve lock and could not fire. Pull up - put target in bottom half of canopy view, get lock and voila fire achieved. At least that's my perception. I say perception because on occasion the medium mounts keep right on firing even if the target gets away from the bottom half of the screen so maybe the real issue is just achieving a good lock/track before pulling the trigger.

Anyway - thanks for all the help. Couldn't have gotten the answer without ya!