Maxwell Render | Official public forum

hello NL, I am rendering a pretty large scene 3000 *2000 , 1 million polys, 150 mb textures... so with 2 GB ram only, I needed to activate the -hd option, it works (although first I was scared to see a very dark render at 4 samples... but it seam to take the anciant alpha route, constantly refining higher unlike without the -hd option, where it shows first the good illuminayion, then after 5 samples, illumination is decreased, and re-adjusted as it continues to render... not the case with -hd)

well everything works but my complaints is ... why with -hd torned ON Maxwell does an iteration (that's how it is called...?) EVERY 3,5 minutes.... and in the case of hd option, it takes a while to display the result on screen... and "soon", when it is going to reach 18 samples, then 3,5 min. are not going to be enough for 0,1 sample to update... so what will that do, update for nothing... + all these 3,5 min "go and go" are going to ruin the hard disk... no?

I am planning to let it render for 10 days, so every 3,5 min an iteration is way too many times.... Is it possible to make it 20 min. or so...? Is it normal...? without the -hd option, it refines every 10 - 11 min.....

Thanks for your precious help....

Oh and BTW, render options is not available until 5 samples, but I think itis useless, it shows a half totally scrambled image...


Hervé

I am surprised nobody knows... hello NL..... hello..

Hi Herve,

1) Please post your questions about instability of LW plugin under its own section and please tell the exact peculiarity you live about it.

2) It's true that w/ -hd option, M~R is using harddisk very frequent and previews are being hard to display for big resolutions since it's not using RAM. I suggest you to test your scene at lower resolutions before rendering at big sizes and don't use -d with -hd option. This is my solution to make things go faster while rendering with harddisk. You still can peek what's it rendering with an external viewer when you want. This feature will be improved and it will be more efficient, less time consuming and more hardware friendly in time.

Best regards,
Tom

tom wrote:Hi Herve,

1) Please post your questions about instability of LW plugin under its own section and please tell the exact peculiarity you live about it.

My bad, sorry for that...

2) It's true that w/ -hd option, M~R is using harddisk very frequent and previews are being hard to display for big resolutions since it's not using RAM. I suggest you to test your scene at lower resolutions before rendering at big sizes and don't use -d with -hd option. This is my solution to make things go faster while rendering with harddisk. You still can peek what's it rendering with an external viewer when you want. This feature will be improved and it will be more efficient, less time consuming and more hardware friendly in time.

Best regards,
Tom

there is something I don't get here... .. why do U mean by don't use -d..? you mean display render image...? Yes I would like no to show it... but where do I type it... in lw, I type -hd in the command line of the LW plugin... mmmm mmm should I type -d also, how is the syntax.. I am pretty lost with command lines..

I'm not sure where not to enter -d in LW plugin but you can launch generated MXS file seperately from commandline with proper switches as you want.

that was what I thought.. I have chaecked the doc, and by default -d is there for the Max plugin I suppose... where in LW it is already set automatically... hmmm, I'll check the command line docs... thanks Tom..