Soldato
- Joined
- 10 Apr 2004
- Posts
- 13,496
oooooo!
Thats just made me want to keep my Conroe rig! ha ha!
Decisions decisions!
Thats just made me want to keep my Conroe rig! ha ha!
Decisions decisions!
Try fraps for recording and showing fps and try rmclock to get a graph of previous as well as present cpu usage across cores
Has FSX improved on the ATC any?
I've just upgraded to a nice quad core @ 3.2, 4gb ram, 8800 etc etc so I might give this another go. I will let you guys know if this makes full use of all the cores, I will be a happy man if it does because I will be able to crank it right up.
You can utilise four cores in SP1 with a little tweak to fsx.cfgIt wont full utilize 4 cores until the next patch iirc, gonna wait till then till i reinstall it.
Phil Taylor's blog said:There is a tweak to control scheduling of threads on cores.
It is not recommended to change these settings unless you have a performance reduction and/or maxed out CPU loads in the PerfMonitor. The tweak is:
[JOBSCHEDULER]
AffinityMask=n
where
n num of cores scheduled
1 = 1 core 0001
3 = 2 cores 0011
7 = 3 cores 0111
15= 4 cores 1111
They look like cirrus clouds which usually indicate instability in the air. Bet the turbulence is fun in the old girl!
Try fraps for recording and showing fps and try rmclock to get a graph of previous as well as present cpu usage across cores
... frame rates alone aren't the only measure of what's going on. Since the threads that are spawned off to core #2 when running as ACES intended is exclusively dedicated to texture fetching, compositing and blitting, none of those operations are going to get "reported" to the frame rate counter...
Don't get so focused on one thing that you become a "frame rate junkie..."
There's a TON of stuff that FSX does in the background that must be done before a single frame gets drawn. The more "processor power" you give to the rendering process (aka: frame rate), the less you give to the "pre-rendering processing" that must be done.
FS is a delicate balancing act, and that is precisely why "tweaking" must be done. No two systems are identical, so there's no "one size fits all" combination of settings that can be applied across the board.
The goal is to find the "sweet spot" on your system that gives just enough time to the rendering process while allowing the compositing process to remain efficient.
Bill Leaming
Gauge Programming - 3d Modeling
Eaglesoft Development Group
Pentium 4 @ 3.0GHz 800MHz FSB/ 2.75GB "Ultra" 800MHz DDR/ ATI X700 Pro PCIe 256MB
NOTE: Unless explicitly stated in the post, everything written by my hand is MY opinion. I do NOT speak for any company, real or imagined...