[Flightgear-devel] Some Strangeness

2006-07-22 Thread Innis Cunningham 
Hi All
Being new to Flightgear under Linux I have noticed a problem.
If I run with the sim the full size of the screen regardless of the
screen resolution I have the hotspot points about 1 inch/25mm
below were the yellow hotspot squares would indicate the hotspot
to be.
If I run with a screen resolution of say 1280x1024 and the flightgear
geometry set to say 1024x768 then the hotspots are right were the
yellows squares indicate they should be.I.E no problem.So if I run
FG at the same resolution as the screen resolution then the hotspots
are 25mm low if I run with the FG resolution less than the screen
then the hotspots are correct.
Also if I run FG with enable full screen the sim operates as a slideshow
Also if I run the sim with a resolution smaller than the screen resolution
and then select the FG window to fullscreen the sim stops to a slideshow.
Has anyone else experienced this problem.
I tried this on both the 737 and 777 with the same results.
I am running FG 9.10 from the FG 9.10 Debian package.
Is this a bug or am I doing something wrong.

Cheers
Innis



-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OT: D-EENE

2006-07-22 Thread Martin Spott 
Georg Vollnhals wrote:
 Martin Spott schrieb:

I can't believe it, there actually is a photo on the net that shows the
aircraft that I did most of my trainig on. It also features my
intructor on the co-seat  :-)

  http://www.flugzeugbilder.de/show.php?id=249541
[...]
 nice - but now we want to get a photo with *you* on the pilot's seat :-)

Getting one with me in the pilot's seat is difficult, but I hope this
one is sufficient to serve as a proof  ;-)

  http://foxtrot.mgras.net/bitmap/FGFS/DEEQA-EDNY.jpg

Thanks to Ingrid Scholl for handing the photo to me,
Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Update: Sun

2006-07-22 Thread Mark 
Hi Melchior,

that's OK. The code has to fit to the existing codebase and so I'll tidy 
it up a bit.
I just didn't look at those details. No problem.

CU Mark

Melchior FRANZ wrote:
 * Mark -- Thursday 20 July 2006 20:31:
   
 After it is in cvs I'd be happy for some feedback and suggestions for 
 improvement.
 

 Here's some already, mostly formal problems. (I'm the pedant here.)
 The important aspects seem to be OK.


   fgGetNode(/environment)); 

 ... in a constructor. Although the existence of the /environment is
 pretty much guaranteed, we still make sure that the node gets created:

   fgGetNode(/environment, true));
 


 --
 consistency:

 +SGPath ihalopath = path , ohalopath=path;

 Now, what is it? spaces around '=' (good) or not? Space in front of
 comma operator?

 +i_halo_color[0] = 1- (1.1* red_scat_f);
 +o_halo_color[0] = 1- (1.4* red_scat_f);

 Operators sticking on numbers at several places. Either spaces around
 operators (good IMHO) or not. Or is they kind of unary operators?  :-}


 --


 indentation:

 +ohalo-setCallback( SSG_CALLBACK_PREDRAW, sgSunHaloPreDraw );
 +ohalo-setCallback( SSG_CALLBACK_POSTDRAW, sgSunHaloPostDraw );
 +
 +   sun_transform-addKid( ohalo );
 +   sun_transform-addKid( ihalo );

 What about aligning those correctly?


 --


 +  if ( env_node ){
 +  env_node-setDoubleValue(atmosphere/altitude-troposphere-top,r_tropo 
 - r_earth);
 +  env_node-setDoubleValue(atmosphere/altitude-half-to-sun, alt_half);
 +  }

 Umm ... what about indenting that correctly?
 Yes, I know, the existing code isn't consistent either. But that's no
 reason to make the situation worse.

 m.

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys -- and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel
   

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Update: Sun

2006-07-22 Thread Mark 
Hi Vassilii,

it is indeed an debugging artifact. At least the using namespace std is.
The rest was existing code. I'll see what I can change.
As for the vector math, I didn't change any of that and this is all from 
the original implementation.
And I don't really want to fuzz with that.

Mark

