[Plugin] FredoTools - v4.5c - 24 Jun 24

fredo6

That occur on SketchUp 2018 and SketchUp 2017, I didn't test it on 2016.

Hi,

I know there is this random bugsplat, but I am unable to reproduce it in my own environment.

If you have it, could you send a report to Sketchup in the bugsplat window, note the bugsplat record number and post or send this crash number to me.

Thanks

Fredo

Mousa_SA

@fredo6 said:

I know there is this random bugsplat, but I am unable to reproduce it in my own environment.

If you have it, could you send a report to Sketchup in the bugsplat window, note the bugsplat record number and post or send this crash number to me.

Fredo

Hi,

I thought this update has a fix for these random bugsplat. The Bugsplat record number is #37782
I have sent the bugsplat report to you as a PM.

Thanks

fredo6

NEW RELEASE: FredoTools v3.2c - 12 Mar 18

FredoTools 3.2c fixes a major bug in the calculation of volume in SolidVolume

See FredoTools plugin home page for Download.

See also main post of this thread for User Discussion.

Fredo

rv1974

Fredo, in this particular model reverse\ orient tool fails to exit with savedresult. could you take a look? Thanks!

kkk.rar

fredo6

@rv1974 said:

Fredo, in this particular model reverse\ orient tool fails to exit with savedresult. could you take a look? Thanks!

I tried on your model but AutoOrientFaces does the job and performs correctly the reversing.

The issue with your model is that each of the 12 subgroups have a quite large number of faces. In particular the two wheels which have 3,218 faces. The whole model would probably need a rework, because the number of faces seems oversized for a rather boxy shape.

I would probably need to optimize the algorithm. The white screen is just when processing the two wheels.

Fredo

JQL

Hi Fredo,

I've noticed that your tools don't follow the convention for selecting a surface with a single click.

The selection method is assuming two or more faces connected by a hidden edge to be a surface, while sketchup convention assumes a surface to be at least two faces connected by a soft edge.

Is this by design?

Thanks,

João

fredo6

@jql said:

Hi Fredo,

I've noticed that your tools don't follow the convention for selecting a surface with a single click.

The selection method is assuming two or more faces connected by a hidden edge to be a surface, while sketchup convention assumes a surface to be at least two faces connected by a soft edge.

Is this by design?

Thanks,

João

In general I assume that if you don't see the edge on the screen, the bounding faces are part of the same click-selection. When Geometry Hidden is turned on, then faces behave as separate.

This may not be what the user wants in some occasions; this is why I also have explicit options with palette buttons.

Which tool of FredoTools are you referring to ?

Fredo

JQL

I'm referring to every tool I guess. I was convinced it had to do with a global selection method defined by LibFredo.

I often require the use of surfaces and treat them as such in Sketchup. But for JPP, reverse/orient faces, or thrupaint, I often had problems and didn't understand why. So I started selectin the surfaces first, with regular sketchup selection tool. So I only recently found out what was happening...

fredo6

@jql said:

I'm referring to every tool I guess. I was convinced it had to do with a global selection method defined by LibFredo.

I often require the use of surfaces and treat them as such in Sketchup. But for JPP, reverse/orient faces, or thrupaint, I often had problems and didn't understand why. So I started selectin the surfaces first, with regular sketchup selection tool. So I only recently found out what was happening...

Is this now as you expect?

Rich O Brien

Fredo,

Is it possible to add Cast Shadows On/Off to the Face Triangulator tool?

JQL

@fredo6 said:

@jql said:

I'm referring to every tool I guess. I was convinced it had to do with a global selection method defined by LibFredo.

I often require the use of surfaces and treat them as such in Sketchup. But for JPP, reverse/orient faces, or thrupaint, I often had problems and didn't understand why. So I started selectin the surfaces first, with regular sketchup selection tool. So I only recently found out what was happening...

Is this now as you expect?

Not quite. What I would expect is that only with soft edges, two or more faces would be considered surfaces, as in sketchup.

fredo6

@jql said:

@fredo6 said:

@jql said:

I'm referring to every tool I guess. I was convinced it had to do with a global selection method defined by LibFredo.

I often require the use of surfaces and treat them as such in Sketchup. But for JPP, reverse/orient faces, or thrupaint, I often had problems and didn't understand why. So I started selectin the surfaces first, with regular sketchup selection tool. So I only recently found out what was happening...

Is this now as you expect?

Not quite. What I would expect is that only with soft edges, two or more faces would be considered surfaces, as in sketchup.

Never noticed for the Hidden?

Can be done, but this impacts everyone that is used to or prefer the current behavior. Indeed, the strng argument is that this is how Sketchup does the selection.

JQL

Well... That's a tough one. Make it coherent with Sketchup or keep it as it is for every user sake?

What if people do what I did and don't use the option as they don't quite understand it?

Or what if, following the hidden preferences you have, you would have an option of surface selection method?

PAragao

Hi all,

I think this tool will be my savior since I keep finding mismatches on the edges of my sketch. However, when I try to tell it to fix the edges it gives the error "Cannot create unit vector from zero length vector"

Anyone has an idea how to solve this?

Thanks.

Date: 08-Apr-18 14:45:11
An error occurred in Edge Inspector
Error during Inspection

Cannot create unit vector from zero length vector

