Installation, use of TS19 and TS22 on one PC issues

oldman777

Well-known member
TS19 and TS22 are both latest Steam versions.
Here I have already written about the black bushes in TS19 with any shader settings: https://forums.auran.com/threads/bush-spline-are-partially-black-in-color.177609/
In TS22, this behavior has changed:
If the quality settings of the launcher shaders are Low, then the splines of the bushes will be of normal color, and all the water is black.
If the quality settings of the launcher shaders are Standard or Ultra, then the splines of the bushes will be black, and all the water will be of normal color.



I created a ticket about this and was told that they had passed it on to the developers.

I don't know much about the behavior of TS22 yet, so I'll move on to what changed in TS19 after installing TS22.

Menu where you select routes or sessions, rotating circle appeared: https://forums.auran.com/threads/rotating-circle.168018/
Bushes and water turn alternately black depending on the shader settings, as in TS22.
If you run TS19 not through a shortcut on the desktop, but through the TRS19.exe from the game folder, then TS22 will start Instead of TS19:


I disconnected the game from Steam client, via the simplest Steam emulator, then TS19 starts as it should be.
Apparently, the steam client has the same command for launching both games, so it launches the one that is newer.
When the launch takes place from a shortcut on the desktop, the command is addressed to the desired game via Steam ID:
steam://rungameid/553520 or steam://rungameid/1784570

I don't think it's possible to fix it somehow, it's just my observations and I decided to share it. :)
 
In TRS22, Basic is the old Standard in TRS19. The name was changed. This removes the PBR effect on the textures.

Start Steam first then run trs19.exe and trs22.exe separately instead of launching through Steam. I have a feeling like you do that Steam is confusing the .exes and running their bath incorrectly. Hopefully, this will work.
 
In TRS22, Basic is the old Standard in TRS19. The name was changed. This removes the PBR effect on the textures.

Start Steam first then run trs19.exe and trs22.exe separately instead of launching through Steam. I have a feeling like you do that Steam is confusing the .exes and running their bath incorrectly. Hopefully, this will work.
I meant, it starts normally via Steam, but directly, TS22 starts instead of TS19.

The biggest mystery for me is why the behavior of textures In TS19 changed after installing TS22.
 
I meant, it starts normally via Steam, but directly, TS22 starts instead of TS19.
Oh, oops! That's not good.

Have you tried uninstalling TRS22 and re-installing again? I hope Steam doesn't think TRS22 is an upgrade from TRS19 in more ways than one...
 
Oh, oops! That's not good.

Have you tried uninstalling TRS22 and re-installing again? I hope Steam doesn't think TRS22 is an upgrade from TRS19 in more ways than one...
I completely reinstalled TS19 and TS22 as well.
The most plausible explanation in my opinion is that steam thinks that TRS22 is an upgrade from TRS19.
 
Steam installs into different directories by default. From the Steam interface click on each version's icon or name and choose Properties > Installed Files and then click the Browse button. A window opens showing the directory used. They should be different. If you use icons on your desktop. The path under the icon to start the program should look something like this steam://rungameid/553520 and not point the executable in the program folder.

Are you sure that each program points to different local data folders? Having two versions pointing to the same local data folder can cause problems like you are describing in your post.
 
Steam installs into different directories by default. From the Steam interface click on each version's icon or name and choose Properties > Installed Files and then click the Browse button. A window opens showing the directory used. They should be different. If you use icons on your desktop. The path under the icon to start the program should look something like this steam://rungameid/553520 and not point the executable in the program folder.

Are you sure that each program points to different local data folders? Having two versions pointing to the same local data folder can cause problems like you are describing in your post.
Of course I'm sure of it. But thanks anyway for trying to help.



 
Trainz Members:
One (me) recently found out that in some Trainz routes the color of water is light blue and not natural.
Well one found that if the Windows 11 screen blue light filter is turned on (blue light filter user adjustable in windows setup),
this can effect the colors of the Train routes.
If one turns off the Windows 11 screen blue light filter then the water (lake, ponds, rivers etc) looks more natural colors.
 
The water is unnaturally blue in TRS19 and up unless we live in Florida and Bermuda, or perhaps Australia. ;-)

On my own routes, I reset the environment to default which sets the colors and lighting pretty close to what we had in TS12 and early T:ANE. Once that's set, I fiddle with the colors and adjust the lighting and definitely darken the water down.

I don't use that blue light filter in Windows 11, I tried it and found it annoying.
 
In the TRS22, some buildings on Marias Pass Route X45 are visible only from a very close distance, if move the camera a little farther, the buildings disappear:



I do not remember how it looked in TRS19, now doesn't make sense to try Marias Pass Route in TRS19, because TRS19 inherited all the properties of TRS22.
 
In the TRS22, some buildings on Marias Pass Route X45 are visible only from a very close distance, if move the camera a little farther, the buildings disappear:



I do not remember how it looked in TRS19, now doesn't make sense to try Marias Pass Route in TRS19, because TRS19 inherited all the properties of TRS22.
The buildings have poor LOD and don't render well. TS12, T:ANE, and TRS19 had the same issue. It was difficult to tell with TS12 because the draw distance was limited to 5000m. We see this now because we have longer draw distances up to 20000m.
 
The buildings have poor LOD and don't render well. TS12, T:ANE, and TRS19 had the same issue. It was difficult to tell with TS12 because the draw distance was limited to 5000m. We see this now because we have longer draw distances up to 20000m.
Did I understand correctly that this is not a special case for me, but a long-known behavior and it is not worth paying attention to it?
 
Did I understand correctly that this is not a special case for me, but a long-known behavior and it is not worth paying attention to it?
Correct, it's a long-known issue and yes, don't bother paying attention to it. As I said in the older Trainz versions we never noticed this because the draw distance was so short to begin with. What I do remember was using the assets on other routes causing stutters and that makes sense.
 
Back
Top