Railworks America

I hope someone can help me:
I just created Markes using Google Earth and RW Tools. I exported them into my route folder and they display in the route correctly.
My only issue is that these Markers aren't shown in the intended order in the right flyout. I tried to give them numbers , but this doesn't work.
So is there a possibility to influence the order of the Markers in the flyout?

Thank you.

I am not sure if reordering them in the route markers' .dcsv file will affect their display order. Even if it does, I think remaking the file would be easier. The points are listed in the order that they are listed in your Google Earth Places folder, so what I do is reorganize them there first, then re-export and convert.

Tori

Toripony wrote:The points are listed in the order that they are listed in your Google Earth Places folder, so what I do is reorganize them there first, then re-export and convert.
Tori

That's the problem. I have them in correct order in Google Earth (in the list/subfolder on the left), depite of that they are displayed incorrect in the RW flyout.

EDIT: Problem solved. You must name your markers this way: 01., 02., ....., 10., 11., ...
Another problem: All markers are now in the flyout, but also the ones of the SanB to Bartsow route. Is there a way to get rid of these?

RailWorks shows all markers within (from memory) 600 km of the origin point of your route. So if your route is near the Cajon Pass route, then you will also see its markers.

If you are building a route in the UK, you will find you end up with hundreds of markers you don't want.

Mike

I found that putting the markers and route template in my developer's folder sturcture fixes this problem and also lets the markers show up in the new scenario creation process. You can pick your starting point from the markers list. I figured this out on my own route that was using san bar and csx mainline markers. If someone puts their markers in the default kuju folder structure it whacks things out.

artimrj wrote:I found that putting the markers and route template in my developer's folder sturcture fixes this problem and also lets the markers show up in the new scenario creation process. You can pick your starting point from the markers list. I figured this out on my own route that was using san bar and csx mainline markers. If someone puts their markers in the default kuju folder structure it whacks things out.

My markers are stored in the Asset Folder under my name, but SanB markers still show up.