

The clue by four was me failing to attribute the fact that enbhost only replaces the memory allocate/release calls in Skyrim, thereby putting Skyrim squarely in the drivers seat. It can use all available RAM (Physical + Swap file) in 3.1GB blocks - it can spawn multiple instances as you'll see me explain if you read through the whole post. The frustration was borne out of people essentially equating the VideoMemorySizeMb setting of enblocal.ini to be the amount of physical system ram ENB could use for its ENBoost functions, which I know to be false. This started out as a post fueled by frustration and turned into me finally realising there was a clue by four smacking me in the face waiting for me to notice.


