[James Ross]

Csantucci, on 15 December 2013 - 07:02 AM, said:

That's great James, :wallbash: To achieve perfection and even more, could you insert the version number in the link name too? :(

Done.

[Csantucci]

Thanks James, now it's really very comfortable to use and also monkey proof.

[Gehe]

Hi All,

since some tine I use the Large Address Aware Feature as described in the Forum just by renaming the executable RunactivityLAA to Runactivity and of course saving the executable Runactivity.
(OS Win 8.1 64-bit)

Now I had a look into the log file to identify missing rolling stock in an activity and saw by chance that the Parameter "Uselargeaddressaware" was "false" (newest build X.2242). Does OR not use the LAA feature or is this just a fault in the logfile.

What are your observations here?


Regards
Gehe

[Lutz_s]

Gehe, on 18 May 2014 - 04:27 AM, said:

by renaming the executable RunactivityLAA to Runactivity and of course saving the executable Runactivity.

Hi Gehe,

you don't have to rename the executable. In recent versions of Openrails exists a button which allows to select, which runactivity should be used. It's on the experimental tab listed at the bottom. I would guess the log file tells you that this button is not selected, nothing else. But as you have renamed the runactivityLAA you get the large adress range. I have this switch selected and i have

Quote

UseLargeAddressAware = (user set) True

in my log file.

Regards Lutz

[dforrest]

You will find that if you do not set the option to which Lutz refers, your system is set back to using the non-LAA version whenever you update the OR version.

------------
David

[Gehe]

Hi Lutz_s, dforrest


thanks for your hints, now I use the switch, the Parameter is "True"
and there is no more need for the annoying renaming procedure after every update.


Regards

Gehe