body_fredotools__edgeinspector.rbe: 3286 -- axes
body_fredotools__edgeinspector.rbe: 3286 -- zero_edge_disolve_edge
body_fredotools__edgeinspector.rbe: 3269 -- block in zero_edge_absorb_final
body_fredotools__edgeinspector.rbe: 3249 -- each
body_fredotools__edgeinspector.rbe: 3249 -- zero_edge_absorb_final
body_fredotools__edgeinspector.rbe: 3379 -- block in zero_edge_resolve
body_fredotools__edgeinspector.rbe: 3367 -- each
body_fredotools__edgeinspector.rbe: 3367 -- each_with_index
body_fredotools__edgeinspector.rbe: 3367 -- zero_edge_resolve
body_fredotools__edgeinspector.rbe: 2706 -- call
body_fredotools__edgeinspector.rbe: 2706 -- block in execute_fixing
body_fredotools__edgeinspector.rbe: 2703 -- each
body_fredotools__edgeinspector.rbe: 2703 -- each_with_index
body_fredotools__edgeinspector.rbe: 2703 -- execute_fixing
body_fredotools__edgeinspector.rbe: 1713 -- robot_fixing_execute_single
body_fredotools__edgeinspector.rbe: 1703 -- robot_fixing_exec
body_fredotools__edgeinspector.rbe: 1686 -- robot_fixing
body_fredotools__edgeinspector.rbe: 1573 -- block in resolver_fixing
lib6operation.rbe: 332 -- call
lib6operation.rbe: 332 -- step_geometry
lib6operation.rbe: 374 -- start_execution
body_fredotools__edgeinspector.rbe: 1573 -- resolver_fixing
body_fredotools__edgeinspector.rbe: 1924 -- block in palette_floating
body_lib6palette.rbe: 3754 -- call
body_lib6palette.rbe: 3754 -- execute_button
body_lib6palette.rbe: 3559 -- onLButtonUp
lib6palette.rbe: 91 -- onLButtonUp
body_fredotools__edgeinspector.rbe: 786 -- onLButtonUp

fredo6

@paragao said:

Hi all,

I think this tool will be my savior since I keep finding mismatches on the edges of my sketch. However, when I try to tell it to fix the edges it gives the error "Cannot create unit vector from zero length vector"

This looks like a bug (I fixed it). It does mean that you seem to have zero-length edges in your model.

By the way, if you are lucky to have 'ill-edged' models, I am interested for testing EdgeInspector.

Fredo

fredo6

NEW RELEASE: FredoTools v3.2d - 09 Apr 18

FredoTools 3.2d is about bug fixing in EdgeInspector.

See FredoTools plugin home page for Download.

See also main post of this thread for User Discussion.

Fredo

JQL

@fredo6 said:

By the way, if you are lucky to have 'ill-edged' models, I am interested for testing EdgeInspector.

Fredo

What exactly are we supposed to find in these models?

fredo6

@jql said:

@fredo6 said:

By the way, if you are lucky to have 'ill-edged' models, I am interested for testing EdgeInspector.

Fredo

What exactly are we supposed to find in these models?

Tiny edges, needle eyes, etc....

Fredo

Areczan

Hi, I'm struggling with the following error. Seems like there's some problem between Fredo Tools and V-ray. I had to reinstall Sketchup and made sure I installed it with "Run as Administrator". Repair function doesn't help either...

Error: #<ArgumentError: wrong number of arguments (0 for 1)>
c:/users/am/appdata/roaming/sketchup/sketchup 2018/sketchup/plugins/fredo6_!libfredo6/lib6upgrade.rbe:158:in initialize' c:/users/am/appdata/roaming/sketchup/sketchup 2018/sketchup/plugins/fredo6_!libfredo6/lib6upgrade.rbe:153:in new'
c:/users/am/appdata/roaming/sketchup/sketchup 2018/sketchup/plugins/fredo6_!libfredo6/lib6upgrade.rbe:153:in show' c:/users/am/appdata/roaming/sketchup/sketchup 2018/sketchup/plugins/fredo6_!libfredo6/lib6upgrade.rbe:66:in time_for_check?'
c:/users/am/appdata/roaming/sketchup/sketchup 2018/sketchup/plugins/fredo6_!libfredo6/top_libfredo6.rbe:377:in block in after_startup' C:/Program Files/SketchUp/SketchUp 2018/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:54:in call'
C:/Program Files/SketchUp/SketchUp 2018/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:54:in require' C:/Program Files/SketchUp/SketchUp 2018/Tools/RubyStdLib/rubygems/core_ext/kernel_require.rb:54:in require'
C:/Program Files/Chaos Group/V-Ray/V-Ray for SketchUp/extension/ruby/init.rb:1:in <top (required)>' C:/Program Files/SketchUp/SketchUp 2018/Tools/extensions.rb:197:in require'
C:/Program Files/SketchUp/SketchUp 2018/Tools/extensions.rb:197:in load' C:/ProgramData/SketchUp/SketchUp 2018/SketchUp/Plugins/vfs.rb:26:in register_extension'
C:/ProgramData/SketchUp/SketchUp 2018/SketchUp/Plugins/vfs.rb:26:in <module:VRay>' C:/ProgramData/SketchUp/SketchUp 2018/SketchUp/Plugins/vfs.rb:4:in <top (required)>'

fredo6

@areczan said:

Hi, I'm struggling with the following error. Seems like there's some problem between Fredo Tools and V-ray. I had to reinstall Sketchup and made sure I installed it with "Run as Administrator". Repair function doesn't help either...

Do you have the problem if you disable VRay?

Fredo