>
> See Environment/cloudlayers.xml for the cloud definitions used in the
> global
> 3D clouds.
Found it, so assume you need to add a reference in the preferences.xml
file to include this xml file for cloud types, correct?
>
>> Two related questions:
>>
>> 1) how does one enable (use) the hi-res
On Sat, May 14, 2011 at 9:13 PM, John wrote:
> Hi,
>
> Was also looking over Thorsten's pics and writeup on the FG forum (assume
> those were the pics referenced) and wondering how to go about setting up
> the cloud scenery.
I think the pics referenced were my photos from a recent RL flying trip
Hi,
Was also looking over Thorsten's pics and writeup on the FG forum (assume
those were the pics referenced) and wondering how to go about setting up
the cloud scenery.
Looked over the README.3DClouds writeup and that pretty much answered the
howto but was unable to find any complete xml files (
Hi Stuart,
Great to hear you figured out the elevation issue. Those were the two
issues that I noticed:
- cloud elevations off
- overcast cloud layers not drawn at all
One other that I haven't paid close attention to, but one time I wondered if
the cloud layer had slid off to the far end of the
Great photos , thanks for sharing !
--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help b
Hi Curt,
I've managed to find the problem, and once I get git to play ball,
I'll make a merge request!
If you've got a list of the 3D clouds bugs you've found and not fixed
yourself, I'd be interested in fixing them.
The flying trip was fantastic. We flew just over 1000 miles over 8
days (19 hou
Hi Stuart, thanks for taking a look. How was your trip? Hope you logged a
lot of nice flying days! Our weather has been pretty much crap around here
and then the nice days I've had to work or had family stuff, so I've logged
about 5 minutes of (RC) stick time so far in 2011. :-(
Curt.
On Fri,
Hi Curt,
I've been looking at the altitude problem all evening, but haven't
(yet) found the bug.
AFAICT the correct altitude (in m) is being passed down the stack and
used to create an altitude offset, so it's not just a case of the
stack using the height of the clouds rather than the altitude. I
Hi Stuart,
I saw that you recently made some updates and bug fixes to the "global
weather" 3d clouds including fixing a problem with overcast coverage and
also making clouds drift with the wind.
This afternoon I started up at my local airport (KANE) and did observe the
clouds drifting, which look
thorsten.i.r...@jyu.fi wrote:
> I'm offering you an explanation, as there may be things I have thought of
> and you haven't.
Well, that's your private interpretation and I do respect that you're
defending your point of view.
Nevertheless, the problem _I_ am talking about is that the recipients
of
>> The way I did the comparison [...]
>
> Your rather elaborate pleadings make me feel that you've been
> implementing a rather 'autonomous' (or 'uncontrollable') system for
> setting weather effects, which - obviously - is destined to drive
> people into a "comparing apples and pears" situation.
thorsten.i.r...@jyu.fi wrote:
>> 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 t
> 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
Thorsten (with an H) wrote
>
> > I haven't fully tested all the options, but in general the frame rate
> > cost seems very heavy.
>
> > Regarding frame-rates: yes, the Local-Weather implementation kills
> > non-high-end systems (mine, too).
>
> I'm getting slightly frustrated here. I've spent m
>> non-high-end systems (mine, too).
>>
> I'm getting slightly frustrated here. I've spent months to improve
> performance, and I feel by now that I at least deserve a fair judgement
> for my effords, i.e. an apples-to-apples comparison rather than a highly
> skewed comparison.
>
Sorry i
thorsten.i.r...@jyu.fi wrote:
> If you want to compare apples to apples, then you have to level the field.
> I've just tested 'fair weather' conditions seen from the same location
> (above KLSV), no cloud movement, same altitude of cloud layers and same
> visibility of terrain (35 km) and clouds (
> I haven't fully tested all the options, but in general the frame rate
> cost seems very heavy.
> Regarding frame-rates: yes, the Local-Weather implementation kills
> non-high-end systems (mine, too).
I'm getting slightly frustrated here. I've spent months to improve
performance, and I feel by
Am 13.09.10 12:02, schrieb thorsten.i.r...@jyu.fi:
>> I run last sources and data and I also see this message. Is it expecting
>> a not yet written feature ?
>>
> No, I have a GIT binary from a while ago supplied by Hooray which does not
> produce the message but detects support available. So
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 Wea
> I run last sources and data and I also see this message. Is it expecting
> a not yet written feature ?
No, I have a GIT binary from a while ago supplied by Hooray which does not
produce the message but detects support available. So there exist versions
of code in which the patch is supplied, but
Hi Thorsten,
- "thorsten i renk" a écrit :
> > I get the same message on start.
>
> Yes, there's a script that checks if a hard-coded vector elevation
> sampling works or if you have to do repeated goedinfo calls. If the
> system is to be compatible with 2.0.0 and to make use of GIT features
> I get the same message on start.
Yes, there's a script that checks if a hard-coded vector elevation
sampling works or if you have to do repeated goedinfo calls. If the system
is to be compatible with 2.0.0 and to make use of GIT features to speed it
up, it has to have some way of knowing if the
> 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?
>
No special option is required
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 t
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 i
> Hi
>
> This is what I get when I try to acitvate 'Global Weather' in the GUI:
>
> Compatibility layer: Checking available Nasal APIs:
> (this may cause harmless error messages when hard-coded support is lacking)
> ##
> Warning: invalid line segment passed
Hi
This is what I get when I try to acitvate 'Global Weather' in the GUI:
Compatibility layer: Checking available Nasal APIs:
(this may cause harmless error messages when hard-coded support is lacking)
##
Warning: invalid line segment passed to IntersectVis
27 matches
Mail list logo
