Hi @JacquesGaudin
Look at my previous answer.
If you have more than one version of RSA the last started version is used when you use API. You can check Dynamo script for a few version one by one (I think the best practice will be close a dyn file end reopen after RSA restart).
On the other hand you can use a few version of Dynamo (eg Dynamo Sandbox) with the same RSA version.
Based on our investigation, we are shure that problem is not depend on RSA version nor Dynamo version but Python interpreter. It works for IrionPython not for CPython.
FWIW I moved into a C# based approach about 15 minutes into my recent dive into making some new nodes for a customer engagement. I have had no issues since and they execute at an order of magnitude faster and more stable (compared to any of the 3 Python Engines).
As I see it, The problem with Python based COM APIs is there are too many translations in the loop, like a really bad game of telephone where person A says something to person B who says the same thing to person C until you get back to person A and it says something totally different.
Let’s say you wanted to create and return a point load generated by Dynamo. That process currently looks like this with Python:
Dynamo > Python > .net > COM > .net > Python > Dynamo
A direct Python interpreter would be more along the lines of (Python > net > COM > net > Python)
With a zero touch node it looks like this:
Dynamo > .net > COM > .Net > Dynamo
Two less conversions in both cases and it works.
While Iron Python managed those conversions, but I suspect that Microsoft put resources no one else has on this, after all that with access to internal documentation of .Net and COM Interop.
IronPython project is still alive with IronPython3 (maintained by volunteers like PythonNet)
since december 2022
IronPython and PythonNet have qualities and defects, to date one does not replace the other.
I don’t want to join this topic to make drama about language event I’m maintaining for some project support upgrade for language. The challenge between engineering, users and technology is always a headache and never fair. We just need to focus on moving forward.
Hi All,
This topic is getting old, But i have had a small hurrah moment. We are currently upgrading to RSA 2025 [uses dynamo 3.0.4… ] and the above problem has been gone.
Thanks to all who has contributed.
Gr Edward