Trainz Update Announcement (SP4)

[johnarran]

N3V's installers are infuriating. All versions TRS19 onwards are registered as TANE. Build numbers in AppData don't correspond to the build numbers as per the Launcher All this makes housekeeping a nightmare. Too many versions now. Too many bugs and unfinished work. Spaghetti works. So disillusioned with the product at the moment.

 

[DennR]

I have made one install of TRS22 PE for each release; original, SP1, SP2 etc., I have one master database (build) and for development and testing different routes and sessions, I have separate build folders. Rather than the random names given by default I rename them, so I know which DB I am selecting. I can run different DBs in each of the TRS22 builds as long as I ensure the build version of the assets in the DB are compatible with the SP release in question. I will create things in the first release so build 5.1 and then I can check that they work in newer releases.

We can switch between databases easily so only one install of the game engine is necessary provided you make regular backups of databases and are happy to reinstall TRS22 if you break it. Again, a new install can simply be pointed to your database for a complete recovery.

 

[jordon412]

Hi Jordon. Which version of 22 do you have? Have you checked to make sure you are on the correct patch stream? I had to change mine from TRS22 to TRS22PE. I think I was getting a similar error.

I just got around to reading the responses. I've got the non-Steam retail edition of TRS22 SP2. I'm trying to update it again because we've changed Internet Service Provider (ISP). We went from Spectrum cable Internet to T-Mobile Wi-Fi. We were originally going to go with AT&T Wi-Fi, but we couldn't get a good signal. I am using TRS22 patch stream.

 

[jordon412]

Well, it looks like changing ISPs resulted in success, even though it took 3+ hours to download and install. I am now up to TRS22 SP3 Build 123801.

 

[pepperref]

Hello everyone

Updated Trainz+ to 126280. No obvious problems, less than 15 minutes. Did a DB update.

Now I see in S2.0 that assets are enabled or disabled, but after selecting anything with my mouse, the asset changes color in the list, but when I try to install it on the route I get 'NO ASSET SELECTED'. The funny thing is that if I use the eyedropper to select the same asset somewhere else in the route, I can then install it.

Incidentally, using Surveyor Classic does not exhibit this same odd behavior.

Is this a bug anyone else has noticed? It virtually eliminates installing any asset that is not yet already available on the route.

 

[pware]

Now I see in S2.0 that assets are enabled or disabled, but after selecting anything with my mouse, the asset changes color in the list, but when I try to install it on the route I get 'NO ASSET SELECTED'. The funny thing is that if I use the eyedropper to select the same asset somewhere else in the route, I can then install it.

To me that sounds like confusion between using the Assets Palette and the new Filter Palette. The eyedropper will always select from the Assets Palette but you may have the Filter Palette open and showing its list of assets (the dead giveaway for this is that all the assets in the Filter Palette list will have a check mark in front of their names).

Make sure that the Assets Palette is open and only select from its list. The list in the Filter Palette is used with the new Bulk Replace Filtered Assets Tool in build 126280.

For references see:-

Assets Palette
Filter Palette
Bulk Replace Filtered Assets Tool

 

[pepperref]

To me that sounds like confusion between using the Assets Palette and the new Filter Palette. The eyedropper will always select from the Assets Palette but you may have the Filter Palette open and showing its list of assets (the dead giveaway for this is that all the assets in the Filter Palette list will have a check mark in front of their names).

Make sure that the Assets Palette is open and only select from its list. The list in the Filter Palette is used with the new Bulk Replace Filtered Assets Tool in build 126280.

For references see:-

Assets Palette
Filter Palette
Bulk Replace Filtered Assets Too

 

[pepperref]

Thank you so much for the quick reply. That was exactly it!

 

[pepperref]

One more thing, the height adjustment is so slow, even at 100% Sensitivity, that it literally takes 2-3 seconds after brushing to see the impact of the height change. This was not the case pre-update.

Any else notice this or am I doing something else wrong?

 

[pware]

One more thing, the height adjustment is so slow, even at 100% Sensitivity, that it literally takes 2-3 seconds after brushing to see the impact of the height change. This was not the case pre-update.

Any else notice this or am I doing something else wrong?

I have not noticed this. How big are your brushes - there is no upper size limit in S2.0 (kilometre sizes are possible) but performance will decrease as the brush size increases.

 

[pepperref]

I have not noticed this. How big are your brushes - there is no upper size limit in S2.0 (kilometre sizes are possible) but performance will decrease as the brush size increases.

My brush sizes are only 0.5m to about 5m.

 

[jaur1]

One more thing, the height adjustment is so slow, even at 100% Sensitivity, that it literally takes 2-3 seconds after brushing to see the impact of the height change. This was not the case pre-update.

Any else notice this or am I doing something else wrong?

I have noticed exactly the same issue, even with the smallest brushes. As I was doing heavy terrain editing, I had to go back to previous build

 

[pware]

My brush sizes are only 0.5m to about 5m.

I have noticed exactly the same issue, even with the smallest brushes.

What is the Grid size of the baseboards you are using?

