Project base point clip removed in revit 2020.2

[Anonymous]

HI Team,

In Previous versions 2020.1, Project Base point clipping is enable and can be disabled. But in Revit 2020.2, the clip of the Project base point is not available.

The over all project can be moved to location with help of Project base point. But now it doesn't appear and there is no connection between the grids and Project base point.

Please answer if any purpose this is done. And Please explain.

Attached image for reference.

Thanks,

Pandiraj.AV

[pfarias]

Hi Steve,

I think that this one was really a "downgrade" case.

Also I think, almost every user will be very grateful if Autodesk Development Team let the PBP stay as before, it really will save a lot of time in the day to day workarounds.

One thing that I don't understand: Why the Autodesk Development Team modified this?..was there something wrong before?

If someone have the oportunitie to "sit in the table" to discus this with Autodesk and try to get this as before, I surely will put him as a hero! 

[pieter7]

---

One thing that I don't understand: Why the Autodesk Development Team modified this?..was there something wrong before?

---

I just wanted to react because there seems to be a sentiment that developers did something against the will of the community, while it was quite the opposite. They removed it because almost all users on the beta forum recommended removing it, because it was believed the clip/unclip of the basepoint caused too much confusion and accidents.

They reached out with surveys and a long topic on the beta forum gathering feedback. I'm sure we can't blame them for following the consensus that came out of that. Of course you can disagree with that decision, but the best thing you can then do in my opinion is signing up for the beta program (it's free and everyone can join).

As to removing the clip/unclip: I personally think it was a great decision. Even in this thread, it's clear that functionality was often misunderstood. I'm glad it was removed, and I believe that this change, combined with making the internal origin and the survey/basepoint/internal origin visible of linked files, we will see less coordinate issues going forward.

[Anonymous]

Did you get the solution to get the problem fixed?

[marko.Zeljkovic]

edit no2:
Hi everybody, just noticed this today.

I have project in BIM360 with shared coordinates. One master file and multiple buildings with each in it's own file.

Previously when I had PBP clipped, I could move it and then the entire building/link would move inside the master file. 
Just realised, I can now do the same thing with Manage>Project Location>Position>Relocate Project. It's just that project basepoint is only a reference for levels, not the tool for moving the project

[dgbao]

Remove 2020.2 and re-install 2020 or 2020.1, that's what I did to solve this. 

[Maria_DaCosta]

Hello,

I used to use the clip unclip function in the cases i linked a DWG file that extended greater than the area available in Revit. I would unclip the PBP and move it to the coordinates closer to the the location where my file was located and that would allow my to link the DWG without problems. Now without this function this solution is not possible anymore. Is there any alternative to obtain this result? Thank you

[ToanDN]

---

@Maria_DaCosta wrote:

Hello,

I used to use the clip unclip function in the cases i linked a DWG file that extended greater than the area available in Revit. I would unclip the PBP and move it to the coordinates closer to the the location where my file was located and that would allow my to link the DWG without problems. Now without this function this solution is not possible anymore. Is there any alternative to obtain this result? Thank you

---

You would do the same because the Project Base Point is always unclipped from version 2020 on. 

With that said, I would not recommend that workflow regardless of what version you are using.  Instead of moving the Project Base Point, I would link the DWG in center to center, move it to align with your model, and acquire coordinates.

[Maria_DaCosta]

Hello,

Thank you for your answer. Can I ask you, in that case, in which way would you move the the link file to align with the model?

Thank you.

[ToanDN]

---

@Maria_DaCosta wrote:

Hello,

Thank you for your answer. Can I ask you, in that case, in which way would you move the the link file to align with the model?

Thank you.

---

By using Move, Rotate, Align tools.  For instance, your DWG file is a site plan and your Revit file is a building model.  You would move/rotate/align the site plan so that the building model is properly located in that site plan.

[cwinchester.hmc]

Hi there @SteveKStafford . I don't think that is quite true. When the clipped state was available for the PBP, changing the elevation moved the whole project to that elevation while keeping the PBP in its relative location. This was important for setting an origin that could be inherited as shared coordinate for linked models. Now the PBP flies all over the place irrespective to geometry. Here's what should happen: When the PBP is selected and the elevation value is entered, the whole project should move to that elevation and the PBP should remain in the relative position that it was. In my opinion, removing the clipped state from the PBP was an error on the part of Autodesk since it broke this functionality. Perhaps Autodesk should consider correcting this in the next release. In the meantime, can you provide a workaround that can achieve the desired result? Thanks.

[RSomppi]

---

@cwinchester.hmc wrote:

can you provide a workaround [workflow] that can achieve the desired result? Thanks.

---

It's already in this thread, a couple of times if I remember correctly...

[cwinchester.hmc]

I believe I acknowledged the workaround @RSomppi  - relocate project. Since this does not suffice, was there another workaround in the thread to which you were referring (link)?

[RSomppi]

There are 5 pages here and I'm sure he posted the correct workflow more than once.

[cwinchester.hmc]

Very helpful @RSomppi. You're a gem. Also: 

work·a·round

/ˈwərkəˌround/

noun

COMPUTING

1. a method for overcoming a problem or limitation in a program or system.

[ToanDN]

---

@cwinchester.hmc wrote:

Hi there @SteveKStafford . I don't think that is quite true. When the clipped state was available for the PBP, changing the elevation moved the whole project to that elevation while keeping the PBP in its relative location. This was important for setting an origin that could be inherited as shared coordinate for linked models. Now the PBP flies all over the place irrespective to geometry. Here's what should happen: When the PBP is selected and the elevation value is entered, the whole project should move to that elevation and the PBP should remain in the relative position that it was. In my opinion, removing the clipped state from the PBP was an error on the part of Autodesk since it broke this functionality. Perhaps Autodesk should consider correcting this in the next release. In the meantime, can you provide a workaround that can achieve the desired result? Thanks.

---

Changing what elevation?  PBP elevation?  If so, which was the clip state of PBB when you changed the elevation?

[cwinchester.hmc]

@ToanDN , forgive me as I try my best to explain the scenario:

I have a model being used to host the civil information and generate topography. In this model I have other building models linked into it so that I can publish shared coordinates. The site model will receive the civil survey coordinates including the elevation above sea level. In earlier releases of Revit, the method for setting/adjusting the elevation of the site would be to change the elevation of the PBP in a clipped state such that all linked models would move relative to this translation. (One tangential advantage to this method would be that any other translations would remain coincident with Revit's internal origin supporting interoperability across other platforms being used on the project). Once the desired coordinates are set and the site model saved, it would also publish the shared coordinates back to the linked building models. Now that this functionality has apparently been removed post v2020, the question remains: how can we make the desired changes to elevation of the project and any linked models now that clipped state of PBP removed? Relocating the project does not achieve the same result since none of the linked models follow. 

[ToanDN]

---

@cwinchester.hmc wrote:

@ToanDN , forgive me as I try my best to explain the scenario:

I have a model being used to host the civil information and generate topography. In this model I have other building models linked into it so that I can publish shared coordinates. The site model will receive the civil survey coordinates including the elevation above sea level. In earlier releases of Revit, the method for setting/adjusting the elevation of the site would be to change the elevation of the PBP in a clipped state such that all linked models would move relative to this translation. (One tangential advantage to this method would be that any other translations would remain coincident with Revit's internal origin supporting interoperability across other platforms being used on the project). Once the desired coordinates are set and the site model saved, it would also publish the shared coordinates back to the linked building models. Now that this functionality has apparently been removed post v2020, the question remains: how can we make the desired changes to elevation of the project and any linked models now that clipped state of PBP removed? Relocating the project does not achieve the same result since none of the linked models follow. 

---

That is the same as using Specify Coordinates at Point > Click the PBP > enter the elevation change.

[cwinchester.hmc]

Thanks for your reply @ToanDN ,

Specifying at point is similar, I see that. However, It is not equivalent to what I was describing. There are more steps that have to follow specifying the point to achieve what could otherwise have been done editing the fields of a clipped PBP. That is the point that I and others in this thread are trying to make. In my opinion, Autodesk threw the baby out with the bath water when they removed the clipping state of the PBP. I would suggest that it make it's way back into future releases to salvage what was previously a very useful function.

[pieter7]

How often do you need to change the elevation of a project, that a few extra clicks/seconds make such a difference?

On the flip side, I often saw the clipped/unclipped state of the base point cause massive confusion leading to time costly mistakes. 

[cwinchester.hmc]

@pieter7 , that is beside the point. And yes, it does make a difference. In either case, there will continue to be plenty of confusion and mistakes - hence this entire thread!