I’m experiencing this strange and serious issue with LayOut. I have a file that, when I update the model, or even re-link it the SketchUp model with the exact same model being used in the viewport, it makes everything Jump to a different location, which as you can imagine, screws up all of my notes and dimensions and clipping masks. This has happened with multiple LayOut files, and each time, what can be seen in the viewport is the same area of the model, meaning, it seems to keep jumping back to the same spot.
I have no idea what this could be. I’ve troubleshooted all of the axis to make sure nothing in the model was moved (even though I debunked this by opening the skp model from the viewport, saving it on my desktop and re-linking that exact file to the viewport, still same issue…).
If you are using the 2020 version, you should not experience the issue that is affecting the 2023 version. If your profile is correct please upload the model so someone can figure out the root cause.
Have you heard if there has been any update on this?
Ive had issues with this alot recently and today I spent three times longer on a project having to constantly reset all dimension lines and annotations.
Ill try 2022 tomorrow as I think this worked fine…
Exactly what I came looking for - This has been happening to me in the current version, but did not ever happen before when I set my scenese up beforehand in SketchUp.
I just created a sheet with 9 options for a front entry of a building (all in same model on different tags). Labeled each of the views. Noticed I missed painting 1 piece of trim (was a glaring error) and reloaded the model. All viewports shrank back to original screen aspect. I had zoomed in on the first one and locked the scale before making copies. Had to move all the labels.
I haven’t set zoom and angle in a SketchUp viewport in years. I’m specifically talking about perspective views that are set by scenes. I will expand the viewport to get the portion of perspective I want to fill a certain amount of paper size, lock the scale, then bring the corners back in to crop the perspective.
When I reload the model (and sometimes when I just reopen the file) the model reverts back to full perspective but shrunk to my smaller corners, ignoring the scale lock. It even happens when the layer I use is locked.
You’ve modified the camera position in some of the viewports from what was set up in the scene in the model. If something happens to reset the camera properties for the viewport, the model will appear to move within the viewport and relative to other content on the page. For example this one on the last page
I see
i had no intention to…
so correct me if i’m wrong, if i select a view and the reset button under camera options doesnt show then the viewport should remain unchanged when i update the model reference and render?
If the camera position property is saved with the scene and you do not change the camera position and update the scene and you do not move the model within the model space, the model should not move within the viewport when you update the model reference in LayOut.
I am having the same issue - but only occasionally. Recently I made a change in the Sketchup model. I saved the model. Note: the camera position had changed when I saved the model, but if I clicked on the view in the views tab, it returned to the original view position that I had been using all along.
I did nothing to change the camera position settings (ie, the saved view in Sketchup is exactly as it’s been since I created the model, I did not “Update” prior to saving my model).
When I went back to layout to “Update Model Reference”, the view had jumped up and to the right, disrupting notes, dimensions, etc.
My understanding is that if you leave the Updated view as it is (ie if you don’t Update the view prior to saving the model), that’s the view that Layout uses, not the most recent, non-Updated view, even if the non-Updated view is saved prior to “Updating Model Reference” in Layout. Is this a bug, or am I getting it wrong?
Whatever’s going on, it’s costing me a lot of time.
Did the camera position get changed in the scene associated with the viewport in LayOut?
I’m not exactly following what you are saying here. Are you modifying the Camera position for the viewport in LayOut? Is there ever a Reset button showing in the Camera section of the SketchUp Model panel?
Please complete and update your forum profile. It’s very much obsolete.
Sorry, I think I might have been using the wrong terminology. I have a template with pre-set ‘Scenes’ for each view. In this particular instance, the ‘Scene’ was a top-down plan view. When I import the model into Layout, I then navigate to that particular scene in the corresponding sheet where I want it.
This ‘Scene’ view stays the same, both in Sketchup and Layout, so that when I update the Sketchup model, then save it, I can go to Layout and right-click on its Sketchup view window, and click the command “Update Model Reference”.
Typically, no matter what view I see in Sketchup, as long as I don’t update the Scene with that view (which I have done accidentally of course, but in this case did not do), then the Updated Model Reference Scene/View remains the same in Layout. It hasn’t moved, changed scale or perspective.
Every now and then, though, Layout decides to re-align the view in the Scene, so that the entire model shifts in some unwanted direction. It’s as if I had moved the Sketchup model from its original place in relation to the origin to a new place. This happened today, and it happened once yesterday as well. I know it sounds like I must have unconsciously updated the Scene in Sketchup, and Layout just followed suit, but in this instance I went back to Sketchup, clicked on the Scene to verify that it was as I had originally set it up - it was. So… a mystery?
Some users have reported this jumping. From what I’ve seen this appears to happen if the viewport was set up such that its center doesn’t correspond with the center of the scene in the SketchUp model. If you relink the viewport the center gets reset. Seems to me it has been fixed but I don’t know what the status is on that.
