I get the following message: Warning: Multiple definitions for ‘Revit.Elements.Element’ are found as Revit.Elements.Element, Rhythm.Revit.Elements.Element Multiple definitions for ‘Revit.Elements.Element’ are found as Revit.Elements.Element, Rhythm.Revit.Elements.Element [afbeelding] This happe…

Rhythm version 2018.9.19 should resolve these issues. [image] I just made my categories the plural version of the word. So category became categories, etc. [image]

I always used the bottom notation. But recently i discoverd the upper notation. And it works. On a other computer i have a other version off Rhythm and then it works. probably if you did not install a package at all, the top notation will work as well I am just curious Why?

I do agree it’s interesting that this happened, does the warning sign show anything you might learn something from?

I updated Rhythm to 2018.3.2 and I’m still only getting the “dereferencing a non-pointer” error. Not sure why you’re having a conflict with the package.

with Rhythm 2018.1.17 then it works with Rhytm 2018.3.2 the upper notation doesn 't work

the only thing a learn from the warning is that rhythm have similar nodes : Element.SetParameterValueByNameCaSeiNSeNSiTiVe and Element.SetParameterByNameTypeOrInstance we already know that :slight_smile:

This is a namespace collision issue. Basically the dot notation doesn’t know which you want: Rhythm.Revit.Element.* or Revit.Element.* as you only told one of the two. Try using a node to code function to find which method your curren setup wants (highlight an element.setparameterbyname node that’s…

[Knipsel2] I uninstalled the rhythm package in this last picture. as i told then the following notation works: Revit.Element.SetParameterByName(element,“Breedte”,value_breedte); Mostly in the code blocks i used the folowing notation: element.SetParameterByName( string, value ) when i transfo…

This is really classic namespace collision. Read about it here: Naming collision A naming collision is a circumstance where two or more identifiers in a given namespace or a given scope cannot be unambiguously resolved, and such unambiguous resolution is a requirement of the underlying s…

Problem with Rhythm package 2018.3.2

Packages

Marcel_Rijsmus March 7, 2018, 8:08pm 9

try DSCore.Element.SetParameter…Builtin_&_DSCore_Modules.xlsx (33.3 KB)

hmm…maybe not

Matching excel values to revit by unique ID

Topic		Replies	Views
Rhythm version i.r.t. elements.setparameter valuebynamecaseseinsitive Packages rhythm , dynamo	2	321	January 2, 2023
Revit 2024 - Rhythm.Revit.dll not loading Packages rhythm	28	199	January 12, 2026
Rhythm Package Missing Nodes Packages rhythm , dynamo	19	498	August 8, 2023
Rhythm Loading Error Revit package	22	495	August 22, 2023
Dynamo Rhythm package problem Packages	11	297	October 3, 2023

Problem with Rhythm package 2018.3.2

Related topics