Hi Fredo, I use Curic Section nowadays, but I've been following FredoSection with interest and will try it fully when I have the time. Still I have a feature request: Could you consider the idea of multilayered offsets from Section. Imagine following scenario: Group has Masonry material applied. Face inside Group has Plaster material applied. FredoSection would create a Section fill with Masonry hatch and an inset of 2cm from the edge that matches the Plaster material, where a Plaster hatch would be applied. If the masonry wall would have several faces painted with plaster, then all these faces would create a plaster offset hatch when sectioned. If you want to make this outstanding, then that plaster offset could be a multiple offset representing several layers: Masonry Group - Section Fill is Masonry Ventilated Façade on external Face - Aluminium 1cm + Air gap 2cm + Insulation 6cm + Waterproofing 0.25cm + Mortar 2cm. Plaster material on internal Face - Plaster 2cm The Object is still painted as Masonry But section would be: Interior Space | Plaster 2cm | Masonry Xcm | Aluminium 1cm + Air gap 2cm + Insulation 6cm + Waterproofing 0.25cm + Mortar 2cm | Exterior Space Xcm would be the leftover value after subtracting these multiple layers offsets.

@alsomar said in [Plugin] QuadFaceTools: You see the model unsmoothed in 3ds Max just because your SketchUp model has unsmoothed lines. Despite the SubD subdivisions making the surface look smooth, if you can see the edges it means the lines are actually unsmoothed. In this frame I can see all the lines Nope. They are soft = false; smooth = true. The smooth attribute is the one actually welding the normals/creating smoothing groups. The soft is a Sketchup-thing only to separate "logical surfaces" which can be selected with a single click. In the legacy version of the exporter, the generated obj from 3dsMax was seen as 2 overlapped meshes: one with the properly welded/smoothed quads (BUT unwelded UV seams between each quad, despite the individual quads being perfectly in place in the UV chart) + one made of floating/unwelded triangles. In Blender the legacy exporter always worked fine (didn't test your fork against Blender, but I guess it could work fine). Another weird/interesting thing is that the same objects, when exported straight out of WrapR work 100% fine. [image: 1772915685108-16a21a1c-6526-4849-b21e-4f0317e7d105-image-resized.png]

If it works in v2024 [see earlier posts] it'll probably work in v2026. Try it. To install an extension from a ZIP archive file rather than from an RBZ you will need either to change the file-type suffix, or even easier use the SketchUcation submenu item to install it from Archive, which works for both RBZ and ZIP archives...

Very nicely done, something of an epic going by looks alone.

What are 'the error messages' ? A BugSplat or something else ? What is your MAC OS ? Select its icon and right-click > context-menu > Run as administrator. A dialog opens, when prompted choose Repair. This will fix any incorrect permissions etc that can cause unpredictable issue. Restart SketchUp to see if anything has improved. Repair will not affect any customization. Double-clicking

@Rich-O-Brien said in SketchyPhysics 3.5.6 (26 January 2015): is a huge undertaking Of course I was thinking about "cheat-coding"

Nice, a breakdown would be cool!

@Rich-O-Brien Thank you Brian. Second course was offset. Had to remove and reset start setback (half stone)for it + Layout from start to change ; ) Again, -thank you for sorting out. [image: 1772479795775-spacerssolved.png]

I am between fear and hope ! Bep

The 'require' code that is unneeded doesn't break anything, just takes a millisecond to process and immediately ignore, slowing the loading time all but imperceptibly... Have a good day too...

Another site with learning tools for those who wish to. AI, not required. https://www.horoma.school/course#hero

@TIG Thank you TIG for your work

nice renders. I see the similaity to twinmotion. and D5. the unreal engine look.

It's almost certainly OK on v2026 as far as it did with recent versions already - which was 'not faultlessly'. But why not try it...

It is very old, but it works with v2026. BUT there are several 'reverse face' tools available that are newer, less flaky, and probably better... e.g. my own 'Fix Reversed Face Materials' which flips faces textured on their backs and reapplies the material, UV-mapping any textures to suit, and includes several other subitem tools to adjust reversed faces and their materials...

These stories tend to reignite my belief in people. With all the stuff on the news it is easy to see young folk as trouble makers etc. A bit of positive affirmation does the world good. I hope both those boys can get over the trauma and move on to better things.

@tig Thank a lot sat.

One further issue you should address before publishing this more widely - e.g. getting it 'signed' and in the EWH. Its file naming does not follow the proper conventions. An RBZ must contain just one .RB file that registers the extension and a folder of the exact same name. Also the convention is to prepend the users 'name' at the start and even a sub-level if the modules do this. So in your case there should be MendelAI_mesh_tools subfolder and a .RB file named MendelAI_mesh_tools.rb You then edit the RB to load MendelAI_mesh_tools/loader Because previous users might also now have the older badly named file/folder installer and loading you need to do some tidying up. Add some code to the start of the RB to check for the existence of mesh_tools_loader.rb and mesh_tools subfolder in the Plugins folder - use File.exist?(str) or better still similar methods in the fileutilities [which you need to 'require'] which will make deleting the subfolder and its contents much easier. So if these files exist you should also add a UI.message_box() to ask the user to restart to sync everything - next time the rogue file/folder won't be found and the code is redundant, but is still needed in any future updates in case a user has skipped this change in 1.0.2... A manual restart is preferable to a forced quit etc as the user might not have saved some work before updating etc.

I also get the "cannot hide layer that is a part of the active path" error when trying to Generate Quadmesh from terrain. This error occurs even when selecting the contours that are grouped. What fixed it for me: move the group of contours to the root context. This error seems to come up if you are working within nested groups. TopoShaper seems to only work in the master context. Ruby Error - CLEANSING - 24-Feb-26 10:33:43 - SU2025.0 - LibFredo6 - v15.8e.txt