If you switch from CPU to GPU, then artifacts appear.
I know that such artifacts are corrected with Epsilon values.
But, for some reason, I cannot pick them up this time.
Blend file: https://dropmefiles.com/LScwZ
Epsilon
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.
Epsilon
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Epsilon
Epsilon
Min: 0.05
Max: 0.5
Result... PS
Also, w/ this file I noticed that whenever I made a larger/broader Epsilon change, CUDA recompiled from scratch.
Didn't do it systematically, but at random... if anyone is willing to check.
Another thing is an error report (using mentioned values):
Epsilon Max. 1.0, it doesn't render anymore and returns this error:
GPU Limit...
PS.
@Dez!
I would advise to retopo/remesh your geo to prevent such headaches in the future. Elongated (long edged) polys are known to cause shading issues.
Keep up the good work.
---------------------------------
PPS
- Epsilon Max 0.1 works fine (default)
- CUDA recompiles from scratch whenever Epsilon Max. value is changed
- full log attached
Min: 0.05
Max: 0.5
Result... PS
Also, w/ this file I noticed that whenever I made a larger/broader Epsilon change, CUDA recompiled from scratch.
Didn't do it systematically, but at random... if anyone is willing to check.
Another thing is an error report (using mentioned values):
Code: Select all
[LuxCore][7163.250] [GeForce GTX 1070 CUDAIntersect] Memory used for hardware image pipeline: 14175Kbytes
Traceback (most recent call last):
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\BlendLuxCore\engine\base.py", line 87, in render_final
final.render(self, depsgraph)
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\BlendLuxCore\engine\final.py", line 54, in render
print('[Engine/Final] Finished rendering layer "%s"' % layer.name)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 0: invalid start byte
ERROR: 'utf-8' codec can't decode byte 0xb0 in position 0: invalid start byte
Traceback (most recent call last):
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 95, in renderCancelHandler
renderStopped()
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 100, in renderStopped
bpy.data.scenes["Scene"].render.use_lock_interface = storedUseLockInterface
KeyError: 'bpy_prop_collection[key]: key "Scene" not found'
Error: 'utf-8' codec can't decode byte 0xb0 in position 0: invalid start byte
Epsilon Max. 1.0, it doesn't render anymore and returns this error:
Code: Select all
[LuxRays][7581.156] [BVHKernel] CUDA program compilation error:
epsilon_funcs.cl(32): error #18: expected a ")"
epsilon_funcs.cl(32): error #308: more than one instance of overloaded function "clamp" matches the argument list:
function "clamp(float, float, float)"
function "clamp(int, int, int)"
argument types are: (const float, float, int)
bvh.cl(144): warning #191-D: type qualifier is meaningless on cast type
2 errors detected in the compilation of "BVHKernel".
Traceback (most recent call last):
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\BlendLuxCore\engine\base.py", line 87, in render_final
final.render(self, depsgraph)
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\BlendLuxCore\engine\final.py", line 48, in render
_render_layer(engine, depsgraph, statistics, layer)
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\BlendLuxCore\engine\final.py", line 60, in _render_layer
engine.session = engine.exporter.create_session(depsgraph, engine=engine, view_layer=view_layer)
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\BlendLuxCore\export\__init__.py", line 215, in create_session
pyluxcore.KernelCacheFill(config_props_copy)
RuntimeError: BVHKernel CUDA program compilation error
ERROR: BVHKernel CUDA program compilation error
Traceback (most recent call last):
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 95, in renderCancelHandler
renderStopped()
File "C:\Users\309\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 100, in renderStopped
bpy.data.scenes["Scene"].render.use_lock_interface = storedUseLockInterface
KeyError: 'bpy_prop_collection[key]: key "Scene" not found'
Info: Compiling CUDA kernels (just once, takes a few minutes)
Error: BVHKernel CUDA program compilation error
PS.
@Dez!
I would advise to retopo/remesh your geo to prevent such headaches in the future. Elongated (long edged) polys are known to cause shading issues.
Keep up the good work.
---------------------------------
PPS
- Epsilon Max 0.1 works fine (default)
- CUDA recompiles from scratch whenever Epsilon Max. value is changed
- full log attached
Re: Epsilon
these values do not work for me.
This model is from CAD.
I plan to render a lot of such models in Luxcore. You need to figure it out, to reach the truth.
Yes, if you do a retopo, then the rendering goes without errors.
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Epsilon
ok, I also applied Scale and set Camera Scale to 1...
anyways this renders fine on my end w/ Blender 2.83.7_LTS & 2.90.1 using BlendLuxCore 2.5 (latest) https://dropmefiles.com/GpKFJ
anyways this renders fine on my end w/ Blender 2.83.7_LTS & 2.90.1 using BlendLuxCore 2.5 (latest) https://dropmefiles.com/GpKFJ
Re: Epsilon
curious. your scene works for me too.
I will play Sherlock Holmes
I will play Sherlock Holmes
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Epsilon
KintuX, thank you, you helped.
I found that you moved the camera closer to the subject and used the Clipping options.
This gave me the idea of looking for a problem in the Clipping parameter of the camera.
Having configured it correctly, the problem disappeared.
I would like to draw the attention of the developers.
If you use these scene settings:
then camera Clipping values require tens of thousands of millimeters
It is curious in this moment that the Clipping parameter can be completely disabled for CPU - everything will work flawlessly. But the GPU requires tuning.
Linux Plasma | Ryzen 5, 32Gb, SSD M2, GT 590 RX | BenQ 27 | Wacom One | Microsoft Ergo | Tie Guan Yin tea
http://dezigner.tilda.ws/
http://dezigner.tilda.ws/
Re: Epsilon
Right totally forgot about it, cuz almost every scene I tackle I automatically sanitize first.
Anyways, all of the above mentioned issues stand still.
And about Scene settings > Units, set Length to Adaptive and you'll get better overview although, the caveat is it's even easier to miss & forget about FP limits, precision span...