Southpaw S&P - Am I Forever Glitched?

I really don’t recall

Hmm. Fair enough, but OP seems to have that problem constantly.

I for one always did it when it became available available across 4 different systems (all but XOne) and never encountered this bug before. Only once did I have him not spawn during the side mission but never again.

It’s definately quite strange. I have 4 characters on UVHM and Axton is the only one who can go through the area. Gaige and Salvador are glitched out and I haven’t done the mission with Krieg yet. Krieg is still at the point where Sanctuary hasn’t taken off, I think I’m going to complete the mission now and see if I can get through Southpaw after turning in the mission. Gaige and Salvador could have done the quest after the take-off (can’t remember for sure though), so maybe that’s why it’s glitched out for them.

I’m with Blackheart on this one.

I’ve probably done the quest alone 11 times. Not once have I run in to the issue.

For my Gaige I ran it as soon as it’s available, that is before Sanctuary takes off.

So I just ran it on my lv 54 Zero. I did the same procedure: Grab mission (before Sanctuary takes off), finish mission, fast travel and turn in at Sanctuary. Save and Quit. I just ran through the map flawlessly for farming reasons.
Also, I took the left route for Assassin Oney (Not the right side with the small room) for both runs.

So it’s only my Gaige that’s glitched at the moment. My other chars aren’t in UVHM status so I can’t run it with them.

That is just so peculiar, especially considering you’ve restarted it.

I’d definitely get a ticket for the issue mate.

Yep, your 1-y is hardlocked.

Ok, so this thread is kind of old, but I managed to resolve the issue. Both my Gaige and Salvador were locked out of the area as well. So I reset the playthrough with them and completed the Assassinate the Assassins mission as soon as I could (completed the mission once I could access Sanctuary). Both of those characters can now go through the area without any issues.

I reset Axton (again), which has apparently resolved the issue on that character. I’m glad others are also getting resolution.