SU version 8 has the Foreground Photo feature in PhotoMatch that makes the model look like the image overlay covers it. What baffles people is that the controls for this behaviour are not in the Match Photo dialog but in the Styles window>Edit>bottom of the Modeling settings tab. Anssi

@mitcorb said: I suspect that porting it through Revit reset the origins/axes of the offending geometry So it does. Revit, although it doesn't use OpenGL, is almost as bad at large coordinates as SU. When Solo imported the DWG file and then re-exported the view, the origin was set at the Revit model origin, not the one in the DWG. Anssi

yeah i am... that is a broken down one ill break it down more. gonna carry on tomorrow. thanks for your help

Perhaps on the other ones, Google is using some internal optimizations to trim your model's vertex count. Maybe it can't do that on this one. One optimization might be to convert a rectangular face with several polys to two triangles, if they all have the same color or texture information. If you colored those polys differently this time around, then Google can't reduce the poly count anymore.

@anssi said: Are you quoting the price of AutoCad LT? The viewing application Autodesk DWG TrueView IS free, http://usa.autodesk.com/adsk/servlet/pc/index?siteID=123112&id=6703438&DCMP=ILC-DWG-PUV ( I noticed that they are advertising for LT on the right of the page, while the "Download now" button on the left, in the text column is much smaller...clever businessmen?) Anssi Thanks Anssi! I got caught myself in that marketing trap, I guess... Now I downloaded the free version.

yes it works... One down, but it handles, xray oddly when exporting tiff.... with transparency on... john

Hey all, I fixed it ith the elp of the support guys at SU. I turned OFF the hardware acceleration and it fixed it immediately. I have an old computer with a crappy integrated GPU that i know does not support openGL fully. Its amazing how fast the CAD model is without GPU !

Hi guys. Thanks for the links Jim. I checked them out. Very cool. Gotta try some of this stuff as soon as someone links to a physics Ruby for MORE TIME @unknownuser said: What is the source of that animation that you show above? Hey mitcorb. Sorry it took a while to get back here. Too many irons in the fire. But here ya go.... http://fireuser.com/articles/solids_vs_surface_modeling_what_and_why_you_need_to_know/ I did some more research though, and I'm curious about NURBS now. I recently purchased a new i7/975 computer and am in the process of researching GPU's for SLI as my motherboard is an EVGA 3xSLI Classified. I want to get into Rendering stuff, but lack of $$$$$ keeps getting in the way. In the meantime I'm researching which way to go for Sketchup/Rendering vs $$$$$ vs 2x or 3x GPU's vs overkill vs budget. I'm actually holding off on downloading anymore plugs for Sketchup untill I get my new computer GPU upgraded and my apps loaded. Which may be a while. So, for now I just have to keep modeling simple stuff on my old P4. Well, enough babbling. Time to get to work. Thanks guys. fitZ

That's bad, I am sorry. Hopefully it will be recovered...

@unknownuser said: . in this case, i didn't scale up.. wondering if jim did anything else to the skp prior to outer shell? I don't remember, but it's possible. However, I just tried it again, this time scalingup 10x and Outershell cleared the inner geometry again. And you are correct, the final piece is not a Solid when using this method for reasons Jeff has indicated.

Is your display driver up to date? Does this happen with all models? Is this one located far (more than a kilometer or two) from the SU model origin point? Anssi

Jim, that's like my problem with "save animation" that refuses to work on one of my machines. At least you have a "work around". Sometimes I loose minimized windows under the task bar, but those can be found.

@chiefwoodworker said: Gai's solution may be more general but does require creating the shape away from the part. On the other hand, it is always good to have several workarounds. Well what I did was to temporarily group your face (until I moved away) then exploded it. So you can actually make the profile "in situ" initially.

I have received a response from the SU team; they were able to reproduce the error and comfirmed the bug: "Thank you for your note. I've opened your file and was able to reproduce the crash when draping on the two scenerios you provided where the drape was onto exploded geometry. When draping onto a grouped surface it would work fine and if I grouped the geometry on your two "exploded target" sections those would also drape fine. The issue seems to be specific to what you're draping on and whether or not its a group when I perform the operation in SketchUp 8." It seems to me that if you group the "target" object it helps... sometimes.

ok I think it has something to do with the right click bug because it works now that I restarted... phew that scared me.

It's not in v6 (I still have it). As far as I remember, it was introduced in v7.1 but indeed has been there for a while.

Hi guys, The problem in this case is figuring out where the 'new' toolbar should be added. I don't have my PC in front of me at the moment, but I think new Ruby toolbars are added at the start of the toolbars, not at the end. On the other thread on this subject (over at our help forum) a suggestion was made that new Ruby toolbars should be floated on first load to avoid this. john .

bump same issue here. Tried using the cleanup plugin from ThomThom, thinking it may be due to the complexity of the model. It really is not that complicated, Just some lattice work for a steel structure. Other models with similar geometry have come in without the error report. What is this attributed to. Texture, polycount or some other miscellaneous sketch up fail. bring on revision 9. Bring back the old way of getting places from Google Earth. (from the Earth UI) it was easier to navigate to locations that are out bush and not on a road.

Yes, this is a known bug but will hopefully get fixed soon.

Hi Jeff! Thanks for the reply! I realized this as I started mucking about with the rubies - I guess I'll have to patch the rubies myself to fix this! Thanks for the heads up though! // Olle