LuxCoreRender Forums

Oh, I remembered that 2D Mapping node has inputs for scale, rotation and offset...

I mean, I remembered badly

Currently, none of these can be textured.

Oh, I remembered that 2D Mapping node has inputs for scale, rotation and offset...

Really looking forward to this feature, so I was thinking a lot about it, and I have two questions: Could you add something like a "seed" parameter? Is it possible, to get more virtually independent value per object? (For Color and Normalized) For example: 1. for texture shift X direction 2. for tex...

It will be super useful!

With Bidir that cloth (too) looks much better.

By the way, this scene is impressive!

More LuxMark comparisons: https://www.engadget.com/2018/09/19/nvidia-rtx-2080-ti-review/ "The gap was even larger with the Luxmark Luxball HDR benchmark, which tests the GPU's OpenCL performance for parallel processing work like 3D and video rendering. The 1080 scored a mere 12,153, while the 2080 w...

https://hothardware.com/reviews/nvidia- ... ing?page=3

B.Y.O.B. wrote: ↑

Thu Sep 13, 2018 8:46 am

The warning tells you the name of the material. Just pin the material node tree in node editor, then search for the material name in the node editor's tree selection dropdown.

OK, thanks

B.Y.O.B. wrote: ↑

Wed Sep 12, 2018 2:30 pm

I guess this only happens in viewport render?

Yes, you're right.

B.Y.O.B. wrote: ↑

Wed Sep 12, 2018 2:30 pm

Anyway, to fix it, you just have to create a new imagemap node, select the same image as on the old node, rewire everything and delete the old node.

I can live with that warning.
(Don't wanna go through all the materials...)

It works now, thank you!

Nevertheless I have a warning:
Material "Glassxgo green": 'bpy_prop_collection[key]: key "Gamma" not found'