I'm part of the LuxCoreRender team (responsible for the Blender integration).
- User Since
- Feb 5 2016, 11:32 AM (245 w, 3 d)
Sep 18 2020
I have put together a minimal script to show the issue without requiring the installation of the BlendLuxCore addon:
You should include a description what the actual bug is.
I thought the problem was that keyframes can't be set on properties of custom nodes, or don't show up in the UI.
Sep 17 2020
With Blender 2.9 and latest BlendLuxCore v2.5 I can not reproduce the problem.
Mar 16 2020
Feb 3 2020
Fixing the crash is all I need. Thank you!
Jan 24 2020
Nov 7 2019
it is not recommended to create and maintain a reference to an object type shader in the top level of a module (shaders are slow to create and use a lot of GPU resources)
Nov 5 2019
Sep 7 2019
I have added update callbacks to all our node/socket properties, however you should consider that this means that every affected addon needs to implement an ugly workaround. In my humble opinion it would make more sense to implement the ugly workaround in Blender once and save all the addon developers the work and the mess in their code (plus the time they spend debugging until they even find the issue and this bug report).
Jul 7 2019
Apr 18 2019
Apr 16 2019
Dec 13 2018
Nov 18 2018
Jun 26 2018
Do you think it's a good idea to add a text input tool?
For people who have no drawing tablet or who have terrible handwriting.
May 2 2018
Could you try a new master build from buildbot?
I havent checked code, but could confirm this issue in 2.79b. However in current master this seems to be resolved already?
I can confirm this, it is fixed in latest master.
I apologize for not checking earlier.
May 1 2018
Apr 17 2018
Jan 8 2018
Please don't forget 96e507d9890e, thanks.
Jan 7 2018
Jan 6 2018
I might have a fix for this.
In the function lib_link_material in the file source/blender/blenloader/intern/readfile.c, the statement IDP_LibLinkProperty(ma->id.properties, fd); is executed twice:
Jan 3 2018
I hope I don't get on your nerves when I say that it would be good to have a fix for this bug in 2.79a.
It is crippling any external renderer addon that uses Datablock ID Properties.
Dec 18 2017
I recently stumbled about this bug as well, so I can confirm it.
They are Datablock ID Properties (see D113), exposed in Python since 2.79.
Dec 11 2017
I just discovered that it also unlinks when undoing something in object mode.
Dec 8 2017
Apr 13 2017
Aug 27 2016
This sounds like a good idea to me.
I hope that external renderers will also be able to use this new editor, to display statistics as well as warning/error messages that happened during the export process (e.g. missing imagemaps).
Jul 12 2016
Another thing that might be a bug: the field for the active camera in the scene tab is always highlighted in red and there are no cameras in the dropdown selection box, although there is a valid camera in the scene.
Official Blender builds do not show this behaviour.
Jul 11 2016
I just tried to start Blender with --factory-startup option and it still crashes, so I doubt that it's caused by my startup scene.
Now I rebuilt Blender with make debug and started it with --factory-startup -d --debug-all and it runs without the startup crash (also with my custom scene).
So the crash is only happening with a default build made with a simple make without options. Is that a release build?
Jul 10 2016
Great to hear of the progress.
Mar 30 2016
Which LuxRender/LuxBlend version was used?
What does this exactly mean: