Hi,
I’m trying to create dimension by reference in the same way in dy Dynamo for Revit 2022 but it doesnt work 
I tried with many settings of level but it still diosnt work( Dynamo and Genius Loci ). Maybe a hint for this problem is that node dimension by element works fine ( with lines as elements)…
Best Regards,
Kamil
What does the warning on the out of the box node say?
Hi @KamilR that one ootb need revit face reference and not autodesk,db.reference as genius loci
@sovitek types faster than I. 
arh dont think so, i cant beat you there, hahah
Thank You @jacob.small and @sovitek . This looks great but for simple case. It would be great to define these faceReferences in way CompoundSurfacesReferences does.This allows also to get references names. Its crucial to set dimension of walls.
yeah there are difference how OOTB vs GL handle dimension, but both method should do it…PS if you use ootb element.faces and sort for sides, and then you can get revit faceReferences, and will be very close to GL, at least do the same job
Which you can do - you’ll have to work out why the GL node is failing though, whcih is going to be more effort on your end. If you open up the node do you see any errors therein? If so, address those. If not, copy the content to the clipboard and paste it on canvas, wire it it and adjust list structure as needed to reproduce the issue.
The biggest problem here is that dynamo can create Dimension.ByReference from Revit.GeometryReferences.ElementFaceReferences, but it doesnt work for Autodesk.Revit.DB.Reference. Its strange because it was ok in Revit 2
Hey,
The difference is that the Autodesk.Revit.DB.Reference is the raw output from the Revit API, whereas the ‘Revit.GeometryReferences.ElementFaceReferences’ is ‘wrapped’ by Dynamo for its use with its nodes. If the custom package (GL) isn’t wrapping, then the OOTB nodes won’t generally work with it. I’m not sure what the change would be.
Hope that’s useful,
Mark
