@Box, oh! that's good, that's very good. Donation made, Thank you Fredo6

If the tubes happen to be components, edit any instance and remove all surfaces not to be painted. Or if the surfaces to be painted have a unique texture applied, then that could be used in the search to select only those faces.

I had this issue - Sketchup Pro 2015, on the mac. I explicitly set model info to a new keyboard shortcut, and the issue went away.

You need to change the association for the KML and KMZ file types to Google Earth. You might have a look at Photoshop's list of file types it is set to open by default. It maybe there are other file types set that you would rather use a different application with.

It would certainly be helpful is susan would post at least an example image of what she's after. Perhaps I misinterpreted the term "umbrella group" to mean a parent group containing the child groups as in my second screen shot. You are right that in most cases, I think it would be desirable to create the edges from intersection in the context of one group or the other.

thank you. Your last procedure worked. for other people with the same problem. it's explained in detail here: https://sites.google.com/site/sketchupsage/problems/other#TOC-How-do-I-retrieve-a-dialog-box-that-has-disappeared-Windows-only-

Thanks for your help! I will try to implement it to the animation.

Thanks guys, as it worked out I did not have a face ready for the texture......one of those Duh! moments

@cotty said: Make sure you've downloaded Make and not Pro. Make install -> 30 days PRO trial -> Make PRO install -> 30 days PRO trial -> PRO (don't revert back to Make, you need a PRO license to continue) this is true for SU2015, it changed in recent releases

@cotty said: It's fixed! Yup, our update affected this (it's served from 3dwarehouse). Sorry, thanks for your patience.

@szumlanski said: That would be great if it didn't break the geolocation feature! I suspect the two are related. They are working on a solution and it seems only a few minutes away....

I opted for the 15" MacBook Pro and am very happy thus far. A complex remodel project that I'm doing construction docs for is moving along without stressing the new machine like it did my old one (I have them sitting side by side...) Not the ideal workhorse for some folks - but as I'm mobile its a good choice for me. I've been using the activity monitor - I can see CPU load but not GPU load, but can check that the discreet card is in play whenever I have this file open. Will do some comparisons on a series of shadow studies I did earlier in the year to see how it handles that.

@gaieus said: I do not often use this export option but it seems to export vector based data which does not contain shadows. May I assume that if you have pdf export options, you also have SU Pro? In this case, you could send your model to LayOut and export from there in hybrid mode which will make your edges vectors but materials (and shadows) remain raster so you get the "best of both". Thank you for this suggestion. Yes, one does get the "best of both".

go for a MSI or Asus w/ a twin cooler.

@cotty said: You can use the normal inferencing system to position a section cut (middle point, guide lines, ...) and you can fix a direction with the shift button ... Do you have an example image or model where it doesn't snap? Thanks. "Shift button"is the answer. I'd never tried using it while it moving the sec plane.

What textures/materials do you have in the model? Maybe there is a color lookup change happening between the PDF and jpg that is making some material look more yellow? To answer your second question, no, jpg does not always look good to me. In particular, unless I have profiles set to 1 they come out very heavy in the jpg. Like Dave, unless I know the recipient can only handle jpg, I prefer png, uncompressed tiff, or PDF.

@driven said: the whole point of any maintenance update is to deal quickly with reported splats... each release has an overview of the changes, do they reflect a possible correction of your issues? Well I just updated so we'll see. Many of mine were outliner-related: often when trying to change nesting order directly in the outliner. Didn't see anything in a quick scan of the release notes re the outliner, so don't know if this release will prove to be more stable in my case. (Although I have gone back to cutting and pasting in place in the model instead of shuffling groups/components in the outliner. Slower by far, but I got fed up with the splats. Kind of defeats the value of the outliner if you can't trust it for the purpose.) @driven said: After a considerable amount of bug chasing on mac's, I find recurring issues being related to 'plugin observers' and 'Auto Save', so I avoid both whenever possible... To do this I disable many plugins until I actually want to use them, including the SU ones, and any 'renderers'... I normally try to keep the number of enabled plugins in any given session to a minimum, but I realized that I had installed several new ones of late and left them all enabled, so a good reminder to pare it back down. As for the autosave, that's a tough one... and a bit ironic that the feature meant to ameliorate the results of a crash can be responsible for those very splats. I've tried to get in the habit of manual saves, but the more engrossed I am in modelling the less likely I am to remember. I would have lost an awful lot of work this last week if it weren't for the autosave file whittling it down to 5 or 10 minutes of lost work per crash. Thanks for your thoughts and 'best practices'. Doug

Viewport works but: Exist viewport window must NOT be full screen. No special cursor used in Windows just std cursor to tug and pull edges and corners. Thanks to Driven for sharing this nifty thingy. dtr

John, I really appriciate you taking the time to help me out. I'll take your advice to create a material folder inside the "old color" folder in user/library path. thanks, chuck. P.S. - Rich, Thanks again for your input also. you helped me learn some more about checking under the hood and that's always a good thing!

Thanks for the suggestion Jim but screenspace wasn't the problem. It was a windows tablet PC setting (right/left handed) that was causing it.