Mission zoning delays on teams


Master-Blade

 

Posted

whats up with mission zoning since i17 ?

If im on a team and the 1st one to a mission door (and quite a fair way ahead of the rest of the team), the loading screen just seems to pause.

I'll wait and wait and can actually hear the mission door opening and closing as other team mates are zoning into the mission.

The loading screen bar then starts moving, zones me in and the rest of the team are on the map already even tho they were miles away.

There is no issue with my internet and im running a i7-930 with 16gig of ram, 5870 ati, SSD, blah blah blah

It almost like the loading now waits for most of the team to have clicked the mission door b4 it zones you in.

Anyone else noticing it ?

its just really annoying since I could have already completed the objectives instead of waiting for zoning.


My LotG sold for 65mil and I'm spending it all on hats

Needlepoint and Hobbytex Champion 1984

Blaming others since 2003

 

Posted

Quote:
Originally Posted by Soliton_Wave View Post
It almost like the loading now waits for most of the team to have clicked the mission door b4 it zones you in.
I've noticed similar behavior even before i17 went live. The only part I feel is i17 specific is that we can still hear what's going on around us before the map finally switches over. I don't remember that before. It used to just keep us in silent limo at the title splasher until it changes to the splasher for the map we are entering.

It does feel like the first person entering the mission is waiting for the rest of the team before the mission is opened, but I think it's just that the process of creating the mission instance is just taking longer for some reason. Everybody else is simply catching up and getting stuck during the process as well, and when the instance is finally ready, everybody finishes zoning at the same time.

The reason I say this is because loading into an SG base does the same thing sometimes, even when solo. Mission and SG base instances do not even exist until they are populated. If somebody is already in the SG base, or I was in it very recently, it will load very fast, but if nobody has been there for a while, the instance has to be recreated, and it takes longer for me to zone into it.

Quote:
Originally Posted by Soliton_Wave View Post
its just really annoying since I could have already completed the objectives instead of waiting for zoning.
Not for nothing, but since it's a team, it's usually common (or not so common) courtesy to wait for other people to arrive before completing objectives or defeating enemies (unless it's a door ambush) anyway... especially if you are not the team leader and/or it is not "your" mission. Otherwise people may miss out on Mission completion bonus, or even just the xp/inf involved in killing the enemies.

Some people argue they are not entitled to the points because they were not in the mission yet and didn't help kill the enemy or whatever, but as a team you should be helping each other get points, not remove enemies/objectives so they get less. If you wanted to solo the mish, then why even join a team?


 

Posted

Quote:
Originally Posted by Master-Blade View Post
QR
Not for nothing, but since it's a team, it's usually common (or not so common) courtesy to wait for other people to arrive before completing objectives or defeating enemies (unless it's a door ambush) anyway... especially if you are not the team leader and/or it is not "your" mission. Otherwise people may miss out on Mission completion bonus, or even just the xp/inf involved in killing the enemies.

Some people argue they are not entitled to the points because they were not in the mission yet and didn't help kill the enemy or whatever, but as a team you should be helping each other get points, not remove enemies/objectives so they get less. If you wanted to solo the mish, then why even join a team?
It depends on team, YMMV. My friends and I mostly doing speed runs and it is irrelevant for us whether we getting mission completion bonus or not. Very often, when mission requires clickie or something like that, only one person will enter that mission while rest of the team will gather at next mission door or zone (2nd mission of Numina, AP and KR of Manti, 2nd mission of Ice Mistral, etc.)


 

Posted

Quote:
Originally Posted by NordBlast View Post
It depends on team, YMMV.
...
(2nd mission of Numina, AP and KR of Manti, 2nd mission of Ice Mistral, etc.)
True enough. For the sake of speeding through specific arcs or TFs, and specifically with people you know, then I certainly agree. I was going by general PuG code of conduct. lol


 

Posted

There's a PuG code of conduct? I can think of quite a few people that should read up on that if that's the case, hehe.


 

Posted

Quote:
Originally Posted by Pyber View Post
There's a PuG code of conduct? I can think of quite a few people that should read up on that if that's the case, hehe.
Want to help me write an official one? That could be fun. lol j.k


 

Posted

Quote:
Originally Posted by Master-Blade View Post

Not for nothing, but since it's a team, it's usually common (or not so common) courtesy to wait for other people to arrive before completing objectives or defeating enemies (unless it's a door ambush) anyway... especially if you are not the team leader and/or it is not "your" mission. Otherwise people may miss out on Mission completion bonus, or even just the xp/inf involved in killing the enemies.

Some people argue they are not entitled to the points because they were not in the mission yet and didn't help kill the enemy or whatever, but as a team you should be helping each other get points, not remove enemies/objectives so they get less. If you wanted to solo the mish, then why even join a team?
yeah thanks

Was really just checking if others were experiencing the same issue, not a lesson in teaming etiquette.


My LotG sold for 65mil and I'm spending it all on hats

Needlepoint and Hobbytex Champion 1984

Blaming others since 2003

 

Posted

Quote:
Originally Posted by Soliton_Wave View Post
yeah thanks

Was really just checking if others were experiencing the same issue, not a lesson in teaming etiquette.
Which is why I answered your original question as well. It's not like I didn't contribute anything at all to your thread. I answered and even agreed with you... mostly.