LuxRender v0.7 Final Release

[tony]

Copy rendering image to clipboard does not work.
It is well or I'm missing some library?
I'm on Ubuntu 9.10

[SATtva]

This is a well known problem. Clipboard works with some applications (i.e. OpenOffice) and doesn't works with others (i.e. Gimp).

[tony]

Thanks SATtva

I tried it with open office; no problems.

Tony

[Martin54321]

Hi,

bugtracer doesn't work for me (maybe it doesn't recognize my few minutes fresh account yet?), so I write it here.

I tried this 0.7 final release as well as three pre-release 07 versions up to RC3, but there are same bugs for me in all these versions including this last final.

I use Luxblend with Blender 2.49 64 bit versions on Linux Ubuntu 9.10, Intel quad core 2.5 GHz, 4 GB RAM.

The scene is simple exterior studio-like (curved desk+objects), no textures for materials, no lights, only BW hdr image for lightning. In version 06 all works fine on every render preset and settings, but in 07 some bugs appear. First, there is some warning popup window (annoying but not affecting rendered image): parameter gain not used, gamma not used, mapping not used and supersample not used. Second, the rendered image has warm yellow-orange cast, eventhough the hdr image for lightning is pure black and white image (and 06 version renders this without cast). This cast can be corrected to some level with lightgroup blackbody temperature, but its never 100% neutral as in 06 version. Third, if I select bidirectional integrator, same warnings appear, but this time adds one more, red and fatal warning: severe error 14 unimplemented light sample_L. This makes the rendered image complete black, evethough the rendering is going on, samples per pixels are growing and CPU is screaming. But no image is rendered, only pure black area.

Martin

[Lord Crc]

bugtracer doesn't work for me (maybe it doesn't recognize my few minutes fresh account yet?), so I write it here.

From your issues it sounds like you're using the 0.6 executable with the 0.7 exporter (luxblend). Are you certain you have updated both? If you go to Help -> About it should show the version number.

[Martin54321]

Thanks for your fast reply, it was as you said. I apologize for my stupidity

[Lord Crc]

No problem, it's an easy mistake to make. Perhaps we should add some code to identify situations like this and issue a warning hmm...

[zsouthboy]

No problem, it's an easy mistake to make. Perhaps we should add some code to identify situations like this and issue a warning hmm...

I always thought we should put a simple version code into both sides and wondered why that wasn't in the spec already; we've seen several newbies to Lux have issues that end up being this exact scenario.

Exporter says "I exported based on version 0.1 of the spec"
Lux can then complain if it's higher than what it knows about, with the option to try to render anyway. (and the reverse, too - exporter version 0.1 but Lux version 0.2 - complain with ability to continue)

[heretic]

Sorry but guess am the first to post a 0.7 final bug

Great stuff - apart from above Id suggest to add "grouped object particle support" as a feature.

[Lord Crc]

Sorry but guess am the first to post a 0.7 final bug

Great stuff - apart from above Id suggest to add "grouped object particle support" as a feature.

Am I a bit thick or did you forget to describe the bug?