Vaerah Posted May 30, 2013 Share Posted May 30, 2013 As this screenshots shows, I am level 55 but the client believes I am below level 10, therefore the WZ queue button stays dimmed and even says I need to be level 10 blah blah. Link to comment Share on other sites More sharing options...
Dev Post AmberGreen Posted May 30, 2013 Dev Post Share Posted May 30, 2013 (edited) Hi there, We are investigating other reports of this nature as well. When you refresh the UI using CTRL+U twice, does it resolve itself for you? Can you provide any additional details? Thanks for the report and for your patience while we look into this! Edited May 30, 2013 by AmberGreen Link to comment Share on other sites More sharing options...
Thufir_Hawat Posted May 30, 2013 Share Posted May 30, 2013 Had the same Ctrl-U twice fixed it Link to comment Share on other sites More sharing options...
Famrir Posted May 30, 2013 Share Posted May 30, 2013 had the same problem, a quick relogg solved it Link to comment Share on other sites More sharing options...
Scorpassailant Posted May 30, 2013 Share Posted May 30, 2013 Had the same problem earlier, resetting UI worked. I was a bit worried for a second there lol Link to comment Share on other sites More sharing options...
Givemedanger Posted May 30, 2013 Share Posted May 30, 2013 Same here. Same bug. Ctrl+U resolves the problem for me. Still it needs to get fixed. Link to comment Share on other sites More sharing options...
Glower Posted May 30, 2013 Share Posted May 30, 2013 Hi there, We are investigating other reports of this nature as well. When you refresh the UI using CTRL+U twice, does it resolve itself for you? Can you provide any additional details? Thanks for the report and for your patience while we look into this! Hit CTRL+U for warzone queue (one time per character) Hit CTRL+U for OPS chat inside warzone (sometimes!) Hit CTRL+U for GROUP chat after warzone (very often) I think "That Escalated Quickly" meme is already here. Please fix all these mini-bugs at once! Link to comment Share on other sites More sharing options...
Joesixxpack Posted June 1, 2013 Share Posted June 1, 2013 (edited) Had this issue yesterday. UI reset didn't fix. Relog + file fix utility thing did. Edited June 1, 2013 by Joesixxpack Link to comment Share on other sites More sharing options...
Pistols Posted June 3, 2013 Share Posted June 3, 2013 Hi there, We are investigating other reports of this nature as well. When you refresh the UI using CTRL+U twice, does it resolve itself for you? Can you provide any additional details? Thanks for the report and for your patience while we look into this! Yes, resetting the UI indeed fixes the issue, but only temporarily. I've fixed it while on my ship, but zoned onto the Fleet and had broke again. Also, when switching characters, the problem can come about. Can you respond with any information in regards to your investigations? Link to comment Share on other sites More sharing options...
Kattla Posted June 4, 2013 Share Posted June 4, 2013 I have this bug all the time when i play on the progenitor. But getting fed up with having to ctrl-u before every time i want to queue, i switched to my toon on the red eclipse server, and there everything worked as it should. Going back to the progenitor, and the problem is there again. Link to comment Share on other sites More sharing options...
Pistols Posted June 4, 2013 Share Posted June 4, 2013 Hi there, We are investigating other reports of this nature as well. When you refresh the UI using CTRL+U twice, does it resolve itself for you? Can you provide any additional details? Thanks for the report and for your patience while we look into this! Any news Amber...details were provided... Link to comment Share on other sites More sharing options...
Joesixxpack Posted June 4, 2013 Share Posted June 4, 2013 Had this issue yesterday. UI reset didn't fix. Relog + file fix utility thing did. Now fixing it with Ctrl U + U. Still happening whenever I log a character in. Link to comment Share on other sites More sharing options...
Exly Posted June 12, 2013 Share Posted June 12, 2013 I was disappointed to see that there was no fix for this in update 2.2. Do you even plan on fixing it? If so, when? Link to comment Share on other sites More sharing options...
Recommended Posts