[Plugin] ExtrudeTools - Full Set
-
TIG, it appears I am seeing a problem with the Extrude Tools extension. Any time I use it if I use Ctrl-Z to undo something, I am winding up with a rectangle at the axis base point in my model. Please see this thread
-
Which of the EEby... tools shows this ?
Initially I can't think of any that place a rectangle at the origin, outside of the main undo-loop ??
More details please... -
@tig said:
Which of the EEby... tools shows this ?
Initially I can't think of any that place a rectangle at the origin, outside of the main undo-loop ??
More details please...The only one I have been using is the vector one. I have tried several times since I first read your reply and have not been able to reproduce it again. It did happen several time before in both 2015 and 2016 (Pro for both).
-
Holaa ! Me podrías decir como descargo el plugin? por favor, no encuentro el link de descarga...
-
@fergutierrezg said:
Holaa ! Me podrías decir como descargo el plugin? por favor, no encuentro el link de descarga...
Look at the bottom of the first post.
-
Hi there,
I have problems with Extrude Tools and Sketchup 2017:
Even after disabling all other plugins I get the following results running for instance “Extrude Edges by Rails” or “Extrude Edges by Rails To Lattice”:
The tool only creates the control/construction points (no faces) and I get some information in the Ruby Console:
Another example: “Extrude Edges by Loft” creates triangulated faces but no Quad Faces if I select this option.
(Some information: Extrude Tools 3.0 (I installed it using the SketchUcation Tool, no problems with Sketchup 2016, system: windows 7, 64 bit, Intel i7 3770, NVidia GTX 750 Ti, drivers: 375.57 and the newest 375.86)Any ideas?
-
Thanks for the reports.
I see it too... investigating...
It's the way v2017 replaces an exploded entity with a duplicate, with another ID, and so you can no longer collect a reference to it before exploding, it must be done as part of the explode itself to get the correct reference...
Working on it - I suspect it affects many of the tools... -
Hi TIG - if you can - have a look at the offset please, it seems the reading is slightly off (no pun!). didn't have time to look at the code myself
-
The whole ExtrudeToolset is foobar thanks to the way v2017 handles exploded entities and looses references but while keeping id's...
I'm working on a fix...
-
yes, the offset was always a smidge off (only in terms of measurements) - other than that, the script works fine on both (on my super system of course), thanks!
-
It's worked great on SU2016 but some Error happen on SU2017. Can u please fix it soon???
-
@hell0304 said:
It's worked great on SU2016 but some Error happen on SU2017. Can u please fix it soon???
I know !
The new API in v2017 breaks some things [references, IDs etc]
I have been working on a fix for the last few weeks...
It has proven awkward !
Watch for updates... -
Thsnks TIG, Watching for this. Though I am holding off on using v2017.
-
i cannot get eebf to work in 2017 I have uninstalled and reinstalled 2017 one plugin at a time starting with freedo tools any suggestions
-
@gmthompson said:
...any suggestions
Suggestions? Yes. Read TIG's last post in this thread. He's working on a fix. I'm sure when he has a suitable fix, he'll release an update.
-
Update is 90% done... but it's not there yet...
-
TIG, we are lucky to get these valuable tools in the first place, I am not going to be pushy over the fix, I can always sort the one piece of geometry in sketchup 2016 until this is sorted to your satisfaction. Many thanks for making sketchup better by your hard work.
-
Updates needed for Sketchup 2017 on "Extrude Edges by Rails" , Lattice, face. Works good on 16 guess it has something to do with ruby 2.2 used in 17.
-
If you look a couple of posts earlier on in this thread, you'll see that the update is in progress...
-
I know 'they' broke it in v2017.
They changed the way exploded groups etc no longer keep an enduring reference to the contents !
I have fixed this in several plugins.
I have fixed it in this toolset too, but I;ve not reissued yet, because I have an intractable bugsplat occurring if the user does an undo after making some forms, in some of the tools.This is very odd, since it seems unrelated to the main problem they created.
In essence, the paths [profiles/rails] are temporarily grouped during the processing to stop them getting messed up by the later processes. At the end it is exploded back as it was. That works fine, but if the user does an undo it bugsplats...
It is very odd.
I am considering alternative solutions...
Advertisement