Vassilii Khachaturov wrote:
 http://www.akermann.org/fgfs/simgear-sun.tar.gz
 
 The chunk
 @@ -109,6 +109,7 @@ void SGSky::build( double h_radius_m, do
  // 180 degrees = darkest midnight
  bool SGSky::repaint( const SGSkyColor sc )
  {
 +   using namespace std;
  if ( effective_visibility  1000.0 ) {
 enable();
 dome-repaint( sc.sky_color, sc.fog_color, sc.sun_angle,
 seems a debugging artifact to me.

 In oursun.cxx the constants (such as sqrt_m_log01) should probably be
 declared as const. Per-coordinate vector calculations there could be
 made to use the sg facilities of plib, but AFAIU it wouldn't change
 much except for shorten the code a tiny bit. It's pretty readable as it is
 anyhow, and fits in very nicely. Also, a patch to Thanks is due along
 with the commit, to mention yourself :)

 Thank you very much!!!

 Vassilii


 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys -- and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel
   

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Cygwin CVS compile error

2006-07-22 Thread Geoff Air 
Hi,

In a Windows XP machine, running cygwin, latest
CVS for simgear and flightgear
I am getting the SAME or SIMILAR error when
linking FlightGear ... well actually when
linking fgjs.exe, under cygwin ... namely -

Making all in Input
make[2]: Entering directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Input'
g++ -DPKGLIBDIR=\/fg-cvs/share/FlightGear\ -g -O2 -D_REENTRANT  
-L/fg-cvs/lib -L/usr/local/lib -o fgjs.exe  fgjs
.o jsinput.o jssuper.o -lplibjs  -lwinmm -lplibul -lsgprops -lsgmisc -lsgio 
-lsgdebug -lsgstructure -lsgxml -lz
/fg-cvs/lib/libplibul.a(ulClock.o): In function 
`_ZNK7ulClock10getRawTimeEv':
/home/GeoffMcLane/plib-1.8.4/src/util/ulClock.cxx:79: undefined reference to 
[EMAIL PROTECTED]'
collect2: ld returned 1 exit status
make[2]: *** [fgjs.exe] Error 1
make[2]: Leaving directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Input'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/GeoffMcLane/FlightGear-0.9-cvs/source/src'
make: *** [all-recursive] Error 1
ERROR in make

Have read what Georg and Fred wrote ... and
having found that libwinmm.a is in
/lib/w32api and in /usr/lib/w32api from -

$ find / -name *winmm*
/lib/w32api/libwinmm.a
/usr/lib/w32api/libwinmm.a

I altered -lwinmm to -llibwinmm in the
'configure' file, and did ./configure -prefix=xxx, and
make again but this time got the error -

Making all in Input
make[2]: Entering directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Input'
g++ -DPKGLIBDIR=\/fg-cvs/share/FlightGear\ -g -O2 -D_REENTRANT  
-L/fg-cvs/lib -L/usr/local/lib -o fgjs.exe  fgjs
.o jsinput.o jssuper.o -lplibjs  -llibwinmm -lplibul -lsgprops -lsgmisc 
-lsgio -lsgdebug -lsgstructure -lsgxml -lz

/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot 
find -llibwinmm
collect2: ld returned 1 exit status
make[2]: *** [fgjs.exe] Error 1
make[2]: Leaving directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Input'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/GeoffMcLane/FlightGear-0.9-cvs/source/src'
make: *** [all-recursive] Error 1
ERROR in make

I altered the same line in configure.ac from
-lwinmm to -llibwinmm
and set the environment -
$ export LDFLAGS=-L/lib/w32api
$ export CPPFLAGS=-DNOMINMAX
then did
$ ./autogen.sh
$ ./configure -prefix=/fg=cvs
$ make

BUT I STILL GET THE ERROR 'CAN NOT FIND'! on linking
fgjs.exe -

Making all in Input
make[2]: Entering directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Input'
g++ -DPKGLIBDIR=\/fg-cvs/share/FlightGear\ -g -O2 -D_REENTRANT  
-L/lib/w32api -L/fg-cvs/lib -L/usr/local/lib -o
fgjs.exe  fgjs.o jsinput.o jssuper.o -lplibjs  -llibwinmm -lplibul -lsgprops 
-lsgmisc -lsgio -lsgdebug -lsgstructu
re -lsgxml -lz
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot 
find -llibwinmm
collect2: ld returned 1 exit status
make[2]: *** [fgjs.exe] Error 1
make[2]: Leaving directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Input'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/GeoffMcLane/FlightGear-0.9-cvs/source/src'
make: *** [all-recursive] Error 1

Note, now there is a -L/lib/w32api and -llibwinmm
in the g++ command line ... version is ...
$ g++ --version
g++ (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)

The 'configure' and 'configure.ac' of cvs simgear and
tar ball of plib-1.8.4, BOTH also use -lwinmm, but I do
not get an error compiling plib or simgear ... but
would not expect one since these are
just static libraries, just for flightgear, well
fgjs.exe ...

Commenting OUT the following lines in
/src/input/makefile.am, I got the rest of FG
to compile ... that is killing the fgjs.exe make,
and js_demo as well, although it may not be a
problem ... I am 'great' at 'hacking' ;=))

#bin_PROGRAMS = js_demo fgjs
#js_demo_SOURCES = js_demo.cxx
#js_demo_LDADD = -lplibjs $(base_LIBS) $(joystick_LIBS) -lplibul
#fgjs_SOURCES = fgjs.cxx jsinput.cxx jsinput.h jssuper.cxx jssuper.h
#fgjs_LDADD = -lplibjs $(base_LIBS) $(joystick_LIBS) -lplibul \
#-lsgprops -lsgmisc -lsgio -lsgdebug -lsgstructure -lsgxml -lz

But still a problem with missing -llibwinmm ...

So putting this back as -lwinmm in 'configure',
and clearing the environment - ie close cygwin
windows, then re-open it again -
then doing just -
$ export CPPFLAGS=-DNOMINMAX
$ ./configure -prefix=/fg-cvs
$ make

AND fgfs.exe LINKED -
Making all in Main
make[2]: Entering directory 
`/home/GeoffMcLane/FlightGear-0.9-cvs/source/src/Main'
g++ -DPKGLIBDIR=\/fg-cvs/share/FlightGear\ -g -O2 -D_REENTRANT  
-L/fg-cvs/lib -L/usr/local/lib -o fgfs.exe  boot
strap.o ../../src/Main/libMain.a ../../src/Aircraft/libAircraft.a
... etc, etc, etc ...
../../src/Environment/libEnvironment.a -lsgroute -lsgsky -lsgsound -lsgephem
-lsgmaterial -lsgtgdb -lsgmodel -lsgtiming -lsgio -lsgscreen -lsgmath
-lsgbucket -lsgprops -lsgdebug -lsgmagvar -lsgmisc -lsgnasal -lsgxml
-lsgsound -lsgserial -lsgstructure -lsgenvironment -lsgthreads

Re: [Flightgear-devel] Update: Sun

2006-07-22 Thread Mark 
After doing some cleanup the patches are ready for review and 
(hopefully) committing to cvs again.

The new versions are here:
http://www.akermann.org/fgfs/halos.tgz
http://www.akermann.org/fgfs/flightgear-sun-2006072201.tgz
http://www.akermann.org/fgfs/simgear-sun-2006072201.tgz

I tried to do some changes on the halo-texture but there was no 
difference, so I'll leave the old one in the package for now.
The code was cleaned and polished and I must admit it wasn't very 
consistent.
Since there are many people involved in this project it's necessary to 
keep to certain conventions.-)
I didn't touch the vector calculations as Vassilii suggested though.

OK, still awaiting comments and suggestions,

Mark

BTW: Is it better to have one big file with all diffs concatenated or to 
provide a file for every file changed?



Melchior FRANZ wrote:
 * Mark -- Thursday 20 July 2006 20:31:
   
 After it is in cvs I'd be happy for some feedback and suggestions for 
 improvement.
 

 Here's some already, mostly formal problems. (I'm the pedant here.)
 The important aspects seem to be OK.


   fgGetNode(/environment)); 

 ... in a constructor. Although the existence of the /environment is
 pretty much guaranteed, we still make sure that the node gets created:

   fgGetNode(/environment, true));
 


 --
 consistency:

 +SGPath ihalopath = path , ohalopath=path;

 Now, what is it? spaces around '=' (good) or not? Space in front of
 comma operator?

 +i_halo_color[0] = 1- (1.1* red_scat_f);
 +o_halo_color[0] = 1- (1.4* red_scat_f);

 Operators sticking on numbers at several places. Either spaces around
 operators (good IMHO) or not. Or is they kind of unary operators?  :-}


 --


 indentation:

 +ohalo-setCallback( SSG_CALLBACK_PREDRAW, sgSunHaloPreDraw );
 +ohalo-setCallback( SSG_CALLBACK_POSTDRAW, sgSunHaloPostDraw );
 +
 +   sun_transform-addKid( ohalo );
 +   sun_transform-addKid( ihalo );

 What about aligning those correctly?


 --


 +  if ( env_node ){
 +  env_node-setDoubleValue(atmosphere/altitude-troposphere-top,r_tropo 
 - r_earth);
 +  env_node-setDoubleValue(atmosphere/altitude-half-to-sun, alt_half);
 +  }

 Umm ... what about indenting that correctly?
 Yes, I know, the existing code isn't consistent either. But that's no
 reason to make the situation worse.

 m.

 -
 Take Surveys. Earn Cash. Influence the Future of IT
 Join SourceForge.net's Techsay panel and you'll get the chance to share your
 opinions on IT  business topics through brief surveys -- and earn cash
 http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
 ___
 Flightgear-devel mailing list
 Flightgear-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/flightgear-devel
   

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] OT: D-EENE

