Is there a known issues with new MacBook Nov 2024 M4 Pro 24 Gig Sequoia 15.2 with Layout 2024?
Its loosing references to SketchUp files.
Can’t relink…
Saved in the same folder saved on hard-drive.
Does not respond… forced to quit.
iCloud backup is disabled.
I would try SU2023 but the licensing robots are not recognizing when I have signed out… or when I have deactivated from the website / Trimble account.
I’ve trashed the json files…
I’m lossing my mind!
https://help.sketchup.com/en/sketchup/system-requirements
Thank you for letting me know that I’m not going crazy…
And i will complain on a different post/thread.
I wish I could say this is Unbelievable!
Or, I’m Shocked!
But I’m not…
I can say SketchUp / Trimble is consistent and reliable in their professional approach.
Yeah two things with Trimble/SU can be always expected: no. 1…don’t expect any advanced notice or timeline or new SU features or product release - they don’t release their road map publicly and likely never will. And no 2. Don’t upgrade OS until SU officially clears support for it. Obviously too late here for no. 2 and not even something you can control when buying a new Macbook - which comes pre-shipped with latest OS. Hopefully they release a patch update soon since SU 2025 is most likely near a March release date and that’s a long time to wait with a non-functioning LayOut. 
Share the SKP and LO file, maybe someone will find something that is weird with it.
Are you using old or new graphics engine?
What happens if you save to anywhere that is not an iCloud folder (like the desktop or documents folder?).
Well, I have disabled iCloud…
And I’m not using a cloud service with regard to saving and accessing the file or files.
The project is saved in a folder along with all relevant reference files, (CSV, RTF, SKP) with the LO file… to both keep it simple and easy to relink/replace files.
Cant share the actual file do to privacy concerns. (I’m moonlighting)
Here is the reference window in document setup.
There are a couple odd things happening… but Ive seen worse. Like to or three SKP files linked and out of date… embedded files not even used. This is clean!
I appreciate the help!
(edit)
Oh… And no.
I am NOT using the super useless and experimental random annotation scaling engine.
I nearly completely forgot…
because its been almost three years since I even needed to run software in Rosette mode, but that seems to be the solution.
Wow… just wow.
So glad we have ugly AI renderings and Trimble Visualizer.
Who needs “dimension strings”, “selection filters”, “layer folders”, “trim/extend”…
Rosette… 3 years and still Rosette is the solution?!?
This works great for me - M2 Max Studio under Sonoma. It’s not random, although it can make some things look weird when working, but export is fine.
Rosetta? Does it matter in practice if you can get paying work done? Is there a noticeable difference?
Well, Sequoia isn’t supported yet, so I’m not sure what you want. It sucks you have a new machine that isn’t playing nice. In some cases one can’t help but upgrade due to needing new hardware, but in many cases we can hold off so that the stuff we use to make €$£ works…
Can you make a small example file that shows the same problem when you’re not using Rosetta? If Rosetta does work around the problem, it ought to also go wrong in Sonoma. If it was fixed by us for Sonoma, it would also be fixed in Sequoia.
I can’t share the file… see above.
I suspect part of the issue correlated to the file having multiple reference files.
Another is how the applications is handling or responding to the SKP files.
…that is to say, the LO file size comparatively is significant.
Too further describe the occurrence:
When using the LO file w/o Rosette regardless of the view ports being in vector or raster… the application would beachball. This problem would happen what seemed randomly at first, but became more pronounced and consistent when changing raster/vector viewports, and updating model references in the “SketchUp Model” window, “Context” window, “Document Setup” option.
The file path is purposely clean and simple. Yet it would beachball for 5-10 minutes then resolve… or not.
I am welcome to discussing the problem directly and privately.
Colin is asking if you can make a small file that you can share that exhibits this behavior. Like a block / cube and a reference and a png - not to share your proprietary file.
Have you purged your LO file?
That PNG that you say is not supposed to be there might be on a page somewhere out of site though, so you’ll have to find it and delete it.
How large are the graphics your are importing into LO? (Pixel dimensions?)
Are you using Raster / Vector stacked viewports? Or can you use the export override to only switch to vector on export?
I have been hired (part-time plus) to Design and Draft for a very unique and bespoke company. They have purchased the laptop because being remote and mobile is typical.
My home office is a MacStudio that is nearly 3 years old. I have no issues. And I have been on this “Merry Go Round” before with Trimble when a few years (maybe 4-6) they did a very similar thing. It caused serious issues for a lot of people. It is my fault to have forgotten that Trimble has failed to be currently compatible for months on end before. I assumed lessons were learned. I was wrong.
I also like the “experimental” graphics engine… EXCEPT! It randomly changes annotation sizes. And the differences don’t relate to what is printed in most cases. So, because i have had these experience with Trimble before… I turned off that option on my Studio the day it was released, never to think of it again.
The problem with the solution being Rosette is a matter of integrity. I’m sharing the solution that I found works on my system to be helpful. But it does seem rather lazy that it IS a solution. AND this many years on… Why do we have new features that address problems that didn’t exist and that were address by ZOOM or MS Teams, Twinmotion and the like…
The priority of BASIC functions are being ignored for shinny trendy features.
But… what do I know. I can only guess whats happening in management’s mind. Yet I’m sure that the “Rank and File” SU software engineers would also like to prioritize fundamentals.
… thanks for letting me rant, I feel better now.
I don’t fully understand.
I could share the file with the models removed… but that would probably solve the issues. Also… this is not happening on my MAcStudio.
I don’t think your asking for a screenshot of a beachball at the “Document SetUp Reference” window or the like.
Perhaps I didn’t elaborate enough?
The cursor will become a spinning beachball when the application becomes unresponsive. When one right clicks the application in the dock, the option to force quit is available. Sometimes if I wait 5 to 10 minutes and do nothing, the unresponsiveness issue will resolve. But that not a solution when it happens again 10 - 15 minutes later.
When I relink or update the file, It will (9 out 10 times) become unresponsive. Usually not again immediately after an update or link has recently occurred. But give it a few minutes… yes it will.
I often purge the reference list. Because Im often switching out models.
The mysterious/unknown PNG or JPEG files when I traced them are less than 300k and seem to be the File Thumbnail(s)
The linked file images… They are small as well…
We can try and isolate if this is a problem with this file / this model. What version was the original LO file and SKP file created in? 2024? 2023? 2022?
Is it just this job that is causing issues?
Have you tried using 2022 or 2023? Does it exhibit the same behavior in Sequoia?
Regarding my post about sharing a file:
What happens when you create a new model (even simple) and then send that to a new LO file. Copy in / Add in your PNGs and XLS (assuming those details aren’t proprietary). Perhaps this won’t cause you issues, and then we know that perhaps it is working OK in Sequoia on your hardware and there is an issue with your files. Or maybe this will also choke the system and then you can share it and Colin might be able to diagnose this for future releases.
I had issues with a couple of my templates in SKP and LO when moving to 2024. I rebuilt them in 2024 and not I have no issues (M2 Studio Max, Sonoma).
And maybe message Colin directly, and see if you can send him the file privately for them to diagnose. I’m sure they deal with NDAs and privacy so perhaps that might be a way to diagnose this.
Otherwise… I’m just a user trying to help.
¯_(ツ)_/¯
I am comfortable sharing with Colin directly. But not in an open forum for obvious reasons. I can create a Zip File with the Project.
I’m am also curious what the factors that are causing this. Years ago i discovered a bug that escalated to a few phone calls with SU, then was patched in the next release only a couple weeks later.
If only for selfish reasons, I’d like to have the application improve…
I am a few days behind on my work due to this. So I don’t have the time to try an recreate the problem; now that I think I have a working solution. Even if its only moderately better, yet bug splats… I still have movement on the project.
I have inherited a poorly managed model files. Meaning that the previous modeler was unaware the "Outliner " and other intermediate aspects… so I then did some really basic housekeeping. And left some problems alone.
The main project or structure within the first model was made a component, then saved separately to be then further developed for Construction Documents. Thus allowing it to be reloaded in the Original Site Model for renderings in situ. With that being said… I don’t believe the poorly organized file is the cause. And the file size is pretty typical.
This first file was originally created on an unknown Windows system by an unknown computer manufacture with a unknown SU version. Yet… all the files have since been opened and saved on the16" MacBook Pro, Nov 2024 24g M4 PRO machine in SU 2024 current to 12/18/24.
I’m curious about rebuilding templates, and what that involves. I have a LO template file that have rather developed Page, Layer, Auto Text setups. None of which can be exported as I’m aware. Leaving the only option to save cleaned copies or Templates files as a practical option.
My guess…
Yes the current OSX is not compatible. Yet will work if only for a brief moment (a few hours). But will become more and more buggy as time continues, (or becomes more complicated).
Perhaps the new OS file structure or M4 Pro chip is just enough different in some way that when files are looking for each other… it breaks. Similar to why cloud storage is not recommended.
So… I thought, there are a lot of folks still using intel based Macs.
And that combination of chip/OSX must be resolved by Rosette.
Perhaps this would do the same thing.
And sure enough…the file no longer was becoming unresponsive and I could repeatedly relink/update, change raster/vector views.
That being said… now that I am back home. I will stay on my MacStudio.
You can click on my avatar and message me directly. That then starts a private discussion with me.
For what it’s worth, I’m using Sequoia on a Mac mini M4 and an M3 MacBook Pro, and not noticing any problems. But, having a file that shows a problem would be helpful. I could also try that file on Sonoma, to test my theory about Sequoia not being the problem.
I’m like you. Limping along in SU Pro for Mac subscription waiting for Trimble to care enough to update the software for the latest macOS. It’s become clear that we, the paying customer, must sit back and wait for SU and LO optimization—NOT NEW BELLS AND WHISTLES—but performance improvements just because we (a) work on a Mac and (b) Trimble pays no attention to the yearly macOS upgrade cycle even though we pay yearly for SU leaseware.
I have since been able to mitigate the issue… but, I did loose a few days of work before I was able to return to the project. Then I had to work all weekend to catch up.
The most frustrating thing was watching the LO file grow larger and larger without any additional view ports or reference files… and this seemed to be causing the application to beachball.
All I can surmise is that the temp files for the viewports that were created for vectors had some correlation. Because as I continued adding viewports then vectored them, the application became unresponsive.
The biggest change I made was to separate my G sheets for the rest of the sheet set. The G sheets have all the text file and spreadsheet reference files, and only one model associated with the Site Plan.
I now I have the viewports all in vector… with no issues. They render in 2-3 seconds with little to no lag in screen position / movement.
It has done some odd things when I insert the same model into the LO file when I have already inserted the file for a previous view port. Lo seems to prefer when I copy and paste a viewport and then change the scene. Which makes me believe that this indicates a file management issue.
The G Sheet file is over 20mb, while the other sheets are less then 10mb. The G Sheets have nearly no model reference. And the other sections have multiple model references… all in vector.
At this point I don’t care why… I have found the work around. Not a solution… but a fix.
Do the G sheets have image files?
How are you ‘adding’ viewports? Copy / paste or Inserting?
Again, without seeing the file it’s very hard to diagnose.
