I was wondering what settings/values can be changed in the various files to control the behavior of AI/traffic services?
I have found that in the consist files you can change the MaxVelocity( x y) statement with good effect.
The first figure, x, is the max speed (in m/s)
The second figure, y, is the accelaration rate (probably in m/s/s, but I've not checked this out). Values of 0.1 and less gives a very slow accelaration, 0.2 to 0.4 seems more normal, 10 and the consist rapidly goes fast!
The Activity Editor does seem to set values for these figures based on the rolling stock in the consist, but for me these values always seem too high. I have also found that changing a consists values after 'compute and save'ing an activity will result in some funny effects (overshooting of platforms etc) so the activity needs to be re 'compute and save'd.
Any other tips?
Controlling AI/traffic behavior
Moderator: Moderators
-
scefhwil
- Well Established Forum Member
- Posts: 907
- Joined: Tue Dec 04, 2001 12:00 am
- Location: Bristol, England
"...you set the default running speed...". I know you can set a start and end speed but where do you do this John?JohnEyres wrote:I often find that once you set the default running speed for a particular service, you will find that you can't change it again. To change it you have to open up the service in wordpad and change the values. Same with start speed too.
- Neptune50006
- Very Active Forum Member
- Posts: 2149
- Joined: Wed Dec 12, 2001 12:00 am
- Location: That place with all the roundabouts!
I thought that the default performance box was to set how strict the timetable was???
Gary.
"Perchance it is not dead but sleepeth."
http://www.lynton-rail.co.uk
Check out the (slow) progress of the L&B for RW here
"Perchance it is not dead but sleepeth."
http://www.lynton-rail.co.uk
Check out the (slow) progress of the L&B for RW here
I did some investigation of the second parameter of the consist MaxVelocity statement. It does indeed appear to be a acceleration value (in metres/sec). The formula used seems to be:
(MaxContinuousForce - friction)/mass
If an engine does not have a MaxContinuousForce value then the MaxForce is used instead.
"friction" seems to be some sort of average value, using the friction at half the maximum speed gives about the correct value.
(MaxContinuousForce - friction)/mass
If an engine does not have a MaxContinuousForce value then the MaxForce is used instead.
"friction" seems to be some sort of average value, using the friction at half the maximum speed gives about the correct value.