Lock-up problem back in 116678

[JCitron]

Alright....let me try to make sense of this. I have purchased tr2022 but have not installed it yet. Just now, I loaded up Tr2019. Without opening any route, I looked at the log files (which I had earlier deleted). Things just scrolled by unmercifully. A ton of obsolete things....textures, all kinds of assets, train cars, etc. What I am thinking of doing is deleting TR2017 and 2019 and then installing 2022. I know that I am going to lose a bunch of work, but if I can get a system that is running w/o all of these lockups, it will be worth it. I am not going to import ANYTHING from the previous Trainz. What are your opinions and or ideas about this?

Make a backup of your TRS19 data-folder first to be on the safe side.

Install a fresh install of TRS22. This will create a new data-folder.

Test it and if it works, then you're all set.

Just for kicks, change the install path to your current TRS19 data-folder. (It'll run a DBR) and test that.

If all works, then there was something wrong with TRS19.

 

[autodctr]

Tr2017: deleted. Tr2019: deleted. ALL data deleted: nothing saved. (Few tears shed.) 2022 installed. NOW.....how do I make sure that what I d-l is not going to be too old and throw errors and make log file go bonkers??? I do not want to get the same problem as before. PLEASE tell me what I can and cannot d-l!

Thank you all for being patient with me........if I had not already purchased 2022, I would probably be gone for good.

 

[autodctr]

17 and 19 deleted.....no backups made or kept. Fresh install of 2022. Nothing downloaded. Started making a new route.....CTD about 20 minutes later. This just a small part of my log file.

! <NULL> : TrainzAssetAccessorCached::OpenAssetFileForReading> missing file: config.chump
+ <kuid:887994:100007> : <kuid:887994:100007> submitted
? <kuid:887994:100005> : TADDeleteAsset
+ <kuid:887994:100005> : <kuid:887994:100005> deleted
+ <kuid:887994:100006> : <kuid:887994:100006> reverted
+ <kuid:887994:100007> : <kuid:887994:100007> reverted
; <NULL> : GSRouter:one(), 4 outstanding node(s)
? <NULL> :
? <kuid2:506034:4357298:5> : MeshResource::LoadResource> <kuid2:506034:4357298:5> | arc:arc:fld:$(builtin)/||971.tzarc||content/kuid2 506034 4357298 5.tzarc|
? <NULL> : Loading mesh summer/track_lod0.trainzmesh
! <kuid2:506034:4357298:5> : Index buffer contains degenerate triangles
? <kuid2:276266:100500:4> : MeshResource::LoadResource> <kuid2:276266:100500:4> | arc:arc:fld:$(builtin)/||1004.tzarc||content/kuid2 276266 100500 4.tzarc|
? <NULL> : Loading mesh wheels_body/wheels_body.trainzmesh
! <kuid2:276266:100500:4> : Index buffer contains degenerate triangles
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
; <NULL> : GSRouter:one(), 4 outstanding node(s)
? <kuid2:276266:100001:7> : MeshResource::LoadResource> <kuid2:276266:100001:7> | arc:arc:fld:$(builtin)/||1004.tzarc||content/kuid2 276266 100001 7.tzarc|
? <NULL> : Loading mesh k4_body/k4_body_mid.trainzmesh
! <kuid2:276266:100001:7> : Index buffer contains degenerate triangles
? <NULL> : Loading mesh k4_body/k4_body.trainzmesh
! <kuid2:276266:100001:7> : Index buffer contains degenerate triangles
? <kuid2:276266:100001:7> : MeshResource::LoadResource> <kuid2:276266:100001:7> | arc:arc:fld:$(builtin)/||1004.tzarc||content/kuid2 276266 100001 7.tzarc|
? <NULL> : Loading mesh k4_night/k4_light_beam.trainzmesh
! <kuid2:276266:100001:7> : TrainzMeshFile_Load> no valid chunks (k4_night/k4_light_beam.trainzmesh)
- <NULL> : VE242: Unable to load animation file 'anim.kin' (file not found, or is damaged).


Can someone plase tell me what is going on??

 

[JCitron]

Well, the log file says nothing outstanding or outlandish that I can see.

My gut says it's a system problem somewhere and not Trainz at all since this is a fresh install with nothing outside of the bog standard install.

Are all your drivers up to date?

Have you tried SFC /SCANNOW to check the integrity of your Windows files?

Have you run chkdsk /f from command prompt? (You'll need to restart to start the scan).

What about system temperatures?

Try memtst86 to test your RAM?

How's your power?

A glitchy power supply will get a bit cranky under load and drop a rail causing things like this. Trainz is very GPU intensive and when the GPU draws more current, the power supply works harder.

Just some things to try.

 

[autodctr]

Well, the log file says nothing outstanding or outlandish that I can see.

My gut says it's a system problem somewhere and not Trainz at all since this is a fresh install with nothing outside of the bog standard install.

Are all your drivers up to date?

Have you tried SFC /SCANNOW to check the integrity of your Windows files?

Have you run chkdsk /f from command prompt? (You'll need to restart to start the scan).

What about system temperatures?

Try memtst86 to test your RAM?

How's your power?

A glitchy power supply will get a bit cranky under load and drop a rail causing things like this. Trainz is very GPU intensive and when the GPU draws more current, the power supply works harder.

Just some things to try.

Drivers uo to date. PSU in good condition. GPU and CPU temps never above 55 C. Memtest has been run with no issues found. Will do the other 2 suggestions and report back.

 

[autodctr]

(fingers crossed) So far, so good. I did not see any obvious problems, but it has been running good so far today.

 

[autodctr]

Shortly after that last post, I reopened Trainz2022. Brought the route up. Went a got a cup of coffee. Was away for about 3 minutes. Came back: game was locked. Mouse would move but couldn't click on anything. I have 2 monitors: Trainz start screen opens on secondary monitor. Route opens on primary monitor. What was interesting was that I could do anything that I wanted on the secondary monitor: email, web, solitaire. Trainz remained locked and I had to use the 3 finger salute to close it. Reopened Trainz and it has been good, but I have been building a lot on the route. I did leave it one time, just to try it, for about 5 minutes and it stayed running.