[Flightgear-devel] Re: today's 3d clouds commit
* Harald JOHNSEN -- Monday 16 May 2005 11:22: - with 'metar' = this is not perfect (lets say buggy) because the real metar data is not fetched before the usual 15 minutes so the layers generated will just use the current data from the property tree. Nono. The metar data are first downloaded immediately at startup, then downloaded again once every minute if the nearest station has changed, else in 15 minutes intervals in any case. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: today's 3d clouds commit
* Curtis L. Olson -- Sunday 15 May 2005 16:40:
Is there something special that needs to be done to activate the new 3d
clouds? Before this commit I got them automatically, now I am just
getting the original textured layer clouds. I don't see anything
promising in preferences.xml ... ?
It's apparently turned off by default, now. You can turn it on again in
the menu under View/Rendering options. Also look into the new dialog
under Weather/Weather scenario. --prop:/sim/renering/clouds3d-enable=1
should work. I have this in my $FG_HOME/preferences.xml (which is loaded
via --config):
sim
rendering
horizon-effect type=booltrue/horizon-effect
distance-attenuation type=booltrue/distance-attenuation
multi-pass-clouds type=booltrue/multi-pass-clouds
bump-mapping type=booltrue/bump-mapping
enhanced-lighting type=booltrue/enhanced-lighting
use-display-list type=booltrue/use-display-list
precipitation-enable type=booltrue/precipitation-enable
lightning-enable type=booltrue/lightning-enable
clouds3d-enable type=booltrue/clouds3d-enable
/rendering
sim
nasal
local
script![CDATA[
INIT = func {
setprop(/ai/models/ship/controls/glide-path,
0);
setprop(/sim/sound/volume, 0.6);
setprop(/sim/rendering/clouds3d-cache-size,
4096);
}
settimer(INIT, 0);
]]
/script
/local
/nasal
What I forgot to mention, and what isn't perfect yet, is the mixture of
3d clouds with plane cloud layers. This causes ugly cutoff effects. And
night/day transition doesn't work well when warping.
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: today's 3d clouds commit
Le dimanche 15 mai 2005 16:51 +0200, Melchior FRANZ a crit :
under Weather/Weather scenario. --prop:/sim/renering/clouds3d-enable=1
should work. I have this in my $FG_HOME/preferences.xml (which is loaded
via --config):
sim
rendering
horizon-effect type=booltrue/horizon-effect
distance-attenuation type=booltrue/distance-attenuation
multi-pass-clouds type=booltrue/multi-pass-clouds
bump-mapping type=booltrue/bump-mapping
enhanced-lighting type=booltrue/enhanced-lighting
use-display-list type=booltrue/use-display-list
precipitation-enable type=booltrue/precipitation-enable
lightning-enable type=booltrue/lightning-enable
clouds3d-enable type=booltrue/clouds3d-enable
/rendering
sim
nasal
local
script![CDATA[
INIT = func {
setprop(/ai/models/ship/controls/glide-path, 0);
setprop(/sim/sound/volume, 0.6);
setprop(/sim/rendering/clouds3d-cache-size,
4096);
}
settimer(INIT, 0);
]]
/script
/local
/nasal
Where do you put the nasal part? I tried in preference.xml this has no effect.
I put it in myplane-set.xml it does work. But only for that Aircraft.
The stormy scenario needs more heavy clouds.
**CVS version one hour ago**
--
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: today's 3d clouds commit
* Gerard ROBIN -- Sunday 15 May 2005 18:48: Le dimanche 15 mai 2005 à 16:51 +0200, Melchior FRANZ a écrit : sim [...] sim nasal [...] /nasal Where do you put the nasal part? I tried in preference.xml this has no effect. I put it in myplane-set.xml it does work. But only for that Aircraft. I put it at the same level where I put the sim group. That is: at top level as direct child of PropertyList. I have never tried it into $FG_ROOT/preferences.xml. Instead I use it in my local $FG_HOME/preferences.xml, which I load via --config. (Actually, it's a wrapper that does it for me, and it could be in ~/.fgfsrc instead). m. FG_HOME ... defined as $HOME/.fgfs/ here ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
