I was playing with amslib and msphysics plugin for an week and I have successfully compiled ams_l8b.so and msp_lib.so compatible to the SketchUp 2026 and fixed many warnings and errors.. it is now working good, but still I have to test all functions, if someone of you want to help me out to text all these so it will be easy and take less time, here is my Whats App + 923 143 142 423 I will send you a copy of working amslib and msphysics.

Version 4.5.8 - 05.30.2026 Added a curved stair option into the stair module. Added two new parameters for curved stairs into the draw and edit menus: Inside Radius, Curve Direction. Enabled treads, risers and framing (primitive) for curved stairs. [image: 1780126748710-wall_su1150_800-resized.jpg]

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]

After a hiatus of 14 years, here's v1.4 Please re-read the edited usage in the first post in this thread: https://community.sketchucation.com/topic/133971/plugin-texturerandomizer Download it from the PluginStore page or ExtensionStore dialog within SketchUp. https://sketchucation.com/pluginstore?pln=TextureRandomizer NOTE how the code and interface was revisited by myself and raumstaerke.de , who added a single dialog for settings using AI.

@bsfranza said: i would appreciate if there was an option to start directly without the initial popup of the material browser Unfortunately, this would require some heavy re-engineering of ThruPaint. Normally, you get it once by Sketchup session, so it's just a smaller inconvenience.

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]

Thank you too

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

Korean language detected by google. I am a SketchUp 2026 (version 26.2.243.64-bit) user. My graphics card is an NVIDIA GeForce RTX 2070 Super. 포럼 사용자들에게 질문이 있으신가요? poleom sayongjadeul-ege jilmun-i iss-eusingayo? What is your question for the forum?

@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…

Bug Report: SU2026 / Fatal crash on startup with D5 Render LiveSync (Errno::EISDIR) Hi Fredo, The last update doesn't fix the D5 issue. Either way, we can only use one of them (LOTT or D5 Render). So now my entire workflow is blocked, and so is the workflow of other D5 and LOTT users. We really need a QUICK fix for this, please. I am reporting a fatal initialization crash occurring on SketchUp 2026.1.2 when using the latest D5 Render LiveSync plugin alongside Lord of the Toolbars (v3.0a) and LibFredo6 (v15.9c). The Master Toolbar (yellow wheels) becomes completely unresponsive, and all custom toolbars disappear from the screen. The Ruby Console highlights an unhandled directory scanning error in lordofthetoolbarsmanager.rbe inside the ghost_command_register method. It appears the script tries to open a sub-directory as a file, throwing an Errno::EISDIR exception. The main folder causing the issue is d5_converter, located at: %AppData%\Roaming\SketchUp\SketchUp 2026\SketchUp\Plugins\d5_converter Exact stack trace: #<Errno::EISDIR: Is a directory @ rb_sysopen - c:/users/[username]/appdata/roaming/sketchup/sketchup 2026/sketchup/plugins/d5_converter> C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:2290:in `initialize' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:2290:in `open' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:2290:in `copy_file' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:1088:in `copy_file' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:887:in `block in cp' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:2481:in `block in fu_each_src_dest' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:2497:in `fu_each_src_dest0' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:2479:in `fu_each_src_dest' C:/Program Files/SketchUp/SketchUp 2026/SketchUp/Tools/RubyStdLib/FileUtils.rb:886:in `cp' c:/users/[username]/appdata/roaming/sketchup/sketchup 2026/sketchup/plugins/!!fredo6_lordofthetoolbars/lordofthetoolbarsmanager.rbe:733:in `ghost_command_register' c:/users/[username]/appdata/roaming/sketchup/sketchup 2026/sketchup/plugins/!!fredo6_lordofthetoolbars/lordofthetoolbarsmanager.rbe:1361:in `command_register' Temporary Workaround found: Renaming the d5_converter folder to _d5_converter allows LOTT to load correctly, but it completely breaks the D5 LiveSync connection. Downgrading D5 LiveSync to v1.6 also works. It seems a simple check to skip directories (like File.directory?) during the ghost_command_register file loop would prevent this crash. Thank you for your work!

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!

Version 3.8.2 - 05.17.2026 Cleaned up the filed and folder structure of the complex roof module. Enabled the truss template in the complex roof module. Added a "Roof Family" parameter into the draw and edit menus of the complex roof module. The complex roof edit menu now displays and allows configuration of custom roof planes.

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.