Obtaining Shaft Opening Curves on Revit 2025

[jasonlkw]

Reaching out to the gurus once more on here…

Having this issue where it’s impossible to extract the Sketch Curves from the Shaft Openings even with the help of different packages as shown below.

Not forgetting to mention that there’s another python workflow by AlexanderVDB on pyrevit forums.

Shaft boundaries

Also noting that there are multiple threads about this on the forum but I have tried them to no avail.

Does anyone here have any similar issues?
My intention is to obtain the curves for a start and split them up to multiple different shaft openings.

Thanks in advance!

[sovitek]

Hi @jasonlkw if i remember you can get the location curves with element location + from clockwork

[jasonlkw]

Hi mate, thanks for the response!
As shown on the image, the Clockwork package seems to be running on IronPython2 so we are unable to use the nodes at the moment without converting to CPython3.

[sovitek]

guess it will work with ironpython 3 but have you tried with cpython probably it could work there as well

edit seems work in cpython 3 as well

[jasonlkw]

Oh, that seemed to work on your end.
Great, thanks for the test. I’ll try it out, maybe a reinstallation of the package would help.

[GavinCrump]

The package itself will be using ironpython i think. In this case I suspect Soren has extracted the python code and switched its engine to cp3.

[sovitek]

yes Gavin, that’s exactly what I did

[jasonlkw]

So, I’ve reinstalled the package just in case and it seems to be returning null values.
One workaround that I did earlier was to convert the current script to CP3.

what happened was it enabled the nodes to function.

Would this mean that the Clockwork package needs to be updated?

[sovitek]

Hi @jasonlkw try copy the python node to canvas and set it cp3 and see if it work…ps element geometry + should work as well…and yes clockwork isnt build for cpython3 and will probably need an update for that…but guess many of them will work if we correct the python engine..

[jasonlkw]

Actually, I’ve tried that method by switching the default engine to run on CP3 but it didn’t work.
It only worked after I have converted the Python script itself to CP3 version.

I have numerous packages installed on my machine so I’m not sure if it caused an issue to the python engine detection.

[sovitek]

not sure, try remove all your package exept CW and see if it will run, then…but not sure if it a conflict with other package…but i know bakery and CW is a bad combination

@jasonlkw

It only worked after I have converted the Python script itself to CP3 version

yes thats what i do as well and then save the node

[GavinCrump]

Its up to package managers to decide if they want to go to cpython3 at the end of the day. Theyre under no obligation to do so.

The only workaround otherwise if you must depend on packages using ironpython is to install the ironpython2.7 package or manage your own python code.

[jasonlkw]

Acutally, I have IronPython2.7 installed and avoided Bakery so far but it’s still not functioning.
The following is a list of what’s installed visibly. Plus Monocle and DynamoIronPython2.7.

Guessing it’s time to begin picking up Python and hit the subscribe button on the Aussie Guru YT lol.

[sovitek]

heheh yeah good idea but it could probably work with ironpython 3 as well if in 25

[jasonlkw]

One of the solution as I checked the list of IronPython packages.

Issue was 2025 is running on Dynamo 3.3 so switching it to IronPython3 did the trick.

[jasonlkw]

Thanks @sovitek for the help. I’ll list your comment as the solution

[sovitek]

happy it could work i guess the reason ironpython 2.7 doesnt work its maybe becaurse you use verion 2.5…guess it will work if you try version 3.2.1 for 25