Zoning to/from Night Ward causes DC

[catscratchfever]

This started with Contact: Belladonna Vetrano, attempting to run a mission in Night Ward with 50+ Vigilante character.  I was disconnected while on the load screen trying to get into the door mission.  First attempt to log back in with that character also resulted in DC.  Was able to log back into Night Ward successfully again.  Any attempt to enter that mission results in DC.  Auto-completed mission and received the same behavior on the next door mission from Night Ward. 

 

At this point, I rebooted & re-validated (no issues found with install).  Above actions still cause DC.

 

Moving from Night Ward to other zones or First Ward causes no issues.  Moving between other zones causes no issues.  Running other door missions causes no issues.  Running a different Night Ward contact (Trilogy) with a door mission in Night Ward causes no issues.  Since this appeared to be related to Praetoria, I tried taking the Tunnel from Night Ward to Imperial City --> DC again.  Was able to log back into Imperial City OK.  Tried Tunnel from Imp City to Night Ward --> DC.  Log back in OK. 

 

Just in case the problem was toon-specific, I logged in with an alt [lvl 46 Vigilante].  Tried base portal to Night Ward --> DC.  Logged back into NW.  Tried Tunnel from NW to Imp City --> DC.

 

In case the problem was alignment related, I changed original 50+ toon back to Hero.  Base portal to Night Ward --> DC.  Re-validated again, just to make sure (no installation issues).  Logged back into Night Ward OK.  Jumped to base (via passcode) and took base portal to Talos, then tried Tunnel from Talos to Imp City, no issues.  Tunnel from Imp City to Atlas, no issues.  Tunnel from Atlas to Night Ward --> DC.

 

Something definitely broken around Night Ward travel.  Anyone else having this type of problem?

[Giovanni Valia]

Night ward is kinda notorious for loading slowly for most people. I used to disconnect a lot when zoning in night ward. My DC problems seemed to stop around the time I started using the x64 version of CoX.

[catscratchfever]

I am using the x64 version and really haven't had any issues until this past week.   And it's not slow, it's a consistent, repeatable DC.  Any character I've tried so far.  Progress bar gets to about 3/4 and then stops, pauses for a few seconds and boots me out.

[blackjacket]

I have recently experienced this same issue.

 

It started when I was running the Market Crash TF in Kallisti Warf. After completing the first mission and exiting, I was kicked out to the login screen. It took me three attempts to log back in before it let me with the character I was on the TF with. I didn't think too much about it until I tried to run a BAF and as soon as everyone accepted and it started to load, I was kicked off the league with an odd mapserve error and then loaded to Oro.

 

I researched the forums and found this post so I tested this Night Ward with the same affect. I get about 3/4 loaded and then it freezes for a long time and then kicks me to the login screen. No other errors or notifications are given. It takes three attempts to log back in with the same character before I am able to return to the game. After I leave Night Ward, I no longer have issues.

 

I have tried going full hero and turning off Ultra Mode with no change.

 

I was able to run Night Ward, Kallisti Warf, and BAF as recently as last week without issue, but as it stands now, any incarnate Praetorian level content is no longer playable.

 

[MetaVileTerror]

Gonna +1 this; Night Ward, First Ward, and Kallisti Wharf seem to have some kind of memory leak issue.  They are the only zones which consistently boot me to desktop after I've visited them a few times on a single instance of the client, or while multiboxing clients.

[catscratchfever]

And now I have two contact arcs locked out because of zoning issues.  The aforementioned Night Ward contact, and now a contact in PI gave me a mission in Kallisti Wharf which causes DC as well.

[blackjacket]

So after several months of troubleshooting, the issue is graphics related and the only way I can get to those zones is to lower my graphic settings all the way down.

 

Hopefully there will be a driver update to my NVIDIA card that will prevent this from occurring.