 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just a quick grass macro I wrote yesterday afternoon. It generates a number
of different mesh2 objects for each blade of grass, and then puts them
randomly onto a plane many times over. Render times were about 20 mins for
the close-up, and an hour for the mowed grass (on and old P4 3GHz).
Post a reply to this message
Attachments:
Download 'grass4.jpg' (220 KB)
Download 'grass3.jpg' (118 KB)
Preview of image 'grass4.jpg'
Preview of image 'grass3.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
very smooth and good-looking!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Looks great, especially the close-up! It seems a bit like it has
focal blur but if the render was only 20 minutes it's probably
just an anti-aliasing effect.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christian Froeschlin wrote:
> Looks great, especially the close-up! It seems a bit like it has
> focal blur but if the render was only 20 minutes it's probably
> just an anti-aliasing effect.
Mm, you can hack focal blur to render in that amount of time. The image
looks like it could use some more samples in the blurring, actually,
which would explain the fast rendering time. :-)
--
William Tracy
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|a|f|i|s|h|i|o|n|a|d|o|@|g|m|a|i|l|.|c|o|m|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|w|t|r|a|c|y|@|c|a|l|p|o|l|y|.|e|d|u|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
You know you've been raytracing too long when you've convinced your boss
that raytracing is really an integral part of your job title (and you
really don't work in a position that requires it).
Quietly Watching
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> Looks great, especially the close-up! It seems a bit like it has
>> focal blur but if the render was only 20 minutes it's probably
>> just an anti-aliasing effect.
>
> Mm, you can hack focal blur to render in that amount of time. The image
> looks like it could use some more samples in the blurring, actually, which
> would explain the fast rendering time. :-)
Yeh, IIRC I only used 20 or 30 samples for the focal blur, it actually came
out better and faster than using AA at a high enough level to look good.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott wrote:
> Just a quick grass macro I wrote yesterday afternoon. It generates a
> number of different mesh2 objects for each blade of grass, and then puts
> them randomly onto a plane many times over.
It would save memory if you created a big group of blades as a single
mesh2. Perhaps create a half dozen of such groups and then create the
entire grassfield with randomly chosen groups.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Very nice!
Any chance of a peek at the code?
Rarius
"scott" <sco### [at] spam com> wrote in message news:4694bb1f@news.povray.org...
> Just a quick grass macro I wrote yesterday afternoon. It generates a
> number
> of different mesh2 objects for each blade of grass, and then puts them
> randomly onto a plane many times over. Render times were about 20 mins
> for
> the close-up, and an hour for the mowed grass (on and old P4 3GHz).
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Very nice!
>
> Any chance of a peek at the code?
Sure, I posted it in p.b.s-f.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wow, that's good! My only criticism is that the mown grass has a pointy tip.
Or at least, I _think_ I can detect a pointy tip.
And thanks for the code, BTW.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yes you're right! I hadn't thought of that...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