2006-07-22 Thread Georg Vollnhals 

 Getting one with me in the pilot's seat is difficult, but I hope this
 one is sufficient to serve as a proof  ;-)

   http://foxtrot.mgras.net/bitmap/FGFS/DEEQA-EDNY.jpg

 Thanks to Ingrid Scholl for handing the photo to me,
   Martin.
   

Hi Martin,
thank you for the picture, now I have an idea how you are looking
- and I like that! :-)
Regards
Georg

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Cygwin CVS compile error

2006-07-22 Thread Georg Vollnhals 
Geoff Air schrieb:
 Hi,

 In a Windows XP machine, running cygwin, latest
 CVS for simgear and flightgear
 I am getting the SAME or SIMILAR error when
 linking FlightGear ... well actually when
 linking fgjs.exe, under cygwin ... namely -

   
Hi Geoff,

thank you for all this feedback, but after trying a *lot* of hours to 
get this error solved I now get another strange one.
I actually have no more time as I tried for days reinstalling, changing 
and recompiling, therefore I now stay with the last working versions I have.

Hopefully Fred and Matthias will give us new precompiled versions on 
ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 (down at the moment) from 
time to time!

Regards
Georg HeliFlyer EDDW

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear source

2006-07-22 Thread Curtis L. Olson 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-16_06:30:33 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx

