Am 13.09.10 11:19, schrieb Vivian Meazza:
> HB-GRAL
>
>
>    
>> Am 13.09.10 00:25, schrieb Torsten Dreyer:
>>      
>>>>>   Should I really apply a patch from the forum before I use this menu?
>>>>>
>>>>>   Thanks, Yves
>>>>>            
>>> Hi Yves,
>>>
>>> these messages come from the "Local Weather" nasal based implementation.
>>>        
>> The
>>      
>>> mentioned patch is not necessary to run the local weather but is for
>>> performance increase only.
>>> Are you sure you get this, when activating "_Global_  Weather"
>>>        
>> (not_Local_)?
>>      
>>> Torsten
>>>        
>> Torsten, sorry, I get this anyway in the log, it's just new here today.
>> But I get a bus error when I try to use 'Global weather' in the GUI,
>> 'Local weather' seems to work. Do I need some special command line
>> options to use 'global weather' from the menu?
>>
>>      
> I get the same message on start. And global weather seems to be totally
> non-op. The old 3d clouds do not appear whatever I select, and the metar
> info appears not to get set. Could we have them back please?
>
> In addition, I get this error when selecting "glider sky":
>
> Nasal runtime error: setprop() value is not string or number
>    at D:/Git_New/fgdata/Nasal/weather_tile_management.nas, line 166
>    called from: D:/Git_New/fgdata/Nasal/local_weather.nas, line 2264
>    called from: D:/Git_New/fgdata/Nasal/local_weather.nas, line 2951
>    called from: D:/Git_New/fgdata/Nasal/globals.nas, line 100
>
> I haven't fully tested all the options, but in general the frame rate cost
> seems very heavy. These were just apparent bugs in the first things I tried
> to do.
>
> Vivian
>
> P.S. why do we need to scratch around in a forum to get a patch that seems
> to be an integral part of this? Is there a problem?
>
>    
OK, I'll try to clarify some things: we have two completely different 
and individual systems here:

1) Global Weather
This is our "good old" weather subsystem and the code I am currently 
working on. Allthough many implementation details have changed, there 
should be no visible change for the user but the unified Dialog. The not 
appearing METAR you mentioned was a bug that should have been fixed 
since yesterday evening 
(http://www.gitorious.org/fg/fgdata/commit/3feeaeb70df26d8dde2da54e7ba55829173888a6).

2) Local Weather
This is an experimental new (and fascinating) approach for a weather 
model created by the forum-user Thorsten (note the additional 'h' in the 
name - this is not me!) It is completely Nasal+Shader+Animation based. I 
(Torsten with no 'h' in the name) am not (yet) involved in this 
development, I do not even fully understand what all this code does.

Both systems are currently more or less incompatible. To use 
Local-Weather, you have to set Global-Weather to "disabled" or both 
systems fight each other (last property-setter wins).

Regarding frame-rates: yes, the Local-Weather implementation kills 
non-high-end systems (mine, too). That's why I am currently preparing 
the ground for better support of the Local-Weather-system in the core 
code. The Local-Weather systems runs scrubby on my system, too and one 
could argue if it was a good idea to add it to the repository at that 
early stage. Personally, I think it has the potential to give us the 
best representation of weather phenomae a simulator can have.

If anything unexpected happens, please post some details, so I can dig 
into it.

Thanks, Torsten





------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to