So in a first for my group, we were hit with three bugged and failed missions tonight.

1st was a defense missions where bugs stopped spawning and missiles stopped shooting.

2nd what the extraction vehicle left immediately when one person entered it.

3rd what no one could get in the shuttle.

This was a serious WTF night, we lost so many samples. While I appreciate the devs, stop trying to balance and fix some bugs.

  • Zeke@kbin.social
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    5 months ago

    We’ve had the pelican end up in the ground and no one could get in. The one where no one could get in was fixed by diving into the pelican (not recent).

  • MelastSB@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    6
    ·
    5 months ago

    For the two Pelican bugs, it’s not really a bug from what I understand. If the pelican gets lightly damaged by stratagems, it will leave with only one player. If it gets heavily damaged, if will start burning and then you might as well call a 380 on the team (unless there’s a kill major order)

  • Kyrgizion@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    5 months ago

    I don’t have many crashes anymore since the last three updates or so, but I get a connection lost error every one in five missions or so now. Usually right before extraction after 30+ minutes of clearing the map.

    It’s seriously destroying my drive to continue playing.

  • all-knight-party@kbin.run
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    5 months ago

    It does really suck ass since these bugs waste the most time, but I think it’s the rarity of these bugs that makes them hard to fix or even notice/report/reproduce. I’ve also had two missions fail in my time, once we couldn’t get on the extract, and once on a fuel shuttle mission the shuttle simply never arrived to be fueled.

    But in 130 hours each of those bugs have only happened literally one time each for me, so reproducing and fixing them is probably complex because it’s so rare.

    Each of us has a combined five failed bugged missions, but only one of those types sounds like the same problem that was reproduced, and that’s one time for each of us separately, and neither of us will likely remember all the different things that happened to get to that point and trigger the bug, and for the devs to have these bugs reported accurately is also not always clear

    for instance you mention a defense mission, but when you say defense mission I think of an eradicate mission where you kill a number of bugs and extract, but then you mention missiles, which means it’s probably the newer mission type where you defend the gates and large missile launcher, which I don’t remember the specific name of. if arrowhead received that report and tried to reproduce it on an eradicate due to miscommunication they’d never figure out how to fix it. Basically, it’s probably complicated but should definitely be fixed

  • loganb@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 months ago

    I will say I had an extra buggy experience last night too. Out of nine or so missions, we couldn’t extract from two of them because no one could enter the pelican. If you did manage to clip into the pelican, you would just hang out in there and never extract.

    I can see the justification of the pelican talking off immediately if its damaged. My team makes a conscious effort to consolidate samples and have that player enter the pelican first if it’s smoking.