[longiron]

Has anyone noticed that when adding new tiles to existing route using TSRE, it doesn't use the same naming convention as MSTS. I've added three tiles to existing route and now I have this. Only discovered when using RR which highlighted the name difference.

 TSRE_TileName.gif (8.09K)
Number of downloads: 3

Does it really matter as everything works as expected in MSTS including RE/AE and game, except to RR?

[Jovet]

longiron, on 18 March 2017 - 03:51 AM, said:

Does it really matter as everything works as expected in MSTS including RE/AE and game, except to RR?

I would think it would matter. Those filenames don't make sense... they're a combination of two different naming schemes. I'm amazed that MSTS tolerates them. But I don't like the combination on principle.

[James Ross]

longiron, on 18 March 2017 - 03:51 AM, said:

Does it really matter as everything works as expected in MSTS including RE/AE and game, except to RR?

I am assuming the bottom three are the new TSRE ones, and I would say they are the correctly-named ones, not the top three. I'd be curious to know where the top three came from (which tool) because my collection of content only has world files in these formats:

• w+123456+123456.w
  
• w-123456+123456.w

The most likely reason they work at all is because "w+2147472451+014287.w" is equivalent to "w-011197+014287.w", except the former is using unsigned 32bit instead of signed 32bit. I wouldn't want to release any content using the former, though, as it only works by chance and may well not work in OR.

[longiron]

James Ross, on 18 March 2017 - 09:05 AM, said:

I am assuming the bottom three are the new TSRE ones, and I would say they are the correctly-named ones, not the top three. I'd be curious to know where the top three came from (which tool) because my collection of content only has world files in these formats:

• w+123456+123456.w
• w-123456+123456.w

The most likely reason they work at all is because "w+2147472451+014287.w" is equivalent to "w-011197+014287.w", except the former is using unsigned 32bit instead of signed 32bit. I wouldn't want to release any content using the former, though, as it only works by chance and may well not work in OR.

I guess I should ask Goku to make a change to TSRE as the top three are new tiles added via TSRE, while the 'normal' tiles were created in MSTS RE

chris

[copperpen]

Just checked the route I started using TSRE5 and world files all have the normal names. Those odd looking filenames come from 2015 and early 2016, so might not be from TSRE5.

[Goku]

The top tiles can't be from TSRE.

[longiron]

If they are not from TSRE, then how would I convert them? Can someone point me to a simple tool on the web? Thanks in advance.

chris

[Goku]

Does the tiles work in OR at all? I'm 100% sure they won't load in TSRE, so if you don't see problems in TSRE, you can remove the files.

[longiron]

I apologize for saying the tile naming was a TSRE issue. Those tile names appear to be duplicates of valid tiles. How they were created I don't have any idea.