Google Sketchup Mac Free Download Full Version

[Florentina Holcombe]

Youcan have multiple sketchup versions installed in your PC, you can use sketchup 2024 then open the project in sketchup 2023 if you need to save as a previous version not supported by sketchup 2024.

The option to save to an older version is not completely removed (yet?).

The Ruby API still allows you to save to any earlier version .skp file. In theory, the Extensions/Plugins that are designed for this can work. However, I have not personally checked them yet.

I learned that I misspoke above. Models saved in 2024 can also be opened in 2021, but per our support policy, 2021 falls outside our supported versions as of Jan. 31 this year. Just want to clarify that and have edited my post above to reflect it.

I have tried installing this plugin in SU Make 2017, however was not able to open a model created in SU Pro 2018. Does this plugin only work on Pro versions not Make? If this is the case, does it still work after the 30 day trial period?

@eneroth3, @DaveR, Thanks both for the reply. I have a licensed SU Pro on one machine, and SU Make 2017 on another machine. Both machines are 64 bit.

I installed the plugin within the extension manager in SU Make 2017. It installed fine with no problem. The signature shows everything is installed ok. However, within SU Make 2017 when I try to open a 2018 created file, it still brings up the message saying the model was created in a newer version and will not open.

Though our adoption rate to the latest version is quite high, it can take time after a release before everyone upgrades. If you are building scripts that rely on functionality from the most recent version, be sure to check the Sketchup.version to make sure your users are able to run your script:

Here are the build numbers for recent SketchUp releases. Note that build numbers in languages besides English are larger for each release, so it is best to check for builds that are greater than or equal to the numbers here.

Sketchup::RenderingOptions#[]= will now raise an ArgumentError if the given value cannot be set for the given key. This is a breaking change since earlier versions of the API would not indicate any failures for such erroneous calls.

Overlays are a new SketchUp API capability which allows developers to persist extension behaviors while you are using other tools. Effectively, extensions can now continue to analyze, visualize, and create information in the modeling window as you continue evolving a SketchUp model using other native tools and extensions. Previously, extension developers were limited to drawing information to the modeling window only when their extension had a tool active .

Made Sketchup.require skip .rbs files that aren't SketchUp scrambled Ruby files. This change is to avoid conflict with Ruby 3's introduction of .rbs file extension for type definitions. (github.com/ruby/rbs)

Fixed crashes that could occur from erasing instances that was part of the current Sketchup::Model#active_path. The following methods will now raise an ArgumentError when attempting to erase entities related to the active editing path:

We added a new interface, Sketchup::EntitiesBuilder, with the purpose of being able to generate bulk geometry with similar speed to Geom::PolygonMesh + Sketchup::Entities#fill_from_mesh but with the simplicity and per-entity control that Sketchup::Entities offer. This is particularly useful for importers where you can expect to see major performance improvements by switching from Sketchup::Entities#add_face to Sketchup::EntitiesBuilder#add_face.

Earlier versions of SketchUp printed the return values to Ruby Console commands different depending on platform. This has been made consistent following the pattern of Ruby's own IRB tool. A side effect of this is that the console now uses .inspect instead of .puts when printing the returned value which makes it less ambiguous in many cases. For example nil vs "" that would otherwise print a blank line in both cases.

Geom::PolygonMesh is now faster when looking up points in large meshes. This also improve performance when adding points to large meshes. Note that the mesh need to be created with an estimated total number of points for this performance improvement to kick in. The lookup of points for large meshes are now O(logN) instead of O(N^2).

Fixed UI::HtmlDialog#set_size and UI::HtmlDialog#set_position on Windows, such that calling the methods doesn't set the focus on the HtmlDialog. This makes the behavior of the method consistent with that on Mac.

For SketchUp 2021.0 we have upgraded the version of Ruby that we ship with SketchUp from 2.5.5 to 2.7.1. Developers should verify that their extensions are working as expected in this new version of Ruby.

Deprecated old method signature: Sketchup.open_file(filename) Because opening a newer file format might lead to data missing, extension developers have to explicitly migrate to the new signature. This is to ensure that no extension inadvertently open and save a file without knowing of potential data loss.

Added ability to vertically align text drawn with Sketchup::View#draw_text. New option parameter :vertical_align can be set to one of the following values: TextVerticalAlignBoundsTop, TextVerticalAlignBaseline, TextVerticalAlignCapHeight or TextVerticalAlignCenter.

