I think Chris's tools have moved on from those old posts... His ColorBySlope tool colors facets according to their 'angle'. In his Plugins subfolder's ..._data.rb near the end you can see how the faces are processed and their angle is calculated as 'segment' [as an integer]. The array of materials [matarray] is inspected and the material number corresponding to the 'segment' is assigned to the facet... If you setup 90 colors then for each degree of slope you get a correspondingly colored material on the face... With just 9 colors you get a 10 degree range of slope between flat and vertical. So for example - set 'low' to green [0,255,0] and high to 'red' [255,0,0] Then the steeper the slope the redder it gets ? The flatter the slope the greener it gets ?? Not all colors will get used - r.g. if the majority are quite flat it's predominantly greens as there are no steep red parts ! [image: lpLh_Capture.PNG] [image: jkZU_Capture1.PNG] [image: vh4B_Capture2.PNG]

Hi Frank, Open the Materials window and click on the Details menu icon on the right edge of the window. Select Open or Create... Navigate to the folder containing the materials you're after and choose Open. Go to the Details menu again and click 'Add to favorites.' That ought to take care of it.

@ John. Thanks for the suggestions I do go into panic mode when I see code. The suggestions are appreciated and would have been tried but... @ Dave, "Reset Workspace" in preferences seems to have cleared it for now and was simple to implement. I was also relieved to find my custom toolbar remained intact. Thank you both. Problem fixed.

Thanks guys, I figured it was just something to report just in case no one else had already, unlikely thought that might have been!

Eric et al: Why are you modelling the dog-bone fillets? Doesn't the CNC software takes care of this? I don't know why I didn't raise this question earlier, but I recall at school when we used the CNC machine we set up the tool paths for the machine to follow - but never modelled the end resulting dog-bone fillets.

Hello Garystan. When you say it won't cut an opening, do you mean that it won't cut an opening period, or that it is cutting an opening in only one face of the wall? SU components are limited in that they can cut an opening in only one surface. But there is a work-around. Can you post your SU model/window component.

Thank you very much, much appreciated.

Not a photo. is a drawing of an artist of 24 years. http://www.diegokoi.it/works.html [image: Ng5H_nessuno-mai---hyperrealism-iperrealismo-diegokoi--10-.jpg]

Thanks ever so much for the response(s) - I will give it a try!

@Tomot You are over thinking this. You will need some spaces in any language's code, so that the 'parts' can be differentiated by the interpreter. The only errant spaces you have flagged up so far are the ones I had previously warned against, and had been advised against in the earlier versions of Ruby too - because although they were 'tolerated' they could be deprecated and become unacceptable... and now they have been! To reiterate... A ' method' can sometimes take an argument or arguments [ .upto(666), .add_line(pt1, pt2), etc] - these arguments are always best passed inside parenthesizes ()... The opening ( should come immediately after the last character of the method, with no space between them. So all you need to do is search for ' (' and then decide it you make it into a simple ' (' when it occurs immediately after a method. Some spaces in code are 'optional' and using them simply helps 'readability' when editing - just like consistent indenting of code-blocks will - but again that was ever so: e.g. xx=12.3 v. xx = 12.3 From what I've seen of your screen-grab images, you have sometimes included other () in parts of your code - sometimes they are not necessary at all. if xxx && yyy is fine. if (xxx && yyy) is too, but the () are NOT needed at all, unless you are nesting tests like this: if xxx && (yyy || zzz) when you need them... All v2014 Ruby2.0 has done is to stop accepting some syntax that was already advised against in earlier versions too. It has not 'moved the goalposts' - rather it has 'set them in firmer foundations'... The advantages of v2.0 far outweigh the inconvenience of tidying up old poorly drafted code. The few other minor changes in its methods, like 'array_to_string', actually bring it to be more aligned with other similar languages like Perl... These changes are unlikely to affect the vast majority of scripts anyway, and if they do they do then it is easily spotted and resolved anyway... Be assured that if you scripts are updated and they work properly for you in v2014, then they should work for anyone else using the same version [and OS and Pro/Make***]. ***If in the unlikely event that one of your scripts contain some OS specific or Pro [v.Make] methods/code then of course, without testing your script on the alternative OS/Pro compatibility cannot be ensured - but that was ever thus...

@jim said: If you click the Fly-out menu, and select "Remove Collection from Favorites", are you able to remove it? hi jim, no, that is the point. remove collection gives you the selection of collection, which are at the bottom of the pulldown menue. this one is on the top..... stan [image: 9gVH_Clipboard02.jpg] [image: i0RG_Clipboard03.jpg]

Thank you for the profile advice. I will immediately do that. As for the OpenGL settings - I will experiment in that area. Thanks again.

I think that may just work.... Thank you sir!

You may have better luck getting an answer in the Skellion topic: http://sketchucation.com/forums/viewtopic.php?t=31947

Have a look there: http://sketchucation.com/resources/tutorials/37-beginner/108-installing-sketchup-plugins

I was able to locate the toll free number in the email and got someone who resolved our issue. Thanks.

Send me your Makerbot and I will try it for you. Sorry, couldn't resist

@unknownuser said: I have a bunch of plugins and don't want to blame a plugin, because some times it is a combination. You should! Plugins must play well with others. Plus, sometimes a conflict is really easy to fix. Anyway, in this case it was not a conflict, it was easy to fix, and I would have never see it if users didn't tell me

@rudbeckia You can try with JoinPushPull, Vector mode with the option Project to plane, as shown here. Otherwise, enclose the terrain in a big box and Intersect / cleanup Fredo

Okay, I feel pretty stupid. I was looking at the page linked from the Extension Warehouse and forgot I wasn't in the Sketchucation thread. I saw no replies and wondered if it was a dead plugin or something. But there are 15 pages of replies in the actual thread. Maybe I need a new, stronger brand of coffee?