Restoring saved game troubles

[geepster775]

If this folder gets crammed and has that much of an impact on the game there should be a mention of it somewhere.

The impact is only felt by people who operate a certain way using certain habits. I have no 'fear of crashes' carryover from MSTS days so I rarely use the save button and the only time I do is when I need to physically step away from the computer. The location chosen was a hidden folder originally so I don't think the intent of the developers was for everyone to be "going there" all that often. We users develop experience over time however that may contradict the original intent, and sharing solutions like this is what forums are for.

Automated saves, saving just for the hell of it with no real need, that some users are currently lobbying for, adding more file clutter, is one of those things that the current saved activity cache system is not really 'ready for primetime' for.

Holding [CTRL] and punching F5 brings up old Hud. Holding [CTRL] and [SHIFT] and punching F5 allows you to page through all the screens of the old hud. Brake info, Loco info, Force info, Dispatcher info, all those usual pages. Holding [CTRL] and punching F5 again makes old hud go away.

One minor correction, it is not the CTRL key, but rather the ALT key. The above paragraph should read

Holding [ALT] and punching F5 brings up old Hud. Holding [ALT] and [SHIFT] and punching F5 allows you to page through all the screens of the old hud. Brake info, Loco info, Force info, Dispatcher info, all those usual pages. Holding [ALT] and punching F5 again makes old hud go away.

[R. Steele]

One minor correction, it is not the CTRL key, but rather the ALT key. The above paragraph should read

Holding [ALT] and punching F5 brings up old Hud. Holding [ALT] and [SHIFT] and punching F5 allows you to page through all the screens of the old hud. Brake info, Loco info, Force info, Dispatcher info, all those usual pages. Holding [ALT] and punching F5 again makes old hud go away.

{Off Topic - apologies } There has been some postings about the AltF5 Hud key being too close to the AltF4 - Escape -- I've hit the wrong one by mistake. Of course, my fault...

[wwhall]

^Yes, I've done that several times, too. I may change the key assignment to something less likely to hit accidentally.

[eric]

Mod note: changed the title to something a little more descriptive than "getting sick of this" which helps nobody understand what the underlying issue really is...

[Kuckoo]

Automated saves, saving just for the hell of it with no real need, that some users are currently lobbying for, adding more file clutter, is one of those things that the current saved activity cache system is not really 'ready for primetime' for.

Reaching for the [F2] key every once in a while is too much effort for some, I guess.

Lost count on how many times I've cleaned the cache and roaming folders.

[Sleepy]

So cleaning out that folder didn't help. Happened again starting a fresh activity not from a save.

[derekmorton]

And if you want any help, we need a log file!

[slipperman]

Hi,
@Derek : Will has already posted two different log files, neither if which show anything relevant to his problem.

@Will : Have you checked out my suggestions in post #26??

Cheers,
Ged

[Sleepy]

Hi,
@Derek : Will has already posted two different log files, neither if which show anything relevant to his problem.

@Will : Have you checked out my suggestions in post #26??

Cheers,
Ged

I haven't tried swapping USB slots yet. I'll get back to you on that and let you know how it goes. As a side note even though the update didn't fix the problem I am glad you guys talked me into it. I absolutely love the way the signals look now and the best thing for me is that it seems to handle memory much better.

[Sleepy]

I'm done with this. I'm going back to the original MSTS. I have absolutely had it with not being to make any changes to engines or signals or anything else without being able to check it since the keyboard controls only work half the time. MSTS may crash alot but at least the control always work. Maybe when someone is asking for help for MSTS the guys that always answer with "why aren't you using OR" can take a look at this post first.

[slipperman]

Hi Will,
If your keys work correctly for MSTS, then, maybe it's some Open Rails setting which is upsetting your PC.
I see you're running Windows 7 Pro 64 bit. If so, why are you running RunActivityAA.exe and not RunActivity.exe?
When a user is having problems which nobody else is, it's not something others can help with because it's usually something 'local'.
Maybe you're running other programs at the same time as Open Rails - it doesn't matter so much with MSTS because OR is more demanding. Your graphics system is an entry level card and may be struggling to keep up with what you're asking it to do. Try setting the viewing distance to the default of 2000 instead of 3000.

By the way, I am, mainly, an MSTS user but occasionally run Open Rails

Cheers,
Ged

