Sorry for not making my post as clear as it should have been, next time I will do better The good thing is, I fixed it! The problem was how I loaded my initial master project. # instead of using c4d.documents.LoadDocument() # i replaced it with c4d.documents.LoadFile() ... and now my xRef works just fine! Thank you again!

@jwzegelaar said in Extending the Command Line with Python: We found a good workaround! We now made a custom commandline plugin where we can add our own arguments. And it works great. If anybody in the future has this issue you can always contact us and we will help. Thanks again everybody for all the help! Hi jwzegelaar, I believe that I share the same needs as you, where I also need to pass in external parameters via a .py file to make modifications to the file before rendering. Unfortunately, I am encountering the same issue as you. Although this post has been quite some time, I am still hopeful for your assistance. Your help would be greatly appreciated and it is highly important to me.

@ferdinand Gotcha. Thanks. Will close this thread now.

Thanks for the offer. much appreciated. But your explanations were good and plenty as usual. I think, I know exactly what is going on.

Hi @m_adam, Sorry for the delay in responding. Yes, the problem has been resolved.

Closing the thread with the following conclusion. No native way to do it in C4D. Manually have to merge them then convert that one file to PYP. So have to manage separate project files. One for source ones and one for merging several PY files.

@m_adam slr. can confirm the FindNodesByName now works as expected on the illustration code I used previously. Thanks

Hello @JACK0319, without further questions or postings, we will consider this topic as solved by Monday 05/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @aghiad322, without further questions or postings, we will consider this topic as solved by Monday 05/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @HerrMay, without further questions or postings, we will consider this topic as solved by Monday 05/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @jpheneger, without further questions or postings, we will consider this topic as solved by Monday 05/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @mikeudin, without further questions or postings, we will consider this topic as solved by Monday 05/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hey @CJtheTiger, sorry for my radio silence here and thank you for updating the thread. In short: you drew all the right conclusions for the general case. A MessageData solution can be quite performant when you know exactly what you are doing and when you must monitor either every object (in the sense of geometry) in the scene graph or at least many of them. For something like monitoring materials, shaders, or tags, the solution is mandatory anyways. The tag solution on the other hand can become a bottle neck when the information flow becomes too expensive. Imagine such dependency propagation tag called DataTag, and you have 1000's of them in a scene. Each tag not only informs then one but multiple other nodes about changes of its host. Due to that there is also overlap, i.e., both DataTag DA and DataTag DB inform a target object T about changes of their host objects HA and HB. But for T this might be the "same" event and it then might be doing work twice. So, when stuff is getting complicated, you. are often better off with a MessageData solution, as you can consolidate things there. Cheers, Ferdinand

Hello @jpheneger, without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @wuzelwazel, without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @ThomasB , without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @cgweasel, without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @cgweasel, without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @FSS, without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @wanderingstan, without further questions or postings, we will consider this topic as solved by Friday 02/06/2023 and flag it accordingly. Thank you for your understanding, Maxime.