My fighter is bugged, and this seems to be permanent!

Shaamaan

Shaamaan
I just filed a bug report here... Suffice to say, my fighter (the first of the two fighter slots I have in my fighter bay) refuses to follow any orders besides "hold" and "maintain formation" (he'll also return to the ship if ordered). Anything else and the NPC responds with a "negative". This happens even after I've exited and relogged back into the game. I've noticed that the "current order" for the fighter is temporarily "defend" whilst the ship is being launched, but then switched to "maintain formation".

Strangely, if I launch the second fighter (second slot), all's fine.

This is a bit worrying - this is the first time I've had a bug "stick" despite logging out and back in.

Did anyone experience something like this? I'd really like to get this sorted out sooner rather than later... :(
 

Stealthie

Stealthie
I had a similar(?) thing with an SRV once.

Every time I deployed it, it wouldn't respond to any controller inputs.

Menu-logged: same thing.
Restart game: same thing.
Self-destructed SRV and bought a new one: same thing.

In the end I just sold the SRV bay, replaced it with another one and it was fine again.
 

60mm

60mm
My fighter refuses to follow orders in Conflict Zones. Once he starts fighting, he stays fighting until dead.

Have also noticed he won't deploy either when ordered to until I go back into the orders menu to do it again and he suddenly decides to obey.

Quite annoying.
 

KevinMillican

KevinMillican
Shaamaan said:
I just filed a bug report here... Suffice to say, my fighter (the first of the two fighter slots I have in my fighter bay) refuses to follow any orders besides "hold" and "maintain formation" (he'll also return to the ship if ordered). Anything else and the NPC responds with a "negative". This happens even after I've exited and relogged back into the game. I've noticed that the "current order" for the fighter is temporarily "defend" whilst the ship is being launched, but then switched to "maintain formation".

Strangely, if I launch the second fighter (second slot), all's fine.

This is a bit worrying - this is the first time I've had a bug "stick" despite logging out and back in.

Did anyone experience something like this? I'd really like to get this sorted out sooner rather than later... :(
Click to expand...

Are you sure the fighter still has ammunition ?

SLFs refuse attack and defend commands when they can't fire
 

Deleted member 38366

D
Seems a known bug, I've had that happen lots of times.

Ways to fix it :
- have it dock and launch again after "Fighter Maintenance check complete" Message
- hop into it yourself and manually check that no Modules (i.e. Weapons) are disabled
- do an FA off Boost and kill the SLF, then launch Spare

Still, very annoying and making SLFs rather unreliable right now. You never know when they go "on strike" :p
 

Shaamaan

Shaamaan
KevinMillican said:
Are you sure the fighter still has ammunition ?

SLFs refuse attack and defend commands when they can't fire
Click to expand...


He's got beam weapons, so... yeah. Unless these are somehow damaged and don't get repaired when at a station or something...

I followed the suggestion to sell the fighter bay. Things seem to be back to normal! Thanks! ...except now the fighter bay is "second" in the list of deployable ships, and I'd really prefer it to be first... I guess I'll have to do something similar with the SRV bay... :p
 
Last edited:

777Driver

777Driver
Shaamaan said:
He's got beam weapons, so... yeah. Unless these are somehow damaged and don't get repaired when at a station or something...

I followed the suggestion to sell the fighter bay. Things seem to be back to normal! ...except now the fighter bay is "second" in the list of deployable ships, and I'd really prefer it to be first... I guess I'll have to do something similar with the SRV bay...
Click to expand...

Glad you fixed. Was going to recommend switching to the fighter and checking if weapons are disabled in the modules tab, worked for me. Others have reported similar issues with varying solutions.
 

Trollymctrollerson

T
I had a bug where every time I told it to attack target, it was like a ghost clicked recall fighter. It would blink like I had pressed that button even though attack target was obviously selected. Of course the fighter would try to dock while I was busy fighting for my life and really needed its help .
 

moorison

M
Something similar happened to me once, the pilot refused to return to dock and flew in a straight line away until he reached the maximum distance of 30km and exploded. I assume the engines were damaged.
 
You must log in or register to reply here.
Back
Top Bottom