Nice modeling...and What Fun!

4...for C&C, thanks (yeah, I don't like the baby blue shutters either :`)

Remus, thanks...and here ya go (answer whatever you were wondering? :`)

Gai, thanks again...the wireframes should answer your question (yes, exploded) and as you probably recall from the Twilight forum: if copies of these components are rotated in a model, they will need to be exploded and regrouped individually for rendering programs (or all the leaf face-me's of that tree component will retain the camera direction of the last copy).

Steve, good to hear...and maybe I should ask for some packaging market research here: I use PayLoadz and PayPal to deliver my trees (great combo BTW, thank you Solo) which charge a flat rate per transaction plus a percentage: so I settled on $33 bundles as a good trade-off. So far I've set my sights on 4 bundles (17+ trees each) in this series: loosely oaks, maples, "willows", "birch"...or, I suppose, more accurately: crumpled leaves, pointy leaves, elongated leaves, oviod leaves. Each set will take me about a month...so the series ought to be done by spring, hopefully. But overwhelming support for smaller sets, say 10 trees for $22, could push me that way...?

YEH Oli...here's 6 & 7 framed by 2 & 5:

I'm WOW-ed as well! Love the reflections!

What is Renditioner BTW?

Thanks alot, Guys...the Live Oak on the right is my fav so far too. But I won't quit till I get a handle on some sweet little Pin Oaks :`)

Oli, yes...more realistic, but not really PR: NQPR, I guess. I am going for two things: a full 3D trunk/branch habit which can be rotated (or the view rotated) to see the multiple changing sides of each tree: so the face-me leaf-bunch png components are each anchored to the branches instead of anchored to the center of the tree as a group. (Note I've rotated the background trees for this image from the last.) Since this forces a higher poly tree structure, I'm using higher res images so they don't "break down" as soon when used in the foreground...hopefully, thus adding some more value for the byte cost.

Dspace, sorta...these are 1meg to 1.5meg, but such is deceiving because the leaf image is 500-600k, so the poly is limited mainly to the tree trunk/branches.

I added Oak 5 to this image...done, to this stage anyway: first render test. Right now I'm thinking the light to dark mix of the leaves is a bit too contrast-y in some, if not all (whadaya'll think?), and the big branches off the trunks need more realistic transitioning (and of course, I haven't spent enough time rotating bark textures.

Hoping here to hear some little nags I might be able to fix for you guys (my future customers :`)

First set of new trees is coming along nicely: Oaks...4 down, dozen+1 to go.

Very Cool!

Alan, I've noticed this in the past too...and now this http://twilightrender.com/phpBB3/viewtopic.php?f=11&t=1123 is yet another reason to fix the SU bug...?

Broomstick, thanks...and good idea, but I think better for you (and other users) to do to their own set as they need (I bet I play with the idea on my own set).

Gai, thanks...and wouldn't that be nice to have the whole scene change with the date (Nice brainfart BTW :`) There is another thread (I'm too rushed to find it this AM) where folks kindly tested the last set in several render apps. These should do even better!

Thanks, Richard...yes, 2.5d face-me and still good for SU woods :`) Here's as close as I rendered...and should have rendered longer to show them off at this size, oops:

Edson...no, not yet: if I get a good response here I'll hurry up the production, though. As far as working in podium: should be same as the last batch I posted (don't have one of these ready for sharing yet) except I exploded the pngs for you. Oh yeah, they're higher res too, so work closer into the foreground.

Jeff...que?

...anyone interested in a new bundle of my trees (a bunch of different tree shapes and sizes, of course :`)? I changed the way I hit the png saturation so color variations show thru when adjusting the season in SU.

Rendered in Twilight: no post-pro BTW.

Purist won't like this reply, but...this happen so often to me (especially where the segments of a curve get near a plane break edge and you'll hit the clipping problem before you can get close enough to redraw) that I always use the old method (basically the drape steps manually):

Hover your road dwg over the site the same as for the drape command...instead use the "extrude edges" ruby to pull vertical faces down thru your site. Now select all and "intersect with model"...do this several times. Then crossing select the vertical faces above or below the site plane (either or not both)...if none of the faces are selected on the other side of the site plane then you are 100% successful (and pretty lucky :`) and can erase all the vertical faces assured your site is cut completely. If you're not 100% you can now easier see where the site is not correctly cut.

Oh yeah, having hidden geometry visible seems to help...or maybe it's just my karma?

So glad you like...fun for me too! Here's the next state:

Lovely...and quite appealing!

Just part of a minature golf course?

Another silkscreen...?: