LuxCore: issues, problems, regressions

[SATtva]

Guys, it seems bump is totally broken in LuxCoreRenderer (LuxBlend API 1.x) at the moment:

Lux classic Path

LuxCore Path (LuxCoreRenderer)

LuxCore Path OpenCL (LuxCoreRenderer), CPU device only

Bump doesn't show up no matter how large is the height value.

[Dade]

Bump doesn't show up no matter how large is the height value.

SATtva, you have to define UV coordinates for the object or LuxCore will not apply bump/normal mapping. If you unwarp the sphere everything will work fine:

This happen because LuxCore use the UV coordinates to define the orientation of the local frame, this has been added in the past in order to avoid some type of problem with anisotropic material (the problem was discovered by Tomb). I have to check what classic Lux does when no UV information are available and replicate the same behavior.

P.S. Pick an option:

[*]Sobol+Sun = sudo rm -rf /
[*]Sobol+Distant light = sync
[*]Metropolis+sun = sync ; sh back_up_system.sh

My eyes were bleeding for the fireflies

[SATtva]

SATtva, you have to define UV coordinates for the object or LuxCore will not apply bump/normal mapping. If you unwarp the sphere everything will work fine:

Ah, that did the trick. But i must say this is very counter-intuitive. Usually one decides to use procedural textures just when he don't want to mess with UV maps, so you can easily assume there is no UV map at all. Could LuxCore generate UV map internally when it's needed?

[Dade]

SATtva, you have to define UV coordinates for the object or LuxCore will not apply bump/normal mapping. If you unwarp the sphere everything will work fine:

Ah, that did the trick. But i must say this is very counter-intuitive. Usually one decides to use procedural textures just when he don't want to mess with UV maps, so you can easily assume there is no UV map at all. Could LuxCore generate UV map internally when it's needed?

LuxCore should be now able to render bump mapping even when UV coordinates are not available, can you try it ?

[jensverwiebe]

SATtva, you have to define UV coordinates for the object or LuxCore will not apply bump/normal mapping. If you unwarp the sphere everything will work fine:

Ah, that did the trick. But i must say this is very counter-intuitive. Usually one decides to use procedural textures just when he don't want to mess with UV maps, so you can easily assume there is no UV map at all. Could LuxCore generate UV map internally when it's needed?

LuxCore should be now able to render bump mapping even when UV coordinates are not available, can you try it ?

Compiled the new feature, but get immidiately kernel compile error with SATtva's testscene now. Also on CLcpu !

RUNTIME ERROR: PathOCLBase kernel compilation error

UPDATE: without OCL is fine

Jens

[SATtva]

And here's another issue which definitely is a bug/regression compared to classic Lux: when calculating emission power it seems LuxCore treats every polygon as a separate object instead of calculating power over all polygons of an object using a given emissive material. Here's a simple test: each meshlight is a separate object, they both are using the same material; a left-hand meshlight is a simple plane (one quad) while a right-hand meshlight is split to 11 faces (11 quads). With Lux classic both meshlights produce the same emission power; with LuxCore emission is multiplied.

Lux classic Path

LuxCore Path

[Dade]

Compiled the new feature, but get immidiately kernel compile error with SATtva's testscene now.

I should have fixed the problem.

[jensverwiebe]

Compiled the new feature, but get immidiately kernel compile error with SATtva's testscene now.

I should have fixed the problem.

Jep, i verify you did cpu + gpu ....

Thx


Jens

[Dade]

And here's another issue which definitely is a bug/regression compared to classic Lux: when calculating emission power it seems LuxCore treats every polygon as a separate object instead of calculating power over all polygons of an object using a given emissive material. Here's a simple test: each meshlight is a separate object, they both are using the same material; a left-hand meshlight is a simple plane (one quad) while a right-hand meshlight is split to 11 faces (11 quads). With Lux classic both meshlights produce the same emission power; with LuxCore emission is multiplied.

I should have fixed the problem:

[SATtva]

Great, thank you!