Page 1 of 1

Invisible Consist Names

Unread postPosted: Mon Sep 21, 2015 11:10 am
by HighGround22
.
Hullo, Mike:

I was attempting to swap the driving consist in a scenario that I recently d/l'd from the Steam Workshop, when I ran into an unusual (for me) problem: I selected the Route Name, then the Scenario Name and clicked Edit Selected Scenario -- all Bog-Standard stuff. But with this scenario, some of the consist names were invisible in the Consists box. Here's the link to the scenario, if you need to take a boo at it:

http://steamcommunity.com/sharedfiles/f ... =519950252

Have I done something I shouldn't have -- or vice-versa?

Thanks for your time, Mike -- and of course, for your wonderful RWT!!

-Jon

Re: Invisible Consist Names

Unread postPosted: Mon Sep 21, 2015 6:19 pm
by mikesimpson
Hi Jon,

I have checked this workshop scenario and for some reason the route author has placed 'New line' characters at the beginning of some consist names like:-

<ServiceName>
<Localisation-cUserLocalisedString>
<English d:type="cDeltaString">
2A52 1606 Canterbury West to London Victoria</English>
<French d:type="cDeltaString"></French>
<Italian d:type="cDeltaString"></Italian>
<German d:type="cDeltaString"></German>

Because of this, RW_Tools reads the service name as a blank line, however selecting it in the list of Consists gives you the content of the consist and you should be able to modify it.

I suppose I could modify RW_Tools to take this into account, but as it has only ever been reported in one scenario, it hardly seems worth the effort. As this has only happened on a handful of consists, I am assuming it is an error on the author's part rather than an attempt to hide things?

Mike

Re: Invisible Consist Names

Unread postPosted: Wed Sep 23, 2015 12:58 pm
by HighGround22
Yeah, I quite agree that the lack of history for this problem would nil-out the prospect of modifying RW Tools. I'll just fiddle with a bit of guesswork to determine which one was the driving consist (I figure it's the second invisible one), and so-forth.

Many thanks, Mike.

-Jon