[JorD1]

A little trick I tried on OR allowed me to use more than 2GB ram.



I tested it with a very heavy route (TRAT321), on the "normal" OR version it crashed in many places, in the modded version works fine.
(Above is with the same visibility settings, lower visibility <1000 worked on standard OR too)

How this trick works:
1. Download and install CFF explorer.
2. In CFF explorer open RunActivity.exe
3. In the left window find File Header and click it.
4. In the right window find Characteristics and click on "Click Here"
5. A new window opens, tick the box before: "App can handle >2GB adress space"
6. Click OK
7. Under File choose SAVE.

DO NOT forget to backup the runactivity.exe first.
Only bug I OR I found after this is that the F5 hud RAM counter will do strange if more than 2 gb is used. (Saying negative or no numbers)

I had it just over 3gb ram doing some test with visibility at 5km on the TRAT321 in prague region.

Cheers Jordi

Edit: Video showing how CFFexplorer and this trick works.


Edit 2: Is it possible to make OR large adress aware from the source. It has advantages in running heavy MSTS routes, otherwise you'll get an OutOfMemoryException.

[James Ross]

JorD1, on 14 December 2013 - 02:33 PM, said:

Edit 2: Is it possible to make OR large adress aware from the source. It has advantages in running heavy MSTS routes, otherwise you'll get an OutOfMemoryException.

It is not a supported configuration for .NET applications, so we cannot make the official versions with this flag. (The correct fix is to use an AnyCPU .NET build and a 64bit OS, but currently we can't do that for other reasons.) However, since I have been making automatically created builds, I can potentially include a specially modified executable people can try without having to use other tools.

[Csantucci]

Yes please! The amount of routes needing that to run well is increasing.

Referring to the automatic builds, it would be nice if inside the filename also the OR revision number could appear.

[James Ross]

Csantucci, on 15 December 2013 - 03:34 AM, said:

Yes please! The amount of routes needing that to run well is increasing.

Referring to the automatic builds, it would be nice if inside the filename also the OR revision number could appear.

The latest build on my site now includes a RunActivityLAA.exe that you can use in place of RunActivity.exe to get /LargeAddressAware support.

I have also added the version number to the downloaded file.

[Csantucci]

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

[JohnnyS]

Quote

That's great James, :wallbash:

Yeah, thanks very much for this and all the other improvements and fixes made by the development team.

[Gary54]

The described modification to the Runactivity.exe intrigues me as I have been working with some very resource intense routes. Given that I am running a 64 bit system, is using RunActivityLAA.exe simply a matter if changing the file name in the latest build to from RunActivityLAA.exe to RunActivity.exe, or are we to follow the procedure described at by JorD1 at the outset of this topic?

Many thanks.

Gary

[Csantucci]

Simply rename RunactivityLAA.exe to Runactivity.exe. That's all.

[Gary54]

Thanks very much for the quick response.

[James Ross]

Gary54, on 15 December 2013 - 11:51 AM, said:

Given that I am running a 64 bit system, is using RunActivityLAA.exe simply a matter if changing the file name in the latest build to from RunActivityLAA.exe to RunActivity.exe, or are we to follow the procedure described at by JorD1 at the outset of this topic?

Yup, just rename it and (because you're on a 64bit OS) you'll immediately get 4GB of virtual address space in OR instead of the usual 2GB. :wallbash:

[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