you can add as many as you want instances of the same ca definition to a node
global ca definitions updates every time when you change the definition source
rootnode doesn’t merge (tectonically it merges but invisibly). so you have to create xref scene first, and after that merge from xref scene whatever you need
Ok… I got the two first points but I’m not sure to clearly understand the third one.
May I ask you a few lines again to be more specific on the merge process?
Thanks for your precious help on that.
read the mxs help first: XRefScene value and Interface: objXRefMgr
these are the things we will use
Ok, I read them.
I have a blury vision of where we are going, there :).
Do you mean that we have to:
create a temporary XRefScene linking the merged source file from the merged destination file,
transfer the custom attributes from the xrefScene rootNode to the destination scene rootNode
delete the xRefScene
#1 true
#2 merge all necessary lights and nodes, transfer attributes, and replace lights and nodes in the merged attributes lists with merged lights and nodes
#3 true
when you xref scene the xref root node will have CA pointed to xref root node children. you have to replace them with nodes from the destination scene
I looked quickly at the merge callbacks.
I didn’t find a way to get the filepath of the scene being merged.
To be clear, are we talking about a custom merging process which doesn’t use the classic merge of 3dsmax?
Ok… I would have prefered a transparent merging through the classic merge process (using file notifications callbacks) but I guess that, even if it was possible, it would slow down all merging process when you merge a file which does not contain any lighting preset.
lightset is your original thing. it’s absolutely appropriate to provide and force a user to use your merge lightset mechanism. it’s how i would do it.
classic merge process doesn’t give you access to merged scene root node anyway
You are absolutely right about the presets.
I was looking forward to apply the same mechanisl for another tool where it would be less appropriate to have a custom merging process, that’s all.
Thanks for the master class, Denis
i’m using scene merge callbacks. the main problem of it is you can’t know the merge filename. that’s why in many cases i have to force a user to use my merge mechanism.
Ok. Very strange, btw…