System.IndexOutOfRangeException at MSTS.ACEFile.Texture2DFromReader (X.1565, tree does not show up in OR)

[Christian Sorenseen]

Please fin enclosed a file Trees.zip.

Content is two tree shapes:

b_laubbaum1.s (Tree 1) and b_laubbaum4.s (Tree 4) with accompanying .ACE-files.

These trees are part of the German Route Pack: Berlin - Halle.

Both trees show up OK in MSTS and in Shapeviewer, but only tree 1 shows up in Open Rails.

Tree 4 shows up as a gray star shaped wall loking character.

I am not proficient enough to see what is wrong with the data in b_laubbaum4.s

but it seems that OR is too pickey.

ChrisD

[James Ross (twpol)]

Grey sounds like a texture loading problem... are there any messages in the log file about either of the textures used here? (Perhaps just attaching the log for a case where the tree doesn't show correctly is easiest.)

[Christian Sorenseen (box1-5)]

I saved the session at a previous run, so here is a short run.

Screenshot shows the missing trees to the left.

first the log

[Christian Sorenseen (box1-5)]

and now the screenshot.

Hope this helps.

Still, this shapefile displays correctly in MSTS ????

ChrisD

[Carlo Santucci (carlosanit1)]

From the log file it seems that OR does not like this file
train simulator\routes\pt_berlin-halle\textures\spring\b_laub4.ace .
First of all, is that file existing?
You attached only the summer textures. If the above file exists, can ou attach it?

[Christian Sorenseen (box1-5)]

Both trees have winter, spring summer and autumn textures.

I enclose a zip where all available textures for the two trees are in their correct folders.

To me the two trees are similar, apart from OR disliking one.

ChrisD

[Christian Sorenseen (box1-5)]

Your question has inspired me to do some more testing.

Only spring is affected, as far as I can see.

Spring/Snow, Summer, Autumn, Autumn/snow and winter all show OK.

Spring "bug" is also present in other Route Packs from ProTrain Series as well as the title Brandenburg - Frankfurt/Oder from TrainsimPro.

Only a few trees are affected.

ChrisD

[Carlo Santucci (carlosanit1)]

Thank You. I can confirm that the attached .ace file causes an error in ORTS. I'm not an expert in graphics, so it's really something the ORTS graphics experts have to tackle.

[Christian Sorenseen (box1-5)]

To further help You to locate the cause of this behaviour, I will trace through my other ProTrain Routes and try to locate other shape files that causes the same problem in OR.

The ProTrain Series is quite extensive, so a lot of present and future users may have one or more titles from the ProTrain Series in their posession.

As long as OR is supposed to run MSTS Route files, it will be a great advantage that OR is able to circumvents this error, whatever it is.

I´ll be back, when I find out more.

ChrisD

[Christian Sorenseen (box1-5)]

I went through a couple of the other ProTrain Routes that had the same problem. Every time it happends to be the same B_LAUB4.ACE in the spring folder that flags the error.

I tried loading the .ACE file into TGATool2A and sent Main Image to editor. Without touching anything, i saved the image again.

Using the Export as ace (Alpha) I ended up wiht the enclosed file.

To me it looks the same visually, but the size has grown from 144,312 to 144,416 Bytes, and more important OR is happy now :)

Maybe this is after all a flawed Texture, but I still do not understand why SView and MSTS does not complain.

Good luck in locating the error.

ChrisD

[Christian Sorenseen (box1-5)]

Correction: Size has grown from 141,412 to 144,416 Bytes.

(It should be possible to EDIT these Comments)

[James Ross (twpol)]

There is obviously something weird about that texture, but we will try and make Open Rails able to load it.

[Christian Sorenseen (box1-5)]

James Ross.

on april 18 You wrote:

"There is obviously something weird about that texture, but we will try and make Open Rails able to load it."

I have just bought Railarts latest MSTS Route: Rathenow - Cottbus, and they still include this faulty Spring Texture.

I have tried to get in contact with the authors, but has so far been unable to locate even an email address.

As we have found out that OR is not to blame, I think You should lay this bug to rest.

Anybody that needs the corrected texture are welcome to write me and I will send it to them.

All the best.

ChrisD