[Plugin][$] FredoScale - v3.6a - 01 Apr 24

[Dave R]

Thank you.

I can see the reason for opening the component for editing because all of them would rotate at the same time. I expect you could still do that with the line but I think I'd leave the component as is and rotate the whole thing.

[JQL]

Fredo,

First of all thanks for this and all your wondeful plugins. There can't be thank enough for this contribution but I've came here bragging with an issue I've come across with Box Scaling to Target.

It is a very useful and natural way of scaling things in Sketcbup and it replaced my S key long time ago. However, today, a very simple operation gave me an unexpected result and I never seen this before. Probably it's because I hadn't noticed it or because of some setting I have changed that I'm not finding right now.

I don't know where an I failing but please take a look at this:

Is there anyway I can override the snapping factor and get on with only the distance on VCB?

Thanks and best regards,

JQL

[fredo6]

@JQL,

Probably a small bug which can be fixed, as the VCB should have the priority over the snapping. I'll have a look and advise

Fredo

[fredo6]

@JQL

Not sure I understand exactly the problem? Does it happen only in the Target mode?

I made a small change in the code to avoid roudning factors in Target mode. Since you know what is the problem and have a model to test it, could you tell me if this gives the expected result.

Just drop the attached file in Fredo6_FredoScale subfolder.
FredoScaleBox.rb

Thanks

Fredo

[JQL]

Fredo,

Thanks for your trouble.

I noticed random results when trying to reproduce the error today, with the old version of the file you now sent. This link is for a video that helps me describe what was happening:

https://dl.dropboxusercontent.com/u/14043066/scale%20to%20box%20random%20behaviour.avi

Funny thing is that today, Box Scale to Target was giving me trouble not along the axis but on the diagonal square.

Your fix seems to clear all randomness and so far I'm getting the expected results though, of course disregards snapping.

I'll keep using it but I'm available for anything you need to test.

Thanks,

JQL

[fredo6]

JQL,

Thanks for the feedback.
If you think this is OK, then I will publish the fix.

Thanks for signaling the bug.

Fredo

[JQL]

Fredo,

Thank you for your time. For me it's more important that the scale is acurate than having it snap, so the fix is more than OK... it's perfect!

Thanks again and best regards,

JQL

[mitcorb]

Hi Fredo:
Here is another question specifically on FredoBend:
In the picture and in the skpv6 I am trying to bend the tan colored element so that its ends touch the rim of the circle on the ground plane. The whole figure is a component and the floating tan element is a group. Place the protractor at the center of the standing circle and bend the object as a group. I even placed a non grouped vertical reference line for the distance of the bend to assist.
Each time I try, I note in the Measurement Box a value of -4.5 degrees. I think I am following the tooltips correctly and visually the object seems to touch down. If I accept -4.5, the edge ends up more like -2.25, so I immediately correct that to -9 degrees and it might bend entirely the other direction, or bend-- I don't know-- maybe -1.125? The inferencing appears to act correctly, but I have to wonder if this is related to JQL's issue? The other real possibility is that I am not properly doing the procedure.
Please show me what I am missing.

---

---

circledesignwarpv6.skp

[mitcorb]

My workaround was to overbend by a smidge, lift the end up to meet the base circle. Bend the other end-- again overbend it. Go back to the other end to set the center of rotation and rotate the other end to touch the face of the circle. If I wanted the bent piece to span to the circumference, I would have to use Scale or Stretch, which I will try next.

[fredo6]

NEW RELEASE: FredoScale v2.5b - 05 Feb 14

FredoScale 2.5b fixes a bug related to the accuracy of scale factors for Box Target mode. This was signaled by JQL (see this thread).

FredoScale 2.5 requires LibFredo6 5.4 or higher.
Ideally, take this opportunity to move to LibFredo6 5.6.

See main post of this thread for Download.

Fredo

[mitcorb]

Hi, Fredo:
See my posting above your update announcement. I updated and then went back to the model. I got a bugsplat and sent it in. This was just an attempt to overcompensate for the bend repeatedly falling short. I measured the angle for the bend with the Sketchup protractor. The value was ~-4.475 deg. Doing the bend with the inferencing I saw ~-4.5 deg.
What I did differently is set the center of the bend on the ground plane below the center of the standing circle and inferenced. Still got the extremity to go only ~half the distance. While attempting to correct this in the Measurement Box, the Bugsplat occurred.
I am sure you are busy.

[tulacong]

Happy new years luna 2014

[fredo6]

@mitcorb said:

Hi, Fredo:
See my posting above your update announcement. I updated and then went back to the model. I got a bugsplat and sent it in. This was just an attempt to overcompensate for the bend repeatedly falling short. I measured the angle for the bend with the Sketchup protractor. The value was ~-4.475 deg. Doing the bend with the inferencing I saw ~-4.5 deg.
What I did differently is set the center of the bend on the ground plane below the center of the standing circle and inferenced. Still got the extremity to go only ~half the distance. While attempting to correct this in the Measurement Box, the Bugsplat occurred.
I am sure you are busy.

I need to revisit the way target is inferenced in this tool, for sure. And post-edition too, as you crash may be related to the fact that, once bent, the shape becomes overly triangulated.
It's an old plugin, and I don't even remember if there is a trick to achieve what you wish to do.

In any case, the value of the angle in the VCB is twice the actual angle measured with the Protractor. I measured 6.382 degree with the Protractor, so you need to enter 12,75 degree in the VCB.

I'll have a look when I have time.

Fredo

[mitcorb]

Thanks, Fredo:
This is an example of something that I have noticed from some time back. I just assumed it had something to do with the nature of 3d modeling in Sketchup, and did not pursue it until now. JQL's question resparked it while I was doodling this model. FredoBend works well enough for modeling by eye and impromptu modification. And, I really wasn't intending to be very precise, because there are other ways to achieve what I was doing.
Thanks again for all you do.

[hiroya]

good

[Mike Whitton]

---

I have just installed SU 2014 - I cannot get any of the Fredo 6 plugins to work. Am I doing anything wrong or are they all not yet compatible with SU 2014?

[Dave R]

Did you just copy the files over from the old installation? Download fresh version of Fredo's plugins from the Plugin Store. Or better, install the SCF Plugin Store plugin and install Fredo's plugins automatically. Make sure you get the current version of LibFredo, too.

[veerlexyz]

Mike,

Turn your Sketchup off and on again. That worked for me.
This is what I wrote about it in the topic Sketchup 2014.
Libfredo6 keeps "Uninstalled" in the list "My Extensions" in "Extension Warehouse" although it is working. I could not install it with the Extension Warehouse but used the .rbz file instead. Same with Fredo Scale and Fredo Tools. These ones were not visible in Sketchup untill I turned the programm off and on again. Although they stay marked "Uninstalled" in "Extension Warehouse" the plugins do work fine.
My other plugins seem to work. Not done them all...

Veerle

[dacastror]

The tools in this plugin having to modify geometry, causing "bugs plats" in one instance with instances nested inside, works well when the tool only affects axes

I understand that exploiting all interior groups solved the problem, but would be good if the user had some kind of warning

I'm using the latest version of this plugin in Sketchup 8 (Spanish version)
I attached a file as an example of a group that can cause problems

grupos.skp

forgive errors of translation (google translator)

[Dave R]

What a strange way of grouping things. It makes no sense.

Still, I'm not having any difficulty modifying it with FredoScale. Maybe you could show what you are trying to achieve?