- complain about attempts to attach a listener to a tied node
- do *not* complain about a listener writing to its own node, but don't
  enter recursion either


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-16_06:48:22 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx

... but then again: it's only a rumor that listeners on tied properties
don't work. And like most rumors, it's untrue. So just output a debug
message.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-17_12:58:53 (ehofman)
/var/cvs/FlightGear-0.9/source/configure.ac
/var/cvs/FlightGear-0.9/source/src/Cockpit/cockpit.cxx
/var/cvs/FlightGear-0.9/source/src/Cockpit/hud_ladr.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_ladder.cxx
/var/cvs/FlightGear-0.9/source/src/Main/fg_init.cxx

Use one standard define for enableing of the Special Purpose FDM code.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-17_13:14:31 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Systems/pitot.cxx
/var/cvs/FlightGear-0.9/source/src/Systems/pitot.hxx

only consider positive airspeed in longitudinal axis


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-17_15:22:45 (ehofman)
/var/cvs/FlightGear-0.9/source/configure.ac

Somehow this test stopped working on my PC. At least the new solution should 
work for ages.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-18_16:35:11 (curt)
/var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx

- Code cleanups.
- Fix a warning about class member initialization order.
- Clear up a problem with the default autopilot behavior on the back side
  of an ILS in preparation for adding a real back course approach mode.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-19_14:46:53 (andy)
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.cxx
/var/cvs/FlightGear-0.9/source/src/Scripting/NasalSys.hxx

