The curves are very, very RAM intensive...more so than anything else with this.
I need to write some documentation at some point about better management of memory with garibaldi.
Memory usable while rendering the example files should not exceed 2.5GB with 100% of curves when I've tested them on MacOS/Win 64bit.
On particular 32bit machine setups processes may be restricted to using 2GB of memory. If you are finding it hard to render the examples then reduce the render percentage in the garibaldi daz studio parameters.
As mentioned in the beta email, on the website and in this forum a 64bit machine with 4GB of memory is currently recommended as the minimum requirements for the current early beta versions.
I sorry but I can't guarantee a good experience for using the Garibaldi Express examples with anything less at the moment.
Hopefully memory usage can be optimised with time, but I can't promise miracles.
One of the nice things about WINE...I've got 'full' access' to the 4 GBs, but with the example, it will 'eat' 3.85 GB of RAM during a render...which basically means everything else is dumped to swap space, but still chugs along. Without the shadowmaps, it is a little 'tamer', but still memory intensive.
I'm having a problem with creation...basically, I can get any single section to work, but moving from, let's say, painting to the next step, I get a crash. I'll email you a dump later.
I suppose I could always dump it on the media center box, create there and use on my machine...(now, if I can get the kids away from the TV, maybe I'll give it a go...).