Dude you sooooo didn't get it. Why even post? I will spell it out slowly for you. 1. Friend logs in on his computer. Switches instances. NO instance bugs. He unlogs. 2. On same computer, I log into my account. Change instances. Instance bug occurs 100% of the time. I unlog. 3. He logs in, instance switches, no bug. The bug is ACCOUNT RELATED, >>>>>>>>>>>>>>> NOT computer related. My friends computer has absolutely nothing in common with mine. This has nothing to do with the fact you have to restart the game to log in. I am not saying changing accounts makes arrows come back. I AM saying it only happens on MY ACCOUNT!

NEW Information!!! I was at a friends house and he had his game. I logged in to do something with my character and happened to change instances and the bug showed up. All the same issues. So we logged off mine and got onto his account. And NO PROBLEMS. This problem is with the account <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< I wonder if this has something to do with being an F2P account when F2P went live. And now something is left over. The person who doesn't have the problem has a recent account. And another friend who does made one the same week as me. I am going to start an F2P account and see if I get the issue. I will update here when I get a chance. I HOPE HOPE HOPE this puts BW on track to fix this issue.

Update on my experiences as requested by DEVS. I apologize for how long it took me to get back to you. I see that now others are having similar issues in other ways. From my testing I have the following behaviors. 1) What disappears a. The overhead target arrow b. The namelplate c. The vertical circle d. Overhead health bars Also: The ground circle is always present. The type of mob (friendly, enemy, player, NPC, green, yelllow, blue, red) is not a factor. Note:There may be other things....perhaps I haven't noticed them. I have also made no attempt to correlate the arrow problems with the other more common UI problems that are corrected by a UI reset. I am also unsure about game OBJECTS (chests, datacrons.....and such). 2) When it happens: a. Switching instances on a planet/fleet/orbital station. It does not matter if I am in a group or not. It does happen on Fleet. It does happen on the various orbital stations associated with a planet (HOTH, MAKEB, QUESH etc......) Note: Some people have reported that not having anything currently targetted at the moment of the instance switch prevents the issue. My testing shows this to be untrue for me. 3) When it does not happen a. If I have just logged in and I have not targetted anything at all. I haven't tested this for consistency but the 2 or 3 times I did it, things appeared to work. b. When entering an FP/OP phase. c. When doing anything OTHER than an instance switch (leaving a planet, going to a planet.....etc) 4) What corrects the issue a. Going to your ship b. Going to another planet/fleet by any of the available methods (terminal, fleet pass, legecy transport...) c. Entering an FP/OP - I won't swear to the consistency of this....I just have not seen it in an FP/OP d. logging out and back in via a game crash - via alt-tab to windows and kill ( if you just log out normally your out of group so you come back in a wrong instance and your back where you started. Crashing out leaves you in group and brings you back to the groups instance and its fixed.) e. Logging out and back in (i.e. you just quit group and come back into game) f. I am unsure about WZ. I don't PVP much but I believe I had the bug in a WZ once. Just won't swear to it on my mothers grave. 5) What does NOT correct the issue a. Entering a story/mission phase b. Dying (in any way shape or form including jumping off cliffs) c. leaving group (without a crash) d. changing groups e. reseting missons/phases f. CTRL-U, CTRL-U. This fixes the various health bar display issues and such that many have reported. But it DOES NOT fix the target issue. 6) Other interesting behaviors a. Having NAMEPLATES forced on in preferences overrides the bug...for nameplates. If there was an override for the arrow and circle I suspect that would work too (but it makes no game sense to have such) b. On some occasions I can see my target arrow, circle and nameplate on a mob in the instance I am in....but I cannot move it by targetting a different mob. It is like I don't 'OWN' it anymore. c. My friend has a different computer but the same video card....and he has all the behaviors - Radeon video cards. Yes we have current drivers. 7) My opinion There is a large hole in the instance switch. But CTRL-U/CTRL-U fixes many of the issues so that it is not really anything more than a minor annoyance. However, the target arrow problem is not being reset by the CTRL-U/CTRL-U. Rather than find out why the bug happens....go after why the User Interface reset doesn't correct it. Beyond this I can't imagine being able to give more information. Unless you want to install some sort of monitor code on my machine - which I will gladly volunteer for. If you want me to test a specific case I didn't cover, I also volunteer for that. The computer I use has very few programs installed as it is a dedicated gaming computer.

Latest patch did not fix this extremely annoying behavior. But please...fix any armor graphics clipping issues while I wait to be able to team. Team in an M.M.O.

What I expect customer service to do is acknowledge the bug. That is all. It's been a serious bug for a year. They instantly fix minor superficial idiosyncracies in armor graphics...but basic game errors go completely unacknowledged. Its just stupid. Every person who pays for this game has a right to expect that a) the game work properly or b) bugs be identified with a prospective fix date. Then we as consumers can make an informed decision on whether to continue subscribing or not. As for 'bumps' being against the forum rules....too bad. If CS would properly interface with customers and give them SERVICE it wouldn't be required. BW apologists should go to a different forum. This is the one for people who have problems with the game.

What exactly is the ToHit process. For example: Roll Attacker Acc (only). If less than attacker Acc then roll Crit/Def roll. Crit/Def Roll: Stack target Def on top of attacker crit and cap at 100%. If roll is less than crit only, attack is a crit. if above attacker crit but less than defender Def, then attack is avoided. If roll is greater than crit+def then anormal hit is scored. ?

