I have two studio subscriptions and I recall the @SketchUpTeam strongly hyped the “Constant updates and fixes” being the driving motivation to subscribe.
It’s been 6.5 months since there was an update to SU 2024!!
The number of bugs that were fixed in 2025 is 48 (plus 5 specific to mac)!
Is it too much to ask when releasing a new version that requires a new install and all of the plugin migration/compatibility updates etc… to also release an update to the outgoing SU version that includes the bug fixes included in the new version?
For example, I switch between monitor configurations on occasion and am currently plagued by this bug, where some of my tools are simply not usable because either the toolbar itself or the window it launches are loading on a monitor that isn’t even connected:
Fixed an issue where multiple screens would sometimes cause problems with toolbars and menus not displaying correctly, or displaying on the wrong monitor.
I’m confused, isn’t the fix precisely sketchup 2025 ?
if you release an update for SU24 that contains all the fixes included in SU25 at the same time you release SU25, then what’s the point of releasing SU25?
Don’t get me wrong, I agree that 6 month between updates is not the deal that was presented in 2019.
No, I am asking that the bugs / known issues get fixed in 2024 and not abandoned for 6.5 months. The new version can include the “new features”
Again, with the release of 2025, they also fixed 48+ known issues from 2024. Those known issues should be fixed in 2024 as well as many of us will not immediately adopt the new full-version.
NO. The fix for 2024 is the Sketchup 2025 release itself. Absolutely make no sense what you ask for.
The migration from one to other should not take more than couple of hours. (BTW. SU 2025 introduced a new Extension Migrator…)
Maybe for a firm of 50 people all using SKP licenses, but for one person…? Download, Install, Test Drive, Migrate Extensions, Open and Save Templates to new folders in SKP and LO. Fuss with tool bars?
Done. Less than an hour for me, but I’m not new to this rodeo.
It’s not about moving myself to the version, it’s more about moving all of my active projects to the new version. The licensing limits me to only working in one version at a time and I am not going to migrate a project mid-design to a new software version with more unknown bugs.
You are wrong. What I am asking for is a version 2024.0.3 that proceeds the last 2024 update that fixes the bugs only and does not include the new features.
Sketchup 2024 was launched 04/24/2024
Update 2024.0.1 was issued 05/14/2024 - bugs fixed
Update 2024.0.2 was issued 08/04/2024 - bugs fixed
6.5 months later: 48+ known bugs were discovered and never addressed in the 2024 version.
After the release of the new major version, the older version was never, ever fixed. Maintenance Releases for older major versions alway abandoned.
What you’re asking for is not a matter of copying and pasting the changes from 2025 to 2024, but rather a very hard, time-consuming development effort.
They’ve never done such a double job. I think you should accept that you got a fix as new major version, and be happy with the new features.
The migration that the user has to do is much smaller than that. Like a pimple on a mosquito’s butt compared to a whale’s body.
I currently use 4 main Sketchup versions and have had no issues with the license. (Okay, sometimes I have to log out of one or the other and Manage Devices, but once a month is tolerable…)
And once you’ve fully migrated to 2025 (trust me it’s worth it) you won’t have problems with licence.
(Well, I have a few licensed Extensions, those might be more complicated to migrate, but not that much)
Edited
PS.:
By the way, to agree with you a little: Due to the problems you write about the 2024 version, I deleted it a long time ago and forgot how “crappy” it was.
That is a wise decision if you have a limited number of projects that have tight schedules. But migrating to a new “incremental” version is approximately as risky as to a new “full” version. A version number is after all just a number.
Let me simplify the ask here as it seems so many are confused.
I am frustrated to see the list of bug fixes that were resolved in this new 2025 version at 48 items. That’s 48 known issues in 2024, a version that has not been updated in over a half a year.
What I am asking the developers to do is continue resolving the known issues throughout the yearly life. Don’t just bail on fixing the current version because there is a new version that will launch in 6 months.
If the list of known issues were maybe a dozen then I certainly wouldn’t be complaining. But several of these issues have been problematic for a very long time.
I’d like to see the incremental updates we were promised and not have to wait 6 months for bug fixes to be resolved. That’s it.
All else said, I am very excited to dig into version 2025 and all of the features and improvements that were brought with it.
I agree with you here. I would hope for more bug / intermediate releases based on the subscription model promises from years ago. Major changes and new features get a new year / number. Fixes should get point numbers. Quarterly updates would be nice…
I perfectly understand what you are asking for, and I agree somehow. But I just wanted to explain you why it won’t happening. I have no influence on it, I’m similar user like you, just shared some thoughts of mine mind, by my experience.
Keeping in mind that I am not a developer, product manager, member of QA, etc… My understanding is that there is a LOT to test code changes against… each change has to be verified on multiple operating systems, multiple platforms, and, in some cases, on different hardware. Once all of that is signed off on, then installers have to be built and launched along with documentation that has to be created (all of which is also tested and reviewed).
This is something that COULD be done more frequently, but the process of all that testing and releasing itself takes time and energy. In order to stick to the annual release cycle, there has to be a time where we stop working on updates and instead work on the new version.
Hypothetically, we could have done another point release between the last 2024 version and 2025, but that may have pushed the release of 2025 out further…
We are all for fixing issues! It seems like there is a time where fixing the old needs to stop so we can focus on releasing the new, better solution.
