I appreciate it.

Animation data are stored in the model. All data related to movements, cameras and visual effects refer to objects of the model via a unique ID. The .animator file is simply a backup file, in case something is corrupted in the model. The fromat is a serialization of the working data structures in the plugin. So, not really designed for a clean export. Exporting the animation would first require that you are able to export the container objects (Groups, ComponentInstance), with their transformations.

You are confounding the calculated circumference of a circle, with the perimeter of a many sided polygon. They are distinct. A circle (or an closed ArcCurve) is not a Drawingelement subclass object. They are virtual helper objects that are actually a series of edges with some extra data attached that is used by the GUI.

@Didier-Bur said in Request Section Management Panel: @alexpacio2013 OK I got it. Currently I'm working on an update of my 'Scenes Tools' plugin and it will do almost what you're after. If time permits, I'll develop a script to choose a scene and to activate (or not) a section plane for that scene and update the scene. Regards, In practice, you need a panel where, once the scene has been sectioned, you can activate or deactivate the sections or vice versa, match the section to a scene Let me know when you're ready. I don't understand why no one thought of this, it's a very important thing. Great.

Je préfère rester anonyme. Merci encore de votre intérêt pour mes plugins.

Please reorganize your extension as a TRUE SketchUp extension. See: https://ruby.sketchup.com/file.extension_requirements.html Also, take note of the various numeric conversion methods that the SketchUp API has added to the Numeric class. (You do not need to write your own conversion formulae.) Here is an example that will default to model units, if the unit argument is blank: def convert_to_inches(value, unit = nil) units = Sketchup.active_model.options["UnitsOptions"] if unit.nil? # use model units case units["LengthFormat"] when Length::Architectural, Length::Fractional return value.inch when Length::Engineering return value.feet else # Length::Decimal unit = units["LengthUnit"] end end case unit when :in, Length::Inches then value.inch when :m, Length::Meter then value.m when :cm, Length::Centimeter then value.cm when :mm, Length::Millimeter then value.mm when :ft, Length::Feet then value.feet when :yd, 5 # NOTE: constant Length::Yard (5) was added for SU2020, # use 5 to avoid NameError exception in older versions. value.yard # yards to inches else value.inch # if inches or unknown end end Also, this is a good read for dealing with units in SketchUp: https://www.thomthom.net/thoughts/2012/08/dealing-with-units-in-sketchup/

FYI, I did report this to Trimble.

@kitesoul99 Above is a little enhancement: select the material before typing matTexture in the console. Regards

@onzki Click your avatar top right of page and choose Edit Profile

@JoMaLeFe English please.

It was flaky last week, when drag-n-drop of the RBZ didn't work on some specific OSs, but then navigating to the RBZ file and selecting it would still work... I'm surprised it's not been properly fixed by now.

Thank you so much for the info.

Yesssss ! Deleting all faces before using find_faces WORKS. Thanks a lot TIG

I'm hoping that it's all in one cluster to be fair, the file was about 60mb, so if I can search the binary manually, and find it myself in a hex editor I stand a chance of manually recovering. I guess I need to create some test files, then view them in a hex editor to find the strings I need to search for.

@TIG Thank you for your input. My understanding of the C SDK is: SUModelSaveToFileWithVersion(model, "SU2021.skp", SUModelVersion_SU2021); - Should save into the "versionless" 2021 format and it should load without any error or warning into SU 2022 and SU 2023 SUModelSaveToFileWithVersion(model, "SUcurrent.skp", SUModelVersion_Current); - should save in the version of the SDK (in this case 2024) But instead both function calls save in SU 2024 format which IMO is an error in the SDK. I'll try to contact them to sort this.

If it does not work using onLButtonDown then try renaming the callback to onLButtonUp. I recall back in the v8 days there were some quirks with one or the other callback method (I think on Mac platform mostly.)

@TIG said in [Code] realign UVs, or: convert projective to affine: @chris341 It is a very old thread ! I've fixed the basic syntax errors and added modules etc. It works in v2024 [should be OK in v2020] - but I'm unsure of its efficacy... Aerilius_UV_realign_uvs.rb Haha yes!! This seems to work, at least at first glance. Just one texture exported. Thank you so much! I will report back if I have any other issues with it.

Hi. Can I help you ?