[Plugin] FredoSection - v1.5c - 30 Jan 26

Gjenio

Adding more standard vector hatch types (ANSI) would be a huge time-saver for me. Currently, LayOut doesn't export them as vector entities, which I need when collaborating with other offices

TIG

There are a lot of ANSI vector hatch patterns...
Here are 900+ paid -
https://www.etsy.com/uk/listing/1602392539/900-autocad-hatch-library-2d-cad?ls=r&external=1&rec_type=cs&ref=landingpage_similar_listing_top-5&pro=1&dd=1&content_source=c2a30f16a8732b6e51f219c67c46c892%253ALTc4ad72921e17107e0a3f67f035a6ecc77a3039a0&logging_key=c2a30f16a8732b6e51f219c67c46c892%3ALTc4ad72921e17107e0a3f67f035a6ecc77a3039a0
These are free -
https://www.cadblocksdwg.com/hatch-patterns-download.html

Perhaps suggest a base set of say 16 patterns ?
If they can add their own patterns it's then down to each user ?

fredo6

I am not familiar with the DWG export from layout.

My understanding is that:

Sketchup only uses Raster material. There is no such concept as Vector pattern. Otherwise, this is just linework.
Layout renders the Sketchup model based on these Raster materials and treats them as images. I am not aware that Layout would convert them to vector.
Layout seems to have a concept of Pattern which can be used for filling shapes. That may well be converted to vector patterns (.pat) when exporting to DWG. However, my understanding is that this only applies to shapes created and painted in Layout, not coming from the 3D model.
FredoSection Vector Hatching is just a set of edges and faces, as the rest of the geometry. So, it renders as such in Layout. But I don't think it will end up as CAD patterns when the Layout document is exported to DWG.

I don't know if I am correct....

sayerdesign

Thank you, all, for picking up this dialogue.
First off, I should give my thanks and gratitude to Fredo6 for making this plug-in happen. Thank you!
For my workflow, I avoid using anything but the Vector setting for scenes in Layout, and I don't use a style that shows the textures unless it's abosolutely needed . Raster doesn't handle lines well and is 'fuzzy'. The Rastor materials included look great in Sketchup, but don't translate over to Layout. When I tried a hybrid compromise, the Rastor section fills become blurry and not very useful.
I'd be more than happy to give examples of hatch patterns I'd love to see available for the types of materials I use creating drawings for cabinetry (in addition to the Vector patterns currently available at least four different types of sheet goods, three types of solid wood, plaster/gypsum and stone countertops would all be fantastic).
If it's something that's doable with relative ease for you, Fredo, how can I help?

fredo6

Raster materials often look blurry in Layout (especially when you zoom). However, when you print the document on paper at the correct paperscale, you get a readable pattern visually.

Anyway, to help progressing, I would suggest you post a few images of you vector patterns (e.g. four different types of sheet goods, three types of solid wood, plaster/gypsum and stone countertops).

sayerdesign

Here's a group of them that were on the https://www.cadblocksdwg.com/hatch-patterns-download.html website that TIG shared previously. If this group were avaiable, that would be great so far as I'm cencerned.

fredo6

Getting these patterns as Vector is technically feasible, at least by me in FredoSection.

However, if you use them in a real model, that would represent a lot of lines (and a longer time to decoarte cut faces). Keep in mind that in FredoSection, a Vector pattern is just drawing edges in the model. Already with simple hatches, you have a lot of geometry created.

As suggested, could you try with these patterns in Raster (most of them are in the standard materials, under 'Patterns') and check they print correctly when the proper paperscale is set in Sketchup scenes and corresponding Layout viewports.

slbaumgartner

I just got these errors reported in the Ruby Console when I opened a new model on my Mac (SketchUp 2026, macOS 26.2). Looks like a bug in handling MDI on the Mac:

<NameError: uninitialized constant F6_FredoSection::FredoSection>
/users/steve/library/application support/sketchup 2026/sketchup/plugins/fredo6_fredosection/bootstrap_fredosection.rbe:579:in `switch_model'
/users/steve/library/application support/sketchup 2026/sketchup/plugins/fredo6_fredosection/bootstrap_fredosection.rbe:459:in `model_changed'
/users/steve/library/application support/sketchup 2026/sketchup/plugins/fredo6_fredosection/bootstrap_fredosection.rbe:391:in `onActivateModel'

fredo6

NEW RELEASE: FredoSectiont v1.5b - 26 Jan 26

Requirements

LibFredo6: v15.8a or above
Sketchup version: SU2026 and above

FredoSection 1.5b is a maintenance release including:

Bug fixing for Mac

Home Page of FredoSection for information and Download.

Main post of this FredoConnect thread.

slbaumgartner

And another error popping up in the Ruby Console on my Mac:

#<NoMethodError: undefined method dialog_close_all' for #<F6_FredoSection::Common:0x00000001738b4f10>> /users/steve/library/application support/sketchup 2026/sketchup/plugins/fredo6_fredosection/bootstrap_fredosection.rbe:587:in close_model'
/users/steve/library/application support/sketchup 2026/sketchup/plugins/fredo6_fredosection/bootstrap_fredosection.rbe:472:in model_changed' /users/steve/library/application support/sketchup 2026/sketchup/plugins/fredo6_fredosection/bootstrap_fredosection.rbe:390:in onOpenModel'

fredo6

NEW RELEASE: FredoSectiont v1.5c - 30 Jan 26

Requirements

LibFredo6: v15.8a or above
Sketchup version: SU2026 and above

FredoSection 1.5b is a maintenance release including:

Another bug fixing for Mac

Home Page of FredoSection for information and Download.

Main post of this FredoConnect thread.