Nodes from Unmaintained / Not Updated Packages

Revit
21

Doesn’t work with points or lines properly.

22

Point.PruneDuplicates is the node which you seek.

There is no equivalent for lines, and the ones which I have seen (IMO) haven’t been accurate enough to be used in production.

23

Take the lines, convert to string… See if they match?

24

I’ve done it that way before, but have also toyed with this algorithm to compare how similar the string representations are:

25

Fun! But realistically comparing the .X, .Y and .Z would make more sense surely if you wanted a , “nearly”.

26

the xyz start/end points of an arc could be the same as the start/end points of a line though.

27

Drops values after N (3?) decimal places, which means that depending on your units (think in a civil context where even in M they exceed the level of complexity). As a result those users get many false positives.

A comparison of point pairs is required to do this well. Something like compare L1’s point 1 to L2’s point 1 and if it matches compare L1’s point 2 to L2’s point 2. This doesn’t account for ‘reversed’ lines though which many users wind up wanting until they don’t…

Usually when you have well structured data I find there are easier ways to accomplish what the comparison is after (i.e. topology).

28

I was talking about just comparing line to line.

If it’s line in Dynamo it says, “line” if it’s arc it says “arc” …
So that’s not hard to extract?

29

Yep! There’s a few ways to do.

However, I am worried we are venturing into the realm of “this node would be cool to have”.

My original question was regarding nodes people depend on that existed already (in popular packages), but have not been updated.

30

Sorreh! I shall kerb my enthusiasm :stuck_out_tongue:

31

Package:

ABT （Elements.Rotate）

Node Name:

Rotate

Details:

Hi John I remember I once search all the package and want to find a node which can rotate a group of Revit.I only find the node called “Rotate” from the package called “ABT” or “Elements.Rotation” can do it perfectly.The package is very old now.Here’s screenshot.You may have a look at it. :smiley:

image
image1904×752 137 KB

Here’s the video of how I use this node to rotate a group.

32

I’m guessing the OOTB one does not work for groups?

33

If so, we should probably make it work with Groups :stuck_out_tongue:

34

Ah I see, there is not a node for generic element rotation in OOTB. Just Family Instances

image
image925×678 41.6 KB

john_pierson 35

:white_check_mark:
20240626-modelGroupRotate

5 Likes
36

Package:

Modelical

Node Name:

CenterLocation

Details:

This is a very useful node.I found it appears in many packages but the one from the Modelical is the one I choose.However the package is still very up to date.But I see in other post it‘s categorized as needs update.

image
image734×196 5.72 KB

You can make a note of this one.Maybe it will get update in the future.Maybe not.Your work is kind like saving nodes from a sinking boat.Hahaha.This node is not in hurry.But we can wait if it’s not updated after a year.You may renew it. :smiling_imp:

image
image816×509 47.8 KB

37

I was messing about with that the other day…
Because I was annoyed a centre of a bounding box didn’t work well for an L-shaped room.

image
image756×412 23.4 KB

Pole_of_inaccessibility.dyn (12.2 KB)

38

Posting an update here to let everyone know that the following nodes will be removed from Rhythm in the coming weeks:

39

If these are being deprecated in lieu of ootb ill be keen to know if viewport get/set box centre will consider true box centre without outlying grids/annotations.

For viewport alignment workflows these generally require temporary view isolation of a nonvisible category to get/set properly. Revitapi methods don’t account for this as comes in my experience and return the centre of the box when selected vs the crop.

40

The Rhythm node just returns the box center as is, which is the same as the OOTB. So at this time it does not do what you mentioned.

However, a node to do that would be nice.