🛈 Announcement
Greetings! The Division forums are now archived and accessible in read-only mode, please go to the new platform to discuss the game
  1. #21
    Bump. Same thing happened to me just now. Insane this hasn't been dealt with. Seems like a super easy bug fix. Playing solo on heroic, encountered rouges in the same area as everyone else, beat them, now I'm stuck on the "search the infirmary" objective. Like why make this mission a part of the manhunt, but not fix this bug? A lot of players are going to run into this. Wouldn't even be that bad if it wasn't on heroic and I didn't have to start the ENTIRE mission over again. At least I'll know now to just let the rogues kill me next time I guess...
    Share this post

  2. #22
    Bump again. Same thing to us (duo) playing heroic.
    Share this post

  3. #23
    This actually just happened to me as well. Same condition as above Occurred 10/06/1820hrs CDT
    Share this post

  4. #24
    Happening right now to me.
    Share this post

  5. #25
    Airjarhead's Avatar Member
    Join Date
    Mar 2004
    Location
    Texas
    Posts
    220
    I had this happen to me, when it was first reported, now it just happened to me again on Heroic. Both of us said - "HOW HAVE THEY NOT FIXED THIS YET"
    So we restart the mission (because it's heroic), and the second time, we didn't get rogues, but it still won't progress past the same point - the game keeps saying "Search the Infirmary."
    Absolutely unbelievable.
    Share this post

  6. #26
    up... same issue here. mission is just for season pass project.
    Share this post

  7. #27
    Same here. Triggered rogues, killed them, mission cannot continue.

    Killed myself, made it back to the same spot. Killed enemies, opened the door progressed forward a little more but now mission haults at the landing of the stairs after autopsy.
    Share this post

  8. #28
    Same as above. Challenging difficulty, if that even matters...
    Share this post

  9. #29
    UbiExcellent's Avatar Ubisoft Support Staff
    Join Date
    Sep 2019
    Posts
    1,269
    Hi everyone! I'm very sorry to see that you all are still encountering this error. I've let our dedicated teams know about this, so they can continue to investigate. In the meantime, if anyone is able to share more footage of this error occurring, that would be very helpful for the report.
    Share this post

  10. #30
    Not sure this helps anything, but ran into this exact issue today (October 28, 2020) and attempted to replicate it as much as I could.

    Steps to replicate:
    1) Start The Tombs mission
    2) Work your way to the "Autopsy Suite"
    3) Check for Rogue Agents spawning in the Autopsy Suite
    4) If Rogue Agents do NOT spawn, repeat steps 1-3
    5) Kill Rogue Agents

    From here things get somewhat subjective without seeing the code, but this is what I can decipher from multiple attempts at figuring this out. I have encountered the Rogue Agents 5 times now in this room, and the same few things ALWAYS happen.

    1) The Rogue Agents open the "locked" door that the player must go through to continue the mission.
    2) The "locked" door remains open once the Rogue Agents spawn, and never closes again
    3) Restarting the mission does not seem to close this door. It remains open for the rest of my playthroughs (whether Rogue Agents spawn or not).

    This leads me to believe that:
    1) The opening of the door by the player is the trigger to continue mission objectives
    2) The state of the door is not reset when Rogue Agents are defeated, and it is also not reset when the mission is reset (although I cannot figure out what exactly resets the state of the door)
    3) Rogue Agents have the ability to interact with objects that are connected to Player Objectives. (This seems like a really poor design decision...)

    I think there are a few possible reasons why this is happening, but again, without seeing the code it is difficult to tell. Hope this helps the devs, because currently I have found no workarounds for the player to overcome this bug once it is encountered.
    Share this post