Again Thanks, John. I'm at a loss also, but you have experience this ? A question, do you ever remember this happening before the hotfix ? Again I'm not sure, but does seem to getting worse in my opinion. And just would like to know why, or what is causing the issue. Shutting down and restarting seems to be the only option, and I'm not convinced this is a fix
Always run full screen, expect when game does a reboot ? and default settings made
Matt
Hi Matt,
I did experience the same. I know exactly what you are talking about. Hours of work only to have it poof off into bit heaven when the desktop shows up!
The issue is actually better with HF2. At least I can work in Surveyor and even drive for much longer. In the HF1 release, I was looking at the desktop after only a few minutes. Yesterday I drove for 5 hours and only crashed my train when I hit a broken track segment that the AI told me was there because he wouldn't drive past it. I thought it was a direction mark issue and BOOM! I saw the ground and the message about derailing. I was also in Surveyor all day too before that and then an hour afterwards before I gave up for the night. The day before that, I was in there for 17 hours. Yup that's a marathon of Trainzing, and I wonder why I dreamt about it when I went to bed!
A reboot is recommended after the crash because the memory is scrambled. Let me explain... In the olden days of Windows, we would get a GPF - remember those? These were in fact a similar situation. In the old days, however, Windows didn't recover well and the machine would eventually crash or crash other programs imediately. What was happening was, and this maybe the issue now too but caused by many, many factors, is memory gets overwritten by mistake due to a coding error. Usually it's not the program that you are running now that causes the problem; what has happened, let's say for example you are running Internet Explorer. You browse the web then decide to run Trainz. Trainz will work until you do something that requires more memory. The problem is IE had left stuff in there and hadn't flushed completely out - like you know what in the drain. Trainz then runs and mixes this wrong stuff with its own data, gets confused and crashes.
The other issue too is sometimes another program could be running at the same time. This will then overwrite some memory that Trainz is using. Trainz doesn't know this occurred and then it reads in garbage, or stuff that doesn't quite add up to what it's supposed to be doing and that crashes the program. This was a common problem with old MS Word 2.0.
In the olden days, this would actually cause the computer to crash, but with Windows 7 and up, even XP could tolerate this, the computer could recover and keep operating. This now is a dual edged issue. Sure the computer keeps ticking, but the program memory cache is now messy. This means that if you try to run the same program that died before, you run the risk of crashing again because the data is really messed up. This can also affect other programs as well, and eventually cause them to crash.
Now, I'm not saying that T:ANE is completely innocent here either. It could be something that it's doing as well that can cause it to crash. This is why it's so difficult to find the problem and big tracing programs need to run at the same time which will write logs for the programmers to read over. (My eyes glaze over when I see this stuff!). The issue too could be some of the content we're using. Remember not all the content is all graphics and pretty stuff. There are tons and tons of scripts, driver commands, session add-ons, and so on, even interactive industries, signals and so on all are talking in the background. These too could have an issue. Perhaps one of the scripts is faulty? It could tell Trainz to go jump in the lake which it so kindly does. The problem is the content will show no faults because the errors are semantical, meaning they are spelled correctly but the meaning is wrong. It's like having a direction marker in the wrong direction on a route. We can spend hours looking for it, but can't see it because it's a direction marker where it should be, but the problem is it's facing the wrong way.
So HF2 does run better, after all this, but it's still wobbly. A save more than often is good and when it crashes, reboot.
John