Re: [Flightgear-devel] splash screen distortion

2005-05-23 Thread Erik Hofman

Dave Culp wrote:
During sim startup, about 2 or 3 seconds before the world appears, the 
splash image is distorted, most often stretched vertically, sometimes split 
in two vertically.  It's been doing this for a long time, maybe a year or 
more, but I've been ignoring it until now. 


Anyone else getting this?


Yes and I think it has something to do with changing the field of view 
at that point. I haven't looked deeper into that though.


Erik

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen distortion

2005-05-23 Thread Adam Dershowitz
Yes, I do get the same thing.
MacOS 10.3
Fg 0.9.8


-- Adam




 From: Dave Culp [EMAIL PROTECTED]
 Reply-To: FlightGear developers discussions flightgear-devel@flightgear.org
 Date: Mon, 23 May 2005 00:06:08 -0500
 To: FlightGear developers discussions flightgear-devel@flightgear.org
 Subject: [Flightgear-devel] splash screen distortion
 
 During sim startup, about 2 or 3 seconds before the world appears, the
 splash image is distorted, most often stretched vertically, sometimes split
 in two vertically.  It's been doing this for a long time, maybe a year or
 more, but I've been ignoring it until now.
 
 Anyone else getting this?
 
 
 Mandrake 10.1
 nVidia MX440 with latest driver
 cvs plib, SimGear, FlightGear
 glut, openal
 
 
 Dave
 
 ___
 Flightgear-devel mailing list
 Flightgear-devel@flightgear.org
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel
 2f585eeea02e2c79d7b1d8c4963bae2d



___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen distortion

2005-05-23 Thread Harald JOHNSEN

Dave Culp wrote:

During sim startup, about 2 or 3 seconds before the world appears, the 
splash image is distorted, most often stretched vertically, sometimes split 
in two vertically.  It's been doing this for a long time, maybe a year or 
more, but I've been ignoring it until now. 


Anyone else getting this?


Mandrake 10.1
nVidia MX440 with latest driver
cvs plib, SimGear, FlightGear
glut, openal


Dave

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

 


This is because of the 2D panel.

Harald.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] splash screen distortion

2005-05-22 Thread Dave Culp
During sim startup, about 2 or 3 seconds before the world appears, the 
splash image is distorted, most often stretched vertically, sometimes split 
in two vertically.  It's been doing this for a long time, maybe a year or 
more, but I've been ignoring it until now. 

Anyone else getting this?


Mandrake 10.1
nVidia MX440 with latest driver
cvs plib, SimGear, FlightGear
glut, openal


Dave

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash

2005-01-19 Thread Jorge Van Hemelryck
In theory, this is a nice idea, but I'm not sure about IPC on Windows.
Forking might be OK, but I'm quite sure that sending a signal is not so
simple, so we would have to come up with something else.

What about doing it the other way around when the user is using fgrun to
launch fgfs ? What I mean is, fgrun might launch some kind of splash
dialog of its own, just to make sure that there is some feedback before
the actual fgfs splash screen is displayed... I'm still thinking about
how to make another app interact with fgfs when it's running, instead of
controlling it via the plib GUI, and part of this could be this splash
screen.

-- 
Jorge Van Hemelryck

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-17 Thread Manuel Massing
Hi,

  I've been holding off my code changes already since Christmas. ;-)

why not tag the planned releases as branches. This way development can
continue in HEAD while the releases can be tested and bugfixed in-
dependently.  This is fairly standard procedure for open source projects (e.g.
KDE, gcc, freebsd).

cheers,

 Manuel

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-17 Thread Durk Talsma
On Monday 17 January 2005 12:51, Manuel Massing wrote:
 Hi,

   I've been holding off my code changes already since Christmas. ;-)

 why not tag the planned releases as branches. This way development can
 continue in HEAD while the releases can be tested and bugfixed in-
 dependently.  This is fairly standard procedure for open source projects
 (e.g. KDE, gcc, freebsd).


Well, I guess every open source project has it's own way of doing things. 
Curt's announcement of a new planned release flagged the start of a feature 
freeze period, but it also coincided with a rare opportunity for me to do 
some development work. So  I decided not to submit any of my work until after 
the release. 

I see some merit in branching, but I guess it would increase the workload of 
the project maintainers, who now need to make sure that bugfixes for the 
release branch make it into the development tree and vice verca. 

