April 16, 200520 yr Just looked over at ati.com to see that the catalyst 5.4 patch is out and there is fix for KOTOR: Star Wars Knights of the Old Republic: Loading the Dantooine level of the game under Windows XP no longer results in slow game performance It's a shame it fixes dantooine on KOTOR when i'm sure most of us would like to be able to play dantooine on KOTORII.. I suppose it gives me something to play until thats fixed though
April 17, 200520 yr Just looked over at ati.com to see that the catalyst 5.4 patch is out and there is fix for KOTOR: Star Wars Knights of the Old Republic: Loading the Dantooine level of the game under Windows XP no longer results in slow game performance It doesn't on loading initally but it returns if you quicksave at certain parts of Dantooine. Good news is you can bypass the problem totally by enabling Disable Vertex Shader Objects.
April 17, 200520 yr Author I fixed it by placing the openGL dll from catalyst 4.7 into the KOTORII directory and that fixed it immediatly which suggests to me that the problem is something to do with ATI drivers. Hence why it's a shame that they still haven't fixed it!
April 17, 200520 yr I fixed it by placing the openGL dll from catalyst 4.7 into the KOTORII directory and that fixed it immediatly which suggests to me that the problem is something to do with ATI drivers. Hence why it's a shame that they still haven't fixed it! <{POST_SNAPBACK}> Yes, the poor frame rate on Dantooine without enabling Disable Vertex Shader Objects seems to only have started from 4.12 onwards. So it should be within the ability of ATI to fix it but they somehow cannot or will not. I guess it's not really an issue as long as you know the workaround. Take note that several Catalysts before 4.11, which might include 4.7, suffer from crashes to desktop after repeated area transitions.
April 17, 200520 yr That fix is for KotOR, not KotOR2:TSL. Unless it's a misprint by ATI, but the fact that KotOR2 still has the problem, it's likely a KotOR issue (they got the other KotOR2 fixes listed correctly).
April 17, 200520 yr That fix is for KotOR, not KotOR2:TSL. Unless it's a misprint by ATI, but the fact that KotOR2 still has the problem, it's likely a KotOR issue (they got the other KotOR2 fixes listed correctly). <{POST_SNAPBACK}> I haven't tested the original but from what I read in the Bioware KotOR forum, it isn't fixed either. http://swforums.bioware.com/
Create an account or sign in to comment