[NickonWheels]

Hi folks

I guess some know this problem too, the downloadable ORTS code when compiled with VisualStudio builds with only using 2GB of memory space, which causes it to crash even on not very object-intense routes, even if you have a 64-bit system. Official "unstable" ORTS versions use 4GB.

Did somebody have an idea on how a private version could work the same way (without any performance disadvantages) as the official versions?

[perpetualKid]

NickonWheels, on 05 April 2020 - 11:12 PM, said:

Hi folks

I guess some know this problem too, the downloadable ORTS code when compiled with VisualStudio builds with only using 2GB of memory space, which causes it to crash even on not very object-intense routes, even if you have a 64-bit system. Official "unstable" ORTS versions use 4GB.

Did somebody have an idea on how a private version could work the same way (without any performance disadvantages) as the official versions?

unless you are switching to an Monogame version (which on the official Code is only available via this pull request https://github.com/o...enrails/pull/40), OR is available as 32bit version only.
You will need to force your code to compile AnyCPU and set the "Prefer 32bit mode" for all projects, or alternatively if the code is compiled to x86 only, use "editbin /largeaddressaware your.exe" to enable LAA mode and use 4GB memory max. In x86 mode you'll only get 2GB as you already experienced, and as said, the only way to go beyond 4GB is to switch to 64bit mode (or AnyCPU) compilation, which requires a Monogame version, and comes with some other challenges.