LuxCoreRender Forums

NVIDIA exposes RTX with a Vulkan extension, Khronos claims they are also working on Vulkan-OpenCL interoperability. When it is available and supported by NVIDIA, we can support RTX by replacing the ray/triangles intersection OpenCL kernel with a Vulkan kernel (i.e. it is about replacing a single pi...

The sample size is very wrong, I guess I forgot to update the value, it should 4 (unable to check the code at the moment). It is the number of samples required for each path vertex and +3 suggests it uses 4 values at the moment. Thank you, alpistinho & Dade! I'll use my own fix for now and wait for...

May be not, can you provide a way to reproduce the problem ? Something like a small python script with a test scene ? I tried to simplify my scene that day, but it seems that easy scenes don't crash... and then I was getting very busy... Today I debugged luxcore with my scene and found the cause: s...

Dade wrote: ↑

Fri Jul 26, 2019 11:16 am

May be not, can you provide a way to reproduce the problem ? Something like a small python script with a test scene ?

Ok! But currently our scenes are big. I'll try to simplify it or make an artificial scene while still reproducing the issue. Please wait a moment.

Are you using border rendering ? P.S. but are you using Blender or directly LuxCore ? Thanks! But what is border rendering? I'm using a program which generates a .scn/.cfg pair and then launch "pyluxcoretool.exe console foo.cfg" with std::system() And I don't know what do you mean by "run a full im...

Is anyone experiencing PATHOCL crashes after seeing "PhotonGI evaluating best radius"? When manual testing, this happends occasionally, and re-run luxcore with the SAME scene usually fixed the problem. But now I'm running scripts to run luxcore automatically (i.e. batch rendering), this crash happen...

Dade wrote: ↑

Mon Jul 22, 2019 9:28 am

It was a bug and I should have fixed this problem.

Thanks! It works now.

Dade wrote: ↑

Thu Jul 18, 2019 8:12 am

OBJECT_ID, MATERIAL_ID and SAMPLECOUNT AOVs are saved in RGB 8 bits (so only 24 bits are stored): https://github.com/LuxCoreRender/LuxCor ... t.cpp#L483

Thanks! The results (luxcore vs VRay) matched now.

Also, if I defined an "ALBEDO" output, but don't have an "AVG_SHADING_NORMAL" output defined, ALBEDO won't be saved. If I defined both, both will be saved. It looks like a bug? (I'm not using OIDN in this case)

Another question: can we store OBJECT_ID AOV in an exr? I'm getting this error: RuntimeError: Object ID image can be saved only in non HDR formats: 4 But in wiki (https://wiki.luxcorerender.org/LuxCore_SDL_Reference_Manual_v2.2#Film_Outputs_.28aka_AOVs.29) OBJECT_ID is marked as "HDR". And with VRay...