These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Issues, Workarounds & Localization

 
  • Topic is locked indefinitely.
 

Serious Issue with Fighters/Fighter Bombers
Author
Previous Topic Next Topic
Zeroniss
Shiva
Northern Coalition.
#1 - 2012-03-18 19:47:39 UTC
Fighter and fighter bombers follow you in warp, but when they return, they sit at a single spot in space. The mothership/carrier then has to go to that spot in space to get them back as they are not returning on their own.

In one instance we had fighter bombers return to the target they had previously been attacking and sit their idle and abandoned after downtime...

This is particularly dangerous if a mothership is warping to a safe POS only to find that it's fighters and bombers sit on the edge of the POS shield and have to be manually retrieved.

This has happened to multiple supers now and we've filed several petitions across all the characters experiencing it. No real response yet, and one of our pilots still has no bombers because his entire flight disappeared. Expect videos soon as we are attempting to replicate the issue on the Test server.

Edit: We have 1 video that is currently in the process of being uploaded. Will update this thread with that video, plus test server results.

If anyone else has been experiencing issues similar or otherwise, please add to this thread.
Gizan
Deep Core Mining Inc.
Caldari State
#2 - 2012-03-19 09:02:50 UTC
i have seen many issues with fighters not returning when warping. or when you warp they follow you but sit idle in the middle of space, and "return to drone bay" has to be pressed several times before they wake up and finally warp back to your ship, but they do like to sit 8-10k away from you doing nothing saying "returning to bay"


has happened with both carriers/supercarriers.
Cougars Scout
CANNOT UNDERSTAND NORMAL THINKING
#3 - 2012-03-20 05:19:55 UTC
Several of us have petitions open with CCP. But yes, FBs are FUBAR - suposedly fixed last DT (the 19th) currently amending my open petition that the error hasn't happened or has become less frequent.