Fleet Launch Failure

  • Okay, this thing happen before, but after yesterdays update it got to another level..

    Doin 14x expos for which I need like 8-10 minutes right now. I don't even want to imagine having someone on lanx and timing hit which can not be sent!!

    Check this asap please and note the players when you screw up something with the update. Also this is happening without any addon activated.

  • I deem you are using the button in the galaxy view to send them.

    If so, you have to wait 1 sec or more before sending a new expo.


    Same for probing, by the way.

    Control Panel -> Settings -> General -> Display members’ signatures -> NO

  • I deem you are using the button in the galaxy view to send them.

    If so, you have to wait 1 sec or more before sending a new expo.


    Same for probing, by the way.

    Not only the galaxy view 16 slot button but also normal fleet tab just pops the fail launch failure. When it pops, doesn't matter on what way I want to send an expo, it just doesn't send it.

  • I deem you are using the button in the galaxy view to send them.

    If so, you have to wait 1 sec or more before sending a new expo.


    Same for probing, by the way.

    Not only the galaxy view 16 slot button but also normal fleet tab just pops the fail launch failure. When it pops, doesn't matter on what way I want to send an expo, it just doesn't send it.

    Ok.


    Well I do not know exactly the new mechanics, but a system has been implemented to prevent sending fleets in a second or less upon return, and some other undisclosed bugs.

    Obviously the system is now too sensitive / restrictive.


    Maybe you used to send your expos very quickly ?

    If so, take it easy while awaiting for the fix.

    if an error occur, wait 15-20 sec before trying again.

    I hope this helps.

    Control Panel -> Settings -> General -> Display members’ signatures -> NO

  • Fleet launch error, fleet in combat messages while being probed, etc. are all 10x what they were...and this goofy 2 to 3 second probe delay crap that requires you to go back out to overview to refresh before going back to galaxy view to probe again is f'n ridiculous.

    And, it sounds like there is a bug with probe spamming that is preventing ABM construction while being IPM'd...

  • Here's a message that was given by the French Game Admin on the board, in a topic noting the same problem:


    "The latest patch has effectively implemented "planet-lock" (a system preventing certain actions from being performed too quickly and/or at the same time as the calculation of a battle in progress) to the feature at issue here, it has already been active for a multitude of other features (merchant, build order, etc.) for a long time but had been forgotten for standard expedition fleets.

    I haven't had time, and won't until next week, to assess whether or not it's sufficient to prevent dodging via this button (in 11.15.5 I had 100% success even when set to +0s) but at first glance it seems to already limit its use to this effect quite a bit. Don't hesitate to give your opinion and I'll raise the subject again on the GF side if need be."

  • Here's a message that was given by the French Game Admin on the board, in a topic noting the same problem:


    "The latest patch has effectively implemented "planet-lock" (a system preventing certain actions from being performed too quickly and/or at the same time as the calculation of a battle in progress) to the feature at issue here, it has already been active for a multitude of other features (merchant, build order, etc.) for a long time but had been forgotten for standard expedition fleets.

    I haven't had time, and won't until next week, to assess whether or not it's sufficient to prevent dodging via this button (in 11.15.5 I had 100% success even when set to +0s) but at first glance it seems to already limit its use to this effect quite a bit. Don't hesitate to give your opinion and I'll raise the subject again on the GF side if need be."

    The only word for GF implementing that which is appropriate is FUBAR. It's FUBAR.