Where was I told not to touch iMaxAllocatedMemoryBytes? Because I never was...
Also, why notch the max size down if it doesn't do anything as it is anyway? And it has not crashed for me at all, so until it does, I'm gonna keep trying to get it to use more memory.
Alright, what these paging bytes do is allocate contiguous page blocks to prevent memory fragmentation, unfortunately the engine's uses preconfigured budgetcaps so you won't actually maximise memory use by modifying the preallocation pages. All it does is extenuate the amount of virtual memory allocated that isn't ever going to be used.
a 32bit app with LAA
usually can't allocate more than 3.7GB, though if the allocation is mainly virtual texture allocations then it might hit 3.87GB at the highest.
the iMaxAllocatedMemoryBytes is warned on almost all steam threads
WARNING! Do not increase iMaxAllocatedMemoryBytes value, because memory fragmentation may cause the game to crash or freeze.
Memory fragmentation is a legit warning, infact its one of the main reasons virtual addressing can be so much higher compared to working set in a non graphical application.
Now while these settings might not cause instability, they definitely can (and do) increase area load times