alfredo_20
Active member
For me it was 189 seconds. I tested my route and didn't find any problems with the track objects. Great job guys!
Trainz Plus Beta SP5 Hotfix - 128907
- Thread starter n3v_laurence
- Start date
- Status
n3v_laurence
Moderator
Thank you again everyone. For the next TrainzUtil command, please test "repairdatabase patcher"
There will be one last TrainzUtil command to check in the next few days.
- Start Trainz to the launcher.
- Click "Trainz Settings".
- Select the Dev tab.
- Switch on "Enable advanced debug tools".
- Close Trainz Settings.
- Exit Trainz entirely.
- Open Trainz to the launcher.
- Developer > "Run TrainzUtil Command…"
- Type the following command and then press enter:
repairdatabase patcher
There will be one last TrainzUtil command to check in the next few days.
Ran the above Trainzutil command and it took 63 seconds to complete.
Then I started up Trainz from Launcher and observed an EDBR taking place silently behind the scenes via "Show Client logs" command...
Did you see this too, @pware?
Have not been able to run any tests so far whilst this EDBR is running.
Still going here - Appears to be looping on this (with fans and CPU running hard):
Getting invalid response to login attempt on Planet Auran cache
May need to terminate this process to protect my PC...
Then I started up Trainz from Launcher and observed an EDBR taking place silently behind the scenes via "Show Client logs" command...
Did you see this too, @pware?
Have not been able to run any tests so far whilst this EDBR is running.
Still going here - Appears to be looping on this (with fans and CPU running hard):
Getting invalid response to login attempt on Planet Auran cache
May need to terminate this process to protect my PC...
Last edited:
Did not notice the EDBR and did not check the logs. I was able to run tests as soon as the Trainz Util command terminated.
WestSideRailways
Active member
ran repairdatabase patcher
took 46 seconds.
Started Trainz, took about 30-40 seconds for the environment to load.....selected route/my content....
3 of my routes showed RED "!".... for about 30-40 seconds then the RED"!" disappeared. opened a route and laid some track without any problems.
took 46 seconds.
Started Trainz, took about 30-40 seconds for the environment to load.....selected route/my content....
3 of my routes showed RED "!".... for about 30-40 seconds then the RED"!" disappeared. opened a route and laid some track without any problems.
I can reliably repeat my above experience. The (not so silent) EDBR after running the repairdatabase patcher command (which completes within 63 seconds) and then starting the simulator from the Launcher to the main splash menu runs indefinitely in the background and utilises all CPU cores at their maximum allowable frequencies.
Appears to hang on one or more processes. Typically, validation of locally obsolete assets...
The only way I can stop it is to exit the main menu and return to the Launcher. Whilst I can access routes and sessions, the performance is sapped by the EDBR taking up most of the processors' capacity.
Once stopped, I can run a simple DBR from the Dev menu in Launcher, and then start the application from the Start Trainz button without initiating yet another background client refresh/ EDBR.
Appears to hang on one or more processes. Typically, validation of locally obsolete assets...
The only way I can stop it is to exit the main menu and return to the Launcher. Whilst I can access routes and sessions, the performance is sapped by the EDBR taking up most of the processors' capacity.
Once stopped, I can run a simple DBR from the Dev menu in Launcher, and then start the application from the Start Trainz button without initiating yet another background client refresh/ EDBR.
WestSideRailways
Active member
Just had a look thru the logs and noticed for the first time that the KUID are coloured Purple.
Don't know if that means anything.
About 98% of the log is taken up by .....Skipping validation as asset is locally obsolete.
Don't know if that means anything.
About 98% of the log is taken up by .....Skipping validation as asset is locally obsolete.
IsambardKingdomBrunel
Joined June 2001
Ran the command twice, first one took 23 secs, the second one 50 secs.
Same as WestSideRailways, most of the log reported skipping validation...................
Mike.
Same as WestSideRailways, most of the log reported skipping validation...................
Mike.
I think the testing here is after you run the database repair command and not so much the command itself. They believe they have fixed the bug that caused the problem in SP5 and now they want to see if the fix broke something else. Just continue to use the beta as you would normally and if something doesn't work as expected report it here. 
alfredo_20
Active member
74 seconds with no problems!
Everything is working fine!
Good job team!
Everything is working fine!
Good job team!
n3v_laurence
Moderator
I've tried to summarise your comments, but there is are a few things that are unclear. After running the "repairdatabase patcher" TrainzUtil command the following things happen:
- Command completes
- You click on "Start Trainz"
- (Please correct or confirm any of the following steps)
- Window opens, and see loading screen(?) running indefinitely (using all resources) - or does the main menu show the 3D Train and menu options?
- Trainz logs show stuck at validation of locally obsolete asset as last entry
- You then close main menu
- Comments indicate you can access Routes and Sessions (assuming this is via Content Manager)
- EDBR is running - is this after closing main menu, is it triggered by clicking on Start Trainz again or something else?
- You manually start a regular DBR to prevent repeated EDBRs from running - I'm assuming when you click on Start Trainz. (please confirm this)
Following run; TrainzUtil.exe repairdatabase patcher
Command completes (63s)
I click on Start Trainz in Launcher.
Window opens (slowly) as there is a silent EDBR/ client refresh going on in the background, which I reveal by invoking 'Show client logs'.
It lasts indefinitely. Last record revealed by 'Show client logs' is often relating to validation of locally obsolete assets, but this is likely not the culprit thread/ process it is actually hanging on...
I'm not sure what the 'patcher' parameter actually does when we run TrainzUtil.exe 'repairdatabase patcher', but it certainly upsets my 119Gb UserData dataset, which was previously up-to-date and in relatively good order. (Can you please elucidate?)
It is not outlined in the Wiki for TrainzUtil.exe which does not yet cover TRS22.
The only way I found I could reliably terminate the indefinite EDBR (without it restarting) was to exit to Launcher and wait for activity to stop. Running a basic DBR from the Dev Menu, and only then opening Trainz normally, seemed to stop the client refresh from recurring.
Hope this clarifies my report and experience.
Last edited:
IsambardKingdomBrunel
Joined June 2001
I knew that already was just adding my fourpence worth buddy.I think the testing here is after you run the database repair command and not so much the command itself. They believe they have fixed the bug that caused the problem in SP5 and now they want to see if the fix broke something else. Just continue to use the beta as you would normally and if something doesn't work as expected report it here.
n3v_laurence
Moderator
How long did you allow the indefinite EDBR to run before trying to terminate it?
Somewhere between 20 and 30 minutes of threshing fans and overheating cores - i.e. much longer than ANY previous EDBR has ever taken (me).
I replicated the experience as mentioned above. Each time it became clear that it was stuck on some intractable process, it was time to terminate the 'repair'.
My UserData folder for this beta build has about 119Gb of files and folders. It (and the Trainz program) is on a Samsung 990 Pro NVMe 4.0 2Tb drive.
I'm running Windows 11 with 32Gb of DDR4 RAM and use an RTX-3070 on this particular rig.
An Extended DBR on a similar-sized UserData folder on the non-beta version of TRS22 Plus, build 128486 ( Same rig, but on a different and slower SSD) takes just 426 seconds or 7.1 minutes.
It appears that something in the TrainzUtil repairdatabase patcher variable is triggering a change to the validation treatment of one or more assets in the Client Refresh that automatically occurs when restarting the Trainz engine (sic) following the 'patcher' run.
Suffice to say, I'm reluctant to test that particular command switch again in 128907.
I replicated the experience as mentioned above. Each time it became clear that it was stuck on some intractable process, it was time to terminate the 'repair'.
My UserData folder for this beta build has about 119Gb of files and folders. It (and the Trainz program) is on a Samsung 990 Pro NVMe 4.0 2Tb drive.
I'm running Windows 11 with 32Gb of DDR4 RAM and use an RTX-3070 on this particular rig.
An Extended DBR on a similar-sized UserData folder on the non-beta version of TRS22 Plus, build 128486 ( Same rig, but on a different and slower SSD) takes just 426 seconds or 7.1 minutes.
It appears that something in the TrainzUtil repairdatabase patcher variable is triggering a change to the validation treatment of one or more assets in the Client Refresh that automatically occurs when restarting the Trainz engine (sic) following the 'patcher' run.
Suffice to say, I'm reluctant to test that particular command switch again in 128907.
I guess I will need to give up on these later updates as they are broken, After hours of trial and error of looking for the possible asset issues there are none to be found. What has happened is that these later builds have broken many of the builtin and the asset scripts as this has happened many times in the past with updates. Seems the more that N3V do updates the more they break and cause poor performance. 
This is not a PC issues the humping animations are very obvious on a large map with a lot of assets in one area. The humping animations are also in the asset pick windows as they turn.
The Trainz build 122411 has none of these issues, all of these later builds have caused the builtin script issues that I can log, but can not repair or update.
Kind regards.
This is not a PC issues the humping animations are very obvious on a large map with a lot of assets in one area. The humping animations are also in the asset pick windows as they turn.
The Trainz build 122411 has none of these issues, all of these later builds have caused the builtin script issues that I can log, but can not repair or update.
Kind regards.
Jon,I guess I will need to give up on these later updates as they are broken, After hours of trial and error of looking for the possible asset issues there are none to be found. What has happened is that these later builds have broken many of the builtin and the asset scripts as this has happened many times in the past with updates. Seems the more that N3V do updates the more they break and cause poor performance.
This is not a PC issues the humping animations are very obvious on a large map with a lot of assets in one area. The humping animations are also in the asset pick windows as they turn.
The Trainz build 122411 has none of these issues, all of these later builds have caused the builtin script issues that I can log, but can not repair or update.
Kind regards.
This thread is in regards to a beta version meant for testing the patching process and not the fully released version.
n3v_laurence
Moderator
Thank you for all your feedback, as we have a new Trainz Plus Beta available, this thread is now locked.
Please post comments on the new thread.
The 4th TrainzUtili command will be asked to be tested in the new thread once the update has been confirmed that no new issues have been introduced.
Please post comments on the new thread.
The 4th TrainzUtili command will be asked to be tested in the new thread once the update has been confirmed that no new issues have been introduced.
- Status