Route-Riter v3.8.53 beta

mikesimpson · Post by **mikesimpson** » Mon Apr 07, 2003 1:00 am

I have uploaded a new RR .exe beta file only to http://members.optusnet.com.au/virtualtrains

I will upload the full version here once I am certain it is working correctly.

New version has following improvements

1. Now checks the CRC of all files against the equivalent Default files, including all seasonal/snow/night textures and terrtex snow files to ensure that those added to the installme.bat are identical to those used by the author.

2. Check Route - Now gives you the option to copy the daytime texture into the snow/seasonal/night folder if there is no equivalent file available. This does not give you correct texturing but at least you do not get an error that a snow texture is missing.

Same with terrtex files.

This option is for users, not authors, however it does give you the option to run routes which are essentially desert routes in the snow if you so wish.

Please note there was a problem with v3.8.50/51 whereby not all default textures were added to the installme.bat thus making the .zip file too large. Hopefully this is now fixed. Please advise of any further problems.

asalmon · Post by **asalmon** » Mon Apr 07, 2003 7:44 am

The facility to correct the SD files seems to be damaged.

For each SD it tries to fix, I get a

Runtime error 75 path/file access error

then

xxxx.sd is already in unicode format.

I also noticed that this version listed several SD's as having a problem with esd 256 or whatever; these errors weren't reported in version ..51 - maybe that was a bug then which has been fixed; or its a new bug now

-Alan

asalmon · Post by **asalmon** » Mon Apr 07, 2003 9:54 pm

oh, how embarassing!

I ran it on another route and it was fine - the one I was trying before had various .s and .sd files read-only!

So I'll test the "make read/write" button and try again!

-Alan

mikesimpson · Post by **mikesimpson** » Mon Apr 07, 2003 10:06 pm

Hi Alan,

Yes, it is best to make all the files read/write first, however RR should catch them rather than fail with an error message. I do check most places for these, but sometimes I forget (I have made everything on my PC read/write so do not notice these errors:-( )

2. The check for ESD entries of 256 has been added. If you run any route in the snow which has such ESDs, then MSTS actually looks in the Snow folder then in Global\Textures for a snow texture and gives an error if it does not find one.

Maybe Kuju will fix this in v2 (they missed it in v1.1 and v1.2 even though it has been documented plenty of times, so maybe they will ignore it in 2 as well?)

asalmon · Post by **asalmon** » Mon Apr 07, 2003 10:38 pm

Is 256 meant to be a setting for just day and night? I thought that check was in previous versions, but obviously not!

Or are there two buggy ESD values?

-Alan

mikesimpson · Post by **mikesimpson** » Tue Apr 08, 2003 10:05 pm

asalmon wrote:Is 256 meant to be a setting for just day and night? I thought that check was in previous versions, but obviously not!

Or are there two buggy ESD values?

-Alan

Yes, it is meant for just day/night - presumably if you run the route in the snow it was intended that just the day textures were used, however MSTS still looks for a snow texture and ends up with an error if it does not find one.

This check was in an earlier version of RR, but has not been working correctly in recent versions.

steam4me · Post by **steam4me** » Wed Apr 09, 2003 4:23 am

Is 256 meant to be a setting for just day and night?

Visit http://www.railpage.org.au/steam4me/tra ... tml#ESD256

As Jim explains, it's better for a route builder to use (0) or (257).