Plugins features in 3D World
-
I just got my copy of 3D World issue 117. It usually doesn't mention Sketchup that much, maybe a small note when a new version is released. But on page 66 I found two whole pages dedicated to 10 Must-have plugins. (The 10th wheren't actually a plugin, but a mention that it's worth to keep an eye on Sketchucation and PushPullbar.
whoop! whoop!
-
Whos had their name emblazoned in print then?
-
- Joint Push/Pull - Fredo
- Soap Skin Bubble - Josef Leibinger
- SketchyBevel - Chris Phillis
- Subdivide and Smooth - Dale
- Tools on Surface - Fredo
- SketchyFFD - Chris Phillis
- Bomb - Rick W
- FredoScale (though they used the old name FreeScale) - Fredo
- RealBooleans - Oscar
- Link to SCF and PPB
So no big surprises. Though I find the example usage of Bomb odd; "exploding everything down to base level before exporting, say, to a renderer." <- when is really needed? Is there renderers that require that? Nuking the model just seem to drastic...
-
No SketchyPhysics?
It's useful…
-
thomthom
it's not that strange to nuke a model before exporting to a render, I've had lots of problems with components having parts missing in the render and things like that. That's specially true for components inside components like trees for example. On the other hand if i explode the components and then turn the geometry into groups (actually when i want to do that i go fist inside the component, turn everything there into a group, get out of the component, and just then explode it because it's much moreeee faster exploding components into groups than to geometry) there's no problem. I guess that's maybe because groups are just geometry "grouped" and the components can have much more "properties". one of the renders that suffers from this is kerkythea's exporter specially for heavy scenes.
David
-
hm... that sounds like they might be running into a SU group bug where group.entities.parent sometimes refer to the wrong definition.
V-Ray suffered from this, but I found a way to patch it.@unknownuser said:
On the other hand if i explode the components and then turn the geometry into groups (actually when i want to do that i go fist inside the component, turn everything there into a group, get out of the component, and just then explode it because it's much moreeee faster exploding components into groups than to geometry) there's no problem. I guess that's maybe because groups are just geometry "grouped" and the components can have much more "properties".
From the API point of view groups and component instances both have a ComponentDefiniton, with very little difference.
Advertisement