Just my two cents,
Durk


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-17 Thread Innis Cunningham
Hi Durk
 Durk Talsma writes
Well, I guess every open source project has it's own way of doing things.
Curt's announcement of a new planned release flagged the start of a feature
freeze period, but it also coincided with a rare opportunity for me to do
some development work. So  I decided not to submit any of my work until 
after
the release.
Does this mean we are not going to get the fixed AI in this release?.

Durk
Cheers
Innis

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-17 Thread Durk Talsma
On Monday 17 January 2005 14:41, Innis Cunningham wrote:
 Hi Durk
   Durk Talsma writes

 Well, I guess every open source project has it's own way of doing things.
 Curt's announcement of a new planned release flagged the start of a
  feature freeze period, but it also coincided with a rare opportunity for
  me to do some development work. So  I decided not to submit any of my
  work until after
 the release.

 Does this mean we are not going to get the fixed AI in this release?.


Hi Innis,

No worries mate (as I picked up while I was down under last year) :-)

I did submit the bugfix, just not the new features. 

Btw, could some of the windows people let us know if the traffic manager now 
works? to activate you need to set traffic manager/enabled and (iirc) 
ai/enabled to true in preferences. (But you can ignore my commented out 
scenarios). 

ai-traffic
   enabled type=booltrue/enabled
   level type=int1/level
  /ai-traffic

  traffic-manager
 enabled type=booltrue/enabled
  /traffic-manager

  ai
   enabled type=booltrue/enabled
   !-- scenarionimitz_demo/scenario --
   !-- scenarioaircraft_demo/scenario --
  /ai


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-17 Thread Innis Cunningham

 Durk Talsma writes
 Does this mean we are not going to get the fixed AI in this release?.

Hi Innis,
No worries mate (as I picked up while I was down under last year) :-)
Keep this up and we may need to make you an honorary Aussi.:-)
I did submit the bugfix, just not the new features.
Btw, could some of the windows people let us know if the traffic manager 
now
works? to activate you need to set traffic manager/enabled and (iirc)
ai/enabled to true in preferences. (But you can ignore my commented out
scenarios).
Look forward to giving it a test in the new release.
Thanks
Cheers
Innis

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] splash screen

2005-01-16 Thread Jim Wilson
My guess is that there isn't anything quick and easy for this release,  but
I'm wondering if anyone has ideas for getting the splash screen up on the
screen faster.   Currently on my p4 2.4 it is taking 10 seconds for the splash
screen to appear.  AFAIK all we need is the geometry and gamemode preferences
to open the window.

Best,

Jim


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


RE: [Flightgear-devel] splash screen

2005-01-16 Thread Norman Vine
maybe something like

