Thats a sensetiv topic… …when you mess up Projectorigin, you can just move all Elements to the desiered place including 2D-Elements. !Never Ever detach Project Base Point!
well, I know that option, but I want to avoid it and wanting to do the same without using Dynamo magic move, also that script is not complete as many other type of elements would not be moved, then so dangerous operation
I saved again and again 3D and 2D Elements and saved the sets.
finally i moved it!
I had this nightmare in a sofistcaded project 6 years ago. The file never healed from this process completly! but we were able to deliver! We had a dislocation of 5m.
How to solve in dynamo you should test Orchid packages…
@jacob.small - Just got to Ware Malcomb - have the same issue on several projects shifting to a requirement for alignment on the “Internal origin”. I found this on Orchid but haven’t tried it yet:
Ideally you don’t move stuff relative to the project origin, as things like views (or the stuff they contain) tend to get nuked as you can’t do it all in one transaction. If done early and you don’t care about sheets/views too much, then it’s fairly easy but it’s likely quicker to link the file into a new .rvt, set the location, and bind it. Then generate new views/sheets as needed.
I am emphasizing it in all the projects (I can get ahead of) to start exactly on the internal origin! All “my” “Core templates” has that (A)(1) ‘starter’ grid on that location. “Do it right the first time” will be the mantra moving forward.
Meantime we have old projects ideally we currently cannot /save-as/ to start our templates for that one previously invisible and seemingly innocuous little origin point.