Deprecated Sketchup::ComponentDefinition#insertion_point and Sketchup::ComponentDefinition#insertion_point= as this feature was removed in SketchUp. It now returns the origin of the definition and the setter is now a noop.

We have upgraded from Ruby 2.2.4 to Ruby 2.5.1. These upgrades tend to introduce subtle changes to the Ruby language that sometimes are difficult for us to find in our internal testing. Our testing has not found any major compatibility issues between Ruby 2.2.4 and the new 2.5.1 and we expect the upgrade for most developers should be relatively straightforward. Please note that any compiled C extensions will need to be rebuilt. Ensure OpenSSL library calls are compatible.

In SketchUp 2019 we have added Sketchup::InstancePath support to our existing Sketchup::DimensionLinear and Sketchup::Text classes. Now when creating a Linear Dimension, or an attached Text object, you can attach it to a nested entity by providing a valid InstancePath object, or an array version of an instance path. This will allow you to create a dimension in model space, but attach it to a valid nested entity. The linear dimension or text will then be attached to that entity, exactly how it is when linear dimensions and text are created via the UI.

SketchUp changed how it presents units. Now it adds a space between the number and the unit indicator. If your extension uses a method of your own creation to interpret strings formatted by SketchUp you might find it doesn't work anymore if you don't account for the extra space. For example:

Added Layout::SketchUpModel#dash_scale to get the current scale value of stipples in a SketchUp Model Ref. A value of 0.0 indicates the dash scale is automatically determined based on the line weight.

Along with the LayOut Ruby API for SketchUp we added the ability to open LayOut files with the LayOut application. This gives developers the ability to write a SketchUp extension purely in Ruby that parses the SketchUp model, writes a LayOut file and opens the LayOut file in LayOut in one smooth motion. This helps create a stronger connection between SketchUp and LayOut and can improve user workflows through the use of developer created extensions.

A big round of applause for the SketchUp Core team for the improvements they have added to the SketchUp application. Well, we also wanted to make sure that these new features were accessible to our developer community. We have introduced new API features for Named Section Planes and Filled Section Cuts. Awesome!

SketchUp core added a feature called Advanced Attributes. This adds some new attribute dictionaries and attributes to Component Instances and Definitions by default on every model. It should be noted that we have blocked the ability to delete the dictionaries via Ruby. This should not be possible, please let us know if you find a scenario where you are able to do so. You can however delete the key/value pairs. The UI will recreate those key value pairs if they do not exist.

Breaking Change - Fixed a bug in Sketchup::Material#name= which allowed the API to create materials with duplicate names. Now it will raise ArgumentError if it's not unique to the model.

Breaking Change - Changed Sketchup::Color class to be common between LayOut and SketchUp. The potentially breaking change is that Sketchup::Color changed to now compare RGBA values instead of the Ruby objects.

Breaking Change - Changed Geom::Transformation#identity? So that it now properly returns true in all cases where the transformation matrix match the values for the identity transformation.

Yes, its that time again - time to update our Ruby Interpreter. We have upgraded to Ruby version 2.2.4. We're hopeful that extensions that use pure Ruby will be able to upgrade to Ruby 2.2 with little difficulty. Please note that any compiled C extensions will need to be rebuilt.

One of the developer features we are most excited about for SketchUp 2017 is a new Web Dialog framework. For SketchUp 2017 we are bundling the Chromium Web Browser with the SketchUp installer. What?! Yes, now SketchUp comes pre-packaged with a single web browser for both Mac and Windows clients. No more trauma from banging your head against the wall while trying to make your web pages compatible with Internet Explorer 8-11 and Safari.

In order to maintain backwards compatibility, we have implemented a new HtmlDialog class in the Ruby API and we have not altered the existing WebDialog class. Extensions that use WebDialogs should continue to work with no changes required.

We have been working to improve our Ruby API documents and the publication process. We switched from an internally tweaked and maintained version of RDoc to YARD for our documentation generation. In the process we had to make many alterations to our documentation in the source code, we made a specialized YARD template to suit our needs. What we have now is a simple way to regenerate the documents in a matter of seconds, and we can push them to a git repo, where they are immediately available publicly. A process that used to take hours of manual html editing and special access to our Sketchup.com webserver, has been reduced to about a 10 minute process to generate and publish the documentation.

3a8082e126