I encountered a major problem when using the Track Viewer software, and I hope to get your help. Hello everyone.When I used the Track Viewer software to make a task path for the Openrails program, I encountered this situation. I asked an expert to guide me how to solve it (In fact, I used to use the path editor in the task editor that comes with MSTS itself to make a path for the task.I am used to it and can basically use it proficiently).Problem description: I established a self-created path. When I changed the direction of the line's turnouts, an unexpected thing happened-the path was interrupted inexplicably.Specifically, when the initial turn-out opening direction is not changed, it is like this,54558267573_2e065e9fe1_m.jpg,giving people the feeling that this is a complete normal line; but after the turn-out opening direction is changed, it is like this,54558214519_9e660af110_m.jpg,giving people the feeling that the path has been interrupted for no reason; when I return to the original turn-out opening direction, it is still like this54558215009_3d56fb9503_m.jpg?!Therefore, I would like to ask experts and masters, what is going on?How should we solve this kind of problem or effectively avoid or prevent this kind of thing from happening?!Well, in any case, I hope that experts or masters will try their best to reply when they see it.And I am also here waiting for your reply, please, thank you first.Take care!Good luck
I encountered a problem when using the Track Viewer, and I hope to get your help
Collapse
X
-
Amen to the size issue. I have seen odd things when I created paths with TV. I would use it to check continuity of a route. Once you pass a large number of nodes, it just won't go further but if you start the path just before that point it is okay until it finds too many more. And sometime it will work in one direction but not the other.Comment
-
When you set an initial path, the path auto-fills to the end.
When you change a switch somewhere along the way after you set a path, the path shortens to the first node just after the switch. That is when you need to PG UP until the path extends all the way to the end.My Open Rails videos https://www.youtube.com/@lakecities3663/videosComment
-
Well, let me re-upload the relevant photos describing the problem. I hope you can help me solve this problem.Thanks first!(May God bless you forever)
I encountered a major problem when using the Track Viewer software, and I hope to get your help. Hello everyone.When I used the Track Viewer software to make an activity path for the Openrails program, I encountered this situation. I asked an expert to guide me how to solve it (In fact, I used to use the path editor in the task editor that comes with MSTS itself to make a path for the activity.I am used to it and can basically use it proficiently).Problem description: I established a self-created path. When I changed the direction of the line's turnouts, an unexpected thing happened-the path was interrupted inexplicably.Specifically, when the initial turn-out opening direction is not changed, it is like this Screenshot - Track Viewer.png ,giving people the feeling that this is a complete normal or continuous line; but after the turn-out opening direction is changed, it is like this Screenshot - Track Viewer - 2.png ,giving people the feeling that the path has been interrupted for no reason; when I return to the original turn-out opening direction, it is still like this?! Screenshot - Track Viewer - 3.png Therefore, I would like to ask experts and masters, what is going on?How should we solve this kind of problem or effectively avoid or prevent this kind of thing from happening?!Well, in any case, I hope that experts or masters will try their best to reply when they see it.And I am also here waiting for your reply, please, thank you first.Take care!Good luckLast edited by letourde; 06-07-2025, 07:15.Comment
-
Well, okay, it turned out to be like this. It seems that it was caused by the excessive number of nodes at this intersection.Now I know what this is all about and the corresponding solution.However, to be honest, the path editor that came with or was built into the previous MSTS program (located within the task and tool editor) is still very useful. I am more familiar with its basic usage, which means I have already been able to use it proficiently.For the path editor software of this Track Viewer program, you should also carefully study the tutorial guidance and add more practical exercises in order to truly use and master its basic usage methods thoroughly and fully.In any case, thank you very much for your careful guidance and enthusiastic replies.I hope you are all well!Take care.Good luck (I also sincerely wish our Openrails simulator program business can develop better and better! Have time to chat here! See you)Comment






Comment