LuxCoreRender Forums

B.Y.O.B. wrote: ↑Thu May 10, 2018 4:41 pm Please test your script with Cycles as render engine.
If it works ok there but not in BlendLuxCore, I will investigate.

Thanks B.Y.O.B,

I did as you suggested.
In cycles, the pattern always appears in the render results, on both computers.
(A link to the scene with cycles for JIC: https://drive.google.com/open?id=1WXLrZ ... 7eJmI1iZYJ)



Would you be so kind to check this issue?

Many thanks,
Igal

igall2 wrote: ↑Sun May 13, 2018 12:38 pm Would you be so kind to check this issue?

No need to roll your eyes.

I have modified your script a bit: https://gist.github.com/Theverat/e2cc13 ... ce63910133
- png output instead of EXR
- lower tonemapper scale so the image is not overexposed
- the main function is called in a loop so I can test it multiple times with minimal effort

I ran the script 100 times and every single image looks correct.

My configuration:
- LuxCore without OpenCL
- Linux

I called the script with

Thanks B.Y.O.B,

I ran your script on Windows computers.
- On Win7 with OpenCL I had no problems.
- On Win10, without OpenCL, 33% of the images were without the pattern.
- On Win10, with OpenCL, 50% of the images were without the pattern.
Is it likely that the problem occurs specifically on Win10?

A screenshot of Win10 without OpenCL results:

We first have to track down what exactly is happening.
From your screenshot it seems like some image is found and loaded for the spot light.
If the image could not be loaded, the image would look like the attached one (pink to signal missing image, and round spotlight cone).

Maybe you rewrite your script so it runs inside Blender, and make it so you can interrupt it. Then let it render until the wrong result appears, interrupt the script and look at the scene to find out what it's doing.

You could also take the current script and enable "only write luxCore scene" (in TXT mode), then perform a diff on all the generated files to see if the error is in the .cfg or .scn files.

If it only happens on some computers but not others, it might even be a hardware problem, e.g. a faulty hard drive?