Serious problem with opacity, heeelp!
Moderator: juanjgon
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
Best.Ray.Epsilon.Explanation.EVER.BORIS!.. I've known how to use RE and that it had to do with scale, but I have much deeper understanding now. Thanx Brother Boris.
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
Yes, I appreciate it too. I didn't have a clue till now!
Vote for Juanjo!
I did some testing and pure 0 is NOT recommended for any scene unless the camera is like <1cm from target. The suggested 0.0000001 seems to work fine for most small scale scenes, even for those <1cm.
So we only need to get this setting readable value i.e. internally divided by 1000 or even 1000000, then the value is always visible and as it has nothing to do with units, that does not change any physical thinking
So please Juanjo, make that change, now it is impossible to know what the real value is. The divident may be mentioned on the label for clarity
Thank you very much for these excellent explanations of this setting, it seems I was not the only one who had no clue what it really does
Antti
So we only need to get this setting readable value i.e. internally divided by 1000 or even 1000000, then the value is always visible and as it has nothing to do with units, that does not change any physical thinking

So please Juanjo, make that change, now it is impossible to know what the real value is. The divident may be mentioned on the label for clarity

Thank you very much for these excellent explanations of this setting, it seems I was not the only one who had no clue what it really does

Antti
AMD Ryzen Threadripper 2990wx (32c/64t),64GB RAM,NVIDIA GTX 1080ti,Win10
Clarisse 4,Houdini 18 (+Octane 2019),Blender2.81,Fusion360,Onyx,ZBrush,SubstPnt...
Started: Houdini 2019, Clarisse 2016
No business, just fun
Clarisse 4,Houdini 18 (+Octane 2019),Blender2.81,Fusion360,Onyx,ZBrush,SubstPnt...
Started: Houdini 2019, Clarisse 2016
No business, just fun

I need to figure how to make it possible, the LW panels float parameter doesn't have more precision. Let me think about it, perhaps I should change this parameter to a string value in the panel, or something like that.atnreg wrote: So please Juanjo, make that change, now it is impossible to know what the real value is. The divident may be mentioned on the label for clarity![]()
-Juanjo
I meant that the input value just internally would be divided by e.g. 1000000 so that when you type in 1, it would internally be 0.000001. That way only change would be how the input value is used, the control type and everything else remained the samejuanjgon wrote:I need to figure how to make it possible, the LW panels float parameter doesn't have more precision. Let me think about it, perhaps I should change this parameter to a string value in the panel, or something like that.atnreg wrote: So please Juanjo, make that change, now it is impossible to know what the real value is. The divident may be mentioned on the label for clarity![]()
-Juanjo

Antti
AMD Ryzen Threadripper 2990wx (32c/64t),64GB RAM,NVIDIA GTX 1080ti,Win10
Clarisse 4,Houdini 18 (+Octane 2019),Blender2.81,Fusion360,Onyx,ZBrush,SubstPnt...
Started: Houdini 2019, Clarisse 2016
No business, just fun
Clarisse 4,Houdini 18 (+Octane 2019),Blender2.81,Fusion360,Onyx,ZBrush,SubstPnt...
Started: Houdini 2019, Clarisse 2016
No business, just fun

For clarification Juanjo said this:
Simple Epsilon Math
All figures in meters. The ratio is the smallest polygon versus the full scene size.
Scene ratio: Recommended epsilon value
1/1,000,000: 0.1
0.001/1,000: 0.0001
0.001/1,000,000: Not possible because the difference in size is too great. One can still try to render a scene in two or more passes
“The simple precision math means that your scene geometry can have about six or seven significant decimal digits between the full scene size and the smallest polygon.”
Simple Epsilon Math
All figures in meters. The ratio is the smallest polygon versus the full scene size.
Scene ratio: Recommended epsilon value
1/1,000,000: 0.1
0.001/1,000: 0.0001
0.001/1,000,000: Not possible because the difference in size is too great. One can still try to render a scene in two or more passes
“The simple precision math means that your scene geometry can have about six or seven significant decimal digits between the full scene size and the smallest polygon.”
Vote for Juanjo!