Hey there! If the MEPover package author is on here, first off your package is a god-send. It’s helped out a ton and I really appreciate the efforts you’ve put into creating it and maintaining it. Thank you, thank you, thank you. Here’s the situation…
I’m QC’ing my company’s scripts as we get things ready for R23 and the
Connector.Shape node is spitting out
null where in previous Revit versions it used to output “Rectangular”, “Round”, etc.
Looking under the hood in the Python node, if I take out the
except error handling there’s a warning about
If I take out the
ToString(), then it outputs some integers (or maybe those are IDs?). Not sure if that helps at all in troubleshooting.
I’ve scoured the Revit API docs website and tried everything I could think of to find the solution on my own, but I’ve hit the limits of my API / Python knowledge.
Thanks for any help you all can provide!
you are using correct template ?
from Autodesk.Revit.DB import *
from Autodesk.Revit.DB.Structure import *
from Autodesk.Revit.UI import *
from System.Collections.Generic import List
from RevitServices.Persistence import DocumentManager
from RevitServices.Transactions import TransactionManager
doc = DocumentManager.Instance.CurrentDBDocument
#Preparing input from dynamo to revit
element = UnwrapElement(IN)
#Do some action in a Transaction
OUT = element
That’s odd. I’m also returning the same integer values from the enumerable, but Lookup still shows them as shapes (as does API documentation). Not sure what’s going on here.
Just in case you’re stuck at the moment, the enumerables are as follows:
-1 - None
0 - Round
1 - Rectangular
2 - Oval
@Draxl_Andreas Yes. All the Python headers look correct. Good idea though. The node has worked great in the last 4 Revit versions prior to 2023, so my guess is some thing changed with the new version, like @Nick_Boyts alluded to.
For any people have same case. Try with this : Class Connector | Open MEP
I think i may have stumbled upon the same problem, im getting nulls in R2013 too.
I dont see a resolution here, was it resolved?