Saved Positions - Use Project Origin as View Anchor

[libengan]

Saved Positions for views on a sheet is a great idea, but as a feature it needs improvement to be truly useful.

The View Anchor is the problem:

According to the Revit Documentation, setting this to "View Origin" is supposed to align plan views to the same spot on each sheet.  However, each view has it's own origin, and if a user selects the crop region of a view and shifts it with the move command, then that view's origin gets moved too (but not if a single boundary line is moved).  So then the views don't align from sheet to sheet because their origins are in a different place.  There is also no way to see or control the view origin with installing a third party plugin like RevitLookup.

All of the other view Anchor options required that the crop regions from view to view be the same size or position in order for the views to be aligned.

All I want is to have my floor plans be in the exactly same spot on each sheet without having to fuss with the crop region positions and sizes.  I think this would be possible if we had the option to set the View Anchor to the Project Origin.

[Ric_Weber]

This is very interesting.  I did multiple testing of this, and the issue appears to be when you specifically use the Move command on that crop region because you can grab the entire crop region and drag it and it won't cause this issue, only if you actually use the Move command.   Weird, but true.  

If you assign the crop region to a scope box that works to get the crop regions all the same size and location as well as long as you haven't used the Move command previously.  So the big take away from all of this is DO NOT use the Move command to move a crop region.  

BTW, I used the pyRevit place origin marker tool to find the origin in each view and on each sheet. Per that tool, the origin actually never changed.  But the placement of the view on the sheet in relation to it's origin definitely did.  Same was true when I rotated the Crop Region with the Rotate tool.  

Something is definitely amiss.  This should definitely be fixed.  I'm wondering if this isn't actually more of a bug and should be reported as such.  I'm gonna try and see what they say. 

[libengan]

This is what Autodesk had to say about it when I reported it (CaseNo:24855171):

[Ric_Weber]

Interesting.   I'll let you know what they say to my ticket... of course I directed them to this ideas forum post, so they'll probably just repeat the same thing.   I may need to investigate that RevitLookup add in and see what that can do.  Thanks! 

[Ric_Weber]

Basically they have said the same thing, but there is a document created now at least that outlines the procedure.  I haven't tested it, but apparently weird things happen with the alignment if you move the title block on a sheet as well.  

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Views-do-not-line-...

Hopefully now that it has been reported (twice!) and they are aware of it, we will see a fix!  Fingers crossed.  

[Mike.FORM]

It would also be nice if they added a way to specify specific points in the model as anchors such as 1A grid line and level intersections (ie Manage Anchors instead of just the drop down list).

You can control crop regions by assigning scope boxes to them but I don't want to add scope boxes just to have my views align on sheets properly.

[libengan]

FYI, I tried using scope boxes to align the views, but that method doesn't work if the crop box was moved using the move command.

[nelma.abdulahe]

I solved by simply deleting the titleblock on the problematic sheet, copying the title block where a view is well placed and pasting it in the "problematic" sheet (aligned to current view). No need to adjust the misplaced view, it will fit perfectly