[image: 1779307396224-depot-collinistr-su-resized.jpg] [image: 1779307504607-collinistr001-resized.jpg]

@Rich-O-Brien Thanks for confirming.

Hi Send me an email at support@sketchucation.com regarding publishing here.

Please rollback to Sketchucation ExtensionStore v5.0.6. There is a bug in the ne licese update. Sorry for that.

No, just an HDRI and a mostly closed area. HDRI comes in via the missing "ceiling". [image: 1779284038891-exterior-view-resized.jpg]

Salut, j'ai préparé mes tablettes d'acide, et j'ai cliqué sur les liens, en vain... je vois pas les vidéos

another finished project: https://youtu.be/4-ISSe_TL2M

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!

Hey, Rayscaper users! Rayscaper 0.9.94 Beta is available. You can get it via: The SketchUcation store. Direct download: Rayscaper_Win_0.9.94_Beta.rbz. I recommend upgrading to the latest version. What Changed? Fix occasional skewed or corrupted textures in renders. Fix render failures when emissive materials are assigned to a group or component instance instead of directly to faces. (Cheers @krass for helping me find this bug!) Full release notes: rayscaper.com/manual/release-notes Help Me Build the Community If you like Rayscaper, please share your renders (final or work-in-progress, it doesn't matter)! This is motivating and helps me showcase its capabilities to new users. Follow me on X. Happy Rendering! Thomas

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)>'

...I'm back from a little trip. Congratulations on this successful test video edit. You've really incorporated quite a lot of CapCut tricks into it

@onzki Try it now

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!

[image: 1779181408079-gif_faut.gif]

[image: 1779181408079-gif_faut.gif]

Share an example SketchUp file that illustrates the issue.

@kesztio : Hi, Emboss was originally coded to create square or rectangular stone blocks in a medieval or renaissance fashion, for my personnal usage. Each selected face is extruded and then the upper face is scaled, according to your parameters. So the script uses the pushpull command, then the scale command. The scaling is done by default around the center of the face (no way to change that). Obiously it works for convex faces but not for concave faces. In your example, the script should scale each of the three parts of the face around their center, then scale the arcs, the re-create the sides (sloped faces. I'm afraid (sure) I can't do that, that's beyond my knowledge. I recommend you to use 'roundcorner' by Fredo6 with the 'bevel' command(see animated gif below). [image: 1779090397210-roundcorner.gif] Link: https://sketchucation.com/plugin/1173-roundcorner Regards

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.

@mamoodoo said: here is just the model To be fair you included a whole bunch of hidden useless stuff. Here's your model fixed and solid. I included the different stages that I used to completely rework it, so you can take a closer look to a better approach. Facade_fixed.skp You don't necessarily need Rhino to work with this kind of stuff, as long as you are well organized and do everything in the proper order. Your approach was fundamentally wrong because you duplicated the geometry 4 times and gave it a thickness BEFORE the deformation. Is better to work with modular flat pieces, then deform, then add thickness, then merge them together. In this way you avoid feeding ~90k veritces into the deformation algoritm when you can Flowify just ~3k vertices. I didn't touch your curves, but I would strongly recommend that next time you balance the polycount of your curves in a more clever way. You have tons of segments for very small curves, but on the other hand you have only 4 segments on the main curvature. That's a quite bad density balance. You should have more segments for the big curve and less segments for the small curves. I suggest to have a look to Fredo's Curvizard for this kind of optimization As a side note, your Flowify rig was completely wrong. You need to connect the corresponding vertices, not the closest ones (that was causing flipping even with basic test shapes) and you should not add tons of unnecessary cells to the grids.