🛈 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. #1

    Challenge missions still not unlocking!!

    Why is this still happening? So far three attempts on Lexington event center and one on consulate. I'm loading in to Lexington one more time, lets see.........again locked!!
    Share this post

  2. #2
    NitroMidgets's Avatar Senior Member
    Join Date
    Apr 2016
    Location
    Dupont, WA
    Posts
    1,650
    The gate being closed on Lincoln Tunnel, doors shut on the Consulate or Lexington, it really just happens far more often then it should.

    This morning it happened but none of us moved forward. The leader switched the difficulty a couple of times ending back up on Challenging. At that point we moved forward and the mission allowed us to start (doors swung open). I have only seen it done once but have been locked out dozens of times so it might have been a fluke.
    Share this post

  3. #3
    It's very frustrating, especially when you have to stare at that loading screen over and over.
    Share this post

  4. #4
    TickTak77's Avatar Senior Member
    Join Date
    Dec 2015
    Location
    Toronto
    Posts
    636
    Finding a new instance normally fixes the issue.

    Frustrating.
    Share this post

  5. #5
    AK_8100's Avatar Senior Member
    Join Date
    Apr 2016
    Posts
    774
    i think it's some client issue with one of the group members and this screw for all the group ... i heard something on SotG about it but didnt really listen to it cause i was pretty mad about pon pon beenies and chit-chat about thin air ...
    Share this post

  6. #6
    yeah they really need to fix this, an actual reset mission option for the leader could help.. bit of a no brainer. i have spent 30mins+ some times trying to get a functional instance and a group of decent players for missions and incursions. im not sure if there is a trick to it, i relog if i was previously in a failed instance attempt.
    Share this post

  7. #7
    never run into this problem. try logging out and back in and then try to reset it again.
    Share this post