Announcement

Collapse
No announcement yet.

2018 Coordination Model Jumps around

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    2018 Coordination Model Jumps around

    Hi all,

    We recently upgraded to 2018 and have brought in NWCs/NWDs to do model coordination inside our Revit model. The models will not stay in the same place and will jump around if you zoom in or out in a floor plan, or orbit in a 3D view. This was similar behavior when we brought in some CAD files that weren't solids, but we could convert those to solids, and then they seemed to work. However, I'm not aware of any method of doing something similar to that for the navis files we receive from the other subs.

    Has anyone else seen this, and are there any fixes? Thanks!

    https://youtu.be/DYtDo5JsCso

    #2
    Looks like either your video card is not up for the job or your model is way too far from the origin point...
    Michael "MP" Patrick (Deceased - R.I.P)

    Comment


      #3
      So our model is at state plane coordinates. That might have something to do with it?

      We are running Quadro M5000 as video cards.

      Comment


        #4
        yep...Guess you are ignoring the too far from origin warning right?
        Michael "MP" Patrick (Deceased - R.I.P)

        Comment


          #5
          I don't have that warning showing up. Not when I bring in a new model, or just listed in the warnings dialogue.

          Comment


            #6
            Go to Manage>Coordinates>Report Shared Coordinates - click on an element near your coordination model.

            What number is reported in the options bar? that number needs to be below 20 miles or you can run into some really funny graphics issues.

            What else is in your model? Just because the coordination model isn't too far from the origin doesn't mean that something else isn't, so go to a default 3D view and turn on everything, also click on the little light bulb in the View Control bar to reveal all hidden elements. Then zoom to fit to see if something else is causing the issue.
            Nicholas Seibert
            Sr. Revit QA
            Autodesk

            Comment


              #7
              Yea, we're way off that. We are matching the architects state plane coordinates, so for N/S I'm at 131 miles. If that's what it is, then that is just disappointing that there isn't any way to fix that. I did unhide everything, and all of our content is all in this one area. We'll just have to go back to linking in CAD files, which don't seem to suffer the same issues, and doing our main coordination in Navisworks.

              Thanks for the reply

              Comment


                #8
                how did you build your revit model to get those numbers? What i am wondering is what linking, acquiring of coordinates stuff like that did you do?
                Nicholas Seibert
                Sr. Revit QA
                Autodesk

                Comment


                  #9
                  I hesitate to correct Nicholas, from Autodesk, but:

                  Putting a spot Coordinate on the SHARED coordinates, can CERTAINLY be more than 20 miles, as long as Shared Coordinates are set up properly (acquired or specified), and the model is within 20 miles of the Revit INTERNAL origin. My current model's SHARED coordinates are 1136 miles from 0,0,0. Model runs like a champ. The model is perfectly centered around the Revit Internal Origin, however.

                  If you go to Annotate: Spot Coordinate, and click on any object, and the Spot Coordinate TYPE is set to Relative Origin... If THAT is more than a couple of miles, yeah... You are hosed.
                  Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
                  @Web | @Twitter | @LinkedIn | @Email

                  Comment


                    #10
                    EDIT: I just see that you referred to REPORT Shared Coordinates, and not using Spot Coordinate. My bad. (Leaving the post up, so the conversation makes sense).
                    Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
                    @Web | @Twitter | @LinkedIn | @Email

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X