Background Running.

[JohnnyC1]

On build Trainz 22+128486 and previous builds and also the Pus Beta. I have noticed that when you think you have shut down/quit Trainz, from either content menu or the main menu, the process continues to run in the background. Sometimes, if you attempt to re-launch Trainz, the game will fail to execute. Open Windows Task Manager, background processes, and scroll amphiboly and check the instances of Trainz running. At present I have two background instances, the original and the second attempt to execute. The first instance has been running for about 2hrs.

Instance 1
CPU usage 8.00-11.00
MEMORY: 15389.6 MB
DISK: 0%
INERNET: 0

Instance 2
CPU usage 0.0%
MEMORY: 15.13 MB
DISK: 0%
INERNET: 0

Processor Intel(R) Core(TM) i7-14700K (3.40 GHz)
Installed RAM 64.0 GB (61.7 GB usable)
Graphics; RTX 4060
Install on 2TB SSD C: Drive : Drive
Data Disk 2TB SSD G

Thanks,
John

 

[pware]

Yes, this has always (as far back as I can recall) been the case with Trainz. Shutting down is not as simple as it is with many other apps. For example, depending on what you have been doing (editing in Surveyor or running driver) there is an open database that needs to be safely closed and this may involve writing out altered data records (assets), closing open records, etc.

It is important to remember that Trainz is actually a DBMS (DataBase Management System) and can have quite a large database (many, many installed assets) to deal with before it exits the OS work space. My rule is after exiting Trainz never immediately shut down the system or restart Trainz - I wait a few seconds (10+) before performing ether of those actions.

However, having the task running in the background for 2 hours is a bit much. Is there something else going on here? Is your AV program scanning Trainz or its database? Have you accidentally started a second copy of Trainz running in the background? This has happened to me and not just with Trainz but other apps as well.

 

[JohnnyC1]

Nothing running. AV turned off.

John

 

[Forester1]

Maybe something triggered a DBR?

 

[HPL]

To be sure Trainz really shuts down, I use a script that kills the process after a 15sec delay. Never had any issue.

 

[JCitron]

If you've recently installed a lot of content or a new version of Trainz, there's some content validation going on. That can take a while to stop before the program shuts completely down.

If I've started a second instance, I'll terminate the second one - the one that doesn't have any activity. Doing so won't cause any issues, but I have terminated the active one requiring a DBR when I started up the program again.