* Ampere K. Hardraade -- Thursday 05 May 2005 20:43:
Just an idea: would it be possible to throw in some random and irrelevent
messages in there as well, such as tying pilot's shoelase, so people can
have a laugh or two while waiting for FlightGear to load?
No. There are only a few messages
Le vendredi 06 mai 2005 11:24 +0200, Melchior FRANZ a crit :
* Ampere K. Hardraade -- Thursday 05 May 2005 20:43:
Just an idea: would it be possible to throw in some random and irrelevent
messages in there as well, such as tying pilot's shoelase, so people can
have a laugh or two while
* James Turner -- Thursday 05 May 2005 10:54:
I don't have much time to delve into this right now (hah!), but I
have some log calls in my local build, which have been fairly
consistent (haven't tested since your changes, Melchior - when I do,
I'll post those numbers).
Would be
* Gerard ROBIN -- Friday 06 May 2005 15:11:
Le vendredi 06 mai 2005 à 11:24 +0200, Melchior FRANZ a écrit :
No. There are only a few messages at strictly defined points. [...] The
only possibility for aircraft designers is to put a message into the
optional title
* Curtis L. Olson -- Thursday 05 May 2005 00:26:
What can happen though if we interleave with the rendering loop on init,
is that for slower displays that take a non-trivial amount of time to
render (or even clear the buffer) then init times can be substantially
slowed.
I'm claim that the
David Luff wrote
Ditto Cygwin for long startup times. I've taken a look in the past, and
loading the airport and nav data consumes the vast bulk of the time. This
happens before any rendering (and before the splash-screen appears, which
I
assume Melchior's patch fixes).
FGFS start-up
* Vivian Meazza -- Thursday 05 May 2005 09:44:
FGFS start-up times under Cygwin have become so long that it is possible to
brew a cup of coffee while waiting ... some might think this useful.
Oh. I hope you mean that the startup time has become much too long over time,
and not that this patch
Melchior FRANZ wrote
* Vivian Meazza -- Thursday 05 May 2005 09:44:
FGFS start-up times under Cygwin have become so long that it is possible
to
brew a cup of coffee while waiting ... some might think this useful.
Oh. I hope you mean that the startup time has become much too long over
On 5 May 2005, at 09:18, Melchior FRANZ wrote:Oh. I hope you mean that the startup time has become much too long over time, and not that this patch made it worse. I don't think that the patch has a noticable effect, neither positive nor negative. Except that it possibly improves the perception and
Melchior FRANZ wrote:
* Curtis L. Olson -- Wednesday 04 May 2005 22:44:
I like the idea. One problem on the windows platform is lack of
feedback from the graphical launcher that anything happened when you
clicked run. It's easy to click run a couple times and end up with 5
copies of FG
Oh, forgot to mention: the only (minor) problem is, that some parts
of the initialization take rather long, so if you switch to another
desktop and back, it may take some seconds until the screen is
refreshed. I thought about putting two or three fgSplashUpdate(1.0);
into fgNavInit() (which takes
* James Turner -- Wednesday 04 May 2005 23:14:
Minor partial objection - the Mac startup is dog slow (like 90
seconds to get to a usable plane in the C172 and SFO), and I think at
least part of the problem is the 'init while idle' scheme - FG wastes
too much time doing rendering type
On 04/05/2005 at 23:40 Melchior FRANZ wrote:
* James Turner -- Wednesday 04 May 2005 23:14:
Minor partial objection - the Mac startup is dog slow (like 90
seconds to get to a usable plane in the C172 and SFO), and I think at
least part of the problem is the 'init while idle' scheme - FG
Melchior FRANZ wrote:
* James Turner -- Wednesday 04 May 2005 23:14:
Minor partial objection - the Mac startup is dog slow (like 90
seconds to get to a usable plane in the C172 and SFO), and I think at
least part of the problem is the 'init while idle' scheme - FG wastes
too much time
14 matches
Mail list logo