A small brush size (up to about 5m) on a 10m Grid baseboard will only work at the intersections of the yellow (10m) grid lines and NOT anywhere else. Brush sizes from 5m to under 10m will work best on the yellow grid lines and slowly/poorly anywhere else. Brushes of 10m and above will have no problems. This has always been the case with Trainz.

A very small brush size (up to about 2.5m) on a 5m Grid baseboard will only work at the intersections of the grid lines (both yellow and grey) and NOT anywhere else. Brush sizes from 2.5m to under 5m will work best on the grid lines and slowly/poorly anywhere else. Brushes of 5m and above will have no problems.

In Trainz Plus using HD grid the smallest brush size you can use is 0.12m (12cm) and it is not restricted to grid lines or intersections.

See Ground Brush Resolution for more details.

 

[pepperref]

What is the Grid size of the baseboards you are using?

A small brush size (up to about 5m) on a 10m Grid baseboard will only work at the intersections of the yellow (10m) grid lines and NOT anywhere else. Brush sizes from 5m to under 10m will work best on the yellow grid lines and slowly/poorly anywhere else. Brushes of 10m and above will have no problems. This has always been the case with Trainz.

A very small brush size (up to about 2.5m) on a 5m Grid baseboard will only work at the intersections of the grid lines (both yellow and grey) and NOT anywhere else. Brush sizes from 2.5m to under 5m will work best on the grid lines and slowly/poorly anywhere else. Brushes of 5m and above will have no problems.

In Trainz Plus using HD grid the smallest brush size you can use is 0.12m (12cm) and it is not restricted to grid lines or intersections.

See Ground Brush Resolution for more details.

Sorry about the delay in responding.

The route I'm working on was upgraded to HD. My brush sizes are selectable down to 0.12m, but the response time is laughable, literally counting 3 or 4 seconds before I see the result of the action. This was not the case before the update.

 

[pware]

The route I'm working on was upgraded to HD. My brush sizes are selectable down to 0.12m, but the response time is laughable, literally counting 3 or 4 seconds before I see the result of the action. This was not the case before the update.

To test this I just converted one of my larger routes from 10m Grid to HD Grid, set the brush size to 0.12m and used the Ground Height Brush set to Height Up. There was initially a slower response (less than a second, not 3 to 4 seconds). I changed the Sensitivity setting in the Tool Options Palette to 100% and the height change response time became normal (i.e. almost instantaneous).

What are your Performance Settings in the Trainz Settings from the Launch window?

Mine are:-

Shadow Quality: High
Shader Quality: Standard
Texture Detail: Normal
Post Processing: High
Water Quality: High
Scenery Detail: Clutter + TurfFX
Antialiasing: 4x

PhysX is ON
Process objects behind camera is ON

 

[pepperref]

To test this I just converted one of my larger routes from 10m Grid to HD Grid, set the brush size to 0.12m and used the Ground Height Brush set to Height Up. There was initially a slower response (less than a second, not 3 to 4 seconds). I changed the Sensitivity setting in the Tool Options Palette to 100% and the height change response time became normal (i.e. almost instantaneous).

What are your Performance Settings in the Trainz Settings from the Launch window?

Mine are:-

Shadow Quality: High
Shader Quality: Standard
Texture Detail: Normal
Post Processing: High
Water Quality: High
Scenery Detail: Clutter + TurfFX
Antialiasing: 4x

PhysX is ON
Process objects behind camera is ON

Mine are:

Shadow Quality: High
Shader Quality: Extreme
Texture Detail: Normal
Post Processing: Low
Water Quality: Low
Scenery Detail: Off
Antialiasing: 8x

PhysX is OFF
Process objects behind camera is ON

 

[pepperref]

Mine are:

Shadow Quality: High
Shader Quality: Extreme
Texture Detail: Normal
Post Processing: Low
Water Quality: Low
Scenery Detail: Off
Antialiasing: 8x

PhysX is OFF
Process objects behind camera is ON

Here's a video to show what I mean.

 

[pware]

Here's a video to show what I mean.

The video is labelled "Private" and will not run.

Try changing your performance settings to match mine starting with setting the Shader Quality to Normal to see if that makes a difference. Then the Antialiasing to 4x and check again.

 

[jaur1]

The video is labelled "Private" and will not run.

Try changing your performance settings to match mine starting with setting the Shader Quality to Normal to see if that makes a difference. Then the Antialiasing to 4x and check again.

This 3 seconds lag with height brush is a bug which happens only in last update, and has nothing to do with game settings. I went back to build 123794, where I work with HD 0.5 m brush 1% sensibility without any problem, and exactly the same settings I had when I updated.

 

[JCitron]

This 3 seconds lag with height brush is a bug which happens only in last update, and has nothing to do with game settings. I went back to build 123794, where I work with HD 0.5 m brush 1% sensibility without any problem, and exactly the same settings I had when I updated.

Report the bug here with as many details as you can and include a link to a working video. If you use Google Drive or One Drive, use that for the video and that will allow you to upload your route to N3V's QA Team to take a look if they have to.

Trainz Bug Report

Turn data collection into an experience with Typeform. Create beautiful online forms, surveys, quizzes, and so much more. Try it for FREE.

n3vgames.typeform.com