Use this forum if you found a bug.
viaEstrecha
Posts: 11 Joined: 25 Feb 2019, 14:52
Location: Bedfordshire, UK
The display is working in TSRE except each of the 2 spawners illustrated is listed as 0m in length, which is clearly wrong.
![Image](https://p2bh0q.ch.files.1drv.com/y4mEuVemKNYiy7aRhI1FpqnoxGSiS3HwBIhWDd0BzeABtaZ7QvTM0OV0cK41RRadIesMGpJYWhm6RD0F0zoYn-iUMSO88MQRn2JJWPVhPEovdclEL3MbI9odvgr2xhpx6iz19PiqaNUeDmhDLK6t2bxvc-_TZHPYDTAIlmXxNfV0nD19m-nAGX9giB2BpQNlx2n?width=1000&height=524&cropmode=none)
The Spawner does not then function in OR and so TSRE is possibly not consistenly writing all the necessary information? It is sporadic - saving the route in TSRE may make one spawner show in OR, but after the next save, it may disappear again. In another route, 3 Spawners work correctly all the time, yet others do not.
The data saved to the .rdb file is the same as in the .rit file:
TrItemTable ( 4
CarSpawnerItem (
TrItemId ( 0 )
TrItemSData ( 4.5367475 00000001 )
TrItemRData ( -45.040825 0.90790892 -67.269508 -5354 14849 )
)
CarSpawnerItem (
TrItemId ( 1 )
TrItemSData ( 107.59483 00000001 )
TrItemRData ( -45.040825 0.90790892 -69.269508 -5354 14849 )
)
CarSpawnerItem (
TrItemId ( 2 )
TrItemSData ( 110.41592 00000001 )
TrItemRData ( -32.124348 0.90790892 -139.75381 -5354 14849 )
)
CarSpawnerItem (
TrItemId ( 3 )
TrItemSData ( 1 00000001 )
TrItemRData ( -42.040821 0.90790892 -31.900345 -5354 14849 )
)
)
In the .w file:
Tr_Worldfile (
CarSpawner (
UiD ( 44 )
CarFrequency ( 12 )
CarAvSpeed ( 20 )
TrItemId ( 1 0 )
TrItemId ( 1 1 )
StaticFlags ( 00000100 )
Position ( -45.0408 0.907909 -68.2695 )
QDirection ( 0 0 0 1 )
VDbId ( 4294967295 )
)
CarSpawner (
UiD ( 45 )
CarFrequency ( 8 )
CarAvSpeed ( 25 )
TrItemId ( 1 2 )
TrItemId ( 1 3 )
StaticFlags ( 00000100 )
Position ( -37.4756 0.907909 -99.5799 )
QDirection ( 0 0 0 1 )
VDbId ( 4294967295 )
)
A little more testing done today and there is a definite discrepancy between the end of the Spawner showing in TSRE and the end being displayed in OR (ie where a vehicle disappears). OR Track Viewer also shows the discrepancy.
Edited 24 March - is it possibly a similar problem to the recoding of Platform/Siding position, which you reported fixed recently here and on Elvas Tower?
Last edited by
viaEstrecha on 26 Mar 2019, 09:30, edited 2 times in total.
Old dog finding it hard to learn new tricks
joe_star
Posts: 4 Joined: 23 Feb 2019, 12:41
Having similar issues as described above.
Seems like the spawner TRItemRData being written in RIT is not right.
viaEstrecha
Posts: 11 Joined: 25 Feb 2019, 14:52
Location: Bedfordshire, UK
Just tried another test in a completely blank route, to be sure:
1. Placed spawner over a few hundred metres of road in TSRE - all looked fine.
2. In OR TV, spawner start and finish were however shown colocated; no vehicle was displayed moving in ORTS.
3. Opened route in old MSTS RE, moved the spawner start and finish slightly and then saved.
4. Spawner now appears and works OK in ORTS and TSRE. The adjusted positions show correctly in OR TV.
5. Moved one end of spawner again in TSRE and saved - that changed position seemed to be ignored by ORTS and OR TV.
So it does appear TSRE is not currently recording the start and finish of spawner such that it is recognised by ORTS?
Old dog finding it hard to learn new tricks
Goku
Site Admin
Posts: 363 Joined: 15 Jan 2019, 18:10
Location: Poland
Contact:
Maybe it is the platform bug too.
Check if moving by keys works fine.
viaEstrecha
Posts: 11 Joined: 25 Feb 2019, 14:52
Location: Bedfordshire, UK
Goku wrote: ↑29 Mar 2019, 16:02
Maybe it is the platform bug too.
Check if moving by keys works fine.
Yes using the keys seems to make the position save correctly. That will do as a workaround, to make the final position with the key and I'm sure you'll add the fix to your long list of work to do!
Old dog finding it hard to learn new tricks