|
|
Post by eegore on Jan 2, 2012 1:12:47 GMT -5
So if you end up with a .0001 FPS on Taris you will need to close all your map tracking.
I think it has something to do with Taris being instanced, (Imps are there but we cant see them)
Shut off all tracking, and all map options in the UI preferences and it runs fine, I dont know why. I tested it by turning tracking back on and sure enough, a framerate drop.
This is for the Bonus quests Republic side when you start reaching the far East of the map. Knight Fall heroic etc.
Just an FYI
|
|
|
|
Post by zarthos on Jan 3, 2012 8:07:40 GMT -5
Yeah you know they had supposedly fixed this memory leak with the first patch but I guess they brought it back with a vengence with the second. Glad to see you found the work around and thanks for posting it, my wife had terrible issues on Taris and was none to happy that I did not  |
|
|
|
Post by Raphael diSanto on Jan 3, 2012 13:11:42 GMT -5
Man, I'm glad I never encountered that.
|
|
|
|
Post by zarthos on Jan 3, 2012 13:16:35 GMT -5
Its a pretty serious mem leak, I have 8 gigs of RAM which is not a ton but I was never effected. My wife has 4 gigs and she would crash dang near immedialty when she entered the Heroic areas. It started the second she picked up the bonus quest line.
|
|
|
|
Post by Sepp on Jan 3, 2012 17:56:56 GMT -5
Yes, the bug is still here. Untracking all the quests you have prevents the bug.
However, if you group with someone, their quests will be tracked (unless you remember to disable that feature) causing the bug to resume. It's a pain.
|
|
