I keep getting these strange issues that occur from time to time that never used to happen. I’m getting more crashes recently and for some reason it resets my default tray and rearranges it and adds new tabs I don’t use. It also removes items in my toolbar or resets to just the main toolbar. This has also happened without crashes as well actually.
The viewports are acting strange too. I can set up a scaled viewport and annotate the scene but if I stretch my viewport in resizes it for a moment but moves my dimensions and leader or tag lines. Now this occurs only if I stretch from the left size and move it to the right. Up and down and from the right size, stretching works as usual.
My model reference is pretty much always broken when I start up a project.
I don’t ever get any response from Bugsplats so I’m sharing here. Not sure what’s going on. Seems like SU and Layout are going backwards.
Did you provide your name or email with the splats? It would be possible to track them and get a clue to the cause.
Did you install correctly by right-clicking on the installer and choosing “run as administrator”? If not, do so. This gives SketchUp the right permissions in Windows.
First of all, thanks for trying to help. I’ve been using SU for over 10 years now or close. The issues I’m having are happening after everything being just fine, using 2026 for 8 months or so and then I discover these things which could be from one day and gone the next just to return again.
One example in SU, not Layout, is the tag window. Some days the tag window in the taskbar is about 6" wide and pushes extensions off the page and other days it’s only about 4" wide.
Strange things are just happening after months of using 2026 that weren’t happening before.
I’ll re-install but I’m saying that this seems to be happening in every version but they only happen after awhile of use and not right of way.
The viewport stretching issue is annoying for sure.
As far as Bugsplats, who knows where those go. I always respond with my email but I’ve never seen a fix or have been reached out to if at all in 10 years.
Are you saying that LayOut doesn’t work properly with dual monitors?
I must confess I’ve stuck with 2025 so far, as reading about the various unresolved SketchUp and LayOut issues fills me with dread! Version 2025 seems pretty stable and does everything I need it to do, so I’ve been reluctant to move away from it.
Maybe I’ll install 2026 alongside it and see how it performs for me.
In 2025 I could span Layout over two of my monitors (using AHK to be precise) and then I could arrange my open files into two vertical groups – one group per monitor and then I could have my floating trays on the 3rd monitor which I toggle on/off as required.
Crucially, after closing, on the next session Layout would remember all of this and I could get on with my productive workflow.
But one of the versions of 2026 broke all of this completely.
However, I’ll walk this back a little as all good politicians and luminaries do – actually it’s not quite as broken with 2026.2.
Just did some testing and it seems with 2026 I can have multiple files open and when I close and re-open the session Layout opens over the two monitors.
What is broken is that you can’t drag files tabs back and forth to tab groups.
One annoyance is that the next session does not re-open with the last tab groups.
Maybe it’s because I am a beta tester and for me it’s one endless continuum and I lose track of what’s what
I didn’t realise you were a beta tester - that strikes me as a fairly thankless task, although you certainly have my thanks.
It does seem that changes to the core SketchUp/Layout code must be difficult to implement without unintended consequences cropping up, which presumably explain both the recurring issues and slow development pace.
This morning I’ve had to rearrange my tray and all my toolbars were missing except the main toolbar that I don’t use. It’s these strange things that are suddenly happening after months of 2026 use. Other issues are gone, for now.
Layout was not recognizing my viewport styles and showing them as missing for time there but that hasn’t happened in a while.
I hope speaking of issues on the forum us helpful as I’ve never seen a benefit to Bugsplats.
Most of the thread has gone to the viewport bug, so I’ll take the one line nobody’s picked up: “My model reference is pretty much always broken when I start up a project.”
That one is worth chasing separately, because it’s actually diagnosable. Document Setup (Window menu on Windows) → References is the source of truth. A highlighted name means out of date — select it and hit Update. If the file has been moved or renamed, Relink repoints it. The pane also shows the stored path for each reference, and that’s the part I’d look at first: breaking on every startup points more at the saved path not resolving at launch than at anything wrong with the model itself.
On the viewport stretch — I can’t explain the left-edge asymmetry from anything Trimble documents, and I’d rather say that than invent a mechanism for it. Two things that are documented and worth knowing anyway:
Dimensions attached to entities are meant to move as the object changes, and that only works with Object Snap enabled. So some annotation movement on a resize is by design, which makes it harder to see where the bug actually starts.
There’s a Preserve Scale option in the SketchUp Model panel under Ortho that governs what happens to the model’s scale when you change the bounding box size. Worth checking how yours is set — I wouldn’t assume which way it ought to be.
The directional detail is the genuinely useful part of your report, though. “Only when stretched from the left” is reproducible, and that’s far more actionable than “viewports act strange”. If it’s already filed as Paul suggests, that specific detail is worth adding to it.
On the references — after you Relink one, does it hold, or is it broken again on the next startup?
So I use two computers and I store my projects on Dropbox, which I know now that Trimble no longer likes. I did it this way for years but now it’s problematic. I didn’t know there were any other ways to relink or update the reference file then you said so that’s the way I do it. It’s been going on since 2025, I was just hoping someone had a way to help with that since updating reference files takes as long as it does. SU just takes a long time to load in the first place just opening a new project.
My viewports are locked to scale and what I’m talking about is when you have an elevation that you’ve annotated and dimensioned using object snaps but make a change or add something in the model that you can now see in the elevation if your viewport is too wide, you can either go hide the object in the model or until lately you can stretch the viewport to cut that object off. In my case, if that object is on the left and I don’t feel like updating the model and waiting for the reference file time to update I’ll just stretch the viewport from the left but the model image in the viewport pops out of scale, get’s distorted and finds it’s scale upon regenerating the scene but moves my dimensions and linked annotations but not when I move the viewport from the right side but that doesn’t help if the item is on the left. Very strange and only started happening in 2026.
Two computers plus Dropbox explains a lot of the reference problem, and the good news is it’s checkable rather than mysterious.
Open Document Setup → References on both machines and compare the stored path for the same reference. If Dropbox sits under a different user folder on each one, the path saved on machine A won’t resolve on machine B, and you get exactly what you’re describing: the file is right there, the link isn’t. Worth confirming the paths are identical strings on both. The other variable to rule out is online-only/on-demand files — if the .skp hasn’t been pulled down locally at the moment LayOut goes looking, it can’t resolve it. Marking the project folder available offline on both machines takes that off the table.
I wouldn’t assume Trimble broke Dropbox specifically, though — I’ve got no evidence either way. The two-machine path difference is real and cheap to test, so I’d start there.
On the cropping: you may not need to stretch the viewport at all. LayOut has a clipping mask for this. Draw a shape over the viewport covering the area you want to keep, select both the shape and the viewport, then right-click and choose Create Clipping Mask — you’re left with only what falls inside the shape, and Release Clipping Mask undoes it. It changes what’s displayed without changing the viewport’s size, and resizing is the exact operation triggering your bug, so it may sidestep the whole thing.
I’ll be straight that I haven’t tested it against this specific 2026 behaviour, so treat it as worth ten minutes rather than a guaranteed fix. If it does hold up, it’s also quicker than hiding the object in the model and waiting on a reference update just to crop something.
Does the left-edge distortion happen on both machines, or only one?
I can live with relinking the files, just hoping someone might have a fix. I was told to store and use my files through Trimble but I don’t feel like dealing with that right now.
I use clip masking all the time but not when I’m in a hurry or if I’m just communicating progress work. The issue is that this never was an issue so some fix broke my viewports. There are times I don’t want to use clip masking as sometimes you don’t always use a rectangle and have to trace the walls you want to see or if you have niche or soffits, etc.
Yes, the viewport issue is on both machines.
I do appreciate your effort by the way, issues resolved or not.
I replied to @Avensora not you. Their replies sound like they are copy - pasting AI and when I drop them into an ai detector they come back with 40% or more probability that they are Ai generated.
And I don’t think @Avensora actually uses / works with LO on a day to day basis.
Tenho passado pela mesma situação, arquivo limpo, todo etiquetado e bem cofigurado… mesmo assim ele trava o tempo todo. As vezes o object snap não reconhece os pontos, viewport travando e sai da escala quando mecho nas bordas, mesmo com o (preservar escala selecionado), Ainda estou me adaptando com a versão 2026. Mas tem alguns detalhes que tem me atrasado muito.
Version 2025 seems pretty stable and does everything I need it to do, so I’ve been reluctant to move away from it.
