Atomic Systems

I downloaded this scenario - https://www.uktrainsim.com/filelib-info ... leid=40121
And I wanted to change some trains/locos in the Scenario but when I click on the Scenario Editor then Timetable only the player train is shown

So I decided to start the Scenario and I get a warning message that I'm missing some vehicles from an XC Class 220
But that is not on the list and RW Tools does not show anything missing
I thought I could change the Class 220 to the Just Trains version but as I can not find which train it, although it will be in the York - Doncaster area, that does not help either.

There is no readme file so it is guesswork

Peter

Further looking at the trains in TSTools there is no 220 so not sure about the message

But we do have a train of Milk Tanks somewhere,
Double Headed 92's on something
Class 86's on MGR services

All the scenarios from DFW are like that, there are no names for the AI services defined in the scenario when you view it in the editor timetable mode. Whether this is due to a fault in the writing or packaging or an intentional ploy to make *meddling* difficult I can't say.
The 220 you're missing will be the RSC model, so just click through the consists in RW Tools' scenario editor to identify and swap it.

I had used F2 to get the thing running so it removed the Voyager - strange as TS Tools did not report it missing when I first checked for missing items

Had a problem with the LNER Azuma with only the Driving coaches showing - I even swapped the consist for the same that had all vehicles showing
Saved the Scenario and they were still showing - pushed Play and the intermediate vehicles disappeared leaving the gangways

I have a feeling because the Author is German is why we can not see the AI services in the Editor
Which also explains the rubbish consists

Peter

749006 wrote: ↑Sat Nov 21, 2020 8:02 pm I have a feeling because the Author is German is why we can not see the AI services in the Editor

It's got nowt to do with his nationality, it's because the AI services have no name in their service/driver icon's properties boxes. Drop into the scenario editor, fly around to find an AI service and double click it's service/driver marker to bring up the properties. No name in there = no name displayed in the time table view.


EDIT:

Strange as TS Tools does shown a name for each of the trains - like 01 - 86 FL TEA

When I said it was because he was German I meant to say his TS is set up with German Language
I have had this problem before where I downloaded a Scenario from RailSim.de and could only see the player train when in Timetable view with the trains correctly designated

Peter

749006 wrote: ↑Sun Nov 22, 2020 2:05 pm I have had this problem before where I downloaded a Scenario from RailSim.de

You can't take a single scenario out of hundreds as being proof that German keyboards cause the problem---how many German scenarios have you downloaded that are OK?

gptech wrote: ↑Sun Nov 22, 2020 7:51 pm

749006 wrote: ↑Sun Nov 22, 2020 2:05 pm I have had this problem before where I downloaded a Scenario from RailSim.de

You can't take a single scenario out of hundreds as being proof that German keyboards cause the problem---how many German scenarios have you downloaded that are OK?

It is not German Keyboards that is the problem but the default Language is German which causes the problem.
You said that the trains don't have any Service information - which is correct for English

Looking in the Scenario Properties this is the Class 66 which sits alongside the 800 at Peterborough

<FrontEndDriverList>
<sDriverFrontEndDetails d:id="281934004">
<ServiceName>
<Localisation-cUserLocalisedString>
<English d:type="cDeltaString"></English>
<French d:type="cDeltaString"></French>
<Italian d:type="cDeltaString"></Italian>
<German d:type="cDeltaString">66 FL JGA</German>
<Spanish d:type="cDeltaString"></Spanish>
<Dutch d:type="cDeltaString"></Dutch>
<Polish d:type="cDeltaString"></Polish>
<Russian d:type="cDeltaString"></Russian>
<Other/>
<Key d:type="cDeltaString">343d783e-1a6a-4358-858c-4aca262ee567</Key>
</Localisation-cUserLocalisedString>
</ServiceName>

66 FL JGA is what TS Tools identifies the train as.

Peter

749006 wrote: ↑Sun Nov 22, 2020 8:22 pm 66 FL JGA is what TS Tools identifies the train as.

That'll be German for 66 FL JGA then.

Now I see what you're on about though--because the ScenarioProperties.xml file doesn't have a language specific entry for any other than German there's nothing to show.

Has this problem not been discussed before? Wasn't the solution to add in the entry from the <German> to the <English>, so that it showed in an English version of the sim?
Or am I talking through an orifice other than my mouth

I remember having the problem before but I did not find a solution - it was 3 or 4 years ago and had slipped my mind
I changed the ScenarioProperties.xml to add the same train info in the English section copied from German but that did not make a difference.

I will give this a miss.

Peter

Somebody on the DTG Forum suggested changing the Authored Language to English and see if that made a difference but it did not.

From memory, a lot of the TS-Tools options first look in the '<English' section for loco names, and if not found there, then look in the French, Italian, German and Spanish sections.

I think that it is necessary to add the loco name to the English section of the loco's .bin file as well as any changes made to Scenario files.

Mike

The scenario is set on the York - Peterborough route using mainly UK Stock apart from a few German wagons from the Kuju ELAP so no problem with the locos description

Each of the entries for the AI services just had a service name in the German language section so I copied those to the English section and changed the Authored Language to English - but it does not seem to have made a difference

TS Tools sees each of the AI services and gives the name and the correct formation

Peter

749006 wrote: ↑Wed Nov 25, 2020 1:14 pm I copied those to the English section and changed the Authored Language to English

Try it with the authored language back as German, and try just the service name change on a clone of the scenario.