animation frames per second MSTS vs OR is this a bug?
#1
Posted 29 March 2015 - 12:09 PM
http://www.elvastowe...tant-number-15/
#2
Posted 29 March 2015 - 02:29 PM
R H Steele, on 29 March 2015 - 12:09 PM, said:
http://www.elvastowe...tant-number-15/
And here the Shape with the 2.5 Frame per second animation speed
In MSTS it works, in OR it produce an error Warning and no animation.
Attached File(s)
-
CHTBlinklicht.zip (20.09K)
Number of downloads: 192
#3
Posted 29 March 2015 - 06:18 PM
Cheers Bazza.
#4
Posted 29 March 2015 - 07:15 PM
Cheers Bazza.
#5
Posted 30 March 2015 - 02:19 AM
captain_bazza, on 29 March 2015 - 07:15 PM, said:
Cheers Bazza.
I have tested the Problem for R H Steele, he has in a Route a animated shape witch produce Warnings.
The animation is not working in OR. But it works in MSTS!!!
This shape has 2 frames and a speed of 1.5 FPS
To change this Shape on 1 or 2 FPS would be a great animation-Difference!
And I think not so many user of a future OR Version 1 would be able to change this animation-speed in a shape.
sorry but for my tests for H R Steele I had found only this shape with 10 Frames an 5 (for Test 2.5) FPS.
Cheers
Eugen
#6
Posted 30 March 2015 - 05:03 AM
My reasoning for this approach was, with the train approaching the crossing, passing, receding, the POV changes with the train. As the train is adjacent to the signal(s) the lights are working. It does not matter if they never actually switch off, because as far as the train is concerned the lights went on, played, then switched off. Check out my signals.
http://www.elvastowe...als-version-10/
Cheers Bazza
#7
Posted 30 March 2015 - 12:08 PM
I tracked it down to the animation line in a shape file, all the warnings although referring to different shape turned out to have the same problem, this line >>> animation ( 2 1.5
So since I know nothing about shape files, I did not want to change anything without first doing some research, part of that was posting the thread.
After reading all the responses, it appears that if it is an OR bug (must be a "feature" of MSTS to read the 1.5) it is a very low level bug. I think the dev team has more significant issues to deal with.
Appears the best fix is to correct the offending line to read animation ( 2 2 or animation ( 2 3 ... which can be done with SearchReplace or TextCrawler (or one of the other similiar programs). That way I can do each file needing correction in many routes at the same time.
(edit: all the above was exposition blather for anyone who has found the same warning and wants to try to correct it)
Thanks to eugenR and the good captain for their advice and knowledge.
#9
Posted 31 March 2015 - 07:10 AM
gpz, on 30 March 2015 - 09:47 PM, said:
I have posted this Bug-Report:
https://bugs.launchp...or/+bug/1438747
Hello Jijun Tang,
thank you for fixing the Problem so quick (X2961)
Cheers
Eugen
#10
Posted 01 April 2015 - 04:44 AM
I too had tried that fix with the aim of uploading it, but renounced because of this problem. It's a bit more complicated...