It seems that after the latest server reset or today's patch a few areas of the game may not be loading correctly. What happened: I logged in to go poke around some of the mobs in the Bridge of Destiny chunk. I died and went back to get my tombstone, at which point I realized there were no monsters where there should have been, my breath bar wasn't showing up, and my tombstone (although loaded) was unmovable. I was booted to the character select screen, logged back in, had a repeat of all of the above, and then finally logged back in, got my tombstone and left, assuming it was a fluke. This happened again while trying to access APW in the Innovus chunk. I got to the freight lift in the center of the harbor and tried to fly over to the main APW entrance. I thought it was odd when I didn't get dismounted flying in - then I saw the mob that loaded to my right (_____ Mantodea?) was showing as a level zero and not moving. The key quest NPC was not there, and the doors weren't interactable. After scratching my head a moment, I was again booted to the character select screen. Repeat this flying to the door bit at least 10 times, logging in every time in the center of the harbor near the lift. Eventually I just started sitting there and chatting about what was going on (at least two others were trying to access APW as well and having the same issues)- and without moving, I was still being booted to the character select screen while sitting in the middle of the harbor. So I just kept loading back in until just recently a helpful GM Kirylia swooped in to reset the chunk. I used the downtime to write this. Thanks! I hope this helps!
In addition. While flying through southern Swamps of Rumug to try to leave the Innovus area, I was randomly dismounted and almost drowned due to consistent ping of around 1200. Once popping my fish gills potion, I hung around a few minutes and the ping never got any better (average of around 1200ish, spiking to 2k-3k, dipping to 300ish, all while staying connected). I recalled to Tanvu and my ping was automatically back to normal ranges.
Since I haven't received much reports about this, I'd recommend submitting in a support ticket so we can gather more info. Please be sure to include your Dxdiag and Msinfo to expedite the process.
