@TIG I would like to thank you ! It's a really simple & powerful plugin to quickly handle texture. So glad you've just made an update. Great job and thanks again !

@ArneSu https://web.archive.org/web/20081226144927/http://www.crai.archi.fr/RubyLibraryDepot/Ruby/EM/screw1_5.rb

The EXTG and PROP terrains must have the same overall footprint. When you have the skirt fitted onto a simplified EXTG group it should still report as 'solid' in Entity info, copy that group to one side and edit that copy. Draw three Guide lines to help locate a new skirt later, on the group's axes. Delete the top terrain, but keep the vertical skirt and bottom face. Next copy the PROP group to one side and edit the copy. This time delete the skirt and bottom face, but keep the terrain geometry. Exit the edit and select the EXTG-copy group and Edit>Cut it to the clipboard. Reopen the PROP-copy for editing. Edit>Paste-in-Place. The EXTG-copy skirt group in now inside the PROP-copy terrain group. If the skirt-group doesn't line up with the terrain's axes, then Move it into place using Shift to restrain the movement in the Red/Green axes only. The guide's intersection should help with this relocation [if needed]. Explode the skirt-group so that the PROP-copy now contains only geometry. Erase any Guides left behind too. The PROP-copy should now contain its terrain top and skirt/bottom copied from EXTG. Exit the edit and check the PROP-copy in Entity Info - chances are it won't be a 'solid'. We now need to make it a solid... Use Thomthom's SolidInspector2 on the PROP-copy to see where the errors are reported. They will be highlighted in Red. Fix the ones that it reports as 'fixable'. If there are other 'non-auto-fixable' errors - e.g. complex holes or inner faces - then you need to dip in and out of SolidInspector2 and the model itself [into PROP-copy group > edit] and manually fix these issues in turn. Use pan/zoom to position yourself over the issues that need fixing... It's best to have sun/shadows on so you can see holes more easily and the Default-materials showing, with the back-material being set to a distinctive color - e.g. bright green. These might be 'flaps' or 'shelves' that need deleting, missing faces that need healing by drawing over edges to force a face to form, or adding diagonal lines to triangulate geometry and force facets to form [it's best to triangulate resistant faces to infill facets, even if the larger hole's perimeter appears 'planar'.] As you do this you might accidentally form internal 'partition' faces and you'll need to delete those too using a section plane to look inside the form can help in this regard. Remember that a manifold solid can only contain edges and faces. That is no nested groups or components. Every edge must support exactly two faces. That means - No 'faceless' edges [i.e. stray lines]. No edges with only one face [e.g. flaps, shelves or hole-perimeters]. No edges supporting three or more faces [e.g. two 'boxes' sharing a common edge for 4 faces]. Faces should be consistently oriented 'outwards' with the back-face materials 'inside' the form. Once you have a solid form reported in Entity Info you are good. Replace PROP with PROP-copy and try CutNFill again on these simplified forms - the skirts should now match so that hurdle is avoided...

@toremitico said: Where can I find the language folder to overwrite From what I can see in the extension there is no language folder, at least in the freeware version. You could edit the HTML files for the dialogs. There are 27 of them. [image: 1780060566623-screenshot-5_29_2026-8_13_06-am.png] I expect you would also need to edit the .rbs files however that will be difficult since they are encrypted. You should contact the author to see if you can work with them to make the changes. The author holds the copyrights to the extension, anyway.

The curved stair primitive is relatively easy to create, it is all the details that are going to be fun. [image: 1780009028680-wall_su1149_800.jpg]

