Beware the hidden SP installer process

[Forester1]

Many of you are well aware of this, but for those that are not, once the SP installer says it is complete it all appears to go away and leave you at the desktop. However, there is still a background process running (Pretty sure this is a DBR), so TRS22 has not in fact, closed out but is still running. The only way to see it is to bring up task manager, set it to details on the left, and then scroll down until the TRS22 process appears. It has been running for several minutes on my machine, so I can't tell you how long it might take, but just be aware that there is a process running.
EDIT: Close to 30 minutes and still running. I am not going to sit here and watch, so won't know exactly how long it takes.

 

[blueodessey]

Many of you are well aware of this, but for those that are not, once the SP installer says it is complete it all appears to go away and leave you at the desktop. However, there is still a background process running (Pretty sure this is a DBR), so TRS22 has not in fact, closed out but is still running. The only way to see it is to bring up task manager, set it to details on the left, and then scroll down until the TRS22 process appears. It has been running for several minutes on my machine, so I can't tell you how long it might take, but just be aware that there is a process running.
EDIT: Close to 30 minutes and still running. I am not going to sit here and watch, so won't know exactly how long it takes.

Good Points Forester,

Especially in Windows which is running a slew of operations, Hard Drives and SSD Drives take time to catch with which is called Delayed writes to Disk.

 

[JCitron]

Very good points indeed.

I brought up a Client Logs window and watched the process until the buffer filled up then closed it. My process, which I also watched in Task Manager ran for another 8 hours on top of that, giving the grand total of 14 hours of rebuild time.

After that, this morning was spent cleaning up the mess for another 2 hours.

 

[blueodessey]

Very good points indeed.

I brought up a Client Logs window and watched the process until the buffer filled up then closed it. My process, which I also watched in Task Manager ran for another 8 hours on top of that, giving the grand total of 14 hours of rebuild time.

After that, this morning was spent cleaning up the mess for another 2 hours.

Well John,

Yesterday as I was getting my Train22 PE to open, it surprised me with a Patch Update of approx 13 Gigs, 128487 Version.

Took about 15 mins to download and install, which is not bad.

Only problem I had was about 611 Faulty assets, which, 1/2 I had recently downloaded, I ended up deleting 200, and the rest, fortunately for me, I could the revert to original from Modified Asset Operation. Spent about 2-3 hrs.

What I don't know is what the Patch fixed/updated. I need to find what this Version of 22 PE update does for me.

Everything else, my Routes are OK.

 

[JCitron]

Well John,

Yesterday as I was getting my Train22 PE to open, it surprised me with a Patch Update of approx 13 Gigs, 128487 Version.

Took about 15 mins to download and install, which is not bad.

Only problem I had was about 611 Faulty assets, which, 1/2 I had recently downloaded, I ended up deleting 200, and the rest, fortunately for me, I could the revert to original from Modified Asset Operation. Spent about 2-3 hrs.

What I don't know is what the Patch fixed/updated. I need to find what this Version of 22 PE update does for me.

Everything else, my Routes are OK.

The patch did fix a few nasty bugs leftover from the previous patches and fixes. Among the fixed things was the maximized window for driver setup and other rules such as the Schedule Library remaining stuck open.

What is annoying about this patch is the beta versions installed fine on my test database. Why did this one totally mess everything up if this was nothing more than the finalized version? My data is still messed up and I'll be at it a few days. I thought that the one faulty asset was it. Bah! I got fooled bigly this time.

 

[blueodessey]

The patch did fix a few nasty bugs leftover from the previous patches and fixes. Among the fixed things was the maximized window for driver setup and other rules such as the Schedule Library remaining stuck open.

What is annoying about this patch is the beta versions installed fine on my test database. Why did this one totally mess everything up if this was nothing more than the finalized version? My data is still messed up and I'll be at it a few days. I thought that the one faulty asset was it. Bah! I got fooled bigly this time.

Copy that Chief,

Keep your head low as nothing appears as it should be.

Guess will need some more Beta Testing.

Additional, Did you see this info on another Thread?

P

Post in thread 'Trainz Update Announcement (SP5)'

Jan 17, 2025

I have just created a new route, laid one piece of track and I can add trackside objects, but if I try to add trackside objects to any of my old routes (pre update) I get 'incompatible spline'.
Any suggestions please. I don't want to lose 13 years of work.

Yep. I'm getting that response too when I try to add a new signal to existing track. Affects speed boards too. Doesn't matter whether I use Surveyor 2 or Classic. Needs to be bug-reported. Likely to be related to the build version update. New routes are at v5.6 and your old routes before re-saving will be 5.5 or older.

• PC_Ace

 

[JCitron]

Copy that Chief,

Keep your head low as nothing appears as it should be.

Guess will need some more Beta Testing.

Additional, Did you see this info on another Thread?

P

Post in thread 'Trainz Update Announcement (SP5)'

Jan 17, 2025

I have just created a new route, laid one piece of track and I can add trackside objects, but if I try to add trackside objects to any of my old routes (pre update) I get 'incompatible spline'.
Any suggestions please. I don't want to lose 13 years of work.

Yep. I'm getting that response too when I try to add a new signal to existing track. Affects speed boards too. Doesn't matter whether I use Surveyor 2 or Classic. Needs to be bug-reported. Likely to be related to the build version update. New routes are at v5.6 and your old routes before re-saving will be 5.5 or older.

• PC_Ace

I did and posted a fix for the track issue. It works but it's yet another step we have to do. The good news is it's more prevalent now not like it was back in T:ANE when it first appeared.