2024 update won't save as older versions?

SketchUp Pro
21

I installed it and it shows up in file as save as legacy
but it doesn’t allow me to select the version to save as.
I tried to open it with 2017 and it won’t open it, still says need 2024 to open file.

22

As the name suggests, it inherits the version of the existing file. So if you open a V2017 file that e.g. you got it from your colleague, the extension can keep its version, but you cant choose older version.

If you have a file you created in SU2024, or Once you saved with the native save, this extension will save onto that new 2024 version.

The extension was originally designed for older SU where you can still naively select to save to the older version.

3 Likes
23

In my opinion this needs to be recalled. I feel that there is a majority or at the very least a large minority of us that prefer versions older than 2020. I’m not a builder, i take warehouse models are export them into a game that i play. I cant do that if i dont have the ability to export to a version that supports plugins.

1 Like
24

I believe that Dezmo’s work here is a solution to that problem.
However, SketchUp’s decision to do this is not for the benefit of the users but, for bringing the whole of the past up-to-date with SketchUp’s projected vision for the future. This will leave many users behind or, at least, struggling to keep up.

2 Likes
25

I’m legitimately curious about this, because I’m kind of torn about how I feel about the whole thing. Can you download warehouse models using the free version of SketchUp and export them that way?

2 Likes
26

SketchUp web just has a download option, so the files come out in whatever version is current.

1 Like
27

BTW though I use a shortcut, the icons are super nice!

2 Likes
28

The free plan you’re using already doesn’t have the ability to use extensions. Also, it’s odd to request a recall on a product you don’t even pay for.

2 Likes
29

I use the free plan to get models into sketchup 8.

30

So you don’t use SketchUp Pro 2024 at all.

1 Like
31

By the way, the most obvious “officially supported” method to export the model as COLLADA File ( model.dae /+ model folder with material images, if relevant/ ) from SketchUp 2024.0, then it can be imported into any older SketchUp version.

(Similarly as you can download 3D Warehouse models via web-browser and import, if you have an unsupported old version of SketchUp.)

32

I can download models but i can no longer export them into an older version of sketchup.

33

The question was more once you’ve downloaded them, it sounds like you’re exporting them to another program (for games I think?). What program is that and do you really need to bring them into the desktop version before doing that?

34

Personally I would avoid getting involved with answering question which actually involve real questions about what constitutes theft.

2 Likes
35

I don’t know which program they use, but Unity for example hasn’t updated their SKP support since 2019 format. As a subscriber developing models to be used in Unity, you would want to keep 2023 or earlier around so that you can save 2019 format files to be used by Unity.

3 Likes
36

Thank you so much for this solution! (…to a problem that shouldn’t exist)

2 Likes
37

Yes, but for how long?

The code logic is still present under the hood in SketchUp. They have removed the UI binding, but the API binding is still there. But my guess is that the goal is to remove that logic from the codebase entirely.

I don’t think that the removal is to force users to upgrade to the most recent version. Otherwise they wouldn’t have developed a versionless format.
I think the removal is to fully take advantage of the development time spent on the versionless format, by getting rid of the old code and simplifying the codebase. That means less maintenance, less development time spent on keeping compatibility with old versions of SketchUp that don’t make any money anymore.

So I’m expecting that ability to me removed from the APIs as well, probably in 2025 or 2026.

There is hope though: in the future, a standalone application or extension can keep using the 2024 SDK to convert a 2025+ model to older versions using the C API.

3 Likes
38

Nobody knows that for sure. There is no clear public statement from the SU staff. However, I agree with your assumption.

Se my comment here:

Also check the Additional warning at the end of my first post in a related Extension topic.

2 Likes
39

I figured it out, works like its supposed to. not as easy to save to other versions as 23 but it works.
thanks for this work around.

1 Like
40

Thanks,that saves my teaching lessons!