POV-Ray : Newsgroups : povray.binaries.animations : 2nd Attempt at Flowing Water... (MPG, 274kb) : Re: 2nd Attempt at Flowing Water... (MPG, 274kb) Server Time
19 Jul 2024 13:32:07 EDT (-0400)
  Re: 2nd Attempt at Flowing Water... (MPG, 274kb)  
From: Tim Nikias v2 0
Date: 29 May 2003 18:59:15
Message: <3ed690c3$1@news.povray.org>
> Great work, Tim! This may be a misuse of your macros, but it seems like it
> could work.

Thanks, but no, its no misuse. Its using the system for something it
wasn't originally designed for, and thus requires more testing and
fiddling. And since the Pre-Processing-Macro is an "inbuilt" part
of the LSSM, its more like an unstable first attempt, than a misuse... :-)

> Interesting comment. Where can I read about this? I only have a vague
> understanding. I think it's possible to precalculate data (one normal
vector
> for each node) with reference for the wave direction. This means, there
will
> be an overall direction (the wind) for the waves, and there will be a
> sublayer where the waves go in all the directions that is specified by the
> precalculated data... But how to push these subwaves around, within a
> reasonable time, I don't know...?

I actually have no idea where you could information on this. I tend to
cook some stuff up myself most of the time. In this case, I'd say I'd
go create the nodes, check which ones are blocked, and then decide
which ones are the "front blocking nodes", meaning the nodes into
which the moving water crashes head-on. Then I'd find the contour,
and try to create some surrounding waves based on the
info I have on stream-direction, blocking nodes, etc. With this
approach, one could also easily try to reproduce those waves which
appear in shallow regions, where the masses move on top of some
boulder and cause a peak on the surface...
Anyways, once the basic flow (which would actually be more like a still
frame from a river) has been generated, I just take some height-data
(probably generated using a function-image of a pattern or such) and
add it onto the nodes' heights. This added height-data may be translated
along some direction and thus add a moving effect onto the base-waves,
and when slightly modifying the function-slice itself, the waves would
also seem to change and move on...

Parsing-Wise, the first generation of the base-flow would be time-consuming
I guess, after that, you just need to generate the mesh for each frame by
parsing through each node and adding the appropriate function-value...
-- 
Tim Nikias v2.0
Homepage: http://www.digitaltwilight.de/no_lights
Email: Tim### [at] gmxde


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.