Not sure what you’re doing in Dynamo as everything we are seeing is in Revit, so I can only guess based on that outcome. My guess is that you’re creating a family instance by geometry, using the node from the springs package. If that’s an incorrect assumption please provide files and screenshots so the larger community can help you more efficiently. Responses to the three questions are below.
Revit works in decimal feet under the hood. 24 meters = 78.7402 feet. You will need to scale down the geometry by 0.3048 units (or the conversion between meters and feet).
If you edit the family instance is there a material applied to the geometry there? I do not believe the springs node nor similar OOTB nodes apply a parameter; only the material on the element, and not necessarily with the right rendering asset(s).
You’d need to edit the geometry after doing the SAT import, but before you do the load family operation. This will require some Python work. From a coding perspective a simpler solution would be to create the object as you are but shift the location points from the min point of the bounding box (what is used now) to the desired center point (be it centroid or center at the base plane).
I’ve fixed this issue by scaling down my geometry as you said using Geometry.Scale node
No material is applied when I choose edit the family… I had to solve this issue by applying the imported material from object styles
I’ll try your idea later
I’ve another questions:
Initially, I’ve created the shaft Family as a a single element along its total height by using solid by union between the the sub-shafts and intermediate slabs as shown in the image below…
But I cancelled this idea because it is not practical and it is binding for the creation of vertical reinforcement of the shaft, So I thought to create only the initial shaft family with Height 4.00m then translate it according my total height using FamilyInstance.ByPointAndLevel node, but I can not find the correct setting of my parameters and I get a gap between the shafts of 4.00m which is Shaft height,
Your idea solved my issue temporarily, because I am facing another issue!!
when my family is offseted, my slabs that are part of the Shaft geometry are placed in wrong location and sould offsetd down with 10cm (Slab thikness) in each level…I tried to resolve this issue with some ways by translating down the shaft with 10 cm, by modifying the shaft height… but no way is succeed…I guess my issue lie to my family point location that I can not change!?
I belive my issue is related to the family point location that I can not find a way to change it!?
If there
If you propose me a python code to change the family point location it will be better
Why not translate the family instances down by the miss distances after creating them? I believe the offset from level parameter will control this for you.
I’m also wondering how you’ll manage when the floor to floor distance or floor thickness varies.
Which node I should use to translate them?..the script become longer and longer!!
I belive the change of the family point location will resolve my issue…is there a way to change it?
Distances between floors and their thickness are supposed same according to the total height
When faced with this question I always ask myself: how would I do this in the Revit UI? First for one item, then many. Try manually adjusting the offset from level parameter in Revit if it exists. If so and it works, an Element.SetParameterValueByName node should work.
Graphs and scripts both tend to grow as we increase our requirements to complete the automation. That said the complexity to move the family instances will be far less than the complexity to edit the location point as the later involves switching the active document.
As you can see in my previous graph I’ve offset the shaft family two time with a distance of 2*H to avoid levels overlay and to be able to interpose the slab opening in each level…but I got the levels name not classified, so I’ve used LevelByElevationAndName node to manage the levels name but they still non classified in Revit although they are in dynamo
I can’t see the issue here, but it appears to be unrelated to the original question of geometry scaling. Please mark a solution to the geometry scaling issue, and start a new topic for the offshoot question.