JediMB Posted January 26, 2013 Share Posted January 26, 2013 I haven't had the chance to notice, but this is great news. I know the patch notes visible to us probably just contain the "most important" updates to make it easier for players to see the changes they're interested in, but it would be nice if there was also a link to 100% complete patch notes that detail every single bug fix. Link to comment Share on other sites More sharing options...
Beslley Posted January 26, 2013 Share Posted January 26, 2013 Did you not notice that your Force-using companions now actually turn their lightsabers off properly when you summon them or dismount? I'm sorry but I was elated. I guess I'm just easy to please. I'm extremely pleased. However, I am NOT pleased that my cartel weapons (lightsaber on my sorc, rifle on my operative, and gun on my trooper) are STILL bugging out. Link to comment Share on other sites More sharing options...
BIG_M Posted January 26, 2013 Share Posted January 26, 2013 and next patch it'll be back again. Link to comment Share on other sites More sharing options...
Kayin Posted January 26, 2013 Share Posted January 26, 2013 Oh my Jaesa stopped impaling herself. Im happy now Link to comment Share on other sites More sharing options...
XeniteKT Posted January 26, 2013 Share Posted January 26, 2013 You have not heard anything because the vocal majority only likes to complain. I have not been in game yet but this is great news. Perhaps they wouldn't complain so much if it didn't take months to fix one small bug. Link to comment Share on other sites More sharing options...
schnopsnosn Posted January 26, 2013 Share Posted January 26, 2013 But now we're back to Tebow'ing(kinda) after logging in when we had a pet summoned Link to comment Share on other sites More sharing options...
Oggthebase Posted January 26, 2013 Share Posted January 26, 2013 Perhaps they wouldn't complain so much if it didn't take months to fix one small bug. I completely agree... And the worst thing is that EAware get people to thank them for fixing something that should not have been broken in the first place. It's like selling someone a car with a broken window, the buyer keeps asking for the car dealer to fix it and after three months the car dealer finally fixes the window and the buyer thanks the car dealer! While it was the car dealer who should apologize for the window being broken in the first place... This just encourages the devs to continue producing crap code and fixing it 'afterward' so that people can thank them for producing crap code... Link to comment Share on other sites More sharing options...
Knockerz Posted January 26, 2013 Share Posted January 26, 2013 (edited) I completely agree... And the worst thing is that EAware get people to thank them for fixing something that should not have been broken in the first place. It's like selling someone a car with a broken window, the buyer keeps asking for the car dealer to fix it and after three months the car dealer finally fixes the window and the buyer thanks the car dealer! While it was the car dealer who should apologize for the window being broken in the first place... This just encourages the devs to continue producing crap code and fixing it 'afterward' so that people can thank them for producing crap code... Software!=car dealer. Every one produces crap code now days. Whether it be code that isn't very efficient or code that doesn't work as intended. This is especially true in the gaming industry now. There is always some thing that goes wrong. You want perfect good code go look at military and industry code for expensive hardware. Although judging by the use F-22 and F-35 even these multibillion dollar projects have bugs and now you expect a game to be code free? Dude if you did any real coding you wouldn't be saying that. How can you say it's a small bug when you haven't even looked at the code? Just because it seems simply doesn't mean it's simple. There is reason wow some times just leaves bugs in game too due it's adverse affect changing code to fix a bug can cause a bug to arise some where else. Although the lightsaber bug needed to be fix, but if it were an npc, mob, or some thing not important or that has almost no effect on the player base it's best to just leave the bug in than try to fix it. Edited January 26, 2013 by Knockerz Link to comment Share on other sites More sharing options...
VassagoOmega Posted January 26, 2013 Share Posted January 26, 2013 Yay! 1 down, 3948760-98345709873475 more to go!! Link to comment Share on other sites More sharing options...
uramu Posted January 26, 2013 Share Posted January 26, 2013 Ah cool. I didn't notice because I'm too bust staring at my double-bladed light saber with only one functional side. Link to comment Share on other sites More sharing options...
Oggthebase Posted January 28, 2013 Share Posted January 28, 2013 Software!=car dealer. Every one produces crap code now days. Whether it be code that isn't very efficient or code that doesn't work as intended. This is especially true in the gaming industry now. There is always some thing that goes wrong. You want perfect good code go look at military and industry code for expensive hardware. Although judging by the use F-22 and F-35 even these multibillion dollar projects have bugs and now you expect a game to be code free? Dude if you did any real coding you wouldn't be saying that. How can you say it's a small bug when you haven't even looked at the code? Just because it seems simply doesn't mean it's simple. There is reason wow some times just leaves bugs in game too due it's adverse affect changing code to fix a bug can cause a bug to arise some where else. Although the lightsaber bug needed to be fix, but if it were an npc, mob, or some thing not important or that has almost no effect on the player base it's best to just leave the bug in than try to fix it. maybe you should read what I wrote before replying? I was not commenting on the size of the bug or whether it was easy to fix. I was commenting on people thanking EAware for fixing something that should not have been broken in the first place. (and before trying to give someone a lesson in coding maybe you should learn who the person is in the first place?) Link to comment Share on other sites More sharing options...
SweKaiser Posted January 28, 2013 Share Posted January 28, 2013 I also noticed...odd it was not in the patch notes. They dont put fixes in the patchnotes anymore, only crap on the CS goes into patchnotes these days as its more important to them. Link to comment Share on other sites More sharing options...
EATtheDEAD Posted January 28, 2013 Share Posted January 28, 2013 well i am a happy camper!! no longer will my sexy jedi ladies stab themselves in the face! YES!!! Link to comment Share on other sites More sharing options...
Jawstheshark Posted January 30, 2013 Share Posted January 30, 2013 Yeah but now half the time when the game thinks my sabers are put away they are still in my hands and therefore renders them up and down like I am jogging when I **** and stabbing myself in the face.. Double tap on Z fixes it, but yeah... not really fixed. Link to comment Share on other sites More sharing options...
Khosann Posted January 30, 2013 Share Posted January 30, 2013 I am sorry but this bug is NOT fixed. When you dismiss your companion, the lightsaber glow sticks to the last position of your companion. If you kill an enemy and your companion retreats to the default player character follow position same thing happens. Confirmed for Kira. If Kira turns off her double lightsaber the downward blade glow remains. When Kira is summoned when you dismount your speeder she comes with her lightsaber drawn but not as a double blade lightsaber but as a single blade lightsaber. Same thing since the initial release. Why they could not fix this? Not enough QA guys or something? Link to comment Share on other sites More sharing options...
Toweleeeie Posted January 30, 2013 Share Posted January 30, 2013 I am sorry but this bug is NOT fixed. When you dismiss your companion, the lightsaber glow sticks to the last position of your companion. If you kill an enemy and your companion retreats to the default player character follow position same thing happens. Confirmed for Kira. If Kira turns off her double lightsaber the downward blade glow remains. When Kira is summoned when you dismount your speeder she comes with her lightsaber drawn but not as a double blade lightsaber but as a single blade lightsaber. Same thing since the initial release. Why they could not fix this? Not enough QA guys or something? This is fixed for me. Ill confirm when i get off work in 3 hours Link to comment Share on other sites More sharing options...
Khosann Posted January 30, 2013 Share Posted January 30, 2013 I have an NVIDIA GTX 580 card. Nothing fixed for me. Not even taxi flickering on Nar Shaddaa or Corruscant. Link to comment Share on other sites More sharing options...
Toweleeeie Posted January 30, 2013 Share Posted January 30, 2013 Yep fixed for me, even on Kira. Link to comment Share on other sites More sharing options...
Khosann Posted January 31, 2013 Share Posted January 31, 2013 Strange... Lihgtsaber bug now it is fixed for me too. Maybe this issue is only related to Nar Shaddaa and Coruscant. Maybe otper planets/areas are not affected. But Taxi flickering on Nar Shaddaa and Coruscant persists. Whatever. Link to comment Share on other sites More sharing options...
Recommended Posts