[Plugin Library] LibFredo6 - v16.2b - 22 Sep 26

fredo6

NEW RELEASE: LibFredo6 v16.0a - 08 Aug 26

LibFredo6 16.0a is a maintenance release. It includes changes related to:

Bug Fixing for ThruPaint (visibility of palette)

Requirements: SU2017 and above

See plugin home page of LibFredo6 for Download of LibFredo6.

Main Post of the LibFredo6 thread

fredo6

NEW RELEASE: LibFredo6 v16.0b - 19 Aug 26

LibFredo6 16.0b is a maintenance release. It includes changes related to:

Bug Fixing for dialogs when V-Ray is present

Requirements: SU2017 and above

See plugin home page of LibFredo6 for Download of LibFredo6.

Main Post of the LibFredo6 thread

pep75

Schermafbeelding 2026-08-27 102436.png

After the update I got this error...Sketchup also won't boot! When I uninstall all Fredo-plugins Sketchup start-up again. Does anyone else has this problem?

Rich O Brien

@pep75 said:

Does anyone else has this problem?

No, did you try uodating SUClock to 3.1?

SketchUp Plugins | PluginStore | SketchUcation

SketchUp Plugin and Extension Store by SketchUcation provides free downloads of hundreds of SketchUp extensions and plugins

(sketchucation.com)

pep75

No! I don't even know what SUclock is...:( But when I remove all the FREDO-plugins Sketchup start normal again.

Rich O Brien

If you look at your error message it references SUClock 2.0

pep75

Thanks, but it also refers to Libfredo6.

fredo6

NEW RELEASE: LibFredo6 v16.1a - 31 Aug 26

LibFredo6 16.1a is a maintenance release. It includes changes related to:

Future compatibility (SU2027)
Bug Fixing, possibly for Mac

Requirements: SU2017 and above

See plugin home page of LibFredo6 for Download of LibFredo6.

Main Post of the LibFredo6 thread

Rienk

@fredo6

Hi Fredo since today 2 september I updated version LibFredo6 V16.0a 8 aug 2026 to the latest LibFredo6 V16.1a but all your plugins dont work anymore. Where can I find the prior version. I would love to get this old one. Because this version workes for me fine. I was working with curviloft and since the latest version it don't work.

I am working on the PC with SketchUp 2026. There is no error message but it does nothing. I tried several times to start SkectUp but it still doesn't do nothing.
I tried several of your plugins but they doesnt start

With regars,

Rienk

fredo6

When you start Sketchup, do you see the menus for the plugins. Do you see the menu Window > LibFredo6 settings.....?

Rienk

Yes you mean the window check Fredo6 Plugins for Update?

Rienk

@fredo6

Rienk

@fredo6

You mean the dialog window "check Fredo6 Plugins for Update?

I started SketchUp again and It seems to work fine with your plugins.
Thanks for your reply.

Rienk

MDVolle

@Rienk My plugins also stopped working correctly with the latest tools update - curviloft is not generating mesh and it appears that edge picker has a typo in it but I can't edit the code

TIG

@MDVolle
Please explain what's not working, any errors, any Ruby Console errors etc.
What is this 'typo' - tell us [ @fredo6 ] so he can fix it...

kashintsev

Hi @fredo6 and all,

After two hours of trying to fix the Fredo update-check crash (spoiler — fixed it), here's what I found. Might be useful for pep75/Rienk/MDVolle above too, since it looks like the same class of issue.

Setup: macOS 26.6, tested side-by-side across three SketchUp installs on the same Mac — SketchUp 2025, SketchUp 2026 and SketchUp 2027, each with its own LibFredo6 16.1a (+ FredoTools + JointPushPull) installed via Sketchucation Tools.

Symptom (SketchUp 2025 and SketchUp 2026 — identical on both): the "Check Fredo6 Plugins for Update" dialog opens completely blank (no version table, no icon, nothing), and the Ruby Console shows:

!LibFredo6: Error when requiring Binary .../Fredo6_!LibFredo6/Binaries/Mac_32/bin_body_Lib6G6.bundle - dlopen(...) tried: '.../bin_body_Lib6G6.bundle' (code signature invalid in <...> '.../bin_body_Lib6G6.bundle' (errno=1) sliceOffset=0x00054000, codeBlobOffset=0x000500B0, codeBlobSize=0x00004CE0), ... - .../bin_body_Lib6G6.bundle
#<NoMethodError: undefined method register_from_key' for Traductor::ChromiumWdlg:Class> .../body_lib6chromiumwdlg.rbe:1498:in show'
.../body_lib6upgrade.rbe:864:in initialize__' .../lib6upgrade.rbe:161:in initialize'
.../lib6upgrade.rbe:154:in new' .../lib6upgrade.rbe:154:in show'
.../lib6upgrade.rbe:66:in time_for_check?' .../top_libfredo6.rbe:514:in block in after_startup'

So the update dialog can't fully init because the ChromiumWdlg engine's native module (bin_body_Lib6G6.bundle) fails to dlopen — macOS rejects its code signature at runtime.

Important: SketchUp 2027, with the literal same LibFredo6 16.1a files, has no problem at all — dialog renders fine, no console errors. So this doesn't look like a corrupted download or a bad LibFredo6 build; it looks like SketchUp 2025/2026 vs. 2027 differ in how they enforce code-signing/library validation for third-party native bundles at dlopen time.

What did NOT fix it (ruling out a leftover-config issue on my end):

Fully quit SketchUp.
Removed every Fredo6 folder + .rb loader from Plugins (LibFredo6, FredoTools, JointPushPull).
Deleted every orphaned Fredo6 key from the SketchUp prefs plist (ALToolPalette_Fredo6_, Fredo6_CheckForUpdateWarning.) — leftovers from older Fredo tools removed previously.
Reinstalled LibFredo6 16.1a completely fresh via Sketchucation Tools.
Exact same blank dialog / same console error on the totally clean install.

What DID fix it (local workaround): re-signing every .bundle under Fredo6_!LibFredo6/Binaries with a local ad-hoc signature:

find ".../Fredo6_!LibFredo6/Binaries" -name "*.bundle" -exec codesign --force --deep --sign - {} ;

After this, the dialog renders completely and the console is clean. codesign -dv on the original file actually reported the signature as valid (TeamIdentifier 66M89AU23J, properly signed 31 Aug 2026) — it's specifically the runtime dlopen/library-validation check inside SketchUp 2025/2026 that rejects it, not a malformed file.

This is obviously just a workaround I have to redo after every LibFredo6 update/reinstall, not a real fix — posting in case it helps track down why 2025/2026 reject it while 2027 doesn't.

fredo6

@kashintsev

Thanks for the description.

For whatever reason, the .bundle binary files fail to load for a question of signing and this only concerns SU2026. Note that in SU2027, the .bundle has the same name but is different, as it is for Ruby 3.4, versus Ruby 3.2 for SU2026).

Could you try with LibFredo6 v16.1g, just published and advise if this gets better.