static void fgIdleFunction ( void ) {
// printf(idle state == %d\n, idle_state);

if ( idle_state == 0 ) {
// Initialize the splash screen right away
if ( fgGetBool(/sim/startup/splash-screen) ) {
fgSplashInit(fgGetString(/sim/startup/splash-texture));
}

idle_state++;
} else {
if ( fgGetBool(/sim/startup/splash-screen) ) {
fgSplashUpdate(0.0, 1.0);
}   
}
if ( idle_state == 1 ) {




 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Jim Wilson
 Sent: Sunday, January 16, 2005 10:39 AM
 To: flightgear-devel@flightgear.org
 Subject: [Flightgear-devel] splash screen
 
 
 My guess is that there isn't anything quick and easy for this release,  but
 I'm wondering if anyone has ideas for getting the splash screen up on the
 screen faster.   Currently on my p4 2.4 it is taking 10 seconds for the splash
 screen to appear.  AFAIK all we need is the geometry and gamemode preferences
 to open the window.
 
 Best,
 
 Jim
 
 
 ___
 Flightgear-devel mailing list
 Flightgear-devel@flightgear.org
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel
 2f585eeea02e2c79d7b1d8c4963bae2d
 

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


RE: [Flightgear-devel] splash screen

2005-01-16 Thread Jim Wilson
Norman Vine said:

 maybe something like
 
 static void fgIdleFunction ( void ) {
 // printf(idle state == %d\n, idle_state);
 
 if ( idle_state == 0 ) {
 // Initialize the splash screen right away
 if ( fgGetBool(/sim/startup/splash-screen) ) {
 fgSplashInit(fgGetString(/sim/startup/splash-texture));
 }
 
 idle_state++;
 } else {
 if ( fgGetBool(/sim/startup/splash-screen) ) {
 fgSplashUpdate(0.0, 1.0);
 } 
 }
 if ( idle_state == 1 ) {
 
 

That won't do it.  You've reminded me that we do need the
/sim/startup/splash-screen property (in addition to geometry, etc).

The problem is we're doing way to much before even getting that far.  It looks
like 90% of the delay is loading the Airport database.  We should be able to
just load the configuration and parameters and do the rest of the work that's
being done in fgInitMain after we get the loop going.  Everytime I look at
this init code I've got to relearn how it works.  It is still a mess.

Best,

Jim


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread D Luff
On Sun, 16 Jan 2005 20:27:10 -
Jim Wilson wrote:

 The problem is we're doing way to much before even getting that far.  It looks
 like 90% of the delay is loading the Airport database.  

The problem is that loading the airport database take *much* (10 times) longer 
on Windows than Linux.  That means that a lot of the core developers don't 
really notice this as much.

We should be able to
 just load the configuration and parameters and do the rest of the work that's
 being done in fgInitMain after we get the loop going.  Everytime I look at
 this init code I've got to relearn how it works.  It is still a mess.

Agreed.  I had a look at some of it recently with a view to automatically 
starting on the into the wind runway with real-weather.  At the moment it can't 
be done, since real-weather is dependent on position, and I'm trying to 
introduce the counter-dependency as well.  What I think needs to happen is to 
init approx location first, then init the environment, then init exact location.

Cheers - Dave

This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks.  Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread Durk Talsma
On Sunday 16 January 2005 21:54, D Luff wrote:
 On Sun, 16 Jan 2005 20:27:10 -

 Agreed.  I had a look at some of it recently with a view to automatically
 starting on the into the wind runway with real-weather.  At the moment it
 can't be done, since real-weather is dependent on position, and I'm trying
 to introduce the counter-dependency as well.  What I think needs to happen
 is to init approx location first, then init the environment, then init
 exact location.


David, as I mailed to you off-list (but probably not yet to FlightGear-devel), 
I'm working on extending the airport code. Part of the new code is going to 
be a function that returns the active runway for a specific airport. 

So, I guess, initialization could be something like (in pseudo code):
1) get airport
2) airport-get weather
3) airport/weather-getActiveRunway
4) user-init  at active runway

Cheers,
Durk


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread D Luff
On Sun, 16 Jan 2005 22:20:07 +0100
Durk Talsma wrote:

 On Sunday 16 January 2005 21:54, D Luff wrote:
  On Sun, 16 Jan 2005 20:27:10 -
 
  Agreed.  I had a look at some of it recently with a view to automatically
  starting on the into the wind runway with real-weather.  At the moment it
  can't be done, since real-weather is dependent on position, and I'm trying
  to introduce the counter-dependency as well.  What I think needs to happen
  is to init approx location first, then init the environment, then init
  exact location.
 
 
 David, as I mailed to you off-list (but probably not yet to 
 FlightGear-devel), 
 I'm working on extending the airport code. Part of the new code is going to 
 be a function that returns the active runway for a specific airport. 
 
 So, I guess, initialization could be something like (in pseudo code):
 1) get airport
 2) airport-get weather
 3) airport/weather-getActiveRunway
 4) user-init  at active runway
 

Hi Durk,

Yes, if you're trying to more intelligently choose the active runway, then 
you're probably wanting both aircraft type and weather set before your runway 
choosing function gets called.  Add stage 1a - get aircraft type (heavy, light 
etc).  At the moment though, you'll be able to set the runway for all the AI 
traffic very nicely, but at startup you'll still have missing information at 
the time of setting it for the user, just as the current code does.

