Lost world
#1
Posted 17 December 2018 - 01:39 PM
This is the second route I've worked on where this appears in Open Rails after editing in TSRE:
What's unusual here is things look ok in TSRE and the problem usually is corrected by editing on the flawed tile.
It's interesting that both terrain and world file entries are affected. I suspect the matter has to do with something in the \tiles directory, quite possible the .t file as I have been applying tertex art in both cases. I may have been doing terrain vertex editing too... I just don't recall. Why this has an affect on the world file data is a complete mystery but perhaps that weirdness is something in OR itself and not something odd in the data files.
What's unusual here is things look ok in TSRE and the problem usually is corrected by editing on the flawed tile.
It's interesting that both terrain and world file entries are affected. I suspect the matter has to do with something in the \tiles directory, quite possible the .t file as I have been applying tertex art in both cases. I may have been doing terrain vertex editing too... I just don't recall. Why this has an affect on the world file data is a complete mystery but perhaps that weirdness is something in OR itself and not something odd in the data files.
#2
Posted 17 December 2018 - 02:17 PM
Is it a 2x2 or larger tile? Open Rails cant handle that & its a known issue afflicting several of the Indian routes.
I do not think merely editing the tile would make a difference in that case though, so yours looks like something else.
I do not think merely editing the tile would make a difference in that case though, so yours looks like something else.
#3
Posted 17 December 2018 - 10:01 PM
> Is it a 2x2 or larger tile?
No, in both routes where this occurred the tile was ordinary.
I wish I had more information available regard what exactly I did on that tile before hand but you know how editing goes... you are here, there, somewhere else and you've done 5 different things. If the problem appeared in TSRE it would be much easier to peg but it only shows up in OR. Scary when it does.
No, in both routes where this occurred the tile was ordinary.
I wish I had more information available regard what exactly I did on that tile before hand but you know how editing goes... you are here, there, somewhere else and you've done 5 different things. If the problem appeared in TSRE it would be much easier to peg but it only shows up in OR. Scary when it does.
#4
Posted 17 December 2018 - 11:23 PM
I have had the same problem on my route. It seems to present itself after several changes of the camera view and/or switching back and forth between OR and the dispatcher windows, possibly any other window. Saving and restarting OR usually fixes it but it is very annoying at times.
#5
Posted 18 December 2018 - 10:46 AM
Jarad, you think it is strictly an OR issue? No use of TSRE where it occurred? Hmmm. I suppose it could be but in my case each occurrence was only after using TSRE at the lost world" locations..
Anyone else see this weirdness?
Anyone else see this weirdness?
#6
Posted 18 December 2018 - 04:07 PM
Idk for sure that TSRE has nothing to do with it but I had this issue before I ever started using TSRE on my route.
#7
Posted 18 December 2018 - 05:32 PM
#9
Posted 18 December 2018 - 07:52 PM
CrisGer, on 18 December 2018 - 05:38 PM, said:
Lost World...i was hoping for dinasaurs
did Sandy River Tom animate themhttp://www.elvastower.com/forums/public/style_emoticons/default/pleasantry.gif
Sorry....
Reminds me of the 'great white void issues' that some routes had in MSTS.
Does this occur and is it visible when viewed from different angles?
Is it near a tile boundary?
Michael
#10
Posted 19 December 2018 - 02:36 AM
Similar Mike but not the same. It affects whole tiles. Sometimes just the terrtex disappears leaving track and structures, and sometimes the trac section disappear or are moved about randomly. However the tdb stays in place and the train continues to follow it.