LuxRender CVS build of 11-07-2008

[Seismo]

Hi,

I don´t know if this is normal, but the plastic material has almost no more glossiness.
I made a test render of 1,12 minutes with the exact same settings and got a huge difference.
I used the standard (blank) render preset.

I´m a noob, so I don´t know if this is relevant or not. Please don´t beat me

[jeanphi]

Hi,

Actually this is a both a feature and a known limitation
The plastic material is modeled as a diffuse substrate with a transparent coating, however the ior of the coating was reversed and this is now fixed. Moreover the sum of the diffuse and specular parts is limited to avoid energy creation but this limitation is currently a bit too hard. I'm trying to improve it so expect a better plastic in the next revision.

Jeanphi

[Seismo]

Ah ok,

I even understand this,

I am really looking forward to the next version.

Seismo

[dyf]

hi guys, sorry to ask here, but i've been looking for a CVS build for mac OSX..
i don't know if it's being done, but i've been searching for it today with no success..

thanks,
dyf

[Harry Beaver]

Hi

I was rendering a scene, everything was running fine, I was close to 1000px/S, but when I came back to my pc luxconsole had crashed

So I tried resuming again, since I used writing an .flm, but I get an error reading the samples (even with this latest CVS), and Lux starts again from zero ...

Is there another way to save the rendering that was already done ?

Cheers

[Dade]

Is there another way to save the rendering that was already done ?

Do you mean a way to resume the rendering (the .tga/.exr/etc. are saved every 3 minutes by default and should contain the rendering of your scene) ? I'm afraid there is no way if the .flm file is truncated/corrupted.

I guess we should copy (to something like .flm-old) the old version of the resume file instead of overwriting because if a crash happen while the file is overwritten everything is lost

[Harry Beaver]

yes indeed, I was talking about resuming with an .flm file.

anyhow, I did a small test and I started a new render, with the latest cvs build, stopped it, resumed it and then it works fine. It isn't compatible with an .flm from the previous version, so I have to start my render again

might be a good suggestion you made there, especially for those who render large scene's. maybe it could be an extra option you can select or de-select for those who don't need it because the copying will take extra disk/cpu amount.

[jeanphi]

Actually if you move the old file instead of copying it, the overhead should be negligible.

Jeanphi

[jananton]

Actually if you move the old file instead of copying it, the overhead should be negligible.

Jeanphi

Hmm, you could end up with a fragmented MFT. I think the following three step process would be easy to implement on the premesis that the *.flm file get written completely every turn.

1st.: rename extension *.bak, if there, to *.tmp.
2nd.: rename current existing *.flm to *.bak.
3rd.: rename *.tmp to *.flm

Then continue the action of writing a new *.flm image file...

No copying or moving at all, only two files that flip identity.
Just my two cents...

Greetings from overcast Amsterdam,

Jan

[jeanphi]

Hi,

Yes, I meant rename, it is the same on any decent filesystem as long as you stay on the same physical disk. However there shouldn't be any overhead or fragmentation incured by just renaming the old flm and creating a new one.

Jeanphi