Out of memory errors

[ElCadaver]

Hi All,
the area I am currently building is huge and detailed, and now when I try to open another area at the same time, I gt an out of memory exception error.

Does this relate to the system ram or the video card ram, or a combination of both?

[Rotku]

http://en.wikipedia.org/wiki/Alzheimer's_disease

It isn't referring to the computer. It's talking about the user.

[ElCadaver]

Really, because I had Dr Steven Hawking over to have a try, and he got the same errors as me?

[Curmudgeon]

System RAM.

The NWN2 Toolset is notorious for its reluctance to release memory back to the available pool once it is done with an operation, and other memory leaks.

If you are working on a machine with less than optimal or beefy specs, make a habit of saving every time you finish doing something, then exiting the Toolset, restarting, and reloading your working area. Close other programs and windows you may have open to release memory to your system. Remove resources you're not using for a given phase of building (Items and Creatures if you're working on areas, say) and only load them back in on an As Needed basis. Exporting areas as ERFs, then stripping them of everything beyond the 5 basic area files (ARE, GIC, GIT, TRN, and TRX) using NWN2Packer, then reloading into a new stripped-down working mod can also clean up some issues. I also make a point of going through the Save/Exit/Restart routine before and after doing any particularly memory-intensive operations (multi-select of groups of objects to change parameters, recompiling scripts, or BAKING areas).

I've been building since before Live, and have been fortunate to avoid the massive file corruption others have reported while Toolsetting. I attribute much of this to turning OFF Autosave and always working in Directory Mode (Save as Directory/Open Directory). I also use SyncBackSE to backup my Toolset working directory on a daily basis to an external HD.

[ElCadaver]

Thanks Curm,
despite having frequent crashes, I always quit out instead of slelcting continue ( which can corrupt modules I'm told), have auto save off, and use directories, so my module seems good, can still export ERF's fine, and noting funny happening as yet.