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

wyatt

Fredo,
Thanks for the quick reply. I have those 2 folders and 2 files, and indeed, the toolbar loads. See the pic.

Is LibTraductor.rb and LibTraductor.def from an old version, or an entirely different script? I actually tried deleting them, but then other (older?) plugins don't work - those errors say that LibTraductor.rb doesn't exist - so I reloaded them. I'm not sure where the .lang file came from. I only need the En version, so maybe that file isn't necessary.
Wyatt

chouaibcl65

thank you , i dont know how to download

Jean-Franco

Hi Chouaib,
go to the end of the first post of this thread and you will find the file to download.

chouaibcl65

thank yououuu

Mocom

i love your plug-ins you are the master thank you.

KarinaGM

I have a problem with the plugin. It suddendly stoped working.
A couple of hours ago I used it normaly. Now I can't bend or twist...
I haven't installed nothing new, just worked with huge files that sometimes crash.

Here I put some screenshots of what is happening now when I try to use radial bend

I downoladed and reinstaled the plugin and Libredo (just in case) in the correct path, just where it was this morning. I checked the list file by file (everything was there), anyway I deleted and place the new ones instead. No luck. Restarted pc (sometimes it works) no luck again.

thomthom

There is a toggle that makes it subdivide the object. Looks like you have turned it off. I can't remember what key toggled it though.

TIG

Read the manual... http://forums.sketchucation.com/download/file.php?id=35246

KarinaGM

well I read it... but until now it never ocured to me that the defaults didn't include slicing.
THANKS!

fredo6

@karinagm said:

well I read it... but until now it never ocured to me that the defaults didn't include slicing.
THANKS!

Slicer is activated by key F4.
Note that all options can also be activated via the contextual menu (right click).

Fredo

Barack

SUCH A POWERFUL PLUGIN--- FOR FREE!!! YOU ARE THE COOLEST!!! :D:D:D!!!

lensman

As I said somewhere else in a review of this plug-in, it goes waaaay beyond that status and should have been a part of the original programme. Google snap this guy up! - No, wait, don't!! - We'd have to pay for this stuff then!

Great stuff.

pyroluna

Someone is advertising for you, Fredo!

TIG

@barack said:

SUCH A POWERFUL PLUGIN--- FOR FREE!!! YOU ARE THE COOLEST!!! :D:D:D!!!

It is 'free' - but like many of us 'scripters' donations are accepted by Fredo - no matter how small they are - then at least it's a recognition of the efforts involved in making these tools for you - a euro/dollar or two/ten wouldn't hurt...

pilou

So comical
[flash=480,385:1r6pod0m]http://www.youtube.com/v/Z7HyPsyLY3A&hl[/flash:1r6pod0m]
[flash=480,385:1r6pod0m]http://www.youtube.com/v/tixFgx-Uv3I&hl[/flash:1r6pod0m]

rafaelds

Hi everybody, specially Fredo!
I'm not sure if this is the right place, but I think I found a bug in FredoScale and would like to report it. Here are the steps to reproduce it:

I've drawn 2 boxes. Each is an individual component. The one in the right has the top texture set to 'projected', the left one does not.

Using planar shearing, I 'shear-ed' both along the blue axis, by the same amount.

I opened the right component for editing. Just opened, did not even click on a single surface. Texture placement gets messed up.

After closing the component it's easier to spot the difference between both textures:

Even after undo'ing the operation, textures are still incorrect:

The same effect happens if the boxes are not components, but with slightly different characteristics: if each box is sheared individually, only the one with the projected textures is 'damaged'. But if both are selected at the same time and the shearing is done to the whole lot, both end up correct, even though textures are set to projected in only one.

I first noticed this effect in a model I am working on, but the problem seems more serious there. After opening the component textures are messed up, and show in different ways if a component is open or closed:

In this case I can't even repair the problem manually. I do have a hidden rectangle with the whole texture, from which I can pick the texture and paint the new created geometry, but the textures never show up correctly, it does not matter if set to projected or not. I wish I had made at least a daily backup... $:\$

fredo6

Rafael,

Can you post the skp file with the two boxes and texture.

Planar shearing is an atypical transformation, because it seems that SU also shears the reference axes of the component and groups. I don't know why, but this is what SU does. And this may be the reason why the textures cannot be projected correctly.

Anyway, I can try to find a way to overcome this

Fredo

PS: For recovering your initial model, did you try to use the autosave version.

rafaelds

Thanks for the quick reply, Fredo!
That model I used for the screenshot I no longer have, it was just something I put together quickly to illustrate. I just made another one, hopefully more explaining.
As for my model, never mind it. I use a program for online backup and sync'ing across computers and it turns out it stores previous versions of files as well.

Attached to this post goes a SKP file. It shows a similar operation performed on a pair of boxes, the one on the right having projected textures. Along the green axis different techniques with and without FredoScale are used, and the differences are shown.

boxes.skp

fredo6

@rafaelds said:

Thanks for the quick reply, Fredo!
That model I used for the screenshot I no longer have, it was just something I put together quickly to illustrate. I just made another one, hopefully more explaining.
As for my model, never mind it. I use a program for online backup and sync'ing across computers and it turns out it stores previous versions of files as well.

Attached to this post goes a SKP file. It shows a similar operation performed on a pair of boxes, the one on the right having projected textures. Along the green axis different techniques with and without FredoScale are used, and the differences are shown.

I had a look at the file, and it seems that it is related to the sharing of the component axes. You can of course remodify the axes so that they are orthogonal, but this does not restore the expected projected texture (however, subsequence projections are OK).
So, I may have no way to fix that, and it may be advised to first deform, and then apply textures.

Fredo

rafaelds

Thanks, Fredo.
I am working around this "issue" by unsetting the 'projected' flag from the appropriate faces prior to shearing with FredoScale. As can be seen in the SKP file I uploaded, FredoScale by itself does what I expected and projecting was unnecessary.