Thanks TIG.

I certainly dream of more than this, but this would be a great step in the right direction. The current UV tools available through ruby do me no good for just the reason you mention. When I want to wrap a stucco material around a column it scales way too large with no means of tiling it as you mention. Creating a custom material for such things is too much of a bother for me and clutters things up. -Brodie

I wonder how that level of detail would come into play in any application? Of course, I don't know enough about internal data handling. Maybe some programs don't use all available data, or maybe they process it differently.

I have had no issues with weld.rb Maybe Recurve is conflicting with weld? I have not yet used Recurve, I will check it out.

Kerkythea

Just beautiful!

Took a detailed look at the model. WOW, you did that on your lunch break! It's your own office isn't it?-)

Hi, I am experiencing similar problem even after I perform a selection only. It happens when I do a region select on part of a large mesh (say 25K faces). At the moment a finish region select operation (release left mouse button) SketchUp freezes for a few seconds and comes back with the selected portion smoothed with the current smoothing option. The smoothing can even be undone. It happens in all modes of selection (+, +-, or -). Triple select or Ctrl-A typically does not suffer from this. It is so annoying...

Ah! Missed that one on my sabbatical.

Well, I reached the high 27000s with a little practice...but its surprisingly difficult when the national borders disappear. I don't know what I'd be like with the USA. I'll bet I couldn't get within 100 miles of somewhere like Omaha or Denver, without state borders to help me....even though I've been there.

Wow, there is indeed a poly or two there

Really nice, I like the racing part.

This is related to the problem of doing a save_as on a component, and giving it different names - it will appear under its original name in the second component browser pane [therefore there could be several variants with the same name displayed there] but it'll kick into it's file name if loaded into the main pane ! I at first thought that it was the externally saved model 'component' title and name being different - but if you manually change the external files 'name' to its 'title' it doesn't help. The instance.definition.path returns the correct file path so it's not muddled there... Seems that there's something saved in a model's data that confuses the import into thinking its the same definition[s]... If you edit the table's groups after it's saved externally it'll then import with the right textured top and rails etc BUT the legs won't change as 'leg' already exists from the first table now in the model, so the import still uses that ! Solution ought to be to rename 'leg' as 'leg2' in the second table's skp file, but it's not going to work as SUp still imports the second table's leg as 'leg' even when it's not called that any more in that external skp !!! Super-confused mess... I think it's also tied into the weirdness where a group definition can have more than one instance - it can't theoretically and the group.make_unique even gives a deprecated method warning BUT it is needed to ensure a copied group that is changed doesn't affect its 'original' sibling... Of course the way to 'fool it' is to make the table out of groups/components with no materials and then apply the material to the component instance! But then UV mapping is a messy business one at a time... It is 'against nature' [ ] to have an app that lets you export variants of a component with different materials and later import them back into a new model but somehow muddle up their identities to such an extent that you can't trust which it is...

Maybe it was just an enlightened moment of Sang and he turned into a light component.

Always generous with the eyes up Alan!!! Thanks mate!!

@linea said: wow, That is pretty amazing, works in google chrome too. Could save some money on PS licenses at my office (I've tried to get them to use Gimp but they dont like the gui). IT DOES OMG! I don't have Photoshop but I'll save a whole lot with this!

Yeah, even if you do not purchase and use it for PR renderings, the eval version (and its 800x600 pixel output) should be enough to experiment with your "products" - as for how they behave there. They should more or less render the same way in Kerkythea then. AND I presume, the soon coming Thea Render would behave somewhat similar - although its material handling is said to be different, still Tomasz is the one who writes the exporter (as of Kerkythea's original su2kt) therefore there shouldn't be any issues with it. I really wonder why V-ray hasn't been made to recognise alpha transparency yet. One of the most powerful rendering applications - and not only for SU but for several, other modelling soft as well. BTW nice trees/shrubs again (what are junipers - trees or bushes?)

They are surprisingly highly detailed. Even after you've deleted all the low poly versions, the higher poly still have a bewildering choice of guages and exhaust configurations superimposed. I guess it's a question of duplicating the model and deleting different configs on different versions. Some of the cars appear to have normal and smashed-up/burnt-out versions superimposed as well. [image: hZjO_pcj.jpg]