On February 20, 2008 05:36:16 pm Mike Schuh wrote:
> On Wed, 20 Feb 2008, Melchior FRANZ wrote:
> >* Melchior FRANZ -- Wednesday 20 February 2008:
> >> One effect that could also be considered is wind speed.
> >
> >Hmm ... and temperature. Very hot should probably reduce
> >the visibility as well,
I just found your FLIGHTGEAR Software package. I marked it for install in
Ubuntu version 7.10, and then tried to get my E-SKY Model 66P02 USB Controller set up for control
of AILERONS, ELEVATOR, THROTTLE, and RUDDER. I use this controller for R/C Programs
FMS and HeliSimRC under Win XP. It has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Curtis Olson wrote:
| Hi Til,
|
| Thanks again for your efforts on this (and to everyone else who
| participated.) I've just committed the most recent version of this
| patch. It seemed to stand up well to my stress tests. There is an
| issue with t
On Thursday 21 February 2008 22:06:02 Melchior FRANZ wrote:
> And, of course, nobody is supposed to use JPEG in cases where
> compression artifacts disturb. But for some textures JPEG may
> be acceptable (with higher quality setting if necessary)
Agreed... I've used JPEG in the past when working o
* AJ MacLeod -- Monday 18 February 2008:
> Now that our data has been "properly" branched, I would like to
> move to using PNG (or, where suitable, JPEG) textures in my models.
OK, I'd say it's decided. No objections, only agreements (and that
includes some more people on IRC).
This doesn't mean
Hi Til,
Thanks again for your efforts on this (and to everyone else who
participated.) I've just committed the most recent version of this patch.
It seemed to stand up well to my stress tests. There is an issue with the
ground-cache code not always returning a proper hit, but that seems
complete
hi curt,
i fear i'm not the right person to answer this. (at least not without doing
some time-consuming research).
i don't *believe* the problem you describe could be related to the deletion of
old tiles. what i can tell for sure is that the correct tiles get deleted. i
had lots of debugging
On Thu, Feb 21, 2008 at 1:51 PM, till busch wrote:
> hi curt,
>
> sorry for being rude. your asking (though not specific enough, imho) had a
> valid point as andy pointed out (in irc). the variable naming was bad.
> apparently in the transition from plib the wrong branch of the condition
> got
> i
hi curt,
sorry for being rude. your asking (though not specific enough, imho) had a
valid point as andy pointed out (in irc). the variable naming was bad.
apparently in the transition from plib the wrong branch of the condition got
in. this patch now fixes the variable names. (and adds comments
I was looking through some of the recent code changes for newcache.cxx and I
see that the time stamping has seen substantial changes though several
revisions and probably does not resemble the plib code any more ... I based
my questions on the contents of your patch not realizing the file had seen
* Melchior FRANZ -- Thursday 21 February 2008:
> No, Nasal has nothing to do with it. It's only the order in
> the main loop.
Well, Nasal has indirectly to do with it: the change in execution
order put the event manager right before the view handling, so
that Nasal code (or other event driven stuf
hi curt,
1. this is a really small patch.
please read the code before posting funny questions.
2. besides of the missing min_index the logic for finding the oldest tile was
plain wrong. notice the comparison operator was wrong? (and in the same
manner max_time=0 was wrong) for those who do not
On Thu, Feb 21, 2008 at 11:11 AM, till busch <[EMAIL PROTECTED]> wrote:
> hi,
>
> as discussed with tim on irc. here comes a quick fix for memory-hungry
> tile
> manager. due to bugs in FGNewCache old tiles where never deleted.
>
> i left the timestamp-updates in the cull-traversal. but imho thing
* Curtis Olson -- Thursday 21 February 2008:
> If you can setup two flightgear machines [...]
Unfortunately not. But if someone wants to donate some good hardware,
I'd try that variant. :-}
> If you don't have the hardware to setup two PC's simultaneously, I could
> walk you through some other
On Thu, Feb 21, 2008 at 11:25 AM, Melchior FRANZ <[EMAIL PROTECTED]> wrote:
> Yes, you wrote me about it. I couldn't reproduce, but told you
> about a bug in the replay system and what you could try. You
> didn't seem to have done that, but otherwise didn't reply either.
> So I considered it resol
* Curtis Olson -- Thursday 21 February 2008:
> not something I have time to look into myself right now,
> but is something I've brought up before,
Yes, you wrote me about it. I couldn't reproduce, but told you
about a bug in the replay system and what you could try. You
didn't seem to have done t
hi,
as discussed with tim on irc. here comes a quick fix for memory-hungry tile
manager. due to bugs in FGNewCache old tiles where never deleted.
i left the timestamp-updates in the cull-traversal. but imho things work just
as well when timestamps are updated in FGNewCache::insert_tile() and
F
On Sat, Feb 9, 2008 at 8:24 AM, Alex Buzin wrote:
> I have write the flight to the file using generic protocol (with
> playback.xml). When replaying flight in Cockpit View all is fine, but when
> I
> switch to Chase View picture starts to jitter.
> I got this at Flightgear-1.0.0 at v0.9.10 this ef
Use the tag in the controller configs to specify a 'fixed'
sampling rate. Personally, I config and tune all my controllers to
run at 20Hz so that there is a good chance they'll work on
lower-end systems without causing problems on faster machines.
LeeE
On Wednesday 20 February 2008 21:56, f
* Thomas Förster -- Thursday 21 February 2008:
> My main idea is not to develop a complicated model. I rather
> try to find some complicated filtering in the hope, that the
> remaining data gives a simple model that's better than the
> conservative setting.
Ahh, excellent. That sounds even better
Thanks for the processing chain.
I'll see if I find some time to look into this in the weekend. Lots of other
data processing (ant distributions, butterfly breathing, etc.) on the bench
already... :)
My main idea is not to develop a complicated model. I rather try to find some
complicated filt
* Mike Schuh -- Wednesday 20 February 2008:
> Not sure how to incorporate sun_angle for values < 0
> (i.e., night). Moon?
I doubt that the moon has much influence (although it slightly
deforms the Earth surface). The sun angle effect is already
contained in the other values, as well as in the li
Changes to the huge compressed files should IMHO generally
be avoided. It means that, no matter how simple the change,
everyone has to download megabytes of data. In most cases
it should be enough to drop Robin a line and to wait for
the next update. (In the last apt.dat.gz one of my routine
airpor
Hi All,
I have edited the Installing_Scenery page in the wiki by fleshing out the
TODOs a little more.
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Installing_Scenery
If someone could do something for fgadmin, that would remove the last TODO
on that page :-)
What's the next page to
Am Mittwoch 20 Februar 2008 schrieb Mike Schuh:
> I wonder if a multiple regression against several factors would turn up
> anything useful:
>
> vis = f(humidity,temp,wind,ceiling,elevation,sun_angle,ground_cover)
>
> Not sure how to incorporate sun_angle for values < 0 (i.e., night). Moon?
>
> g
25 matches
Mail list logo