System.IO.InvalidDataException at ORTS.Simulator.InitializePlayerTrain (X2194, SP Hyrail)

[Mike Brady]

Using the SP_Hyrail locomotive from trainsim.com, RunAppLAA failed during startup from the menu. The error box requested that I file a bug. It did return to the menu. Routes tried (from trainsim.com; they work with other consists) are Cow Creek Canyon and Potash. Splash screen displays, followed by an error box on it regarding the startup failure. Log of the Potash attempt is attached.

[Derek Morton (derek-a)]

Could you check this please:-

Warning: Ignored missing wagon D:\trainsims\msts-UPSP\trains\trainset\Hyrail\Hyrail1_SP.eng in consist D:\trainsims\msts-UPSP\TRAINS\CONSISTS\hyrail_pickup_truck_SP.con

[Mike Brady (mjbrady-j)]

Interesting ... there isn't a .wag file for that item. But, as with a number of other single-unit engines (like the RDCs) the wagon is defined within the .eng file - the first section of the file. I did have to edit the .con file because as distributed it was pointing at the wrong file (pointed at a nonexistent one in the same directory) - did that do it?

Just tried it again in MSTS and there was no complaint until I tried to start exploring with it - then got the standard train database error. Your error message is more specific, but I'm still not sure what to fix.

[Mike Brady (mjbrady-j)]

Attaching the hyrail1_SP.eng file for reference.

Did quick-check parentheses in the .eng file and the key ones, at least, seem to match.

[Derek Morton (derek-a)]

>then got the standard train database error

Can you post that error please, as it will point to the problem.

[Mike Brady (mjbrady-j)]

Updating bug:

1) in MSTS, causes a "Send/Don't Send" error, but only after attempting to start running a route using the SP Hyrail truck. Initial error box is the traditional "Error reading train database" box, followed (if "yes" is pressed) by Send/Don't Send. MSTS starts fine, and runs fine with any other train.

2) compared the .eng file for this item to the one for the Seaview doodlebug, which works. Nothing appears to be missing or added compared to the doodlebug in terms of sections, and all of the referenced files (shapes, etc.) are present in the correct folder. The doodlebug also has the wagon definition in the .eng file. Note: I did have to fix the consist file from the distribution archive; it had an incorrect folder name.

3) I have not yet run Route-Riter on the Hyrail, but will do that this evening if I get a chance.

[Derek Morton (derek-a)]

Error reading train database means that a consist is calling for a vehicle that does not exist.

The Error Box should contain the missing item, can you have another look please.

[Mike Brady (mjbrady-j)]

The file mentioned is the .eng file, but again I could find no errors. Ran Route-Riter on it and it couldn't find anything either. Your other suggestion turned out correct: the directory wasn't correct in the .con file. Fixing that makes it work correctly in both ORTS and MSTS - no more errors. BTW, that directory was wrong in the distribution archive, so other users beware. Nice item to use, though, now that it's working.

So ... close bug ... it isn't one ... though the error message was no more helpful than the generic one that MSTS provides despite having much more detail.

[Derek Morton (derek-a)]

This is just a missing file.

OR should not crash on a missing file, it should notify the user.

Can a programmer pick this up please.

[Mike Brady (mjbrady-j)]

If it's any help, I am attaching the .con file with a comment added about the change to the directory that is needed to fix the MSTS and ORTS crashes.

[Mike Brady (mjbrady-j)]

Well bleep. The comment didn't appear despite editor having said it saved it. Anyway, the EngineData line is the culprit. Second parameter is the directory. The original .con file had just plain "Hyrail" there - after changing to the directory name used for the rest of the distribution it works fine.

[Cédric GNIEWEK (sharpeserana)]

Does the problem still happen with version 1.4?

[Launchpad Janitor (janitor)]

[Expired for Open Rails because there has been no activity for 60 days.]