LuxCoreRender Forums

epilectrolytics wrote: ↑Mon Apr 29, 2019 9:31 am Happens also with Cycles

Then it's either a problem in your scene setup or a bug in Blender.
Maybe check the camera and focus object for constraints or modifiers, they might screw things up?

Found the cause of the problem
All objects in this scene (downloaded from Blenderartists somewhere) have an origin of 0,0,0 so their origin is out of geometry.
As this is only a test I probably won't rerender.

Thanks for your help B.Y.O.B.!

I'm working on a "Split RGB" texture.
It can be used to replace setups like this one:

B.Y.O.B. wrote: ↑Wed May 08, 2019 11:41 am I'm working on a "Split RGB" texture.

I also created the counterpart and merged them into LuxCore master.

I've noticed if you export the scene (cfg) texture gamma settings aren't exported, they are always 1

B.Y.O.B. wrote: ↑Thu May 09, 2019 10:53 am I also created the counterpart and merged them into LuxCore master.

A welcome addition to the node system, thanks!

nigec wrote: ↑Thu May 09, 2019 11:56 am I've noticed if you export the scene (cfg) texture gamma settings aren't exported, they are always 1

IIRC the FILESAVER engines saves all images with gamma 1, so this should be correct.

Filesaver has no gamma set, tonemapper is gamma 2.2
It seems really odd that those settings aren't exported.. the material looks horrible exported unless I manually change the gamma setting to what it was in Blender
I can't show you right now the difference, maybe later today

edit:
Ok the Filesaver I did for the Sketchup view is the same, I need to do some tests
the lxs export coming out of Sketchup has gamma as set by the user

Gamma correction is pre-applied to image maps so they are always stored in memory with gamma 1.0, when exported they all have gamma 1.0.

It is done to improve performance: never do at run-time something you can do as pre-processing.