Unable to fire weapons

BossDrum

BossDrum
Hi all

I purchased a Thrustmaster T.16000M joystick but I am experiencing issues firing weapons during a battle.
Sometimes it works sometimes not.
I have tried mapping the primary fire key to another button on the joystick but it still only works intermittently. When I have left the battle, usually it works again!
I am able to fire if I map the fire key to the left mouse button, but the Thrustmaster or the way it interacts with Elite Dangerous is just weird.

I've checked that all buttons are working and calibrated within Windows properties for the joystick.

Has anyone else experienced a problem firing weapons with the T.16000M joystick?

Thanks
 

abumonkey

abumonkey
Are you sure it's not an in-game power issue i.e. you are near the limit of the powerplant for your ship with weapons deployed and so can run out at certain times? I think I had something similar in a viper once that was down to that?

Abu
 

Zplintz

Zplintz
Has the usb port or hub you are using got enough power?

Too many devices in a hub (especially unpowered hubs) or the front ports on the case (which often do not provide as much power as the ones connected to the motherboard at the back) can cause issues.

Sorry if this is teaching you to suck eggs but have you tried clearing your config completely and starting over?
 
Last edited:

abumonkey

abumonkey
Keevan Vass said:
I have seen this as well. Lasers right? I think it may be a graphic issue as I have still seem enemy shields light up. Never seems to happen with multi cannons.
Click to expand...

With me in the viper it was a laser issue. Power went down but no graphics to show the shots, but weirdly only in a viper I had, none of the other ships. Never really bottomed out whether a power issue or bug, maybe need to head back to where viper stored to test it out...
 

bonsek

bonsek
Sometimes gimbal weapons that are under the canopy will not fire if the target is in the upperhalf, meaning the gimbal can't gimbal enough ;)
 

Zplintz

Zplintz
bonsek said:
Sometimes gimbal weapons that are under the canopy will not fire if the target is in the upperhalf, meaning the gimbal can't gimbal enough ;)
Click to expand...

It's a good point (and certainly that's better than shooting your own nose off) but wouldn't that be exactly the same for mouse fire?
 

Benaron

Benaron
I have the same joystick and the same problem. Others on the net have reported this too.

This joystick uses rubber membrane buttons (not the best). I think I may have squeezed the trigger too hard too many times hehe.

Now, I just keep clicking the trigger until it does work. At least until I can figure out what to replace it with.

If you're a do it yourself, you could try repairing the membrane:

https://www.youtube.com/watch?v=BvAu_GtdSPQ
 

bonsek

bonsek
Zplintz said:
It's a good point (and certainly that's better than shooting your own nose off) but wouldn't that be exactly the same for mouse fire?
Click to expand...

Hmmm, have you tried pressing the left shift (UI focus) and try firing your weapons after?

When I used TrackIR with Voiceattack to access the side panels, and then turn my head to the center, sometimes the game will still think that I am in the panel UI and the power distributor hat switch, trigger, and FSD buttin on the joystick would not work.
 

Thanatos

T
I have an X-55 and have similar issues. Sometimes will not fire - sometimes thrusters won't work and power distribution that I have mapped to a HAT switch doesn't function.
I think its related to some other bind or keypress interfering. I notice sometimes the comms panel has dropped and I hit c which scrolls it up and things start working.
Other times I need to quit and reload. It might also be related to the UI focus - I sometimes have weirdness with the F12 bind - recenter blocking other input, hitting the re-focus bind again gets it out of this state.

Its so random its hard to put a finger on the root-cause.
 

Benaron

Benaron
Thanatos said:
I have an X-55 and have similar issues. Sometimes will not fire - sometimes thrusters won't work and power distribution that I have mapped to a HAT switch doesn't function.
I think its related to some other bind or keypress interfering. I notice sometimes the comms panel has dropped and I hit c which scrolls it up and things start working.
Other times I need to quit and reload. It might also be related to the UI focus - I sometimes have weirdness with the F12 bind - recenter blocking other input, hitting the re-focus bind again gets it out of this state.

Its so random its hard to put a finger on the root-cause.
Click to expand...

You can tell if the problem is with your joystick or the game.

Exit the game and then go into control panel/devices and printers, here you should see your joystick. Right click on the icon, then select "Game controller settings" the click the Properties button. Now you can check all your buttons, hat etc.

On my T.16000M, it skips the trigger button about once every ten times I press it. More of a nuisance really. I would have thought the X-55 would be better, given the price.
 
Last edited:

BossDrum

BossDrum
I've tried two different joysticks now and they both fail to fire during a battle.
I am able to fire at all other times, for example I found a funeral barge and was able to fire my default lasers (Cobra MK3) as a test.
It just seems that whenever there is a real need to hit an enemy, they just do not fire at all.
I've tried changing the graphics quality but that made no difference.
 

Tarman

Tarman
Benaron said:
You can tell if the problem is with your joystick or the game.

Exit the game and then go into control panel/devices and printers, here you should see your joystick. Right click on the icon, then select "Game controller settings" the click the Properties button. Now you can check all your buttons, hat etc.

On my T.16000M, it skips the trigger button about once every ten times I press it. More of a nuisance really. I would have thought the X-55 would be better, given the price.
Click to expand...

X-55s have a bad QC rep. Great when they're working; garbage when they're not, with lame support. Saitek lovers are better off getting a well-maintained 52.
 

Thanatos

T
Its not an X55 issue. Its related to the another bind, or input mode blocking the new input.
A good example is when the comms chatter panel is open UI focus won't work - close comms panel with 'c' and it works.

it seemed worse in b1.1 - have not tried released 1.1 but will later.
I have exited the game and checked button functions. I have even re-mapped the failing button (and the bind mapping tool in Controls menu registers the input).

Once I get a better handle on what's triggering it for me i'll ticket it.
 

Thanatos

T
Thanatos said:
Its not an X55 issue. Its related to the another bind, or input mode blocking the new input.
A good example is when the comms chatter panel is open UI focus won't work - close comms panel with 'c' and it works.

it seemed worse in b1.1 - have not tried released 1.1 but will later.
I have exited the game and checked button functions. I have even re-mapped the failing button (and the bind mapping tool in Controls menu registers the input).

Once I get a better handle on what's triggering it for me i'll ticket it.
Click to expand...

This is really starting to annoy me. The issue is 100% related to the chat window opening.
It seems to default to opening all the time - dropping out of SC the chat window is open, and I need to push 'c' every time else other joystick functions (seems only the HAT switches) don't work.

I'll ticket this as I can't see anything wrong, and hitting 'c' resolves it 100% of the time.
 

mickeeie mouse

Banned
M
im having this issue on my x52

the primary fire button(trigger button 1+15) is very intermittent in its operation, i thought the fire button was faulty, but it seems to be working fine in the control panel, and other games. dont know whats going on

MM

edit: it was the ps2 cable that had worked loose, all good now
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom