Having a wave state that gets initialized based on the wind in the first
METAR, and has a huge rate limiter slowing down the visible effects of any
later updates of wind speed, would probably be the most realistic simple
approach for ocean waves. Wind takes some time to build waves, more time
for
On Friday 20 January 2012 16:16:18 Emilian Huminiuc wrote:
On Friday 20 January 2012 15:01:35 Torsten Dreyer wrote:
The shader scales the texture with windspeed and rotates it to get
the
right orientation, but the actual rate those change is too quick to
look good, and gives the
Are we fixing the right problem? I was observing mach 5 speed waves while
the weather wind was changing.
On Sun, Jan 22, 2012 at 8:18 AM, Torsten Dreyer tors...@t3r.de wrote:
Played around with it a bit. I got reasonable movement sensation with
wind-filter-time set at ~1000.
The flutter
The shader scales the texture with windspeed and rotates it to get the
right orientation, but the actual rate those change is too quick to look
good, and gives the impression of very high speed, that's why I
suggested a longer interpolation time for the values passed to the
shader, and to
On Thursday 19 January 2012 00:14:34 Torsten Dreyer wrote:
Hi,
due to a bug in weather-utility.nas, the wave shader properties were
stuck at a constant value for wind-speed zero.
There was more unfortunate code in that file, so I refactored it as
xml based property rule. This is the
Am 19.01.2012 11:27, schrieb Emilian Huminiuc:
I had another question, could the wind vectors reported to the shader
be interpolated on a longer (10x - 20x or so) time frame, or could
they be updated only once a given time (1 minute or so)?
I ask this in an attempt to cure the fast moving
Am 19.01.2012 11:59, schrieb Torsten Dreyer:
Am 19.01.2012 11:27, schrieb Emilian Huminiuc:
I had another question, could the wind vectors reported to the shader
be interpolated on a longer (10x - 20x or so) time frame, or could
they be updated only once a given time (1 minute or so)?
I ask
It seems like the wave go into hyperspeed while the interpolation process
is happening, and only settle down and look right after the interpolation
is complete.
Curt.
On Thu, Jan 19, 2012 at 3:54 PM, Torsten Dreyer tors...@t3r.de wrote:
Am 19.01.2012 11:59, schrieb Torsten Dreyer:
Am
Hmm - actually, the wind properties _are_ interpolated over time if set
from METAR which can be easily verified by observing
/environment/sea/surface in the property browser and changing the
global-weather scenario from, say stormy monday to fair weather.
Despite the fact that the properties
Hi,
due to a bug in weather-utility.nas, the wave shader properties were
stuck at a constant value for wind-speed zero.
There was more unfortunate code in that file, so I refactored it as
xml based property rule. This is the relevant commit:
10 matches
Mail list logo
