[bejack]

I´m trying to render a scene in a high resolution. Desired resolution is 16000 x 12000. Crashes even with a horizontal resolution of 10000 pixels. After voxelisation the application crashes and a apple window with error listing pops up.

you can see the render settings and statistics here...

http://www.kantereit.de/maxwell/mxclstatistic.jpg

done on Macpro 8gb ram. os 10.5.4

cheers - bjoern

[JDHill]

It's not a bug, you don't have enough memory to use Multilight at such resolutions:

[bejack]

puh. surpise surprise. didn´t know that this takes that much ram.

otherwise... if i reduce the amount of different emmiters it may work with my 8gb of ram?

[JDHill]

You would probably just have to test it - Kabe's calculator says it will take almost 6GB @ 16k x 12k with no Multilight. At 10k x 12k, it says you could have two Multilight channels going with about 7.2GB, so I guess that's right on the edge. Alternatively, render at reduced-size and blow up the final images.

[bejack]

ok. i´ll try that tomorrow. otherwise i have to get more ram.

the final image for the client has to be 24k * 18k. will be printed on a really large panel for a marketing sign

so i really have to blow it up in every situation which i allready suggested.

thanks for your advice and sorry for posting a "non-bug"

[bejack]

so i did some tests and changed the amount of emitters in the scene. i merged some of them and now there are 2 left plus the environment channel. in all 3 channels.

when i take mxc and calculate the amount of ram needed for a 10k x 7.5k image it tells that 6gb are needed.

trying to render this crashes mxcl.

so i went down with my resolutions step by step and mxcl always crashes.

5100 x 3825 is the biggest size that works. everything bigger than that crashes mxcl.

at the moment i have 9gb of ram inside this machine.

can this be really because of only 9gb ram?

[JDHill]

It's not possible for me to know the answer to that - besides for the space needed for the MXI data, there are other things to consider:

- MXC says it was adjusted for 1.5, maybe requirements are different now
- you need space for your 3.25-million triangle model
- what are the numbers and sizes of textures used
- which other processes are running

However, it also occurs to me now, you are on OSX, but your screenshot shows the MXCL GUI - isn't that still a 32bit-only application on OSX? On 32bit, you will run out of memory somewhere short of 4GB usage.

[bejack]

yep you´r right.

i don´t know how much memory is used for the model in itself. no idea.

the rest of the textures is about 40mb for 42 textures.

i´ll just try the 64bit preview to see what will happen...

[bejack]

the 64bit version is runnung at the moment at a resolution of 8k * 6k.

the activity monitor tells that it uses short by 7.5gb of ram and 12gb on the hd.

voxelization ran really fast using all 8cores (cpu load 792%). but after the first sl the performance goes down and an average cpu load of 80-120 % is running....

so it seems that i have to render the scene at the max. of 5100 x 3825px with the 32bit version...

[Mihai]

It will seem during the first SL the processors aren't being used since it's updating the view. Let it render for longer, it will use all the available CPU power.

[bejack]

ok. i´ll keep it running and tell about the ongoing statistics

thanks for the info.

[bejack]

just a short report... during the last 24hs the image reached sl9.
8.6gb of ram were used and the virtual memory raised up to 60gb. then i got a message from the finder "the programm is running out of hard disk memory. please free some space"

but... there were still about 40gb on the hard drive left over...

so i had no other chance to switch the machine off, cause nothing was reacting anymore.

so i started the rendering again with lower resolution (7000 by 5250)

curious what will happen...

[Daniel Hruby]

On a final image that big, I would think the MXI could reach over 100 GB and easily use up your free space. Do you have another drive you can write the MXI out to?

[bejack]

Hi Daniel, i already tried this some time ago. The drive has had 150gb free but the error message was still the same...

[kami]

are you still using multilight? if you have the time to tweak all the lights, you won't need multilight anymore which needs a lot of memory.