Load error for routes not being used and no throttle setting display

[Claude Debnam]

I'm using .1771. I get a load error message in the Menu for routes not being used and stored by train store and there are no throttle setting display. I do get the dynamic setting display.

[Claude Debnam (c-debnam)]

When using my rail driver is when I have no throttle settings indication. The train and engine brake will not respond either. When I switch to the keyboard everything works as it should.

[Bill Currey (wjcurrey)]

Committed X1775 for fix throttle settings indication. See discussion at http://www.elvastower.com/forums/index.php?/topic/22697-alerter-problems-again-and-minor-cabview-problem/page__gopid__130499#entry130499 for details.

AFAIK OR dose not support uncompromising of files for train store. The files have to be completely by train store to be loaded by OR. Train store is for MSTS not OR

[Claude Debnam (c-debnam)]

Basically what I'm saying is that before .1771 came out the menu did not show routes that were not unstored. It now does this and gives the load error. I'm not saying that train store is for OR as I know that it's not. I'm saying that with the latest updates the menu is behaving differently that before.

[Bill Currey (wjcurrey)]

The clarification changes the picture. X1771 only changed one line of code for the raildriver, which only modifies the RunActivity.exde. The last changes to Menu.exe which was X1769 (X1770 = X1769 since it was not compiled). Were you running a version prior to X1769 ? Suspect that X1769 is causing your problems not X1771 .

[Claude Debnam (c-debnam)]

All version after .1771 have done the same. I'll try 1777 when I get home from work.

[Bill Currey (wjcurrey)]

Version 1777 will do the same thing for the Menu as 1771. The real question is X1769 or what prior version worked. As indicated 1771 made no explicit changes to Menu.exe but X1769 did

[Cédric GNIEWEK (sharpeserana)]

Does the problem still happen with version 1.4?

[Derek Morton (derek-a)]

All routes must be unstored before OR runs.

This is not an OR bug, its a procedure issue