Sharlybg wrote: ↑
Sat Mar 02, 2019 1:53 pm
Is modification about Luxcore shading will broke compatibility with user current asset ? i hope no. with all assets we moving to luxcore it will a total waste
Materials/shaders won't break.
Light brightness in old scenes might change when opened in a more recent version of the addon, if I do the changes you and others have suggested about light settings simplification.
lacilaci wrote: ↑
Sat Mar 02, 2019 1:57 pm
I would be surprised if 2.3 with some material changes wouldn't break compatibility. And it should, to establish some new grounds for broad userbase.
Whenever possible I will try not to break compatibility. For example, I could remove all material nodes from the "add node" menu and replace them with the disney principled shader and this would not break backwards compatibility - if I leave the old nodes in the code. They could not be added in new scenes, but old scenes would continue to work. Just an example of what's possible.
Other times, compatibility breaks in non-obvious ways. For example, when a user has not changed the value of a property in an old scene, and I change the default value of this property, the scene will render differently when opened in the new version of the addon because it will use the new default. However, if the user has set a value to the property, it will not change.