Page 1 of 1
ISSUE: Collection Instancing: view port okay, final bad
Posted: Fri Mar 13, 2020 2:36 pm
by FarbigeWelt
Well, I guess you agree there is obviously gone something wrong...
- Final Render
- View Port
Blender 2.82
BlendLuxCore 2.3 beta3, latest build, 2020.03.12
LuxCoreRender 2.3 beta3, latest build, 2020.03.07
Please, check scene file and fix the issue.
Re: ISSUE: Collection Instancing: view port okay, final bad
Posted: Fri Mar 13, 2020 3:40 pm
by B.Y.O.B.
Two completely different and unrelated evaluated objects are sharing the same memory address in the depsgraph.
I am now taking the memory address of the original objects as keys, which seems to work.
It may be that Blender is deleting the evaluated object at the end of the loop iteration and it can happen that the same memory space is afterwards used for the next object.
Thanks for the report, this bug would have been super hard to spot otherwise.
I fixed the problem.
(edit: I realized that I had already found this behaviour in the past, unfortunately I forgot it when optimizing the dupli export - silly me).
SOLVED: Collection Instancing: view port okay, final bad
Posted: Sat Mar 14, 2020 2:31 pm
by FarbigeWelt
B.Y.O.B. wrote: Fri Mar 13, 2020 3:40 pm
I fixed the problem.
Hi B.Y.O.B.
Thank you very much for solving the problem
The issue is fixed in the current latest builds.
As you can see, collections are instanced in final render as expected.
- 2020-03-14 Final fixed
Blender 2.82
BlendLuxCore 2.3 beta3, latest build_67a8a70, 2020.03.13
LuxCoreRender 2.3 beta3, latest build_410a62f, 2020.03.13