Rework the naModLock()/naModUnlock() semantics to be more
maintainable.  The rules are simple (extension functions are called
*with* the lock, which must be dropped before calling naCall(), which
grabs it) but the tracking of when the lock was held was getting a
little confused.  Keep a nasal call depth count in the subsystem to
figure out whether we are making a sub-call and thus hold the lock.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-19_22:43:07 (curt)
/var/cvs/FlightGear-0.9/source/src/Main/main.cxx

Always check for if glPointParameterIsSupported, even if we haven't asked
for point light distance attenuation, because we may want to toggle this
on via the rendering options gui.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-19_22:47:39 (curt)
/var/cvs/FlightGear-0.9/source/src/Main/renderer.cxx

Add a configuration property to turn on/off the use of point sprites.

Generally you want point sprites for performance reasons when enhanced runway
lighting (and smooth points) are activated.  Most hardware doesn't
accelerate the rendering of standard smooth points, so without point sprites
you will kill your night time performance if you turn on enhanced runway
lighting.

Note that enhanced runway lighting breaks our clever scheme to make the
runway lighting brightness vary with the relative view angle.  This means
with enhanced lighting on, all lights are equally bright no matter what
direction you view them from.  So perpendicular runways are just as bright
as runways you are directly lined up with (when enhanced runway lighthing
is activated.)

You can revert to the original lighting scheme by turning off enhance runway
lights, turning off distance-attenuation, and turning off point-sprites in
the rendering options menu.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-21_10:48:57 (curt)
/var/cvs/FlightGear-0.9/source/src/Main/renderer.cxx

Small tweaks to point lighting configuration to better control the appearance
of approach rabbits.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-21_14:37:04 (curt)
/var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/navradio.hxx

Add support for a back-course mode.  Nothing changes visualy, but this
reverses the autopilot helpers so that the FD/AP can properly fly a BC appr.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-22_03:00:56 (mfranz)
/var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD.hxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_instrument.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/HUD_misc.cxx
/var/cvs/FlightGear-0.9/source/src/Instrumentation/HUD/Makefile.am

add MIL-STD-1787B Aiming

[Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data

2006-07-22 Thread Curtis L. Olson 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-16_15:51:55 (mfranz)
/var/cvs/FlightGear-0.9/data/Aircraft/bo105/Instruments/tach/tach.xml

allow 140% for rotor and turbine RPM


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-20_09:30:03 (curt)
/var/cvs/FlightGear-0.9/data/gui/dialogs/rendering.xml

Add an option to toggle point sprites on/off for runway lighting.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-20_09:31:25 (curt)
/var/cvs/FlightGear-0.9/data/preferences.xml

Default to turning point sprites on for runway lighting.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-20_12:52:55 (mfranz)
/var/cvs/FlightGear-0.9/data/Nasal/gui.nas

fix indentation


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-21_13:21:34 (mfranz)
/var/cvs/FlightGear-0.9/data/Docs/README.hud

first fragment of a README for the new HUD  ... to be continued


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-21_18:31:30 (curt)
/var/cvs/FlightGear-0.9/data/Aircraft/Citation-Bravo/Citation-autopilot-curt.xml

More autopilot tweaks and tuning.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-21_18:32:15 (curt)
/var/cvs/FlightGear-0.9/data/Aircraft/Citation-Bravo/Nasal/kfc-200-curt.nas

Added approach and back course modes.


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-22_03:00:59 (mfranz)
/var/cvs/FlightGear-0.9/data/Docs/README.hud

add MIL-STD-1787B Aiming Reticle (stadiametric; TODO: standby)


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
2006-07-22_16:02:49 (mfranz)
/var/cvs/FlightGear-0.9/data/Docs/README.hud

diameter is now an input channel (and thus changeable at runtime)


2f585eeea02e2c79d7b1d8c4963bae2d

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT  business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel