DUST Search - Sticky:[Feedback] One teammate left behind when squad queuing and Cance...

All Channels

Feedback/Requests

Sticky:[Feedback] One teammate left behind when squad queuing and Cance...

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: [1] 2 :: one page

Author	Thread Statistics \| Show CCP posts - 1 post(s)

CCP Rattati C C P C C P Alliance 19657	Posted - 2015.04.03 07:31:00 - [1] - Quote Dear players, explain this to me in detail, I know what happens, but it's good to get the actual perfect time line from you guys. Also, why would, like some have proposed, switching the Circle button for cancel queue help with the issue. Reply ASAP! "As well as stupid, Rattati is incredibly slow and accident-prone, and cannot even swim"

MINA Longstrike Kirjuun Heiian 2451	Posted - 2015.04.03 07:45:00 - [2] - Quote Circle is used to close window... And cancel/back out. If you've already found a match and you go to 'close window' with circle you instead leave queue and either force your squad to manually cancel (because the squadlead can't back the squad out to a 'deploying' match) or to back out once in match. Also I occasionally notice 'Scotty errors' when my squad is thrown at a match that we have just one too many people for. Hnolai ki tuul, ti sei oni a tiu. Kirjuun Heiian. I have a few alts.
xp3ll3d dust The Southern Legion 183	Posted - 2015.04.03 07:50:00 - [3] - Quote sit in merc quaters making a squad put RF3 in shared chat channel people X up, you send invites, or send invites to people that X'd up earlier wait a few minutes, eventually queue up for a match while queuing a mate finally accepts the invite. "Hey mate how you going?" "Going good guys" timer is still going, but new squad member isn't in the timer, and doesn't know that the timer is going squad gets "getting ready for deployment" we get into the match, still chatting. the newly joined member hears the MCC announcements over someone else's comms and goes "hey wait did you guys deploy already?" we all groan and back out CPM1 Candidate > A richer Dust app ecosystem means more player engagement!
xp3ll3d dust The Southern Legion 183	Posted - 2015.04.03 07:52:00 - [4] - Quote MINA Longstrike wrote: If you've already found a match and you go to 'close window' with circle you instead leave queue and either force your squad to manually cancel I honestly didn't know that was a problem. I've gotten so used to just pressing "start" to close the hud after queueing CPM1 Candidate > A richer Dust app ecosystem means more player engagement!
gustavo acosta Capital Acquisitions LLC Bad Intention 1108	Posted - 2015.04.03 07:52:00 - [5] - Quote Cancelling Deployment for the entire squad while waiting for deployment in addition to searching for battle, or squad leader given the ability to kick his squad from battle would be abuse-able and very blunt solutions. Solutions nonetheless Edit: Maybe add the ability for individual squad-mates to re-sync into the queue of their squad-leader, but I'm not sure how feasible that is. GimmeDatSuhWeet isk We found a new pope to teach shield users how to shield tank, all hail pope redblood the 6th
STYLIE77 KILL-EM-QUICK Rise Of Legion. 512	Posted - 2015.04.03 08:53:00 - [6] - Quote While building a squad or adding players from various chat channels (Alliance, corp, pub, pc, ect..) many squad members are in other screens. Fittings, market, leaderboards, mail, ect. Squad members spam O too many times closing windows and backing themselves out of the match maker. Squad leaders do it as well, however some or none of the squad cancels out with them. I have ran squads for hours on end and it happens multiple times a night, to a point now that we often confirm with everyone when we cancel out that no one has deployed. Now you just look at how many squads are ran a day, and you are looking at hundreds of instances that squads are not deploying together simply because the squad leader or members hit the circle button one time too many. http://caughtyouflinching.ytmnd.com/
WeapondigitX V7 The Exemplars 323	Posted - 2015.04.03 11:11:00 - [7] - Quote STYLIE77 wrote: While building a squad or adding players from various chat channels (Alliance, corp, pub, pc, ect..) many squad members are in other screens. Fittings, market, leaderboards, mail, ect. Squad members spam O too many times closing windows and backing themselves out of the match maker. Squad leaders do it as well, however some or none of the squad cancels out with them. I have ran squads for hours on end and it happens multiple times a night, to a point now that we often confirm with everyone when we cancel out that no one has deployed. Now you just look at how many squads are ran a day, and you are looking at hundreds of instances that squads are not deploying together simply because the squad leader or members hit the circle button one time too many. this happens to me
Haerr Negative-Feedback. Negative-Feedback 2694	Posted - 2015.04.03 11:27:00 - [8] - Quote From most menus one is able to back out of that menu with O. Except for the battle finder, where O is cancel deployment. For example if you are sending (or responding) to a mail while the chat window is open or what not and you want to back out of the menus and you happen to have the battle finder beneath there is a risk that you press O one to many time and cancel your deployment. Simply making O back out of the battle finder instead of cancelling deployment would work wonders. If you can also make the squad 're-queue' automatically when someone joins and/or leaves the squad, or if you make it so that anyone that joins the squad is automatically put into the queue with the rest of the squad that would be awesome.
Mad Syringe ReDust Inc. 763	Posted - 2015.04.03 11:43:00 - [9] - Quote Haerr wrote: From most menus one is able to back out of that menu with O. Except for the battle finder, where O is cancel deployment. For example if you are sending (or responding) to a mail while the chat window is open or what not and you want to back out of the menus and you happen to have the battle finder beneath there is a risk that you press O one to many time and cancel your deployment. Simply making O back out of the battle finder instead of cancelling deployment would work wonders. If you can also make the squad 're-queue' automatically when someone joins and/or leaves the squad, or if you make it so that anyone that joins the squad is automatically put into the queue with the rest of the squad that would be awesome. This^ Another (not so elegant fix) would be, to have another window popping up, to confirm cancel by pressing X, that would make sure to avoid unintentional cancellation of queing. I think the cleanest way is to make triangle the backout button when in battle finder... Edit: there are also occasionally left behind squaddies, who don't make it into battel for connection resions (I assume) since they often have this problem several times in a row. But that will probably be more difficult to solve.
Celus Ivara DUST University Ivy League 314	Posted - 2015.04.03 11:45:00 - [10] - Quote What everyone else has said. I'll add that in addition to changing the button from O, a "Your squad is still deploying. Confirm leave battle? YES/NO" pop-up message would be welcome too. Only would be needed if in a squad and not squad leader. 100% we need a tweak in this area; especially with possible new systems punishing squads bailing battle. Worth noting though, that there are legit times when a player wants to remain in MQ while squad deploys. Sometimes RL hits when you're in squad, and it's best to walk away from the controller for 10min safe in MQ, rather than AFKing a battle dragging down your squad and team. EDIT: Hah, jinx @Mad Syringe! ;)

