Requesting a "please explain" :)

BlackLegionnaire

BlackLegionnaire
The gist of it.

Last night i'm out Bounty hunting with my beloved Viper, everthing is cool. I log off go to sleep.

This morning:

I launch, get to my RES, find a wanted ship, initiate attack and all of a sudden my 2 turreted pulses (2 F) aren't firing!!!!! What the hee?
I didn't change anything! everything was like it was last night when they worked. DAMMIT....i love those 2 turreted pulses....whats going on? Anyone had this happen?

At least my class 1's fire.

Its a bug right? Needs to be fixed....This is serious! Its no small bug!


cheers guys
 

Grumbleweed

Grumbleweed
It could be almost anything, here are things I can think of off the top off my head.

- is it the controller? Try firing the guns using the keyboard instead.
- is it the ships weapons module? Check that the weapons are enabled in the right hand panel.
- is it your pc/controller drivers? Try checking the trigger input in some other way, like the control panel in Windows.
- Is it the game controls settings? Elite still has the habit of resetting your controls to default settings if it doesn't detect your controller on start up (which is very stupid of them)

There are probably other things that it could be, but work backwards until you find the issue. I'm sure you'll be bounty hunting in no time. If you find its a bug, go ahead and file one, but do include much more information than you did in your first post.

I hope that helps, fly safe.
 

BlackLegionnaire

BlackLegionnaire
Grumbleweed said:
It could be almost anything, here are things I can think of off the top off my head.

- is it the controller? Try firing the guns using the keyboard instead.
- is it the ships weapons module? Check that the weapons are enabled in the right hand panel.
- is it your pc/controller drivers? Try checking the trigger input in some other way, like the control panel in Windows.
- Is it the game controls settings? Elite still has the habit of resetting your controls to default settings if it doesn't detect your controller on start up (which is very stupid of them)

There are probably other things that it could be, but work backwards until you find the issue. I'm sure you'll be bounty hunting in no time. If you find its a bug, go ahead and file one, but do include much more information than you did in your first post.

I hope that helps, fly safe.
Click to expand...

Trust me bro, i've changed nothing since last night, when it worked. I use mouse and keyboard.
Point 2 and 3....nothing changed there.

.....pretty sure it's a game bug....

Thanks for trying to help man.
 

ArakAtak

A
Did you happen to switch USB ports where your controller is plugged in?

Are you using a custom profile via Saitek software and is it enabled before launching the game?

Check the control settings in game are still selected for your controller. I had a similar thing happen the other week and lost all secondary fire. It had auto selected a different profile under controls for some reason. I had just had everything unplugged that day so maybe the different port triggered something.

ah - I just saw you said mouse+keyboard so ignore the Saitek idea. Still double check the bindings within the program. I had to reenable mine a couple of times. I think I ended up assigning sec fire to something else before it worked again. Then I could return back to my original binds.
 
Last edited:

Jockey79

Jockey79
As far as I am aware, turrets don't fire unless fired upon, and even then you have to be sure they are on the right fire mode in the right hand panel.

Try putting them to forward fire only, fire them (be sure they are working)
Then try both fire modes (target and fire at will) out in combat.

[Also, I have seen sub targeting wreak havoc with turrets - try fighting using sub targeting and without (just main hull hits) ]
 
Last edited:

BlackLegionnaire

BlackLegionnaire
ArakAtak said:
Did you happen to switch USB ports where your controller is plugged in?

Are you using a custom profile via Saitek software and is it enabled before launching the game?

Check the control settings in game are still selected for your controller. I had a similar thing happen the other week and lost all secondary fire. It had auto selected a different profile under controls for some reason. I had just had everything unplugged that day so maybe the different port triggered something.

ah - I just saw you said mouse+keyboard so ignore the Saitek idea. Still double check the bindings within the program. I had to reenable mine a couple of times. I think I ended up assigning sec fire to something else before it worked again. Then I could return back to my original binds.
Click to expand...

Keyboard and mouse brother!
Its a game issue...im convinced its a game bug, Turreted Pulses 2 F are bugged.
The pulses are meant to commence firing when you Target your....TARGET! :) The simple act of pushing "T" on a "WANTED" target should commence firing.....
and it stopped doing that....not a controller issue
 

CMDR UBERPEITSCHE

C
Same always happens to me when equipped with 2 Class 2 turrets on the Viper.
Only on the Viper and sometimes only one of the two stops working, it's a bug.

And yes I know how turrets work, never failed on any other ship.
 

BlackLegionnaire

BlackLegionnaire
CMDR UBERPEITSCHE said:
Same always happens to me when equipped with 2 Class 2 turrets on the Viper.
Only on the Viper and sometimes only one of the two stops working, it's a bug.

And yes I know how turrets work, never failed on any other ship.
Click to expand...

So i'm not cookoo....

Jockey, i'll try forward fire again....pretty sure I already did :)
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom