Agree not persistent. However, setting to only Core1 takes up most of its capabilities. Giving Trainz Core1 & 2 give about 60% in Core1 and 50% in Core2. Since Trainz is GPU bound on my system no use adding it to Core3. Now need to play around to see if it really matters.
i2500K 3.5ghz, 8gb memory, GTX550 1gb W7 64bit
===========================================
I ran the route I am working on - Picatinny by GFisher. Adding lots of new vegetation, hi-res textures, new buildings, etc... Makes it a hi-load route (CPU/GPU).
At certain points in the route I always experience bad stutters, maybe up to 4 in a sequence of about 1 second each. One spot is over a second. Having Trainz use 2 cores (according to Task manager) does not help. At least in my view my the problem (stuttering) is not a function of the CPU.
Having satisfied myself (could be wrong) that the GPU may be the issue I need to mess about there a bit.
Previously I have tried an endless number of program options settings and none eliminated the stuttering/pauses. If I run one of the visually simple desert routes there is no stuttering. I can see why such routes seem to hold some popularity despite being visually boring.
I know that my desire for the best visual appearance places some quite large objects (megabits) into the view of the train. But using the older blurred stuff (texture and assets) is not acceptable to me. However, if the only solution is a $500 video card forget that. I failed to note that I am getting 50FPS (FRAPS) at the time of the stutters. If a stutter turns into a pause I see the FPS drop.
RW3 is turning into a pure game. Trainz has a broad set of capabilities that should allow it to simulate almost any railroad function with a modern level of visual quality. However, if the penalty is stuttering, that can only be cured with money, I see no reason to use the product.