Hi there,
currently having some issues with transferring geometry from Rhino 8 to Revit 2025. What seems to be a simple task leaves me clueless right now.
The idea is the following and pretty straight forward:
Given some planar surfaces, I’m extracting their boundary curves to create floors.
But once set, the AddFloors-Component shows “1. Transaction RolledBack and aborted.” and won’t transfer anything.
After setting up a completely clean and fresh new revit file to make sure it was no issue produced in the initial one, I accidently found out that if I rotate the rhino surface randomly (exept for 90° steps) and move it out of it’s position it transfers flawlessly and as expected yet out of place. If I move it back to it’s initial position, it disappears again.
I also stripped my GH-file to its bare minimum, just to make sure. Tried projecting the boundary to a different CPlane, Level, and am slowly running out of ideas.
Thanks for getting back to me.
Here’s what I can provide right now.
That Revit 2025-file just contains the floor-type (otherwise basically the autodesk-Architecture-template) and the Rhino 8- file is pretty obsolete, since the surfaces have been internalized in the GH-file.
It appears, that loading Grasshopper with the surfaces internalized transmits the floors to Revit exactly as wanted from time to time. Not on every start and disappears again, once the surfaces are being worked on. Sometimes changing the floortype brings them back. Can’t find any consitency here.
That’s what I thought but I checked all the share parameters and deleted anything suspect. Before I ran the script I had all the parameters in the model, when I reran the script this error occurred, it created about 5 of the parameters and wiped the others even though the node is set to update.
It was running fine a week ago. I’m on and off testing this stuff.
Try setting your group. I set it to Data and it errors, I set it to something out and the create parameter node turns black. But I’ll open it up and give it a test now.
(i hope so), Line is a little bit out of axis. But it’s fine.
