NorthernWarrior wrote:Just to emphasise my previous post, I have just successfully set up some markers for a new route startup using the method I described so providing you don't export direct to DCSV but allow the Blueprint Editor to handle the xml output by RW Tools (changing the flag path to Marias Pass), it still works. Could I suggest then Mike, the best thing for now would be to put back the ability to do markers step by step which was in previous versions but not the latest which AFAIK only had the direct to DCSV option. Bypassing the Blueprint Editor is probably not a good move.
Hi Vern,
I will look at that, but I removed the method using the Blueprint editor as it did nothing the direct to DCSV offered and was confusing for those without much experience of the Blueprint Editor.
Changing the flag path to Marias Pass, or any other route will still not work for anyone other than those who already have the routes in question. The flag is still in the original Kuju\RailSimulator file, which is still outside of an .ap file so really should be the one which most people still have installed. So really there is no certain way to know that a route you have uploaded will have visible marker flags unless you point the the route markers .bin file to your own RouteMarkers folder and include your own flag. (I don't really think RSC would complain if you distributed a copy of their flag with your route, but you never know?).
Code in the RouteMarkers .bin file would then be, as in Pacific Surfliner indicating the flag model was in the same folder as the .bin file:-
<FlagBlueprint>
<iBlueprintLibrary-cAbsoluteBlueprintID>
<BlueprintSetID>
<iBlueprintLibrary-cBlueprintSetID>
<Provider d:type="cDeltaString"></Provider>
<Product d:type="cDeltaString"></Product>
</iBlueprintLibrary-cBlueprintSetID>
</BlueprintSetID>
<BlueprintID d:type="cDeltaString">RouteMarkers\flag.xml</BlueprintID>
</iBlueprintLibrary-cAbsoluteBlueprintID>
</FlagBlueprint>
Mike