uGridsToLoad Limit: maximum allocated RAM on 64bit < 3GB?
Posted 31 May 2012 - 03:57 PM
Posted 31 May 2012 - 04:00 PM
Posted 31 May 2012 - 07:07 PM
Posted 01 June 2012 - 12:49 AM
Sorry, I should have been more specific: I mean if Skyrim is never utilizing more than 3 gigs, then it could be Windows memory manager not playing nicely with certain processes and graphics hardware software memory managers. Then throw in the game's memory management, and we have several memory handlers that don't necessarily work efficiently together, resulting in paging out to disk and increasing chances of head-on collisions ... = CTD.
I am guessing that Windows memory management may be the culprit ....
Just speculation though. s4n is probably right, alluding to the issue being with the game's memory management limitations (hence the uGrids bugs with increasing values above 5)
Posted 01 June 2012 - 03:45 AM
Posted 01 June 2012 - 07:01 AM
Actually getting some use out of that much ram is rather a problem, one solution is to buy a ramdisk application that turns your unused memory into a virtual harddisk that is roughly 8000 times faster than the fastest ssd. You can copy all of your skyrim directory here and launch skyrim, needless to say load times will be a thing of the past and so should any ctd's or slowdowns involving any type of memory management or disk management. FYI if you encounter any type of drm issues you can probably circumvent them by judicious use of symbolic links, ask again if it arises and many here could help with that.
Additionally there are special ini settings which should increase ram usage for specific game uses. Many of these have been tested fairly exhaustively back in November with little to no effect on memory usage or gameplay excepting uGridsToLoad and uExterior Cell Buffer. Posted merely in case you want to try them out of curiosity to see if something has changed since then.
uExterior Cell Buffer=200
uInterior Cell Buffer=18
Posted 01 June 2012 - 09:27 AM
Posted 01 June 2012 - 10:50 AM
Posted 01 June 2012 - 06:32 PM
A 32 bit windows application can reference a full 4GB of RAM, and thus it can also request more than 3GB. But requesting and actually being granted are two different things. The supposed 3GB limit on Windows 32-bit systems is constantly misunderstood and thus misrepresented and has to do with hardware addresses being "memory mapped IO reservations" in Windows. It's a horrible design.
By default a 32 bit windows application will never ask for more than 3GB of memory from the system' date=' memory management above that would have to be specially coded. One of the primary differences between 32 and 64 bit applications is the radical increase in memory supported, from 3GB to 64GB but until consoles go 64bit we won't see any games that do. Since skyrim was coded for consoles and only ported to pc later [b']and [/b]it only supported 2GB on launch, its more than a little unlikely that this special above 3GB code has been written.
To make matters worse, 32-bit Windows allocates up to 2GB of system memory for the kernel, leaving the rest for user space. Applications requesting more memory than is available in user space can still be granted the extra memory that is reserved by the kernel, but it's not guaranteed. Microsoft introduced the /3GB switch in order to help special cases by forcing the 32-bit kernel to only reserve 1GB, leaving 3GB available for applications (more like ~2.3GB after hardware addresses eat up what's left).
Point being, on a 64-bit system with sufficient RAM, a 32-bit application should have no problem using 4GB of RAM.
Posted 02 June 2012 - 08:45 AM
Posted 02 June 2012 - 04:32 PM
Posted 07 June 2012 - 09:18 AM
Posted 07 June 2012 - 01:21 PM
Posted 08 June 2012 - 05:06 AM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users