I was getting in a LuxCore a reflection where sun center was black, so like doughnut.
Is the filesaver hdr export half float?
The original floats on hdr between 65536 - 140288 are replaced with 1.00E+010
Original Sun on hdr
Exported Sun on exr
Filesaver hdr export half float?
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Re: Filesaver hdr export half float?
I did scale all the float values down on hdr. Highest is now 65000.
Reduced random with BiDirVMcpu start radius 5 times.
Turned on path.clamping.variance.maxvalue = 1599999967232 (just in case when there is some small default value).
Sun spots are still not fully gone. Maybe it's mix material between 2 nk data materials. Like when i mixed null material with glass and got 40 digit energy levels compared to only glass that had 2 digit.
Reduced random with BiDirVMcpu start radius 5 times.
Turned on path.clamping.variance.maxvalue = 1599999967232 (just in case when there is some small default value).
Sun spots are still not fully gone. Maybe it's mix material between 2 nk data materials. Like when i mixed null material with glass and got 40 digit energy levels compared to only glass that had 2 digit.
Re: Filesaver hdr export half float?
I'm looking at the code and the conversion between float and half is done by OpenImageIO (so this looks more like an OIIO problem than Lux). However you have to consider that any number larger than 65520 can not be written in half float format:
So all the values larger 65520 should be just clamped as "infinity". You are pretty much working outside a the range of values half format can handle.
(from https://en.wikipedia.org/wiki/Half-prec ... int_format)Integers equal to or above 65520 are rounded to "infinity" (if using round-to-even, or equal to or above 65536 if using round-to-zero, or strictly above 65504 if using round-to-infinity).
So all the values larger 65520 should be just clamped as "infinity". You are pretty much working outside a the range of values half format can handle.
Re: Filesaver hdr export half float?
Yes the blender exr export from image editor seems to be also half float even when you select full float.
Re: Filesaver hdr export half float?
Not sure if it is a BlendLuxCore problem or just a Blender problem in general.
Re: Filesaver hdr export half float?
From Blender 2.79b in general saving singular 140000 float value turns into 40.469
Re: Filesaver hdr export half float?
Have you tried to export the scene and to render/save with LuxCoreUI ? My first answer was about LuxCore code but I think BlendLuxCore goes trough Blender to save an .exr so trying to use LuxCoreUI may be a workaround.
Re: Filesaver hdr export half float?
I only rendered the scene with LuxCore ui, not in Blender.
I'm pretty sure it's only VMC issue, can't see any of that in Classic BiDir.
Or maybe the gap 0.1 mm between 2 volume interfaces.
I'm pretty sure it's only VMC issue, can't see any of that in Classic BiDir.
Or maybe the gap 0.1 mm between 2 volume interfaces.
Re: Filesaver hdr export half float?
Removing 0.1 mm gaps didn't fix dark sun center, anyways this is easy fix in image editor.
Sun max brightness 65 000
path.clamping.variance.maxvalue = 159999996723281818181818181818
glass reflectance is set to 0.333
Sun max brightness 65 000
path.clamping.variance.maxvalue = 159999996723281818181818181818
glass reflectance is set to 0.333
Re: Filesaver hdr export half float?
If you want no clamping, you can just disable it (or set it to 0 if you do it through the .cfg file).