Can't get into same instance with Party (anybody?)

7/6/2017 10:00 PM
Title: Can't get into same instance with Party (anybody?)
Reproduction Rate: Once
Blocker? Yes
Details:

I got dropped after about 30 seconds of network symbol, when I came back in I couldn't see my party member anymore.

A fellow was talking about visiting my vendor while I was next to it, but I couldn't see him. I thought he must have been in Friends Only, but it looks like I was in limbo instead.

Viola (my partymember) left for the world map, didn't see my shield on the maps, came back in, still can't see me. I went out to the overworld and couldn't see her (she was there again), so went to another town where I knew a friend was but we couldn't see each other.

Steps to Reproduce: Log out of a different account (maybe not necessary,) and in with another. Somehow, you have entered the twilight zone. No idea how to replicate.
User Specs:
OS: Windows 10 (10.0.0) 64bit
CPU: Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz (8) System RAM: 16322
GPU: NVIDIA GeForce GT 650M GPU RAM: 995
SotA.EarlyAccess.LIVE.Win.64.626.Date.07.05.17
Area: POT_forest_metropolis_01_template/PaxLair
Area Display Name: PaxLair
Loc: (-167.7, 36.0, 391.7)

 

I've had this in multi mode. Which mode were you in

 

I was in Multi, they were in Multi, I made them check, and I did as well.

 

Mutli seems to split to help load, so I had exactly that - I had a toon, I wanted to run another toon to meet it, they didnt end in the same zone. were you grouped?

 

I've seen this a few times but never had any solid replication steps and not sure if it would even be possible to do so. The issue would appear to be at least in part on the server side, do the devs have tools to interrogate the current state of an avatar's server session that would give us some hints? If so it may be worth poking one the next time it happens.

Closing the game out completely and starting it up again seems to fix it.

 

I think this is related to a larger issue we are investigating and already working on. Closing the client fully as Wintermute noted is the workaround for now. While it can still happen, also always check to make sure everyone is on the same build. The loading screen should tell you but it is easy to miss. Sometimes everyone thinks they are all on the same build but after re-check they are not, and we need to eliminate these situations for our tech side.

 

This was a late night session, so you guys had been closed for quite a while when we all got in.

Closing it did take care of it.