Hi, sorry for a late reply. I`m on windows 11, Nvidia 5070, SU v.26.2.243. And yes, it seems that the icon or the shortcut to activate a Fredo plugin tool must be doubletapped og hold for a sec. Exsample: selecting a box that I made and turened in to a group, then tapping the shortcut keys made for this tool (ctrl+shift+s) nothing happens. But if holding those keys for more than a second or holding ctrl+shif, then doubletap the S key the tool activates. and if i select the box and hover over the icon for that tool and click once, nothing happens, but if i double click the tool activates. This seems to bee with som of the Fredo tools but not all. Not working is: Tools on surface, Fredoscale (except for the cuick launcher icon, that calls upp the menu on one click), Joint push pull. Stencil, Fredo Stencil and more But som are working with one click ie.: FredoBend, Move and align ++ This is so wierd, and i have no idea of why this is. I was messing around with the Graphics settings for som "random crashes" after updating skechup, but they are now back to their original settings.

It works fine in SU2026 for me. The box is a component in this case. [image: 1779799408521-bm.gif]

@TIG I installed version 5.0.6 but it still doesn't work

@Didier-Bur Well, obviously the Roundcorner was the first one I tried – and failed exacly like the other popular bevel plugins. As long the bevel plugins can't do the simple and trivial trick to strictly preserve vertexes (even if they would fall back to 0-length edges) and keep the matches between the appropriate vetexes from the original and the beveled contour, it will surely fail on slightly more complex shapes as the concave one in my example. In these circumstances I'll be tempted to develop a workable extension for myself…

Extension Errors Report SketchUp: 26.1.252 OS: Windows 11 Ruby: 3.2.2 Extension: Layers Panel (1.2.2) Error: LoadError (cannot load such file -- Win32API) <internal:C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb>:85:in require' <internal:C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb>:85:in require' C:/Users/thana/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/jbb_layers_panel/layers_panel.rb:21:in <module:JBB_LayersPanel>' C:/Users/thana/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/jbb_layers_panel/layers_panel.rb:5:in <top (required)>' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/extensions.rb:197:in require' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/extensions.rb:197:in load' C:/Users/thana/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/jbb_layers_panel.rb:51:in register_extension' C:/Users/thana/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/jbb_layers_panel.rb:51:in module:JBB_LayersPanel' C:/Users/thana/AppData/Roaming/SketchUp/SketchUp 2026/SketchUp/Plugins/jbb_layers_panel.rb:35:in `<top (required)>'

Hi, has anyone tried this in 2026? I’ve noticed that the [Re]Name button has a glitch. On the first click, it produces strange 3- or 4-digit scene names like Scene 625, Scene 626, Scene 627. When you click the [Re]Name button again, the second time it corrects itself and gives the expected sequence, such as Scene 1, Scene 2, Scene 3, and so on. Thanks!

How big is that object ? Small geometry has issues because points closer than 1/1000" are regarded as coincident by SketchUp's engine. So tiny edges aren't made and the associated face can't be supported. Have you tried scaling it up x100 [or more] doing the 'rounding' then scaling it back down. Tiny geometry can exist within a model, but it can't be created by SketchUp.

thankyou this worked for me

@medeek Hey Nathan, Thanks for pointing that out. While Medeek Wall is excellent for framing, our primary focus with MuzWalls is specifically on masonry and solid wall construction. We are developing the extension to handle the nuances of these workflows in depth. Regarding wall interactions: MuzWalls utilizes a logic-based system for corners. It features an auto-miter capability that detects when two walls meet and automatically calculates the connection based on their respective angles. This allows the walls to join seamlessly as a continuous structure rather than remaining as overlapping or separate groups. We are continuously refining this system to ensure that masonry wall interactions inside SketchUp feel clean, intelligent, and highly automated. We'd genuinely love to get your feedback on this — and the wider community's too. Draw a couple of walls, drop a window, drag an endpoint around and see how the corners hold up. 3-day trial, no card required: https://muzwalls.com Best Regards Muzwalls - Morteza

If you want to disable it then you should use the 'SketchUcation' Plugins Manager red-button to 'Unload' it. After a restart of SketchUp it should no longer load. Pour désactiver ce plugin, utilisez le bouton-rouge «Décharger» du Gestionnaire de Plugins «SketchUcation». Après le redémarrage de SketchUp, il ne devrait plus se charger.

@Gowri211034 I can see in our system your user has made several purchase attempts. Unfortunately I can not see any of these purchase payments being completed. Have you received a receipt about the payment from PayPal or Stripe? If yes, please send it to support@sketchucation.com and maybe also by private chat to me.

@Rich-O-Brien Thanks, Appreciate the heads-up. I’m currently polishing nEVEn before the Extension Warehouse release. More screenshots and workflow demos coming soon.