Norman Vine writes:
Yes, I've had this discussion as well. The sun should stop being a
light source once it's, say, 15-30 deg below the horizon. Otherwise,
it lights up the bottoms of objects at night.
I think all that is needed is to change to 'ambient' lighting only after the
Andy:
Thanks for the info. I'd be reluctant to put together an
Input/Joysticks/Saitek/X45.xml file that I couldn't actually test. If
you have a chance to hobble one together some time, I'll be very
grateful.
All the best,
David
--
David Megginson, [EMAIL PROTECTED],
The CVS server is not working for me at the moment. It was working 10 hours ago when
I last tried it.
$ cvs diff
cvs [diff aborted]: recv() from server cvs.flightgear.org: EOF
- Julian
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I've sent mail to Curt about this point already, but while I'm
waiting, I thought I'd throw out the question to the list. I've
patched FlightGear so that (a) runway edge lights are not visible from
improbable distances (like 50km or more), and (b) runway edge lights
are not visible at all while
David Megginson writes:
Norman Vine writes:
Yes, I've had this discussion as well. The sun should stop being a
light source once it's, say, 15-30 deg below the horizon. Otherwise,
it lights up the bottoms of objects at night.
I think all that is needed is to change to 'ambient'
Norman Vine writes:
Probably more with the 'model' now being in it's own 'graph' which
is called after other code has 'mucked' with the lighting after it was
setup to use the proper 'ambient' and 'diffuse' valuse for the 'time of day'
The model is not in its own graph in external view,
David Megginson writes:
Norman Vine writes:
The model is not in its own graph in external view, and this problem
far predates the new model code in any case. Here's a thread from
December 2000, when it was already an old problem:
David Megginson writes:
Norman Vine writes:
Probably more with the 'model' now being in it's own 'graph' which
is called after other code has 'mucked' with the lighting after it was
setup to use the proper 'ambient' and 'diffuse' values for the 'time of
day'
The model is not in its own
Tony Peden wrote:
On Wed, 2002-07-03 at 11:40, David Megginson wrote:
Tony Peden writes:
I don't know how many interdependencies there are, but the js related
source and headers total 142k.
Check that, 212k.
That's pretty close. I wonder how bad the dependencies are.
OK,
Norman Vine writes:
globals-get_model_mgr()-draw();
globals-get_aircraft_model()-draw();
That's mostly dead code. FGModelMgr::draw is now a no-op and should
be removed (Jim?):
void
FGModelMgr::draw ()
{
// ssgSetNearFar(_nearplane, _farplane);
//
I'm currently applying a range limit of 12,000m (about 6nm) to the
lights (the range is from the middle of each runway). Personally, I
suspect that that might be far too generous, but I don't want to make
the range too short for very long runways. What does everyone else
think?
All the
David Megginson wrote:
Thanks for the info. I'd be reluctant to put together an
Input/Joysticks/Saitek/X45.xml file that I couldn't actually test. If
you have a chance to hobble one together some time, I'll be very
grateful.
I was afraid you'd say that. :) Here is an X45.xml file that I've
I'm getting it too. Cygwin tree from 5 days ago or so...
- Original Message -
From: Paul Deppe [EMAIL PROTECTED]
To: FGFS-Devel [EMAIL PROTECTED]
Sent: Saturday, July 06, 2002 12:12 PM
Subject: [Flightgear-devel] RE: [Plib-devel] Autogen/configure now fails,
related to GL
In the
On Sat, 06 Jul 2002 13:49:36 -0700,
Andy Ross [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
Arnt Karlsen wrote:
..(during the Falklands War, the Britts tested refuelling of
Harriers and Sea Harriers, from ships, in-hover refuelling,
believe I saw this in Air Progress magazine
Realistic night lighting would be great.
I know how MSFS nightlighting works (Its fairly trivial), so if we
could change the lighting parameters for the 3D model only (I guess we
do not want MSFS lighting for the rest), we could have night-lit
aircraft. Often, this looks really great, I
Yes, I've had this discussion as well. The sun should stop being a
light source once it's, say, 15-30 deg below the horizon.
IMHO it should be possible to have different rendering parameters for
the aircraft than for the rest of the scenery, for example by having
it in its own tree. Then, you
In the $fgroot/Lighting you can control the ambient and diffues
lighting based on sun angle.
Curt.
David Megginson writes:
Norman Vine writes:
Probably more with the 'model' now being in it's own 'graph' which
is called after other code has 'mucked' with the lighting after it was
On Sun, 7 Jul 2002, David Megginson wrote:
patched FlightGear so that (a) runway edge lights are not visible from
improbable distances (like 50km or more), and (b) runway edge lights
are not visible at all while the sun is above the horizon, but haven't
committed these patches yet.
I think
Attched find an xml file dc3.xml that includes edits that allow
accelleration on the main gear and relativly easy wheel landings. With
these changes, I can leave the tail wheel unlocked for take-off and
landings.
Changes:
1. Relaxed the stall width for both the wing and the hstab. A dc3
19 matches
Mail list logo