Mad Syringe ReDust Inc. 763	Posted - 2015.04.03 11:49:00 - [11] - Quote Celus Ivara wrote: 100% we need a tweak in this area; especially with possible new systems punishing squads bailing battle. Worth noting though, that there are legit times when a player wants to remain in MQ while squad deploys. Sometimes RL hits when you're in squad, and it's best to walk away from the controller for 10min safe in MQ, rather than AFKing a battle dragging down your squad and team. EDIT: Hah, jinx @Mad Syringe! ;) For future life improvement, if possible, make the left behind squaddie first in the fillup qeue if anybody else is leaving the battle on the side of the squad. This would make it more bearable for the squad to stay in battle, and have a chance that the guy left behind gets dragged in later.
Celus Ivara DUST University Ivy League 314	Posted - 2015.04.03 12:08:00 - [12] - Quote Mad Syringe wrote: Celus Ivara wrote: 100% we need a tweak in this area; especially with possible new systems punishing squads bailing battle. Worth noting though, that there are legit times when a player wants to remain in MQ while squad deploys. Sometimes RL hits when you're in squad, and it's best to walk away from the controller for 10min safe in MQ, rather than AFKing a battle dragging down your squad and team. EDIT: Hah, jinx @Mad Syringe! ;) For future life improvement, if possible, make the left behind squaddie first in the fillup qeue if anybody else is leaving the battle on the side of the squad. This would make it more bearable for the squad to stay in battle, and have a chance that the guy left behind gets dragged in later. Agreed. Plus, if we could make that part of a larger "Attempt to join friend's battle?" system, that feature would likely get a lot of love/use by the playerbase! (EDIT: ...though it could muddy-up Team Balancing. )
Adipem Nothi Nos Nothi 8510	Posted - 2015.04.03 13:54:00 - [13] - Quote Haerr wrote: From most menus one is able to back out of that menu with O. Except for the battle finder, where O is cancel deployment. For example if you are sending (or responding) to a mail while the chat window is open or what not and you want to back out of the menus and you happen to have the battle finder beneath there is a risk that you press O one to many time and cancel your deployment. Simply making O back out of the battle finder instead of cancelling deployment would work wonders. If you can also make the squad 're-queue' automatically when someone joins and/or leaves the squad, or if you make it so that anyone that joins the squad is automatically put into the queue with the rest of the squad that would be awesome. ^ Shoot scout with yes. - Ripley Riley
Blade Vulu Crux Special Tasks Group Gallente Federation 6	Posted - 2015.04.03 15:38:00 - [14] - Quote In regarding one squad member being left behind I seen this issue caused by two reasons. The first, has been address already, is the regards to people pressing o "circle" to cancel out of other windows. I admit I myself have been guilty of this. My usual response to this is to tell my teammates to go without me and I will just work on my fitting or skill planning. This error of mine has been due to several reasons though most have been just purely forgetful accident other by rushing from one window to the other. - In the solutions provide by the other players in this thread. I believe it can be a possible solution. Though I must admit an additional pop up window could possibly be difficult in general for programming (but it might be a necessity). - The re-sync idea is an awesome idea (hopefully is something that can possibly implemented) though I could see the one programming issue is the player cap (by that I mean max players in the battle or per team). - My proposal for a solution is to change the cancel deployment of tapping "o" (circle) to holding down "o" (circle for 10 seconds). This way to avoid extra programming by the yes and no window/ alternate button & as dust creators you can keep the cancel button the same. (now granted I don't know if this technically easier for a programmer or not. so if it is not, I apologize in advance ). The second time I see this issue is when the squad receives a new player while they are deploying or has already started the search for battle. The timeline for this is at follows: Version A 1. squad with four members are seeking battle. 2. A fifth (5th) member joins while the squad is already searching. 3. the rest of squad gets the deployment notification while the fifth (and 6th if another joined) does not get the same notification. 4. The fifth (5th) and if applicable the (6th) members get left behind. Version B 1. Squad with "x" amount of open spots is open. 2. squad has been searching for battle and has gotten notification of being deployed soon. 3. Someone joins (whether from invite, alliance, corp, or public) the squad at that time. 4. Those with the squad when they first were searching for battle gets deployed. Any the join after the initial search for battle gets left behind. Solutions to this issue: The current solution that squads and myself use (which is just make shift) is that if we have people join during the search for battle; squad leads cancel the search and set up a new search. The system seems to then recognize that someone has join and puts them back together with the squad for deployment . Admittedly sometime if not fast enough we get the groans that someone got left behind. Proposal: I will guess is to look into the system where it seems not to recognize that someone has join squad after requesting to search for battle. Maybe a way to have scotty take a few seconds to recheck the squad numbers before setting out to deploy. Again thank you for you concern and checking this out. Hopefully this might give insight and possible ideas to fix.
Ares 514 D.A.R.K L.E.G.I.O.N D.E.F.I.A.N.C.E 1422	Posted - 2015.04.03 18:05:00 - [15] - Quote Haerr wrote: From most menus one is able to back out of that menu with O. Except for the battle finder, where O is cancel deployment. For example if you are sending (or responding) to a mail while the chat window is open or what not and you want to back out of the menus and you happen to have the battle finder beneath there is a risk that you press O one to many time and cancel your deployment. Simply making O back out of the battle finder instead of cancelling deployment would work wonders. If you can also make the squad 're-queue' automatically when someone joins and/or leaves the squad, or if you make it so that anyone that joins the squad is automatically put into the queue with the rest of the squad that would be awesome. Exactly. These changes would be a big quality of life improvement for everyone. Overlord of Broman
Regis Blackbird DUST University Ivy League 705	Posted - 2015.04.03 20:01:00 - [16] - Quote Haerr wrote: From most menus one is able to back out of that menu with O. Except for the battle finder, where O is cancel deployment. For example if you are sending (or responding) to a mail while the chat window is open or what not and you want to back out of the menus and you happen to have the battle finder beneath there is a risk that you press O one to many time and cancel your deployment. Simply making O back out of the battle finder instead of cancelling deployment would work wonders. If you can also make the squad 're-queue' automatically when someone joins and/or leaves the squad, or if you make it so that anyone that joins the squad is automatically put into the queue with the rest of the squad that would be awesome. ^ This
shaman oga Dead Man's Game 4293	Posted - 2015.04.03 22:42:00 - [17] - Quote It happens when: Someone receive Scotty message (some kind of internal error with some deployed and some other not). Someone join squad when you are already searching for a battle (maybe w/o mic, need to restart search). People checking PC battles time while not being squad leader and press O to change tab. Squad leader accidentaly tap O when waiting for deployment while rest of the squad enter he does not. Disconnection and other various errors depending from game/internet/psn Caused by human nature (when a friend write LFS a moment after you deploy) That is almost all i think. Pimp my Barge
abdullah muzaffar G0DS AM0NG MEN General Tso's Alliance 530	Posted - 2015.04.04 05:49:00 - [18] - Quote There is alao a chance of a player getting scottied when squad queues. He does not do anything wrong on his end, but is instead greeted by a black screen after waiting for deployment, and after a few seconds/minutes is greeted by the mesaage 'You have been returned to your merc quarters, the battle you were fighting is no longer available.' Happens frequently for me with certain mercs. IJR took my soul. RIP 20/3/15 5:14
Regis Blackbird DUST University Ivy League 706	Posted - 2015.04.04 08:11:00 - [19] - Quote What if: The battle finder automatically cancel any search / queue whenever a squad changes (adding / loosing players). It's quite logical really, since the total Mu score for the squad will change, and I guess a new search is needed to take this into account. This will eliminate / reduce the scenario where a fresh squad member is left out if he joined while searching.
Luther Mandrix WASTELAND JUNK REMOVAL 474	Posted - 2015.04.04 12:17:00 - [20] - Quote The second time I see this issue is when the squad receives a new player while they are deploying or has already started the search for battle. One solution could be this. Automatic squad Lock when the Squad leader hits deploy. Invited players not in squad can not get in squad may help this problem.

Luther Mandrix WASTELAND JUNK REMOVAL 475	Posted - 2015.04.04 12:25:00 - [21] - Quote Someone receive Scotty message (some kind of internal error with some deployed and some other not). My question to devs is Why does Scotty give us this message in the first place.If we knew that maybe we could do something different. 1.Every 10 games shut down ps3 so the memory cache empty's. 2.Every 5 games reform squad (Is there a information trail 3 USA Player,2 UK,1 Eastern Europe using up resources that could be emptied if squad just reformed from scratch)
Nothing Certain Bioshock Rejects 1617	Posted - 2015.04.05 16:40:00 - [22] - Quote It happens to me because while waiting to find a match I play with my fittings or skills or something else. Then I close the screen and accidentally hit O one time too many. Because, that's why.
LOOKMOM NOHANDS 456	Posted - 2015.04.05 19:07:00 - [23] - Quote CCP Rattati wrote: Dear players, explain this to me in detail, I know what happens, but it's good to get the actual perfect time line from you guys. Also, why would, like some have proposed, switching the Circle button for cancel queue help with the issue. Reply ASAP! Example 1 Someone goes to check something in the market and sees waiting for deployment pop up in the corner. Knowing this means he will not have time he just hits circle a bunch of times to close it out but finds out that his mercenary is standing in front of the battle finder stand meaning he has now canceled the match. Example 2 Squad is searching, you start deploying and all of a sudden you hear "I got Scotty". This one is actually fairly common, it is weird the cases that it happens in. Example 3 Squad lead sends an invite to a player from corp chat and goes ahead and hits search. The squad soon learns that the player who was invited did not join until after search was hit meaning he will not be coming along for that battle. Example 4 PSN gives its lovely DNS error that is less common but still exists. Example 5 Black Screen. This just does not need an explanation even tho it is FAR less common it still happens. I think that pretty much covers the possibilities but I could be missing some.
Lady MDK Kameira Lodge Amarr Empire 347	Posted - 2015.04.06 07:44:00 - [24] - Quote The only time this has happened to me in squad was me being ham fisted and pressing O accidently while holding the controller. If I'm in a squad shouldn't the squad leader be the only one who can cancel deployment? Rather than switching buttons about and bringing inconsistancy to which button does what? Anyone getting annoyed by reading of the above post should consider the following. I don't care so neither should you :)
Fox Gaden Immortal Guides Learning Alliance 6163	Posted - 2015.04.07 15:01:00 - [25] - Quote xp3ll3d dust wrote: sit in merc quaters making a squad put RF3 in shared chat channel people X up, you send invites, or send invites to people that X'd up earlier wait a few minutes, eventually queue up for a match while queuing a mate finally accepts the invite. "Hey mate how you going?" "Going good guys" timer is still going, but new squad member isn't in the timer, and doesn't know that the timer is going squad gets "getting ready for deployment" we get into the match, still chatting. the newly joined member hears the MCC announcements over someone else's comms and goes "hey wait did you guys deploy already?" we all groan and back out Then add to this a few squad members who are not on Coms, and don't get the message to back out. Then even if you kick the people who did not leave match, your squad is still glitched so everyone has to leave squad and then form a new squad before you can Que again. Hand/Eye coordination cannot be taught. For everything else there is the Learning Coalition.
Fox Gaden Immortal Guides Learning Alliance 6163	Posted - 2015.04.07 15:04:00 - [26] - Quote gustavo acosta wrote: Cancelling Deployment for the entire squad while waiting for deployment in addition to searching for battle, or squad leader given the ability to kick his squad from battle would be abuse-able and very blunt solutions. Solutions nonetheless Edit: Maybe add the ability for individual squad-mates to re-sync into the queue of their squad-leader, but I'm not sure how feasible that is. If there was a way to put squad members who are not in battle on a waiting list to be added to the same match if a space becomes available, that might help. If we had that, maybe make it possible to join deployed Corp/Alliance squads in the Squad Finder. Hand/Eye coordination cannot be taught. For everything else there is the Learning Coalition.
Kaeru Nayiri Ready to Play 917	Posted - 2015.04.07 21:37:00 - [27] - Quote Fox Gaden wrote: gustavo acosta wrote: Cancelling Deployment for the entire squad while waiting for deployment in addition to searching for battle, or squad leader given the ability to kick his squad from battle would be abuse-able and very blunt solutions. Solutions nonetheless Edit: Maybe add the ability for individual squad-mates to re-sync into the queue of their squad-leader, but I'm not sure how feasible that is. If there was a way to put squad members who are not in battle on a waiting list to be added to the same match if a space becomes available, that might help. If we had that, maybe make it possible to join deployed Corp/Alliance squads in the Squad Finder. Would love this. +1 Know what cannot be known.
Vyuru Algintal Core Gallente Federation 100	Posted - 2015.04.08 01:02:00 - [28] - Quote There are certain screens that prevent you from deploying, or cannot be accessed once deployed. The one that comes to mind is the Aurum purchasing screen. If you are in this screen, waiting for a match, it will prevent you from being deployed with the rest of your squad. Or if you are running solo waiting to be deployed, you won't be deployed until you leave the screen. ~Vyu
Dreis ShadowWeaver Negative-Feedback. Negative-Feedback 2624	Posted - 2015.04.08 21:54:00 - [29] - Quote MINA Longstrike wrote: Circle is used to close window... And cancel/back out. If you've already found a match and you go to 'close window' with circle you instead leave queue and either force your squad to manually cancel (because the squadlead can't back the squad out to a 'deploying' match) or to back out once in match. I can't believe people forget to not press circle whilst they're deploying... If you absolutely must close the window (), open your Neocom, open something like your Skills, and then just close that window. Creator of the 'Nova Knifers United' channel Caldari blood, Minmatar heart <3 I'm a monster
THUNDERGROOVE Fatal Absolution Negative-Feedback 1704	Posted - 2015.04.12 19:55:00 - [30] - Quote Seriously. Just remove the ability for anyone but the SL to cancel. If the SL cancels bump everyone out of match when they load in. Easy peasy problem solved Mace yourself, blame someone else itGÇÖs okay, no one will believe you AIV member.



Pages: [1] 2 :: one page
First page \| Previous page \| Next page \| Last page

COPYRIGHT NOTICE
EVE Online/DUST514, the EVE/DUST514 logo, EVE/DUST514 and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to OMG Labs to use EVE Online/DUST514 and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, OMG Labs. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.

GimmeDatSuhWeet isk