Your mail is stuck in proprietry format on a box I can't boot at the moment BTW 
:-(  As soon as it's resusitated (reinstall OS) I'll take a look at it.  If 
it's still in your outbox, perhaps you could hit the send button again...

Cheers - Dave

This message has been scanned but we cannot guarantee that it and any
attachments are free from viruses or other damaging content: you are
advised to perform your own checks.  Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread Curtis L. Olson
Jim Wilson wrote:
Norman Vine said:
 

maybe something like
static void fgIdleFunction ( void ) {
   // printf(idle state == %d\n, idle_state);
   if ( idle_state == 0 ) {
   // Initialize the splash screen right away
   if ( fgGetBool(/sim/startup/splash-screen) ) {
   fgSplashInit(fgGetString(/sim/startup/splash-texture));
   }
   
   idle_state++;
   } else {
   if ( fgGetBool(/sim/startup/splash-screen) ) {
   fgSplashUpdate(0.0, 1.0);
   }	
   }
   if ( idle_state == 1 ) {


   

That won't do it.  You've reminded me that we do need the
/sim/startup/splash-screen property (in addition to geometry, etc).
The problem is we're doing way to much before even getting that far.  It looks
like 90% of the delay is loading the Airport database.  We should be able to
just load the configuration and parameters and do the rest of the work that's
being done in fgInitMain after we get the loop going.  Everytime I look at
this init code I've got to relearn how it works.  It is still a mess.
 

Let's please hold off on touching any of this and restructuring the init 
order until *after* the upcoming release.

Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt 
HumanFIRST Program  http://www.humanfirst.umn.edu/
FlightGear Project  http://www.flightgear.org
Unique text:2f585eeea02e2c79d7b1d8c4963bae2d

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] splash

2005-01-16 Thread Alex Perry
Why can't we have a tiny little app that is just intelligent enough
to find the XML file, check whether we should be splashing ourselves,
knows to abort quietly if not, and otherwise brings up a splash window?

Given something like that, with very very few library dependencies,
we should be able to fork that off as the very first thing we do.
While the main program is still trying to get the DLLs linked up,
the forked utility would long since have put up the splash screen.

When we have the main loop running and the simulator has run one second,
we simply send a signal to the splash and it gracefully suicides.

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread Jim Wilson
D Luff said:

 On Sun, 16 Jan 2005 20:27:10 -
 Jim Wilson wrote:
 
  The problem is we're doing way to much before even getting that far.  It 
  looks
  like 90% of the delay is loading the Airport database.  
 
 The problem is that loading the airport database take *much* (10 times)
longer on Windows than Linux.  That means that a lot of the core developers
don't really notice this as much.
 

Actually I'm running linux and its with an optimized fs so most things load
very quickly.

 We should be able to
  just load the configuration and parameters and do the rest of the work 
  that's
  being done in fgInitMain after we get the loop going.  Everytime I look at
  this init code I've got to relearn how it works.  It is still a mess.
 
 Agreed.  I had a look at some of it recently with a view to automatically
starting on the into the wind runway with real-weather.  At the moment it
can't be done, since real-weather is dependent on position, and I'm trying to
introduce the counter-dependency as well.  What I think needs to happen is to
init approx location first, then init the environment, then init exact location.
 

Absolutely, but all that can be done after the loop starts so that we can get
the splash up there more quickly.

Best,

Jim


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread Jim Wilson
Curtis L. Olson said:

 Jim Wilson wrote:
 
 Norman Vine said:
 
   
 
 maybe something like
 
 static void fgIdleFunction ( void ) {
 // printf(idle state == %d\n, idle_state);
 
 if ( idle_state == 0 ) {
 // Initialize the splash screen right away
 if ( fgGetBool(/sim/startup/splash-screen) ) {
 fgSplashInit(fgGetString(/sim/startup/splash-texture));
 }
 
 idle_state++;
 } else {
 if ( fgGetBool(/sim/startup/splash-screen) ) {
 fgSplashUpdate(0.0, 1.0);
 }   
 }
 if ( idle_state == 1 ) {
 
 
 
 
 
 That won't do it.  You've reminded me that we do need the
 /sim/startup/splash-screen property (in addition to geometry, etc).
 
 The problem is we're doing way to much before even getting that far.  It 
 looks
 like 90% of the delay is loading the Airport database.  We should be able to
 just load the configuration and parameters and do the rest of the work that's
 being done in fgInitMain after we get the loop going.  Everytime I look at
 this init code I've got to relearn how it works.  It is still a mess.
   
 
 
 Let's please hold off on touching any of this and restructuring the init 
 order until *after* the upcoming release.
 

Yes, of course.  So far this release looks good to go from here.  I'll test a
bit more tonight,  but I don't see any reason to hold back.

Thanks,

Jim


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread Durk Talsma
On Sunday 16 January 2005 23:07, Curtis L. Olson wrote:


 Let's please hold off on touching any of this and restructuring the init
 order until *after* the upcoming release.

 Curt.

Curt,

I've been holding off my code changes already since Christmas. ;-)

Cheers,
Durk


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] splash screen

2005-01-16 Thread Mathias Fröhlich

Hi,

On Montag 17 Januar 2005 08:03, Durk Talsma wrote:
 I've been holding off my code changes already since Christmas. ;-)
Me and Vivian too.

  Greetings

   Mathias

-- 
Mathias Fröhlich, email: [EMAIL PROTECTED]

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] Splash screens or website snapshots.

2004-05-18 Thread Erik Hofman
Hi,
We desperately need new splash screens and website snapshots. Esp. the 
snapshots are hopelessly out of sync.

Any volunteer?
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


[Flightgear-devel] Splash screen

2003-07-22 Thread Frederic Bouvier
Here is splash screen I just designed, featuring the 
747 and the Golden Gate Bridge :

http://perso.wanadoo.fr/frbouvi/flightsim/splash.rgb

-Fred



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


Re: [Flightgear-devel] Splash screens

2002-07-03 Thread John Check

On Wednesday 03 July 2002 1:59 pm, Cameron Moore wrote:
 * [EMAIL PROTECTED] (John Check) [2002.07.03 00:32]:
  On Wednesday 03 July 2002 1:19 am, Cameron Moore wrote:
   I decided to make a couple splash screens out of some nice screenshots,
   and I'm curious how they look on other systems -- mainly if they are
   too dark.  They are straight out of FG -- no tampering except for the
   text, of course.  If you want to test them, you can get them from here:
  
 http://unbeatenpath.net/software/fgfs/Splash/
  
   One is of the A-4 during an initial climb with runway lights in the
   background.  The other is an overhead shot of the c172 at dusk.
  
   If you try these out, let me know what you think.  Thanks
 
  I really really like the A4 one, but it's too dark IMO.

 This is what I expected, but wanted to share them before I get bored and
 go back to jacking with valgrind.  I'll try to get a little more
 sunlight next time and see how that goes.

 Thanks, everyone

What might work nicely is pause the sim, save the flight
then play with the time.

TTYL
J

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



[Flightgear-devel] Splash screens

2002-07-02 Thread Cameron Moore

I decided to make a couple splash screens out of some nice screenshots,
and I'm curious how they look on other systems -- mainly if they are too
dark.  They are straight out of FG -- no tampering except for the text,
of course.  If you want to test them, you can get them from here:

  http://unbeatenpath.net/software/fgfs/Splash/

One is of the A-4 during an initial climb with runway lights in the
background.  The other is an overhead shot of the c172 at dusk.

If you try these out, let me know what you think.  Thanks
-- 
Cameron Moore
[ If you think nobody cares about you, try missing a couple payments. ]

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Splash screens

2002-07-02 Thread John Check

On Wednesday 03 July 2002 1:19 am, Cameron Moore wrote:
 I decided to make a couple splash screens out of some nice screenshots,
 and I'm curious how they look on other systems -- mainly if they are too
 dark.  They are straight out of FG -- no tampering except for the text,
 of course.  If you want to test them, you can get them from here:

   http://unbeatenpath.net/software/fgfs/Splash/

 One is of the A-4 during an initial climb with runway lights in the
 background.  The other is an overhead shot of the c172 at dusk.

 If you try these out, let me know what you think.  Thanks

I really really like the A4 one, but it's too dark IMO.

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] Splash screens

2002-07-02 Thread Frederic Bouvier

They are too dark. I can't see them. Only the text.

It's on Win2k

Cheers,

-Fred

- Original Message - 
From: Cameron Moore [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, July 03, 2002 7:19 AM
Subject: [Flightgear-devel] Splash screens


 I decided to make a couple splash screens out of some nice screenshots,
 and I'm curious how they look on other systems -- mainly if they are too
 dark.  They are straight out of FG -- no tampering except for the text,
 of course.  If you want to test them, you can get them from here:
 
   http://unbeatenpath.net/software/fgfs/Splash/
 
 One is of the A-4 during an initial climb with runway lights in the
 background.  The other is an overhead shot of the c172 at dusk.
 
 If you try these out, let me know what you think.  Thanks
 -- 
 Cameron Moore
 [ If you think nobody cares about you, try missing a couple payments. ]
 
 ___
 Flightgear-devel mailing list
 [EMAIL PROTECTED]
 http://mail.flightgear.org/mailman/listinfo/flightgear-devel
 



___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel