Issues with frequent "pausing" in 2009, 2010, and 12 (latest builds on all three), sometimes lasting longer than the usual 3-5 seconds, which usually leads to total lock.
System specs;
Operating System: Windows XP Media Edition (5.1, Build 2600) Service Pack 3
Model: Dell DXP051
CPU: Intel(R) Pentium(R) D CPU 3.40GHz (2 CPUs)
Memory: 2GB Crucial Ballistix
Video: NVIDIA GeForce GT430 1GB
Sound: SB Audigy
Hard Drives:
C:Western Digital WD5000AAKX-001CA0 462.0 GB 7200rpm
F:SanDisk SDSSDH120GG25 114.5 GB solid state drive
Trying out a new utility recommended by JCitron from http://technet.microsoft.com/en-us/sysinternals/bb896653
That's what I got running at startup, no fluff allowed. Fire up Trainz in windowed mode, select a route and session, drive;
That's the usual, 60-80 percent CPU usage for trainz.exe. Switch to #4 view and roam around is usually the quickest way to trigger the pause in driver;
And that's what I get, trainz.exe drops to 0% CPU, TADDaemon jumps up to 50% CPU, after a few seconds TADDaemon drops back to 0% and trainz.exe starts running again. Happens a lot more frequently in surveyor, even on brand new routes with little to no detail.
System specs;
Operating System: Windows XP Media Edition (5.1, Build 2600) Service Pack 3
Model: Dell DXP051
CPU: Intel(R) Pentium(R) D CPU 3.40GHz (2 CPUs)
Memory: 2GB Crucial Ballistix
Video: NVIDIA GeForce GT430 1GB
Sound: SB Audigy
Hard Drives:
C:Western Digital WD5000AAKX-001CA0 462.0 GB 7200rpm
F:SanDisk SDSSDH120GG25 114.5 GB solid state drive
Trying out a new utility recommended by JCitron from http://technet.microsoft.com/en-us/sysinternals/bb896653

That's what I got running at startup, no fluff allowed. Fire up Trainz in windowed mode, select a route and session, drive;

That's the usual, 60-80 percent CPU usage for trainz.exe. Switch to #4 view and roam around is usually the quickest way to trigger the pause in driver;

And that's what I get, trainz.exe drops to 0% CPU, TADDaemon jumps up to 50% CPU, after a few seconds TADDaemon drops back to 0% and trainz.exe starts running again. Happens a lot more frequently in surveyor, even on brand new routes with little to no detail.