bump to get CS attention.

Thanks. I did not know that. I will try it.

After I switch instances, because I joined a team in another instance, my nameplates and target arrow are gone. Some people do not experience the error if they reject the auto request and change manually. I however get the error either way. It is very hard to team without a targeting arrow. I have had this problem since the first day back on Nov 2012. I have put in a ticket after every patch and it gets closed without comment. I have, deleted the game and reloaded it, repaired the game, updated drivers, .NET, and C++ . After waiting 6 months, I am wondering how much longer I should wait for a fix or even <GASP> acknowledgement. I am not the only one with this error (search ont he forums). I know personally 3 people and on the forum several more. Give me any answer. Here is multiple choice so as to not take up too much of your time. Select one that applies. a) It is a bug but will never be fixed b) It is not a bug and it's your problem c) We have noted your request and have not yet determined if it is your problem or ours - please hold your breath and we will get back to you in the future d) Due to the low number of players with this issue (it is a bug) we will never investigate nor acknowledge this bug in the known issues. Do not hold your breath as you will not get a fix in your lifetime. At least not while you continue to subscribe - after all - if you are willing to continue giving us money - why should we fix the issue? Signed, Ignored by CS

I still have this bug. I put a ticket in every patch and it gets closed and I get no acknowledgement at all. Seriously getting mad about this. It is a royal pain in the ***. They fix bugs that are superficial (my left toe is the wrong color when using <near impossible armor to find that no one uses>) and leave this bug untouched. What the hell.

I help new players out when I can. I figure, if I help new players enjoy the game faster, more will stay with the game and that expands the player base. A small player base seems to be the death bell for an MMO. And I like this MMO. That being said, sometimes veterans are not as nice as they should be IMHO. The Alt-F4 answer to almost any question is annoying. So, from helping people out, you see some patterns. Mostly they fall into 'Didn't read the codex' or 'Doesn't read the map or its tool tips' or 'Just missed it". These are normal. The noob mistake that I think is a problem is - new players come to the fleet for the first time and do not take the advanced class mission just off the elevator. I see this often....a lvl 17 guy in Hammer Station with pitiful DPS or a Jedi on Tyhon who can't beat a lvl 14 boss even though he's lvl 18. I take them back to fleet and point them at the guy. Then I ask them (politely) why they didn't take the mission. And common answers appears to be 1) Carrick station was cool and I wanted to look around, then I couldn't find it. 2) It wasn't a mandatory mission so I didn't take it. 3) How was I supposed to know it was important. The fact that it is not mandatory, implies it is optional.This problem is compounded by the fact that they can leave Carrick station with their ship, moving on with the class missions, without an advanced class. I think we are loosing players to this issue. Bioware should consider making the selection of advanced class - or at least talking to the guy on Carrick station - MANDATORY. Maybe you don't have to make class selection mandatory before leaving Carrick Station but I would consider it as an option. At least put a green triangle over his head and put it in the mission list. This would help everyone....noob and veteran alike.

I fixed my reference to 'live' to be F2P live. Sorry for the confusion. And it's nice to know I'm not alone. SOme of the other behaviors listed I had not noticed but I will try to test them out.

My instance switch has been bugged since F2P live (though now I am a subscriber). After a switch, the name plates and targetiing arrow are gone, never to return. This is especially debilitating because the reason to switch instances is to team. And after a switch I can't tell what my target is in any kind of combat fray. I once got tossed off a team for breaking CC repeatedly because I CANNOT TELL WHAT MY TARGET IS. And NO ...reseting the UI does not fix it. And NO...I am not the only one with this problem. One of my mates has the same issue. I have put in a ticket after each and every patch and they just get closed with no response and apparently no activity. Come on BW. Fix the bloody thing. I am paying for this game and this is not a 'quality of life' issue. I don't do heroics or any kind of teaming whatsoever as i don't want to be a burden to my team mates. I do however notice that cartel market bugs get fixed overnight. I have several characters approaching 50 and I am under the impression that lvl 50 content is not solo friendly. I am reconsidering my subscription at this point. Possibly one more patch then I am out.

I don't want double XP. I know that my opinion will be very unpopular. Can I turn it off please? Basically I will not be playing any of my characters at all during double XP weekends.

Super easy easy method to solving the Traken-4 puzzle. *** SPOILER ALERT***** Don't read down if you don't want to know how to solve this puzzle. You can of course look at the initial state and put it into this puzzle solver and poof out comes the answer. The answer will get you there in one iteration. http://www.ueda.info.waseda.ac.jp/~n-kato/lightsout/index.html But if you don't want to 'cheat' then do this: Look at the current state of the puzzle. You dont need to 'number the poles' but it is easier if you draw a 3x3 grid on a piece of paper and put a dot wherever a pole is OFF. Now go click EVERY off pole that was off when you recorded the state. Ignore whether the poles change state as you click them...just click every off pole that was off when you recorded it. Now you have a new state. Again record every OFF pole. Then click every pole that was off. Repeat as needed. Depending on the initial state, most can be solved in 3-5 iterations - but some are longer, some shorter. If you miss a pole or click the wrong pole it will screw it up. Just again record the state and click every off pole.