Will PvP queue's be fixed?

So my friend was waiting in queue for 40 minutes, gave up, un-queue'd then re-queue'd. He waited 40 minutes again with no pop. He was complaining in TS about it...I got a play-by-play. lol. At that point I decided to PvP, but instead of asking him to un-queue again, I just queued by myself. I thought just maybe it needed more people. 15 minutes later, it popped for me. However he didn't get a pop.

(of course he took his frustration out on me)

How come I got in quicker? This is NOT the first time I got in before him, even if I queued after. And there are times were he will get in before me...

I've googled this issue, and it seems it's old. Will it ever be fixed? It seems odd that it happens in the first place.

Are you in the same grand company?

Quote:

---

Originally Posted by Sunako

Are you in the same grand company?

---

Yeah both in flames.

Is this Wolves Den or Frontlines?
Wolves Den takes your ranking into account to ensure somewhat even teams.

If it was Wolves' Den, your pvp rank will determine how quickly you get into a game, due to the matchmaking system. If it was Seal Rock, make sure he was queued as 'E' language only, as the wrong language can screw your queue up.

I've noticed some trouble when I queue up as one job, immediately switch to another, and then go about my business. I've sat in queue so long I forgot I had even done it (90+ minutes) and then when I switched back to Warrior and exited to re-enter, I got a match in 15 minutes (which is about my average as Maelstrom).

Quote:

---

Originally Posted by Dotsusama

I've noticed some trouble when I queue up as one job, immediately switch to another, and then go about my business. I've sat in queue so long I forgot I had even done it (90+ minutes) and then when I switched back to Warrior and exited to re-enter, I got a match in 15 minutes (which is about my average as Maelstrom).

---

That honestly sounds like you're getting stuck in a dead lobby, then you unqueue, change classes, and coincidentally don't get stuck that time around. Unless you notice reliably getting stuck in queues like that for any particular class, I wouldn't put too much stock into what you seem to notice with it.

In case you don't know, having less-popular PvP languages checked in your language preferences for the DF raises your chance of getting stuck in the dead lobbies of those languages. It's smart to only stick with the main language of your data center, as that can help avoid dead lobby issues.

It was for frontlines. I don't know if he has more than 'E' checked. I'll sneak a look at his search info. Thanks for the replies.

The queue for PvP is different from other instances. Some people consider it as a bug while others say it's working as intended. In any case you will usually get stuck in dead queues; how it occurs it's beyond me.

The "trick" we use in my PvP LS is simple. Re-queue every 10min of waiting since it seems you can get into PvP depending on your assigned instance NOT queued time. Check on the in-progress too and if someone tells you they got into a match then re-queue again hoping to get into the instance assuming someone drops it which occurs quite often.

Pre-mades vs solo ques can cause the DF to have an aneurysm. It depends on the circumstances, but a lot of small and stupid things can cause the system to get mucked up.

I don't know how accurate any of this information is, but, from what I've been hearing around the watering hole, It seems that the way the DF is set up and continually "locking" the same groups together has a lot to do with how spots get filled in Seize. I dunno though, so take this with a grain of salt.

Supposedly, the DF takes the first 24 people from the same GC that qued and puts them together, but, if there is a pre-made in the mix, it can have trouble filling the blanks and can cause a lot of problems, especially if the pre-made is not a complete pre-made. For example, say you have a Pre-made of 7 in que. DF is searching for one person to fill the eighth spot. You guys qued as a pair, and it suddenly has an extra person it can't fit in, so DF gets all gummed up because it doesn't know what to do. You guys break up your pre-made pair of two, and DF slots the first person who qued between the two of you in the free spot. The other person gets the shaft.

In your case, the 15 minute delay was probably because you missed the match. Notice that a seize match is roughly 15-20 minutes (depending on how fast one team is winning, of course)? That's not a coincidence. Basically, the DF tried to find a spot for both of you in the same party, but couldn't. Keep in mind that even if there had been an open space in Alliance A and C, the DF could not split you up to fill both spots. It runs on the PvE set up, so it can't compute that kind of thinking. So, when it tried and failed to slot you both, it gave up and went ahead with the match by filling the spots with solo quers (even if they qued after you). Now, most of us have noticed that, in seize, when we repeatedly que immediately after each match we get slotted with the same familiar faces (which can be good or very bad). That's partly because of the limited number of PvP'ers available at any given time of the day. This same feature (or side-effect of the way DF is forming groups) would mean that you'd have to wait for the match to end before DF could slot you into a spot. Whichever one of you qued first, gets the first free spot. The other person gets left behind until DF can find another group, or someone quits the group you're in.

How likely this is to happen depends on how many people are available to play PvP on your server. If you only have 30 people from your GC trying to que at that particular time of day, than six of them will always be in limbo, waiting for the match to end or a spot opens up. The more people que, the more people have a longer wait to get in. The only time that wait would shorten is if the number of people trying to que from your GC reaches 88. Then the DF can make two full groups instead of one with spare change... only, there's still a problem. The DF still has to match you against opponents. So, if 88 people are qued from Adders and, but Mael and Flames only have 24 each, one full group of Adders get's left in the dust waiting for ques from an entirely different GC.