LuxRender v0.8RC2 release

[jensverwiebe]

When i try to download the win32 non opencl version the file name is 0.8rc1.
Is this the right one file wrong name or is it what it says?

I checked and found it was just forgotten in the URL --> http://www.luxrender.net/release/luxren ... OpenCL.exe

Thats the right one, i take care it will be corrected soon...

Jens

[jeanphi]

Hi,

Thanks for the report, it's now fixed.

Jeanphi

[DoctorJellybean]

Thank you!

It would be great if the releases could be distributed as installers as well, for the non-geeks Quite a few users get totally confused with the self-extracting archives.

[rikb]

Nice work!

[patro]

Dear developers,
thank you for the great job.
a big thanks goes to LordCrc that always has time to spend for me and my requests.

[camara]

Well done! It's amazing how active the Luxrender dev are! Thank you very much!
Just a small reminder, the CRF files are still not included on the download and for a new user looking for the new goodies maybe is hard if they are not in the same package.

[patro]

Well done! It's amazing how active the Luxrender dev are! Thank you very much!
Just a small reminder, the CRF files are still not included on the download and for a new user looking for the new goodies maybe is hard if they are not in the same package.

I agree,
or just a installation window in the upcoming installer of the 0.8 version... with links for cfrs, nk, tabulated data databases etc

[A-man]

I suppose I have the first usage problem.. This only happens with microdisplacement enabled, the very first message in the log after export says "Unable to open image file.'' It still renders everything normally except for microdisplacement doesn't have any effect. I haven't been able to get microdisplacement working in any other version, so maybe it's just me. Im running win 7 64 bit, with the 64 open cl version of .8 RC2.

[jeanphi]

Hi,

I've not seen this issue, microdisplacement is working fine here, but I'll let Lord Crc give a more definitive answer.

Jeanphi

[A-man]

When it posts the error, it gives empty quotation marks after the word file, like this:
Unable to open image file ''
I don't know if that will make any difference, but I didn't include that in my first post.