Trainz Plus Beta SP5 Hotfix - 128907

[n3v_laurence]

Hello Everyone,

As most of you are aware, there was an issue with DLS and locally installed splines which caused an error when trying to place trackside objects. We have a Hotfix for this issue with build 128907.

This build has a fix for the Extended Database Repair process that was identified as the cause of the fault.

To ensure the patch is fully tested, we ask that everyone install some DLS and locally installed track spline assets using build 128486. Once these assets are installed, please run an Extended DBR.

• Steps to Run an Extended DBR

1. Start Trainz Launcher
2. On the launcher, click on the developer on the top of the screen
3. Hold down the CTRL key
4. Left click on Rebuild Database

Once the Extended DBR has completed, confirm that DLS and locally installed splines are reproducing the incompatible spline issue again.

• Steps to test DLS & locally installed splines

1. Start Trainz
2. Create a new route
3. Place down DLS or locally installed track splines
4. Attempt to place trackside assets on the track splines from step 3
5. Observe: Incompatible Spline Error (top right)
6. Save the route

After corrupting the assets with the Extended DBR and confirming the issue reproduces, please patch to 128907 on the Trainz Plus Beta update stream.

Please first retest the save route by re-attempting step 4, then repeating the first 5 steps. Then resume testing any of your unique routes and assets.


Change log (128486 to 128907)

• [Fix] Extended Database Repair asset corruption

INSTALLING & PATCHING:

For Trainz Plus Beta via the Trainz Plus Beta Stream
Trainz Store Only:

PC: Requires Trainz Plus 128486 (PC). This is a small patch 20 MiB for build 128907

Please use https://n3vgames.typeform.com/to/xRdryu to report any bugs or issues found regarding any ongoing incompatible spline issue or asset corruption due to the EDBR.

 

[zatovisualworks]

An N3V Dev team hotfix is expected (or desired) (or welcomed) (or advisable) (or essential) (or compulsory).

 

[pware]

To avoid any possible confusion and "Why can't I get the patch" posts ...

This Patch is on the Trainz Plus Beta Stream, not on the normal (non-beta) Trainz Plus or TRS22 streams.

You have to have your Trainz Plus Trainz Settings --> Install --> Update Stream set to Trainz Plus Beta

Otherwise wait until the beta testing has been done and the patch is released for the non-beta (mere mortal) users.

 

[n3v_laurence]

To avoid any possible confusion and "Why can't I get the patch" posts ...

This Patch is on the Beta Stream, not on the normal (non-beta) TRS22/Trainz Plus stream.

You have to have your Trainz Settings --> Install --> Update Stream set to Trainz Plus Beta or TRS22 Beta

Otherwise wait until the beta testing has been done and the patch is released for the non-beta (mere mortal) users.

It is currently only on the Trainz Plus Beta update stream. It is NOT on the TRS22 Beta stream.

 

[pware]

It is currently only on the Trainz Plus Beta update stream. It is NOT on the TRS22 Beta stream.

Thanks for that. Post edited.

 

[pware]

I can confirm that the patch works on newly installed DLS track.

 

[wreeder]

Ok, Patch appears to be successful.
I downloaded Pencil42's new track into build Trainz Plus 128486 (PC)
Run an EDBR to undo the Trainzutil fix that had been applied.
Created a new route in Trainz Plus 128486 (PC) and attempted to place signals on the newly downloaded track and got the error. Saved the route.
Applied hot fix patch.
Started new version and opened route I had saved above and was now able to place trackside objects.
Created a new route in this build and was able to use the newly downloaded track and place trackside objects with no errors.

Bravo, Dev Team.

 

[PC_Ace]

Reproduced the issue in the previous Build 128486 to confirm that the EDBR does indeed cause the incompatible spline error.
Applied the hotfix patch and observed that the silent DBR following application also takes a very long time to complete (Is it in fact an EDBR?) Similar to my experience with the SP5 update patch.
My first EDBR took 457 seconds (i.e. a longish time on my machine). The silent EDBR took much longer, tripping up on validating assets that are locally obsolete.
Still waiting for that to complete to allow me to continue my testing - and deliberately invoke another EDBR as per the instructions above...

Edit Update: Subsequent deliberate EDBR took a relatively 'normal' 341 seconds to complete.
Ran Trainzutil.exe Prebuild to precache newly installed assets. It re-cached all in any event as it does following an EDBR.

Verified that the hotfix patch has resolved this issue satisfactorily. Congrats!

 

[JCitron]

I can confirm the patch is successful. Good job, Brew Crew!

 

[n3v_laurence]

Thank you to all those who have tested the hotfix build 128907. As the extended database repair fault appears resolved, we would like to take the time to test out additional database repair commands using the TrainzUtil.

Please test the TrainzUtil command "repairdatabase"

1. Start Trainz to the launcher.
2. Click "Trainz Settings".
3. Select the Dev tab.
4. Switch on "Enable advanced debug tools".
5. Close Trainz Settings.
6. Exit Trainz entirely.
7. Open Trainz to the launcher.
8. Developer > "Run TrainzUtil Command…"
9. Type the following command and then press enter:
   repairdatabase
   

After running the TrainzUtil command, please retest the previously saved test route and then continue to use your unique databases and report if any new issue arises.

Please also keep an eye out on this post, as in a few days I will post another TrainzUtil command to test out.

 

[PC_Ace]

Thanks for this update @n3v_laurence.
Running repairdatabase from trainzutil.exe appears to be a standard DBR and not an EDBR. Is that your impression too? (No issues, BTW).

 

[n3v_laurence]

Thanks for this update @n3v_laurence.
Running repairdatabase from trainzutil.exe appears to be a standard DBR and not an EDBR. Is that your impression too? (No issues, BTW).

That would be correct. The next trainzutil command will be extended. I'll request and update the steps over the weekend for that. In the mean time, please just use the database and be sure there are no newly introduced issues.

 

[WestSideRailways]

TrainzUtil Command <repairdatabase> run without any problems.

 

[wreeder]

Command repairdatabase ran and everything appears to be working as expect.

 

[alfredo_20]

Same here! No problems during de database repair

 

[JCitron]

Same here. No issues running the DBR.

 

[n3v_laurence]

Thank you everyone, for the next TrainzUtil command, please test "repairdatabase extended"

1. Start Trainz to the launcher.
2. Click "Trainz Settings".
3. Select the Dev tab.
4. Switch on "Enable advanced debug tools".
5. Close Trainz Settings.
6. Exit Trainz entirely.
7. Open Trainz to the launcher.
8. Developer > "Run TrainzUtil Command…"
9. Type the following command and then press enter:
   repairdatabase extended

After running the TrainzUtil command, please retest the previously saved test route and then continue to use your unique databases and report if any new issue arises.

Keep an eye out on this post, as in another few days, I will also post another TrainzUtil command to test out.

 

[G.M.]

Done the extended one
6 errors and 23056 warnings
took 180seconds, cause i have only 12349 items installed
worked fine

 

[wreeder]

I've run the new command, I am able to attach trackside objects without an error on my test route.
I will continue to test this build.

 

[PC_Ace]

Running Trainzutile exe 'repairdatabase extended' took 549 seconds on my installation rather than the 22 seconds taken by the plain 'repairdatabase' but net result was the same - no additional spline errors noted following subsequent testing.