Duel core amd's and torque
by arteria3d · in General Discussion · 09/22/2006 (4:58 am) · 48 replies
Hi,
Dont know whether anyone else running a duel core machine has noticed this, but when you run a torque level it takes around 2-3 minuted for the level to settle down to a descent FPS.
When i first run torque, the fps is no more than 3, then after a few minutes the fps goes right up to a normal level for my paticular level.
Apparantly doing some research a lot of games are having problems with AMD and also intel duel core machines, but there are fixes.
Has anyone else experienced this?
Steve
www.arteria-gaming.com
Dont know whether anyone else running a duel core machine has noticed this, but when you run a torque level it takes around 2-3 minuted for the level to settle down to a descent FPS.
When i first run torque, the fps is no more than 3, then after a few minutes the fps goes right up to a normal level for my paticular level.
Apparantly doing some research a lot of games are having problems with AMD and also intel duel core machines, but there are fixes.
Has anyone else experienced this?
Steve
www.arteria-gaming.com
About the author
Owner of uk based Ltd company ArteriaMediaLtd. with a trading name of Arteria3d Website;arteria3d.com
#42
I have to agree. I'd say a big part of why I've hardly played BF2 at all since I bought it was due to how much of a pain it was to get it running on my shiny new dual core machine.
Of course immediately after I got it running the news of 2142 was leaked. :)
10/10/2006 (11:09 am)
Quote:
I'd like to work around this though, as compelling users to install something like that is not ideal.
I have to agree. I'd say a big part of why I've hardly played BF2 at all since I bought it was due to how much of a pain it was to get it running on my shiny new dual core machine.
Of course immediately after I got it running the news of 2142 was leaked. :)
#43
Did the patch work for anyone?
10/11/2006 (3:26 pm)
Heh, well 2142 is a trainwreck, so no worries there ;) People might be happier if they just fixed BF2, made some new maps, called it BF3 and sold it for half price.Did the patch work for anyone?
#44
I picked up a few fps by using the optimiser, but then the FPS skyrocket, well.. double at least, when I open up the task manager and set affinity to one core here on my rig.
10/12/2006 (5:28 am)
Brian, it's highly possibly AMD would donate a cpu or two to the Garage for product testing purposes, it's worth asking anyway. I picked up a few fps by using the optimiser, but then the FPS skyrocket, well.. double at least, when I open up the task manager and set affinity to one core here on my rig.
#46
What I was experimenting with, was in the other thread discussing 64bit or dual core issues titled torque too fast, and that was to put this in winwindow.cc - Unfortunately my problem isn't that it runs too fast, but too slow, due to no communication of the timing difference between the threads on the seperate cores .. i think
granted, I don't have alot of experience with c++ and torque but I'm pretty sure that sets the affinity to only one core, ...but it doesnt go into affect right away, theres probably a better place you could stick that so it would go into effect immidiately as a work-around untill an offcial fix for this exists.
10/12/2006 (2:40 pm)
Have an amd dual core and install the dual core optimizer, unless theres another step I'm unaware of.What I was experimenting with, was in the other thread discussing 64bit or dual core issues titled torque too fast, and that was to put this in winwindow.cc - Unfortunately my problem isn't that it runs too fast, but too slow, due to no communication of the timing difference between the threads on the seperate cores .. i think
SetThreadAffinityMask(GetCurrentThread(), 0x01);
granted, I don't have alot of experience with c++ and torque but I'm pretty sure that sets the affinity to only one core, ...but it doesnt go into affect right away, theres probably a better place you could stick that so it would go into effect immidiately as a work-around untill an offcial fix for this exists.
#47
Yes, it does, for the main thread. And given that Torque does pretty much all work on the main thread (except for Theora decoding and DNS resolution), it solves the problem pretty well (although you may perhaps get jerky video playback).
The ideal place to put this is in the main function of your program, or even better, in DllMain. Call Sleep(10) after calling it, too, because I believe the change doesn't happen until the thread gets re-scheduled.
10/12/2006 (3:46 pm)
Quote:I'm pretty sure that sets the affinity to only one core
Yes, it does, for the main thread. And given that Torque does pretty much all work on the main thread (except for Theora decoding and DNS resolution), it solves the problem pretty well (although you may perhaps get jerky video playback).
The ideal place to put this is in the main function of your program, or even better, in DllMain. Call Sleep(10) after calling it, too, because I believe the change doesn't happen until the thread gets re-scheduled.
#48
10/12/2006 (5:10 pm)
The AMD patch seemed to fix the problem on my machine. Again - not an ideal solution. Better to have a work-around within Torque. 
Torque 3D Owner Jay Barnson
Even if they did, 50%+ of users wouldn't have it.