I'm using Vray and it has an option that overrides all materials and make them the same. However transparent materials also gets opaque so thats why I wrote this plugin.

Infinitely extending xlines can't become lines [edges] - they need a start and an end. 'Short' xlines can become lines [edges] as they have a length... Project2 has 'short' options for some xline operations...

Undrop multiple Funny things (click image) [image: QrQi_Piltigthom.jpg]

诞!

Thanks for the reply, TIG. I did try your script over night and yes, it is quite different!!!! Thanks; i think it will be a handy addition..... I love this place.

I moved all of my development files out of Plugins yesterday. With the exception of the updated file, it is the same os the online version. But here it is again just in case. protrude.zip

Thanks TBD, so your temp folder is called "TMPDIR"

Here is a shot of the functionality I am working on. This would allow a practically infinite number of scenes which will be expanded and collapsed in the normal way (not yet shown) based on the scene on the focus line. [image: 6yLK_Sceneexpand-collapse.png] This part is easy but how to make collections or groups of scenes, as with components, requires some time to work through necessary amendments to the interface, together with SU display/ web dialog interaction. I am working on these*. @chris fullmer said: An extra row of scene tabs is not possible through ruby. But it would be possible to make an entirely new scene manager through webdialogs that could be organized an possible way. But Webdialogs seem to give everyone lots of headaches because they work differently on Macs and PC's. Chris Don't think about this unless you use a Mac. Anyway it will be solved; maybe not here. By the way, how many members actually use a Mac? A useful statistic for the politicians among us I think. Keep in touch Chris edit *See this topic

Dammit, I came to this thread via another and didn't notice it was a year old. I guess this project died out then.

thanks Chris, I PM'd you earlier with some ideas actually!!!

I agree - more times than not you should model on Layer0, then put the collection of bits as groups/component-instances on different layers... This method let's you change the current layer BUT be careful to keep your raw geometry on Layer0...

Cool indeed this new plug! Bravo!

WOW thanx, just got it...really cool plugin. Now hwy didnt i bought this earlier. hee hee This will help sooo much ..thanx

Thanks

Would it be possible to just write a script that selects only outer edge lines, and then uses .find_faces to cover them?

@dave r said: Does this answer your question? I haven't used it but it's on my list. That's great. I need to talk to Rick somehow as there is a new version in hand. The reason I asked the question (in case you are interested) arose from a conversation with Red, viz: I think we should stop calling it a document. It is a machine like an ATM that does work people exclusively used to do. Because cgScenes interface moves I don't think it is difficult to see it as a machine but there will be trouble if you describe a cgScene-energised Sketchup model a machine. But it is; it will provide graphical answers for an owner, architect, engineer, local authority, buyer, logistics person, crane driver, brickie, hotel operator, maintenance man, cleaner ... More than this any of them can make their own scenes from the same model in the format that suits them best. Maybe some people in similar competences make suitable devices and styles to be used by their colleagues. Ah but supposing they alter the model. Well, there should be only one model kept by its owner; what gets passed around are the saved scenes with notes (e.g. in the Scene description box). Additions or amendments by authorised persons is slightly different but equally simple. Do you have it on your list for a similar reason? I'd be very interested to hear Chris

@adamb said: Writing a simple importer that eats static hierarchical geometry and materials is straightforward. Isn't that enough for Sketchup? can it make use of more of the data?

This problem really annoys me! So, SU uses the order of creation rather than the distance to the camera to decide what should be in front? Shouldn't that be relatively easy for Google to fix?

Hi Rick and others. I've found WELD to be a little clumsy of late. Maybe it just what I'm wanting it to do but in one instance i can get it to weld all selected then if I select other lines that may touch the previous one and ask to weld then everything gets exploded!! An update would be much apprcaited, Rick... BTW, Simplify contours script from long ago is attached... SimplifyContours.rb