Jerky motion of consists in AI mode - TS2009

TS2009:Jerky motion of consists at an unacceptable level in AI mode -> Tracking View. OK in External View and Free Roaming View.
I created a Trial route:- bare base board with a simple single track route, some signals plus cameras and just ONE loco + 3 carriages. No jerkiness as far as I could detect.
On a route with a complex track layout + 10 steam locos the jerkiness is unacceptable. If I reduce to 1 loco the jerkiness is appreciably less - but still unsatisfactory really.
I won't give a historical account but in my ignorance I wonder whether I could have been overloading my PC/Graphics card eg too many locos/complex track layout/too much "scenery"?
For information computer spec is 1000GB Hard disk; 4GB of "fast" (RAM?) memory, AMD Quad core processor.
Graphics Card: NVIDIA Geforce GTX 460: 1024 MB Performance Graphics.
 
this might help. i also have 2009 and run about 14 to 15 consists. just before going to drive i delete missing content found in the upper left menu in surveyor.. most of the time it help. i say most of the time but not always. i also don't do a lot of superdetailing back away from the cameras.
one thing i noticed is as the session go on that the jerkiness seems to increase[ about a hour or so].

e7500 intel dual channel,8 gigs ram,gtx560 1024 ,100gig harddrive.
 
It also helps when the amount of different assets are kept to a minimum in the camera view. Depending on the angle of view, external, I find the stutter is reduced to virtually 0. The greater the angle, above 45deg the better and I have a similar spec computer. Hope this helps.
 
I'm working on your welcome suggestion. "Trainz Veteran" has also suggested that I try to minimize the detail in a camera view. How do I cope with an urban situation (eg a moderately-sized station) in which there is a lot of detail. also what do you mean by "the greater the angle, above 45 deg, the better? thanks for giving me your attention.
 
Hi Northeastern,

I have seen this numerous times in Driver. The cause is usually too much of a good thing such as too many splines or too many trees and buildings. Try thinning out the buildings, particularly those that aren't seen by the you in Driver. The classic frame rate killers are grass and tree splines. Try to find suitable replacements such as clump-grass objects and tree objects instead of splines.

In addition having too much stuff in a scene, sometimes poorly made models can cause this, in particular those older models that lack LOD models (Level of Detail) which increase the detail as you get close to the scene. Without LOD your driver session will stutter and the assets will pop into place suddenly. Lots of splines can be a framerate killer.

What I do is press ALT+Y and get down and walk the route in Surveyor. If there is any jerky motion, I edit the area and remove objects and possibly replace them with suitable replacements. In other cases, I have even replaced whole baseboards and rebuilt the area, usually for the better, and that has resolved the problem.

Hope this helps.

John
 
Wow! Thanks for your quick response - I'll go to work on implementing your suggestions. I assume that I can't do anything about (any) models not having LOD (how would I recognise them?) other than deleting them !
NE
 
Wow! Thanks for your quick response - I'll go to work on implementing your suggestions. I assume that I can't do anything about (any) models not having LOD (how would I recognise them?) other than deleting them !
NE

There's no way of really knowing until you try. A model here and a model there without LOD is fine, but when you get a bunch of them in one spot that's when you have a problem. If the program stutters in Surveyor, it'll surely stutter in Driver.

John
 
Back
Top