Torsten Dreyer
> > http://img832.imageshack.us/i/fgfsscreen0011.jpg/
> Yes - that doesn't look right.
> There are two files responsible for setting the cloud layers:
> FGDATA/Environment/metarinterpolator.xml
> FGDATA/Environment/cloud-layers.xml
>
> if you run fgfs --log-level=info, can you co
On Monday 13 September 2010 19:57:55 Alasdair wrote:
> I have recently been delving into FG's innards, with a view to fixing
> some problems with the speech handling capabilities. This has led
> indirecly to my having to understand how XML files are parsed.
>
> Now in SG's XML folder is a program c
Just a heads up.
One more change is needed for MSVC100 - metar linker does not have a path to
sg.lib
(should be ..\..\..\..\3rdParty\lib)
Alan
--
Start uncovering the many advantages of virtual appliances
and start
> http://img832.imageshack.us/i/fgfsscreen0011.jpg/
Yes - that doesn't look right.
There are two files responsible for setting the cloud layers:
FGDATA/Environment/metarinterpolator.xml
FGDATA/Environment/cloud-layers.xml
if you run fgfs --log-level=info, can you confirm you see something like thi
Torsten Dreyer
>
> > Oh dear. The problem seems to be in the coverage column. All the global
> > weather scenarios set all the correct data except the coverage. If I
> > attempt to set those manually they set back to clear.
> >
> > 3d clouds work correctly if I select the scenario manual. They a
> I'd be interested to run such a comparison myself. Could you translate
> the described conditions into a set of command line parameters against
> 'default' FlightGear/GIT startup so I/we can make sure not to interfere
> with local customizations ?
I don't think it can be done from the command li
6 matches
Mail list logo
