[R H Steele]

Got several of these warnings in the SAL Fla Div Route in the log (not a show stopper, just learning how to clear warnings from the log)

"Warning: Cannot parse the constant number 1.5 in c:\2ts\csx\routes\salfladiv\shapes\ci_flasher_dual.s:line 4682"

going to line 4682 we find:

animations ( 1
animation ( 2 1.5 >>>>>>>>>>>>>> line 4682 ...................... Should the 1.5 be changed to 1? Is that all this is...just an errant .5 got in there? (what's the consequence of leaving the error as is....I really don't want to do that) Some other animation entries are animation ( 2 30 .... so should the 1.5 be changed to 15?
anim_nodes ( 5
anim_node MAIN (
controllers ( 0
)
)
anim_node Disk.1 (
controllers ( 1
linear_pos ( 3
linear_key ( 0 0 0 0.03048 )
linear_key ( 1 0 0 -0.03048 )
linear_key ( 2 0 0 0.03048 )
)
)
)
anim_node Disk (
controllers ( 1
linear_pos ( 3
linear_key ( 0 0 0 -0.03048 )
linear_key ( 1 0 0 0.03048 )
linear_key ( 2 0 0 -0.03048 )
)
)
)
anim_node Disk.2 (
controllers ( 1
linear_pos ( 3
linear_key ( 0 0 0 0.03048 )
linear_key ( 1 0 0 -0.03048 )
linear_key ( 2 0 0 0.03048 )
)
)
)
anim_node Disk.3 (
controllers ( 1
linear_pos ( 3
linear_key ( 0 0 0 -0.03048 )
linear_key ( 1 0 0 0.03048 )
linear_key ( 2 0 0 -0.03048 )
)
)
)
)
)
)
)

[eugenR]

In gmax this numbers have the following definition:

animation ( 10 5
10 = Number of animation steps (frames)
5 = Number of frames per second (speed of the animation)

In gmax I can only enter whole numbers as animation speed, I can't enter 2.5

But if I manipulate after the shape manualy and enter 2.5 as animation speed:
OR give the known warning and there is no animation
MSTS make an animation speed of 2.5 frames/s

Perhaps with others 3d-Tools it would by possible to enter 2.5 as animation speed?
I doesn't know, if OR will take this problem as a Bug, because MSTS has no problems with an animation speed of 2.5

and for the moment in your case:
animations ( 1
animation ( 2 1.5
you cange it to a whole number:
animation ( 2 1
or
animation ( 2 2

[R H Steele]

Thanks eugenR, I posted in the OR bug forum about this thread. If MSTS is reading it as 1.5 then OR should also, or at least read it with a value the team thinks will work. Maybe there is more to it than meets the eye. I don't have any knowledge of GMAX, so thanks for the answer. At least now I know what I am changing.