Hi guys,
I have a large topography that I am placing some components onto. I have places first phase successfully. But when i try to place it for another portion, i get the following error. Furthest object is 11 km away from the origin. If needed I can share the file in DM.
Yes, I saw that. Funny thing is it was less than 15 kms and I ended up placing them manually. How can I place them manually but not programatically? That is weird.
I’m curious as well, I’ll do some testing today on the limits. There is conflicting Revit info on the actual limit and how it can be handled.
Is there any update on this matter, I am facing a similar issue where I can’t place components directly from GH, but I can place them manually.
I didn’t get any further. @kike was there a workaround for this?
My workaround is placing them any where close to origin and then using a custom move component to move them to place… I also thought element location component does this but it gives the same error so not sure what happens inside the element location
But wanted to know if there was another method to not have to edit definitions
Hi Mohamed,
Did you find any workaround about the issue?
Hi @Japhy , not sure if that was always the case… but I believe the GeometryEncoder would convert values to Revit’s native Feet in the below?
I can poke around a bit on this tomorrow, if i recall this is the method to convert units.
Just went back to check the source code and looks like it should be internally converting the values to revit’s feet equivalent, so not really sure what’s going wrong on my side…
Hi @M.Tarabishy,
There are two methos called ToXYZ
one from Point and one from Vector.
In your screeshoot you are conecting a vector so the second is called.
Conversion from point assumes the point is a position in the world and translates units.
Conversion from vector assumes is a direction and don’t. This looks like a good idea to preserve unit length vectors at its time, but I see the confusion.
I will a take a look to it.
Thanks for pointing it out.
Thanks @kike , I see that now… I was just rebuilding the component from my initial post for RVT move element which used to work (I was probably a bit smarter back then xD).
@Direnc_Demirbas below is the component similar to what I used before to resolve the above issue (haven’t faced it recently), hope it helps you out.
RiR_MoveElement.gh (5.0 KB)
