It really would be a good feature if it could be done. Sort of like you can shuffle history in Photoshop.

Google won't really ever buy a script and implement. They would want to write it themselves. They also like to encourage developers to write scripts, because it adds capabilities to SU, and makes SU even more popular. Soo, it doesn't make a lot of sense for Google to implement things that others have already made, because its not cool to say 'hey, develop scripts', then turn around and re-write them to distribute with SketchUp, and not pay the author. So its not really a good business model for them to follow the way they currently run things. But even still, we had booltools before they released their solid tools. Making a terrain from 3d points was a script before the sandbox tool were added in version 5. Like Alan said, 3dtext was a plugin first, then SU wrote it. So they have done it a few times, though I'm not sure they really did it on purpose per se.

Maybe the side walks are full of dog shit. Anyway, dog shit or not, people in my town have always walked on the road, too. At least as far as I remember. Nothing new in that.

better late than never: happy birthday!!!

Hi, Rocky: No, I have not tried Jitter, but I am aware of it. I assumed it was designed to automatically displace every vertex in a model a random distance. I have not seen any examples of a Jittered model.

Many of you receive a SketchUpadate Newsletter. It is irritating that the first, seemingly 'the most important', information was: @unknownuser said: Most folks who use SketchUp are also fans of Google Earth, so I thought I'd let you know that there's a new version available. We wound rather appreciate an info when SU8 Maintenance release will be ready.

you have this plug by Wikii remove inner face faces who can maybe help you ?

@ODM: Thank you for your reply. Yes, it is understood that with the right hardware there should be minimal problems with the program. But inherent in the program(s) are limitations that cause display problems such as clipping, which can happen when geometry is created sufficiently far from 0,0,0 or when geometry is created sufficiently small enough, or when there is a significant amount of geometry. Knowing all of this from many discussions in this forum by others has not answered what the thresholds really are. Maybe I need to read some more in OpenGL pages. Perhaps the information is there and I have overlooked it.

Thanks, Earthmover: In the back of my mind, I was thinking that ThomThom had already solved this with Vertex Tools. That's why I said I should know better than to ask this. Maybe this post belongs instead in the Sketchup 12 wishlist thread.

Ah, yes: Thanks, Charly and Jeff.

Every time there is a new SU version they seem to raise the bar a bit but we are at 1.5 (or so) so this should not affect SU users IMO. Also I can imagine what high end graphic cards we would need to run SU!

I have Kerkythea on board, but I have been mainly focused on modeling and understanding the capabilities of Sketchup since I joined here. Eventually, I guess I will do some rendering.

Hi guys, not sure what I'm doing wrong here with this resynthesizer plugin... 2012-02-09_1355.swf For some reason it is not finding the adjacent content; rather the trees!!!

Thanks, ThomThom: Your reply is sufficient. I should have realized the materials thing being related to the default component geometry. (Apparently, all 3d programs insert a default object?) It seems that the validity check was automatic when there was a problem earlier on in my modeling "career". Not that it can't happen again, and again, and again.

Hi Mitcorb, hi folks. I agree that it could be a nice addition. For example, a "Selection" button added to the "Model infos --> Statistics" that would activate only when something is selected. Clicking on this button would update the infos to thoses in the selection. Then the buton would show "Whole model" instead of "Selection" to allows the user to switch back to the statistics for the whole model. Similar to a toggle switch. Just ideas.

@ThomThom: Not only see, but draw on them. As Chris's 3 lines tool allows. I am in modeling mode at this time, not doing any rendering, where your tool would be very useful.

Thanks, Chris: You are very kind to reply. As a matter of educating me, do you happen to know what factors would contribute to this condition, other than my ignorance? This appears analogous to Autocad block insertion points issues, but I don't know. (And it is rather involved process to correct this in Autocad, too.) I assume there is no easy script fix for this. Or is there? EDIT: After performing the operations suggested by Chris Fullmer, I gained a little better understanding of the problem. The component axes (not the workspace global axes) are normally connected with the bounding box of the component or group upon creation. If some modeling operation "corrupts" this relationship, the component axes may become divorced from the bounding box. It just so happens that while using SketchyFFD in SU6 I discovered that the deformation matrix was being formed at or near the divorced group axes, and because of this offset, some squirrelly results were happening after moving the matrix into position around the target group and applying the deformations. So, this may be a caveat for users of SketchyFFD, whatever version, to be sure that the axes are in the right location.