Garr3tt on 28/4/2008 at 19:44
first of all srry bout the new thread and all...
but i just fount a simpler fix to the whole dual core issue. so admins feel free to add this to the closed tweek guide. k so it goes as follows:
u set the affinity of "exploer.exe" to cpu0
and all "child" applications thus our "t3.exe" and "t3main.exe" will have their affinity set to cpu0 from the start.
I added this only because, and this might be worth saying also in the tweek guide, as i started the game on two cores it ate up 50% of my cpu usage and frose for a time. with this simple non intrusive fix u can avoid all probls caused by dualcores.
PS: to undo this simply check cpu0 and cpu1 on the afinity of explorer.exe
bikerdude on 29/4/2008 at 08:44
Hi
if you still have issue Pm and I`ll send you my patched t3.exe
biker
Garr3tt on 29/4/2008 at 17:47
i was actualy offering a less intrussive alternative to patching as it dosent always work but eh well if u prefer patching .... :erg:
Dario on 5/5/2008 at 14:28
Thanks for the tip :) ...but wouldn't setting Explorer.exe to single-core pretty much disable most (or all) apps from using the second core? (and thus render half your CPU useless)