LO 2025... many glitches happening, anyone else?

LayOut
, ,
1

Hi, I recently bought a new Macbook Pro M4 Max 48MB RAM, and upgraded to SU/LO pro 2025. SketchUp is generally performing beautifully. Layout is performing intermittently… sometimes quick and stable, and sometimes incredibly glitchy. Many things happening that I’ve never encountered in 15 years of using this software, including an inability to select SU model view ports, an inability to paste references of SU model viewports after copying them, forever spinning on certain instances of updating a scene (forcing a ‘force-quit’). Text greying out, then correcting when I change pages back and forth. I’ve tried it with the experimental graphics engine on and off, which seems to impact the text color issue, but nothing else. This is very bad for my workflow, already costing me hours of lost productivity in the last few days. Anybody have any idea what is going on? I was so excited to upgrade to 2025, and at this point it seems non-functional.

1 Like
2

Go back to 2024 for production work. I skipped 2023, 2024 was great, 2025 has been fine for me with some intermittent bugsplats - Mac M2 Studio Max Sequoia.

Then test a few things in 2025:

In LO:
Are you sending in any bugsplats with your email?
Does it happen with a simple model (draw a cube, send to LayOut, add annotations)?
Are you using templates in SKP and / or LO that were built in a previous version?
Are you using new or old graphics engine in LayOut?
What are you trying to render your models in - raster, hybrid, vector?

In SKP:
Are you using environments? Do have extras that you are actively using? IIRC there is but related to the copy / paste issue.

3

I have had similar issues.
Received some helpful tips on my plea, link here

good luck

1 Like
4

Thanks for the quick reply here. In terms of using LO 2024 for production work, are you aware of whether or not there are issues saving SU files in 2025, and then using them in LO 2024? I am fine to eliminate ‘environment’ settings, and not use the new PBR textures, which seem like the two main issues that might cause compatibility concerns?

To answer your questions:

  • I have been sending in all bugsplats, yes. Really hoping that the Trimble team is honing in on this.
  • I haven’t experimented with a simplified model. The problem has been relatively intermittent, and I’m under a lot of time pressure on my current work deliverables, so I’ve just been trying to get these projects done!
  • I am using templates that were developed in a previous version, yes, 2024 to be precise. I haven’t tried isolating this workflow yet, in terms of starting a whole new set of work fresh within the 2025 system. I’ve been in the middle of projects that have been built out using 2024, and now I’m trying to migrate them up to 2025. Perhaps starting new projects in 2025, and finishing existing ones in 2024 (for both SU and LO?) is the right move? Gets a little tricky to track which version is opening which file, but that is a hassle I’d be willing to navigate if it makes everything work smoothly.
  • I’ve tried the classic and experimental graphics engine in LO… doesn’t seem to make a difference. I find that I don’t really like the line-weight representation using the experimental engine, especially when zoomed out, and it appears that swapping between experimental and classic does nasty things to text bounding… screws up a whole bunch of text the second I swap.
  • I typically render LO in hybrid, being very cognizant of the weight of the SU model. When things start feeling heavier/slower, I’ll swap back to Raster, but I sure like using hybrid better, and using drafting mode with the shortcut key for accurate referencing.
  • I have experimented with environments, which are really awesome… so yes, that may be related to my copy paste issue. I’ll try purging, and see if this improves things.

Thanks!

5

Yes, we’re familiar with your crash stack. We can’t repro it, but Sage @ateliernab got it one day, and couldn’t get it the next day. It’s a timing thing that’s hard to reproduce, but ping me on a personal message and we can chat more about it. One way to avoid it is to make sure auto rendering is off, and control the rendering on a page as needed.

One theory would be that an M4’s speed might make it more likely? I don’t have one, or I’d test that theory.

Barry

1 Like