Anyone else have a character "stuck" in South Shroud?

[Rezzo]

So here I am today in a hunt party running around when we get a notification that the A rank has spawned in South Shroud. I teleport to Quarymill because the hunt mob is only a few feet to the south west of that town. Once the zone loaded I summoned my chocobo and was able to to take about three steps before the game crashed to the desktop. At first I thought nothing of it, usually I can log right back in if something like this happens. Not this time. Each time I log back in, and select my Rezzo character, the zone starts to load and then the game crashes to the desktop.

Now here's the interesting part: If I log in and select an alternate character, that is on the same server but in a different zone, I have zero problems. I can run around on this other character in any zone I choose, (with the exception of South Shroud as I'm afraid to go back there until I can log back into Rezzo), without issue. But when I log out back to the title screen, then proceed to the character select screen and choose Rezzo, the zone starts loading and the game crashes to the desktop.

Now I already have a ticket submitted to support about this issue, so I'm not really looking for help troubleshooting the problem. What I am looking for is to see if anyone else is having the same problem I am.



TL;DR: Teleport to Quarrymill in South Shroud, game crashed, can't use character in that zone but can use characters in other zones. Has this happened to anyone else since the 2.35 patch?

[Enkidoh]

I've found Quarrymill tends to have a lot of players idling around waiting for Odin to spawn (even though he can appear anywhere in the Shroud, a lot of players just like to base themselves in Quarrymill for some reason). So it's possible there's so many player characters in that one spot your computer is crashing due to the strain (especially if there is a Hunt NM there). Unfortunately, there's not much I can suggest sadly.

[TomTom1968]

Happened to me once, solved on its own after several hours and I was able to login again.