RE: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: data/Data/AI
Martin Spott wrote [...] Did you manage to take off? With a BO105 it's pretty easy, it is feasible with the C172 but for the TSR-2 the strip is too short. I was too lazy to shift the starting position to the beginning of the 'runway', otherwise it _might_ have worked out. So I crashed into the sea I don't know. Mathias provides you with a perfectly good carrier-capable aircraft, and you use every other kind ... :-) Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: data/Data/AI
Vivian Meazza wrote: I don't know. Mathias provides you with a perfectly good carrier-capable aircraft, and you use every other kind ... :-) Well, I'm doing everything in small steps: On the Octane it is a larger undertaking to rebuild FlightGear and after I've finished I'd like to know where I made the mistakes :-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Nasal
On Thursday 18 November 2004 01:33, Boris Koenig wrote: sure, right - but putting nasal scripts into module tags like in other PropertyList encoded XML files isn't yet supported natively. Also, I don't think Vance wanted to link the Nasal script to a particular action ? I don't want to lecture Vance about how he should go about doing the InHG to mBar conversion, but I think that his Nasal script should _only_ be executed when the altimeter setting is changed. IMHO it would be simpler to use the scale tag. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Nasal
Roy Vegard Ovesen wrote: On Thursday 18 November 2004 01:33, Boris Koenig wrote: sure, right - but putting nasal scripts into module tags like in other PropertyList encoded XML files isn't yet supported natively. Also, I don't think Vance wanted to link the Nasal script to a particular action ? I don't want to lecture Vance about how he should go about doing the InHG to mBar conversion, but I think that his Nasal script should _only_ be executed when the altimeter setting is changed. IMHO it would be simpler to use the scale tag. Sounds indeed very reasonable and less complicated if the conversion is the only thing he needs to be done. --- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] TaxiDraw-0.2.3 released
David Luff wrote: On 11/17/04 at 6:09 PM Martin Spott wrote: ftp://ftp.uni-duisburg.de/FlightGear/Devel/taxidraw-0.2.3-IRIX.bz2 Thanks, I've updated the link to it. Err, while you're at it: ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-SolSparc.bz2 and ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-IRIX.bz2 I kept symlinks to 'Devel/' for compatibility, martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Nasal
Roy, I didn't think of using the scale tag; I'll take that route for the mBar conversion. Thanks, Vance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Roy Vegard Ovesen Sent: Thursday, November 18, 2004 5:31 AM To: [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Nasal On Thursday 18 November 2004 01:33, Boris Koenig wrote: sure, right - but putting nasal scripts into module tags like in other PropertyList encoded XML files isn't yet supported natively. Also, I don't think Vance wanted to link the Nasal script to a particular action ? I don't want to lecture Vance about how he should go about doing the InHG to mBar conversion, but I think that his Nasal script should _only_ be executed when the altimeter setting is changed. IMHO it would be simpler to use the scale tag. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] TaxiDraw-0.2.3 released
Martin Spott wrote: ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-SolSparc.bz2 I forgot: Needs SMCxpm, SMClpng, SMCjpeg, SMCliconv and GCC runtime (The Usual Suspects). Maybe I'll create another binary with static libs, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Nasal
Here's a snippet of code to convert the inhg property value to mbar and then use this to rotate the left-most digit on the mbar display. The code doesn't seem to work; Is this the correct usage of the scale tag? I can't find an example of its use for a 3D cockpit. animation typetextranslate/type object-namemb_digit_4/object-name property/instrumentation/altimeter/setting-inhg/property scale33.86/scale factor.0001/factor step1000/step !--scroll20/scroll-- axis x0/x y1/y z0/z /axis /animation Thanks again, Vance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boris Koenig Sent: Thursday, November 18, 2004 8:27 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Nasal Roy Vegard Ovesen wrote: On Thursday 18 November 2004 01:33, Boris Koenig wrote: sure, right - but putting nasal scripts into module tags like in other PropertyList encoded XML files isn't yet supported natively. Also, I don't think Vance wanted to link the Nasal script to a particular action ? I don't want to lecture Vance about how he should go about doing the InHG to mBar conversion, but I think that his Nasal script should _only_ be executed when the altimeter setting is changed. IMHO it would be simpler to use the scale tag. Sounds indeed very reasonable and less complicated if the conversion is the only thing he needs to be done. --- Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [OT] Keyhole
The Ultimate Interface to the Planet: http://www.keyhole.com/ Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] TaxiDraw-0.2.3 released
Martin Spott wrote: Err, while you're at it: ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-SolSparc.bz2 ftp://ftp.uni-duisburg.de/FlightGear/TaxiDraw/taxidraw-0.2.3-FreeBSD.bz2 For FreeBSD-5.x. Needs from the FreeBSD Ports Collection: libiconv, wxgtk-2.4, gtk-1.2, glib-1.2, png, jpeg, tiff Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear on FreeBSD; how to deal with 'configure' ?
Martin Spott wrote: This is what I get (config.log): configure:8351: gcc -march=pentiumpro -o conftest -mfpmath=sse -fomit-frame-pointer -ffast-math -O3 -D_REENTRANT -I/usr/local/include -I/opt/FlightGear/include -I/usr/X11R6/include -L/usr/local/lib -s -L/opt/FlightGear/lib -L/usr/X11R6/lib conftest.c -lopenal -lm /opt/FlightGear/lib/libopenal.so: undefined reference to `pthread_create' [...] I managed to override this by adding a flag into 'configure': rm -f conftest.err conftest.$ac_objext \ conftest$ac_exeext conftest.$ac_ext if test $ac_cv_search_alGenBuffers = no; then for ac_lib in openal; do LIBS=-l$ac_lib -lpthread $ac_func_search_save_LIBS ^ cat conftest.$ac_ext _ACEOF /* confdefs.h. */ _ACEOF cat confdefs.h conftest.$ac_ext cat conftest.$ac_ext _ACEOF /* end confdefs.h. */ To 'do it right' (TM) I thought I'd pick the corresponding place in 'configure.ac': *) dnl default unix style machines AC_SEARCH_LIBS(alGenBuffers, openal) LIBS=$LIBS -lpthread ^ OPENAL_OK=$ac_cv_search_alGenBuffers ;; but apparently this is not the correct place, at least it doesn't get transferred over to 'configure' during automake/autoconf. Where do I add the desired flag ? Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Nasal
Roy Vegard Ovesen wrote: On Thursday 18 November 2004 16:53, Vance Souders wrote: I wish I had a clue about how to add text chunks to the 3d animation code :-| What exactly do you want to do ? Do you want to animate text ? If you only want to add text layers, then there are numerous examples in the instrument files - e.g. the ADF panel is a good example. Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Nasal
Roy Vegard Ovesen wrote: On Thursday 18 November 2004 16:53, Vance Souders wrote: Here's a snippet of code to convert the inhg property value to mbar and then use this to rotate the left-most digit on the mbar display. The code doesn't seem to work; Is this the correct usage of the scale tag? I can't find an example of its use for a 3D cockpit. animation typetextranslate/type object-namemb_digit_4/object-name property/instrumentation/altimeter/setting-inhg/property scale33.86/scale factor.0001/factor step1000/step !--scroll20/scroll-- axis x0/x y1/y z0/z /axis /animation Thanks again, Vance Hmmm... I guess that the factor tag does the same for 3d as the scale tag does for 2d, so you should put 33.86 inside the factor tag, and remove the scale tag completely. But I'm not sure about this. I wish I had a clue about how to add text chunks to the 3d animation code :-| Here's another way of doing it: data/Aircraft/Spitfire/Models/boost.xml. The data between the interpolate and /interpolate tags converts inHg to psi and changes the output from absolute to gauge. You need to work out the factors involved by hand though. Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Small patches ...
Hi Erik,
I think we can go there step by step. And I have several additional patches
floating around here which might be worth anyway.
ai-jump-fix.diff:
The moving ai models will jump around realtive to the moving aircraft model.
I can see that with the carrier but others have noticed that too with ai
aircraft before.
The reason is that all SGSystems are called with a dt value which is not
necessarily a multiple of 1/hz.
In contrast, most FDM's use the _calc_multiloop function from FGInterface
which forces the time update to be a multiple of 1/hz for the FDM aircraft.
As a result, in the worst case, the FDM aircraft has moved nearly 1/hz seconds
further than the rest of flightgear (1/120sec*300kts that is about 1.3m).
That patch forces the time update to be a multiple of 1/hz.
carrier-controls.diff:
Add some controls required for carrier operations:
/controls/gear/launchbar
should be 1.0 if the launchbar is lowered, that means the aircraft should now
be arrested at the catapult.
/controls/gear/catapult-launch-cmd
Should be set to 1.0 when the aircraft should be launched from tha catapult.
Erik, could you please apply these?
Thanks!
Greetings
Mathias
--
Mathias Frhlich, email: [EMAIL PROTECTED]
Index: src/AIModel/AIBase.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/AIModel/AIBase.cxx,v
retrieving revision 1.31
diff -u -r1.31 AIBase.cxx
--- src/AIModel/AIBase.cxx 16 Nov 2004 09:33:21 - 1.31
+++ src/AIModel/AIBase.cxx 18 Nov 2004 17:12:09 -
@@ -78,8 +78,8 @@
}
void FGAIBase::update(double dt) {
-ft_per_deg_lat = 366468.96 - 3717.12 * cos(pos.lat()/SG_RADIANS_TO_DEGREES);
-ft_per_deg_lon = 365228.16 * cos(pos.lat() / SG_RADIANS_TO_DEGREES);
+ft_per_deg_lat = 366468.96 - 3717.12 * cos(pos.lat()*SGD_DEGREES_TO_RADIANS);
+ft_per_deg_lon = 365228.16 * cos(pos.lat()*SGD_DEGREES_TO_RADIANS);
// Calculate rho at altitude, using standard atmosphere
// For the temperature T and the pressure p,
Index: src/AIModel/AIShip.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/AIModel/AIShip.cxx,v
retrieving revision 1.11
diff -u -r1.11 AIShip.cxx
--- src/AIModel/AIShip.cxx 16 Nov 2004 19:48:09 - 1.11
+++ src/AIModel/AIShip.cxx 18 Nov 2004 17:12:09 -
@@ -84,9 +84,9 @@
}
// convert speed to degrees per second
- speed_north_deg_sec = cos( hdg / SG_RADIANS_TO_DEGREES )
+ speed_north_deg_sec = cos( hdg / SGD_RADIANS_TO_DEGREES )
* speed * 1.686 / ft_per_deg_lat;
- speed_east_deg_sec = sin( hdg / SG_RADIANS_TO_DEGREES )
+ speed_east_deg_sec = sin( hdg / SGD_RADIANS_TO_DEGREES )
* speed * 1.686 / ft_per_deg_lon;
// set new position
Index: src/Main/main.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Main/main.cxx,v
retrieving revision 1.186
diff -u -r1.186 main.cxx
--- src/Main/main.cxx 20 Oct 2004 08:18:29 - 1.186
+++ src/Main/main.cxx 18 Nov 2004 17:12:16 -
@@ -240,6 +240,22 @@
real_delta_time_sec
= double(current_time_stamp - last_time_stamp) / 100.0;
+// round the real time down to a multiple of 1/model-hz.
+// this way all systems are updated the _same_ amount of dt.
+{
+ static double rem = 0.0;
+ real_delta_time_sec += rem;
+ double hz = fgGetInt(/sim/model-hz);
+ double nit = floor(real_delta_time_sec*hz);
+ rem = real_delta_time_sec - nit/hz;
+ real_delta_time_sec = nit/hz;
+ // Finally fool the _calc_multiloop function in FGInterface.
+ // That is, avoid roundoff problems by adding the roundoff itself.
+ // ... ok, two times the roundoff to have enough room for two operations.
+ real_delta_time_sec *= 1.0 + 2.0*DBL_EPSILON;
+}
+
+
if ( clock_freeze-getBoolValue() ) {
delta_time_sec = 0;
} else {
Index: src/Controls/controls.cxx
===
RCS file: /var/cvs/FlightGear-0.9/source/src/Controls/controls.cxx,v
retrieving revision 1.12
diff -u -r1.12 controls.cxx
--- src/Controls/controls.cxx 10 Sep 2004 17:53:34 - 1.12
+++ src/Controls/controls.cxx 18 Nov 2004 17:12:10 -
@@ -81,6 +81,8 @@
gear_down( true ),
antiskid( true ),
tailhook( false ),
+launchbar( false ),
+catapult_launch_cmd( false ),
tailwheel_lock( false ),
wing_heat( false ),
pitot_heat( true ),
@@ -157,6 +159,8 @@
steering = 0.0;
gear_down = true;
tailhook = false;
+launchbar = false;
+catapult_launch_cmd = false;
tailwheel_lock = false;
set_carb_heat( ALL_ENGINES, false );
set_inlet_heat( ALL_ENGINES, false );
@@ -468,6 +473,14 @@
FGControls::get_tailhook, FGControls::set_tailhook);
fgSetArchivable(/controls/gear/tailhook);
+
Re: [Flightgear-devel] Re: FlightGear on FreeBSD; how to deal with
Erik Hofman wrote:
Martin Spott wrote:
but apparently this is not the correct place, at least it doesn't
get transferred over to 'configure' during automake/autoconf. Where do
I add the desired flag ?
Take a look at FlightGear's configure.ac. It should have a special
section for FreeBSD plib support.
The OpenAL check already happens in SimGear - this is the place where
it doesn't work. I tried several things, including removal of the
whole FreeBSD -lpthread cheat clause, but I still didn't succeed.
So I'll stick to the manual 'correction' until I understand - at least
partially - how automake/autoconf works. This might take some time :-)
Besides this, I had to make some very small changes. One of them is in
Simgear - please don't ask me _why_, I just can tell you that it makes
the whole thing work ;-)
--- simgear/screen/extensions.cxx~ Thu Nov 4 16:14:59 2004
+++ simgear/screen/extensions.cxx Thu Nov 18 17:52:25 2004
@@ -113,7 +113,7 @@
if (libHandle != NULL) {
fptr = dlsym(libHandle, func);
-char *error = dlerror();
+const char *error = dlerror();
if (error)
SG_LOG(SG_GENERAL, SG_INFO, error);
}
Adding to that, FreeBSD-5.x, at least 5.3 appears to have a modified
joystick interface. For every occurrence of '-lplibjs' I had to add
'-lusbhid'. This is the case for src/Input/js_demo, src/Input/fgjs,
src/Main/fgfs and utils/js_server/js_server
Curt, you can add FreeBSD-5.3 to the list of supported platforms :-)
It is not _that_ fast as recent tests with XOrg CVS on SuSE-9.0 but
this might simply be related to the not that upt-to-date XOrg release
that comes with FreeBSD-5.3,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on FreeBSD; how to deal with 'configure' ?
Erik Hofman wrote: Take a look at FlightGear's configure.ac. It should have a special section for FreeBSD plib support. Eh, make that pthreads support. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SimGear configure.ac
I believe, there is an unintentional line wrap in configure.ac: --- configure.ac~ Thu Oct 21 14:19:05 2004 +++ configure.acThu Nov 18 20:06:32 2004 @@ -185,7 +185,7 @@ CFLAGS=$save_CFLAGS else dnl This is cheating a bit. pthread_exit comes with using -pthread, not --lpthread +dnl -lpthread ac_cv_lib_pthread_pthread_exit=yes fi LIBS=$save_LIBS Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on FreeBSD; how to deal with
Martin Spott wrote: The OpenAL check already happens in SimGear - this is the place where it doesn't work. I tried several things, including removal of the whole FreeBSD -lpthread cheat clause, but I still didn't succeed. So I'll stick to the manual 'correction' until I understand - at least partially - how automake/autoconf works. This might take some time :-) This change would serve FreeBSD. Does it make any sense, does it break other platforms ? --- configure.ac.original Thu Oct 21 14:19:05 2004 +++ configure.acThu Nov 18 20:13:07 2004 @@ -167,8 +167,8 @@ AC_CHECK_HEADER(pthread.h) AC_CHECK_LIB(pthread, pthread_exit) if test x$ac_cv_lib_pthread_pthread_exit = xyes -a x$ac_cv_header_pthread_h = xyes; then -CXXFLAGS=$CXXFLAGS -D_REENTRANT -CFLAGS=$CFLAGS -D_REENTRANT +CXXFLAGS=$CXXFLAGS -D_REENTRANT -lpthread +CFLAGS=$CFLAGS -D_REENTRANT -lpthread fi if test x$ac_cv_lib_pthread_pthread_exit != xyes -a x$ac_cv_header_pthread_h = xyes; then dnl FreeBSD: System has pthread.h, but -lpthread library check Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] SimGear configure.ac
Martin Spott wrote: I believe, there is an unintentional line wrap in configure.ac: --- configure.ac~ Thu Oct 21 14:19:05 2004 +++ configure.ac Thu Nov 18 20:06:32 2004 @@ -185,7 +185,7 @@ CFLAGS=$save_CFLAGS else dnl This is cheating a bit. pthread_exit comes with using -pthread, not --lpthread +dnl -lpthread ac_cv_lib_pthread_pthread_exit=yes fi LIBS=$save_LIBS Ok, fixed ... 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 [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: data/Data/AI
On Thursday 18 November 2004 08:01, Vivian Meazza wrote: Martin Spott wrote [...] Did you manage to take off? With a BO105 it's pretty easy, it is feasible with the C172 but for the TSR-2 the strip is too short. I was too lazy to shift the starting position to the beginning of the 'runway', otherwise it _might_ have worked out. So I crashed into the sea I don't know. Mathias provides you with a perfectly good carrier-capable aircraft, and you use every other kind ... :-) Regards, Vivian :) um, yes - the TSR-2 probably isn't the best a/c for carrier stuff. The FDM needs really an overhaul because the take-off performance isn't right - it currently lifts off at a lower speed if reheat isn't used :( - and it was designed to have a good stol performance, albeit with extending nose-gear to increase the AoA. The current FDM is pretty poor in this respect. LeeE ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear ATC problem
Adam submitted a patch to simgear/compiler.h which #defines the include location of gl.h, glut.h, and glu.h along with patched files that eliminate direct references and #include the #defined symbol instead. This change propogates through simgear and flightgear and depricates the FG_GLUT_H symbol in the FlightGear configure.ac script. The changes should now all be in CVS. You will need to cvs update both SimGear and FlightGear. This change allows a clean build [hopefully] :-) on OSX and should affect any other platform. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d Adam Dershowitz wrote: Here is the list of files, just to help with the paths: SimGear: Index: simgear/compiler.h Index: simgear/scene/material/matlib.cxx Index: simgear/scene/sky/dome.cxx Index: simgear/scene/sky/clouds3d/SkyCloud.cpp Index: simgear/scene/sky/clouds3d/SkyDynamicTextureManager.hpp Index: simgear/scene/sky/clouds3d/SkyLight.cpp Index: simgear/scene/sky/clouds3d/SkyMaterial.hpp Index: simgear/scene/sky/clouds3d/SkyMinMaxBox.cpp Index: simgear/scene/sky/clouds3d/SkyRenderableInstanceCloud.cpp Index: simgear/scene/sky/clouds3d/SkyRenderableInstanceGroup.cpp Index: simgear/scene/sky/clouds3d/SkyTexture.hpp Index: simgear/scene/sky/clouds3d/SkyTextureManager.cpp Index: simgear/scene/sky/clouds3d/glut_shapes.c Index: simgear/scene/sky/clouds3d/glut_shapes.h Index: simgear/screen/GLBitmaps.cxx Index: simgear/screen/extensions.hxx Index: simgear/screen/screen-dump.cxx Index: simgear/screen/screen-dump.hxx Index: simgear/screen/texture.cxx Index: simgear/screen/texture.hxx Index: simgear/screen/tr.cxx Index: simgear/screen/tr.h Index: simgear/xgl/xgl.h FlightGear files Index: src/ATC/ATCdisplay.cxx Index: src/Cockpit/cockpit.cxx Index: src/Cockpit/hud.cxx Index: src/Cockpit/panel.cxx Index: src/GUI/gui_funcs.cxx Index: src/GUI/layout-test.cxx Index: src/Main/fg_os.cxx Index: src/Main/splash.cxx Index: src/Network/ATC-Inputs.cxx Index: src/Time/light.cxx Index: src/Time/light.hxx Index: utils/Modeller/3dconvert.cxx By the way this list includes the version of ATC-Inputs.cxx with the includes that you suggested, rather than just commented out code, so that it should work properly. Thanks for taking care of this. It will be nice to be able to build on a Mac from src with no changes. Please let me, and the developer list, know when you have made these changes in CVS. Thanks, -- Adam ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Nasal
I have 4 3d quads that represent the 4 digits of a millibar display embedded in a 3D altimeter. I need to read inches HG from the property system, convert it to mbar and then use that as a texture translation offset for the quad digits. There are lots of examples for 2D gauges, but none for 3D gauges. Here's a portion of the code that drives the HG portion of the altimeter (This works fine). !-- inches HG display -- animation typetextranslate/type object-namehg_digit_4/object-name property/instrumentation/altimeter/setting-inhg/property factor0.01/factor step10/step !--scroll20/scroll-- axis x0/x y1/y z0/z /axis /animation animation typetextranslate/type object-namehg_digit_3/object-name property/instrumentation/altimeter/setting-inhg/property factor0.1/factor step1/step !--scroll20/scroll-- axis x0/x y1/y z0/z /axis /animation Works fine. Here's a bit of the code for the mbar digits (note that the conversion factor is multiplied into the factor (.001 * 33.6)): animation typetextranslate/type object-namemb_digit_3/object-name property/instrumentation/altimeter/setting-inhg/property factor0.0336/factor step100/step scroll20/scroll axis x0/x y1/y z0/z /axis /animation This doesn't work one bit. I initially thought, no problem, I'll embed some nasal into the altimeter's xml file but that isn't supported. I want to make the T6's cockpit fully functional so any suggestions are welcome. Thanks, Vance -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boris Koenig Sent: Thursday, November 18, 2004 11:59 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Nasal Roy Vegard Ovesen wrote: On Thursday 18 November 2004 16:53, Vance Souders wrote: I wish I had a clue about how to add text chunks to the 3d animation code :-| What exactly do you want to do ? Do you want to animate text ? If you only want to add text layers, then there are numerous examples in the instrument files - e.g. the ADF panel is a good example. Boris ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear ATC problem
The changes should now all be in CVS. You will need to cvs update both SimGear and FlightGear. This change allows a clean build [hopefully] :-) on OSX and should affect any other platform. the flightgear tests directory build is broken on mac os x (10.3.6) Making all in tests source='est-epsilon.c' object='est-epsilon.o' libtool=no \ depfile='.deps/est-epsilon.Po' tmpdepfile='.deps/est-epsilon.TPo' \ depmode=gcc3 /bin/sh ../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../src/Include -I/Users/ima/Desktop/FlightGear/fgdev9.6/include -g -O2 -D_REENTRANT -c `test -f 'est-epsilon.c' || echo './'`est-epsilon.c est-epsilon.c:13:19: OpenGL/glut.h: No such file or directory est-epsilon.c: In function `main': est-epsilon.c:17: error: `GLfloat' undeclared (first use in this function) est-epsilon.c:17: error: (Each undeclared identifier is reported only once est-epsilon.c:17: error: for each function it appears in.) est-epsilon.c:17: error: parse error before a est-epsilon.c:19: error: `a' undeclared (first use in this function) est-epsilon.c:24: error: `t' undeclared (first use in this function) make[1]: *** [est-epsilon.o] Error 1 a workaround is to skip the tests by building from the makefile in src/flightgear/src. The fix is to modify compiler.h in simgear to contain: # define SG_GLUT_H GLUT/glut.h for __APPLE__ glut.h is in the GLUT.framework on mac os x, not the opengl.framework. The other apple specific ones are OK. Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