[Sleepy]

The RunActivityAA is the large address aware version correct? What would be the benefit of limiting its use of extra available memory? I've had the viewing distance at 2000 before. No difference. I upped it after getting this card. I don't think the video card is struggling as I've seen the FPS range from 150-200 with vertical sync off. As for background programs I don't have anything extra running. It's just so frustrating since I have no keyboard issues on anything else. And now seeing the task of having to go through every consist and activity to eliminate OR only stuff, having routes and rolling stock I paid for and can't use and just stepping backwards from OR when its such a dramatic improvement from MSTS just makes me want to ditch everything all together.

[R. Steele]

I've re-read the thread...originally this was the problem:

Could somebody please explain to me why when i restore a saved game there are several keyboard functions that will not work. Mostly the throttle. The escape key and F keys will all still function.

You have updated the version you use...correct? So to be sure...

1. Which OR version are you currently using?
2. SPECIFICALLY...which keyboard functions do not work? (Throttle is normally the A and D keys.)
3. Have you checked your key assignments Options tab -- Keyboard.
4. Please attach a current OR log.
5. It has been documented that some programs "grab" keys and interfere with other programs...there are programs to check to see if there are conflicting key assignments.

[geepster775]

Awhile back, I ran into a unique problem in Open Rails where trains would behave like they were hitting a bumper post upon coming to any curved track. I spent about 4 days trying to diagnose it, thinking of all the possibilities. I asked here if anybody was seeing the same phenomena and nobody replied in the affirmative. I was on my own.

I then shut the PC down, detached the cables from my OS disk, hooked up another disk with another copy of the same version OS already loaded, ran the same Open Rails app (the OR app and route content is on a separate SSD, so nothing there changed) and the problem was non-existent when the other OS platter was active. That told me something was probably mucked up with the OS/Win Updates process on the original disk. I wiped that bad copy of OS right down to removing partitions, reinstalled the OS fresh, applied all re-bundled patches in one swoop that had been previously applied monthly over many years and bring the OS up to the current date, reinstalled all my usual daily use productivity apps, and everything with OR worked once again.

Proving the problem was not Open Rails, but actually something OS/WinUpdate or unknown browser-acquired virus related that clearly stomped on some critical files needed by Open Rails to function properly. It took me about 24 hours to recover the freshly rebuilt OS drive.

If I had known better, I could have exercised seniority privilege and asked other people to solve my problem that was solvable only by me, believing that I was too old to have to "go there" and worry about reinstalling an OS after 10 years of monthly updates, or that as a pensioner I couldn't afford a new computer or even a separate disk drive to prove my hypothesis with the old computer. I, too, could have probably retreated back to MSTS and in order to claim the problem didn't exist there, and that all my OR investment would now be lost.

But I liked my fix better.

[crstagg]

Awhile back, I ran into a unique problem in Open Rails where trains would behave like they were hitting a bumper post upon coming to any curved track. I spent about 4 days trying to diagnose it, thinking of all the possibilities. I asked here if anybody was seeing the same phenomena and nobody replied in the affirmative. I was on my own.

I then shut the PC down, detached the cables from my OS disk, hooked up another disk with another copy of the same version OS already loaded, ran the same Open Rails app (the OR app and route content is on a separate SSD, so nothing there changed) and the problem was non-existent when the other OS platter was active. That told me something was probably mucked up with the OS/Win Updates process on the original disk. I wiped that bad copy of OS right down to removing partitions, reinstalled the OS fresh, applied all re-bundled patches in one swoop that had been previously applied monthly over many years and bring the OS up to the current date, reinstalled all my usual daily use productivity apps, and everything with OR worked once again.

Proving the problem was not Open Rails, but actually something OS/WinUpdate or unknown browser-acquired virus related that clearly stomped on some critical files needed by Open Rails to function properly. It took me about 24 hours to recover the freshly rebuilt OS drive.

If I had known better, I could have exercised seniority privilege and asked other people to solve my problem that was solvable only by me, believing that I was too old to have to "go there" and worry about reinstalling an OS after 10 years of monthly updates, or that as a pensioner I couldn't afford a new computer or even a separate disk drive to prove my hypothesis with the old computer. I, too, could have probably retreated back to MSTS and in order to claim the problem didn't exist there, and that all my OR investment would now be lost.

But I liked my fix better.