BlendLuxCore Development

[B.Y.O.B.]

BTW, there are missing files for the full render blender test

Look in http://cg.tuwien.ac.at/~zsolnai/luxrend ... stscene.7z

@Dade I'll write a detailed post later.

[acasta69]

Hi,

in Texture Properties panel everything is empty:

Capture.PNG (11.29 KiB) Viewed 7395 times

So for example we cannot define a texture to be used with a modifier (or we can do that by temporarily switching to another render engine).
Is this just still to be done, or am i missing something about the new interface? I did not find a way to do that in the nodes editor.
(If this is just a dumb question due to not knowing Blender enough, please accept my apologies... )

[Sharlybg]

Hi,

in Texture Properties panel everything is empty:


Capture.PNG

So for example we cannot define a texture to be used with a modifier (or we can do that by temporarily switching to another render engine).
Is this just still to be done, or am i missing something about the new interface? I did not find a way to do that in the nodes editor.
(If this is just a dumb question due to not knowing Blender enough, please accept my apologies... )

Maybe it is related to the fact that the new blendluxcore addon will allow only one material system : node tree shader.

A question for you BYOB.
Do you think new fix in blender 2.79a will solve the limitation we had in the past about color ramp implementation for luxcore ?

[B.Y.O.B.]

in Texture Properties panel everything is empty:

It's something I did not yet get around to, will come eventually.
You can create an issue on BlendLuxCore's github repo so I don't forget about it.

Do you think new fix in blender 2.79a will solve the limitation we had in the past about color ramp implementation for luxcore ?

I don't think so.
We can now create real links to datablocks, but we still can not create many datablocks in Python. I think color ramps are as far away as before.

[Dade]

Wasted a few more hours on camera motion blur. Super frustrating, still does not work.

What is not working ? I mean, do you get unexpected results out of LuxCore or Blender ?

I noticed today that all motion blur transformations are global2local and not local2global like the instance transformations. This was required for compatibility with old Lux.

I have aligned motion blur with instances and they now work accepting the some type of transformation (NOTE: this breaks the compatibility with the past for motion blur).

Was this the source of some confusion ?

[B.Y.O.B.]

This means that we no longer have to invert object matrices for the "motion.x.transformation" props, right?

[Dade]

This means that we no longer have to invert object matrices for the "motion.x.transformation" props, right?

Yes, exactly.

[B.Y.O.B.]

What is not working ? I mean, do you get unexpected results out of LuxCore or Blender ?

I'll start with camera motion blur (only the camera is moving, all objects are stationary).
My plan was to do motion blur like the default Cycles mode for now, which is called "center on frame".
Basically we say that the current frame is time 0.0 and we have the shutter time, e.g. 1.0 second. Then the start time would be -shutter / 2 and the end time would be shutter / 2.

... looking at my own comments ("# TODO why does this not work as expected?", "# TODO: seems like this is not needed - why?" and the like) I realized that I'm doing exactly what I'm warning against here: https://github.com/LuxCoreRender/BlendL ... pi_tips.md
I "deleted" the original camera properties because I set the "scene.camera.motion.*" properties after I define the camera...

Fixing this and then we'll see if I still struggle.
Already got some nice glitch art because of some wrong matrices:

[B.Y.O.B.]

Ok, now it's working a lot better.
I found out that I have to invert the camera matrix.

However, something weird is still going on - do you have an idea what could be wrong?
Only the camera is moving here.

[B.Y.O.B.]

Also tested with only positive time values, image looks exactly the same.
I guess if I had a debug build the assertions would already explode in my face, looks like a lot of Nans.

sorry about the double attachments by the way, the forum keeps deleting them when I try to correct it, so I won't touch them anymore.