[Flightgear-devel] need assistance with /sim/startup/browser-app and debugging property system values please (Help problem)
Warning: long append
The problem with help on mac os x (possibly other platforms) --
http://mail.flightgear.org/pipermail/flightgear-devel/2005-November/
040462.html -- is still occurring.
somehow something is switching /sim/startup/browser-app from open
after it is set in Main/options.cxx, but before options are processed
from the command line
(help works if I start fgfs with --browser-app=open)
I am using the following arguments to fgfs to generate a log to
examine the problem:
--log-level=info --trace-write=/sim/startup/browser-app --trace-read=/
sim/startup/browser-app
Using grep on the source tree, I see the following /browser strings:
[/src/fgdev9.9] ima% find . -name '*.[ch]xx' -print | xargs grep $1 /
dev/null
./src/FlightGear/src/GUI/gui_funcs.cxx:string help_app =
fgGetString(/sim/startup/browser-app);
./src/FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, webrun.bat);
./src/FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, open);
./src/FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, launchWebJumper);
./src/FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, envp);
./src/FlightGear/src/Main/options.cxx:// SG_LOG( SG_GENERAL,
SG_INFO, help app is fgGetString( /sim/startup/browser-app ) );
./src/FlightGear/src/Main/options.cxx: SG_LOG( SG_GENERAL,
SG_ALERT, help app is fgGetString( /sim/startup/browser-
app ) );
./src/FlightGear/src/Main/options.cxx:{browser-
app, true, OPTION_STRING, /sim/startup/browser-
app, false, , 0 },
The tracing functions aren't seeing ANY changes to /sim/startup/
browser-app (from the log I guess they start after
/sim/startup/browser-app is set in Main/options.cxx, but these
functions are not seeing any changes after they start
either.)
By the time the app is up and running and I select Help from the Help
menu, the value has been changed
(it should be open on mac os x, but is netscape which is not
installed on the system).
Does anyone have any suggestions on how to explore the problem in gdb
to see what is going on? Where is a value like /sim/startup/browser-
app stored in memory
in a running copy of fgfs? Any suggestions on which property
functions to look at?
Thank you
Ima
A partial runtime log follows (help information lines prepended by
*** )
Using Mac OS X hack for initializing C++ stdio...
*** help app is open
*** Tracing writes for property /sim/startup/browser-app
*** Tracing reads for property /sim/startup/browser-app
Finished command line arguments
Initializing splash screen
ATI Radeon 7500 OpenGL Engine
Max texture size = 2048
Depth buffer bits = 16
Loading Airport Database ...
Data file version = 715
[FINISHED LOADING]
Loading Navaid Databases
opening file: /src/fgdev9.9/data/Navaids/carrier_nav.dat
opening file: /src/fgdev9.9/data/Navaids/TACAN_freq.dat
Standardising rwy number from B to 0B
Fixes
Attempting to set starting position for KDCA:33
runway = -77.0383, 38.856 length = 1585.26 heading = 142.76
Position for KDCA is (-77.0328, 38.8504) new heading is 322.76
Searching for airport code = KDCA
Position for KDCA is (-77.0398, 38.8515)
Initializing Time
Current greenwich mean time = Sat Dec 17 11:19:54 2005
Current local time = Sat Dec 17 06:19:54 2005
Reading timezone info from: /src/fgdev9.9/data/Timezone/zone.tab
Using zonename = /src/fgdev9.9/data/Timezone/America/New_York
First time, doing precise gst
snip
Initializing environment subsystem
2005/12/17 10:51
KDCA 171051Z 35003KT 10SM OVC250 01/M04 A3041 RMK AO2 SLP296 T00061039
METAR from weather.noaa.gov
closest station w/ metar = KDCA
WIND: [EMAIL PROTECTED] knots
Altitude = 15
Temp at alt (C) = 1
Temp sea level (C) = 1.02786
Altitude = 15
Dewpoint at alt (C) = -4
Dewpoint at sea level (C) = -3.997
Initializing Lighting interpolation tables.
Initializing Interpolator for /src/fgdev9.9/data/Lighting/ambient
Initializing Interpolator for /src/fgdev9.9/data/Lighting/diffuse
Initializing Interpolator for /src/fgdev9.9/data/Lighting/specular
Initializing Interpolator for /src/fgdev9.9/data/Lighting/sky
Reading sound sound from /src/fgdev9.9/data/Aircraft/A-10/Sounds/A-10-
sound.xml
Loading sound information for: engine
Loading sound information for: whine
Loading sound information for: engine
Loading sound information for: whine
Loading sound information for: rumble
Loading sound information for: rumble
Loading sound information for: rumble
Loading sound information for: gear
Loading sound information for: gear-lock
Loading sound information for: gear-lock
Loading sound information for: gear
Loading sound information for: gear-lock
Loading sound information for: gear-lock
Loading sound information for: gear
Loading sound information for: gear-lock
Loading sound information for: gear-lock
Loading sound information for: squeal
Loading sound information for: squeal
Loading sound information
[Flightgear-devel] OT: Engineered Material Arresting Systems, or EMAS
http://cnn.netscape.cnn.com/news/story.jsp?idq=/ff/story/ 0001/20051209/1734884529.htmewp=ewp_news_1205jet_skidphotoid=20051209I LCA101floc=NW_1-T According to the above news report, Engineered Material Arresting Systems or EMAS are available on 18 runways at 14 airports with short runways (I assume they mean in the US, they mention kennedy (KJFK) specifically as having at least one). They are sometimes placed at the end of runways with no 1000 foot overrun area. Is this something that can be modeled in FlightGear? Any ideas how it could be done? (post 1.0) thanks! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] OT: picture of two USAF thuderbirds in mirror formation
Off topic, but something similar to this might make two interesting AI aircraft for around KSFO or KDCA or Nellis AFB, Nevada, USA where they're based. 8-) Best regards, Ima From netscape.com gallery: http://cdn-channels.netscape.com/gallery/i/p/popular112105/ apohcomrr_AVIATION_NATIO_1B.jpg The netscape.com/gallery caption reads: Two U.S. Air Force Thunderbirds perform a mirror formation during Aviation Nation Air Show at Nellis Air Force Base in Las Vegas on Saturday, Nov. 12, 2005. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RenderTexture::BeginCapture(): Texture is not initialized!
James, Sorry to hear you're having so much trouble. Unfortunately, everything is working for me just fine with latest CVS... opening file: /Users/arthur/Projects/FlightGearOSX/data//Navaids/ carrier_nav.dat /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat RenderTexture::BeginCapture(): Texture is not initialized! I've seen the RenderTexture::BeginCapture() message for a while but it doesn't stop fg from loading. Help is still broken, but we knew that 8-( I get sound but the sound dialog mute checkbox has no effect, but we knew that too 8-( /Users/arthur/Projects/FlightGear/../SimGear/SimGear/simgear/ threads/SGThread.hxx:233: failed assertion `status == 0' I take it you're building FlightGear --with-threads, I am too. also -- without-x My log after starting, running help, turning sound off and on and exiting is: Using Mac OS X hack for initializing C++ stdio... help app is open opening file: /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/ carrier_nav.dat /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/TACAN_freq.dat Failed to find runway 28R at airport KDCA RenderTexture::BeginCapture(): Texture is not initialized! Initialising callsign using 'Aircraft/c172p/Models/c172p.xml' Initializing Nasal Electrical System WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/ w080n30/w077n38/1l' sh: line 1: netscape: command not found FlightGear also works with --aircraft=A-10cl Using Mac OS X hack for initializing C++ stdio... help app is open opening file: /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/ carrier_nav.dat /Users/ima/Desktop/FlightGear/fgdev9.9/data/Navaids/TACAN_freq.dat Failed to find runway 28R at airport KDCA RenderTexture::BeginCapture(): Texture is not initialized! Reading xml electrical system model from /Users/ima/Desktop/ FlightGear/fgdev9.9/data/Aircraft/A-10/Systems/A-10-electrical.xml Initialising callsign using 'Aircraft/A-10/Models/A-10-model.xml' WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/ w080n30/w077n38/1l' Abort trap At first if failed right after this line: /Users/arthur/Projects/FlightGearOSX/data//Navaids/TACAN_freq.dat But then I uncompressed TACAN_freq.dat.gz and carrier_nav.dat.gz and got past that. And now it aborts with RenderTexture. As long as things go like this there'll be no Mac release anytime soon. Try a make clean in simgear and flightgear and rebuild. What version of mac os x and gcc/xcode are you using? I am on: 10.4.3, gcc -- version 4.0.1 (build 5247), xcode 2.2 (which I'm not using, I only build from the command line). I am using latest cvs for plib, simgear, and flightgear As strange as it sounds, you might try rebooting. I know, I have to do it at least 4 times a year, too! 8-) VERY frustrating grin Not at all like a certain other os I could mention. Sorry I haven't been feeling very well the last few days and haven't been paying close attention... the weather is a balmy yet humid below freezing Uggh! Just the thing for arthritis... 8-( Good luck! Thanks everyone for your work on this release which I hope to find time (and energy) to play with soon. Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] XCode project files
Please do commit them, I've had hand-rolled projects for all three for some time, but they're out of sync. If I find any issues, I'll let you know. Is it worth creating a developer directory under FlightGear CVS to contain things like these xcode project files and developer instructions for cygwin here http://www.opensubscriber.com/message/ flightgear-users@flightgear.org/2485584.html mentioned on the flightgear-user list or Norm's cygwin openal work (or at least a link to the current versions)? Maybe developer could have os-specific directories like macosx, cygwin, etc or just put everything in developer directory. These aren't utils and probably don't belong in the utils directory... but this would keep them in a standard place accessible to everyone from the source tree. It seems like we see similar problems that people are maintaining by themselves (projects (build files) for xcode and for MS visual C/C++ come to mind) thanks! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] XCode project files
This would require someone to maintain the project files. I plan on leaving the FlightGear project soon after the 0.9.9 release so wouldn't be able to. Arthur, If the project files were in cvs, then you personally wouldn't have to maintain them. Whoever needed to use them would see about updating them so that others could use their work (in a perfect world). 8-) I think it would avoid duplication of work -- i.e., multiple people each doing their own xcode file and make the work done like yours easier to find. At a minimum, maybe there could be a document pointing to the cygwin doc and your macflightgear project on sourceforge? Personally, I think in the source tree is much easier to find... Sorry to hear you're leaving after 0.9.9. Thanks for all the work you've put into flightgear! Take care! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use
Help Help from the gui on mac os x is still broken.
The help application is STILL set to netscape even after the
options.cxx change
(this is the main/options.cxx change applied to GUI/gui_funcs.cxx also).
Thanks!
Ima
Applying this patch fixes it for mac os x:
Index: FlightGear/src/GUI/gui_funcs.cxx
===
RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/GUI/gui_funcs.cxx,v
retrieving revision 1.37
diff -u -r1.37 gui_funcs.cxx
--- FlightGear/src/GUI/gui_funcs.cxx12 Nov 2005 11:40:57
- 1.37
+++ FlightGear/src/GUI/gui_funcs.cxx13 Nov 2005 11:27:54 -
@@ -237,7 +237,20 @@
#if !defined(WIN32)
-string help_app = fgGetString(/sim/startup/browser-app);
+string help_app = fgGetString(/sim/startup/browser-app);
+
+//SG_LOG( SG_GENERAL, SG_INFO, Help application -- help_app );
+SG_LOG( SG_GENERAL, SG_ALERT, Help application -- help_app );
+
+#if defined(__APPLE__)
+help_app = open;
+#elif defined(sgi)
+help_app = launchWebJumper);
+#else
+envp = ::getenv( WEBBROWSER );
+if (!envp) envp = netscape;
+fgSetString(/sim/startup/browser-app, envp);
+#endif
if ( system(xwininfo -name Netscape /dev/null 21) == 0 ) {
command = help_app + -remote \openURL( + path.str() + )
\;
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use
Vassilii,
Doesn't it mean that something resets it between the options
parsing and
the GUI help stuff processing?
probably, putting the same SG_LOG in the patch right after the set in
options.cxx, I get:
help app is open// correct
During the help call, I get:
Help application -- netscape //incorrect
I'd rather see a patch that finds
the offending code modifying it, if that's the case.
me too, but this is a workaround that would permit help to work on GM
fg9.9, which I imagine is going out soon. It only hits one function
which is used for help and all changes are only done at compile time
and should not affect other oses.
Just grepping for browser-app in fgdev9.9/src:
find . -name *.[ch]xx | xargs grep browser-app
./FlightGear/src/GUI/gui_funcs.cxx:string help_app = fgGetString
(/sim/startup/browser-app);
./FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, webrun.bat);
./FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, open);
./FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, launchWebJumper);
./FlightGear/src/Main/options.cxx:fgSetString(/sim/startup/
browser-app, envp);
./FlightGear/src/Main/options.cxx:// SG_LOG( SG_GENERAL, SG_INFO,
help app is fgGetString( /sim/startup/browser-app ) );
./FlightGear/src/Main/options.cxx: SG_LOG( SG_GENERAL, SG_ALERT,
help app is fgGetString( /sim/startup/browser-app ) );
./FlightGear/src/Main/options.cxx:{browser-
app, true, OPTION_STRING, /sim/startup/browser-
app, false, , 0 },
this is beyond my abilities 8-( I wasn't trying to blow it off,
really! 8-)
BTW: there's
an option to debug/trace every property read/write for a given
property,
sorry I can't say more right now as I am logging into my mail remotely
at this moment w/o any graphics around to test the things.
Thanks very much for your information, I would like to find out more
about this debug/trace property thing that you mention.
Best regards,
Ima
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] compiling Simgear...
I get an error now compiling Simgear . I cant cut and paste from the terminal but make stops at : [visual_enviro.o]Error 1 Has anyone run across this before? I'm not sure if your error is my error, but I saw an error in simgear's visual_enviro on mac os x (and fixed it by installing the latest openal from www.openal.org). i think I might have needed to do a make clean of simgear too, I don't remember, sorry. I have a similar problem with building SimGear under cygwin. I am unable to get a cygwin version of openal (openal_cyg.tgz of a few days ago isn't working). The error is that there's no AL/alut.h found. I have removed all old versions of openal from my system that I could find. Making install in environment make[3]: Entering directory `/cygdrive/s/flightgear/fgdev9.9/src/simgear/simgear/environment' if g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -I/cygdrive/s/flightgear/fgdev9.9/include -g -O2 -D_REENTRANT - MT visual_enviro.o -MD -MP -MF .deps/visual_enviro.Tpo -c -o visual_enviro.o visual_enviro.cxx; \ then mv -f .deps/visual_enviro.Tpo .deps/visual_enviro.Po; else rm -f .deps/visual_enviro.Tpo; exit 1; fi In file included from ../../simgear/sound/soundmgr_openal.hxx:53, from visual_enviro.cxx:33: ../../simgear/sound/sample_openal.hxx:50:22: AL/alut.h: No such file or directory visual_enviro.cxx: In member function `void SGEnviro::drawRain(double, double, double, double, double)': visual_enviro.cxx:422: warning: converting to `int' from `double' visual_enviro.cxx: In member function `void SGLightning::lt_build_tree_branch(int, Point3D, float, int, float)': visual_enviro.cxx:503: warning: passing `float' for converting 4 of `void SGLightning::lt_build_tree_branch(int, Point3D , float, int, float)' make[3]: *** [visual_enviro.o] Error 1 make[3]: Leaving directory `/cygdrive/s/flightgear/fgdev9.9/src/simgear/simgear/environment' make[2]: *** [install-recursive] Error 1 make[2]: Leaving directory `/cygdrive/s/flightgear/fgdev9.9/src/simgear/simgear' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/cygdrive/s/flightgear/fgdev9.9/src/simgear' make: *** [sginstall] Error 2 I tryed download from openal cvs (as outlined on www.openal.org), and was able to build and install the openal/linux directory correctly. However, I am getting an error building the openal/alut directory after the make install of the openal/linux directory succeeds. I get a lot of warnings from the aclocal process (shown below as there's many). Then creating libs/libalut.dll.a I get a large number of undefined references as shown here: gcc -shared .libs/libalut_la-alutBufferData.o .libs/libalut_la-alutCodec.o .libs/libalut_la-alutError.o .libs/libalut_l a-alutInit.o .libs/libalut_la-alutInputStream.o .libs/libalut_la-alutLoader.o .libs/libalut_la-alutUtil.o .libs/libalut_ la-alutVersion.o .libs/libalut_la-alutWaveform.o -o .libs/cygalut-0.dll -Wl,--enable-auto-image-base -Wl,--out-implib, .libs/libalut.dll.a Creating library file: .libs/libalut.dll.a .libs/libalut_la-alutBufferData.o: In function `_alutPassBufferData': /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutBufferData.c:119: undefined reference to `_alGenBuffers' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutBufferData.c:120: undefined reference to `_alGetError' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutBufferData.c:136: undefined reference to `_alBufferData' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutBufferData.c:139: undefined reference to `_alGetError' .libs/libalut_la-alutInit.o: In function `_alutSanityCheck': /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:27: undefined reference to `_alcGetCurrentContext' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:34: undefined reference to `_alGetError' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:40: undefined reference to `_alcGetContextsDevice' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:40: undefined reference to `_alcGetError' .libs/libalut_la-alutInit.o: In function `alutInit': /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:67: undefined reference to `_alcOpenDevice' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:74: undefined reference to `_alcCreateContext' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:82: undefined reference to `_alcMakeContextCurrent' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:84: undefined reference to `_alcDestroyContext' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:85: undefined reference to `_alcCloseDevice' /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:77: undefined reference to `_alcCloseDevice' .libs/libalut_la-alutInit.o: In function `alutExit': /cygdrive/s/flightgear/fgdev9.9/src/openal/alut/src/alutInit.c:130: undefined reference to `_alcMakeContextCurrent'
[Flightgear-devel] OT: FYI, mac os x developers, xcode 2.2 has been released
Installing the new xcode 2.2 software on mac os 10.4.3 took about 50 minutes. (During which I did a make clean 8-) of plib, simgear and flightgear) Rebuilding plib, simgear and flightgear (latest cvs around 1pm gmt) took about one hour. Running fgfs, I get an abend: OpenAL error (AL_INVALID_VALUE): constructor (alutLoadWAVFile) terminate called after throwing an instance of 'sg_exception' Abort gcc --version powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5247) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. the old gcc version was: gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) Copyright (C) 2005 Free Software Foundation, Inc. Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] cygwin FG build break latest CVS + run time error
To fix the build break you need to patch: Index: FlightGear/src/Time/sunsolver.cxx===RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Time/sunsolver.cxx,vretrieving revision 1.6diff -u -r1.6 sunsolver.cxx--- FlightGear/src/Time/sunsolver.cxx 11 Nov 2005 14:46:15 - 1.6+++ FlightGear/src/Time/sunsolver.cxx 12 Nov 2005 14:06:20 -@@ -23,6 +23,11 @@ * $Id: sunsolver.cxx,v 1.6 2005/11/11 14:46:15 ehofman Exp $ */ ++#ifdef HAVE_CONFIG_H+# include config.h+#endif+#ifdef SG_HAVE_STD_INCLUDES# include cmath// # include cstdio I am using the openal_cyg.tgz from http://www.mail-archive.com/flightgear-users@flightgear.org/msg10995.html The run time error I get is: Russian: (âÞçÚÐ ÒåÞÔÐ Ò ßàÞæÕÔãàã alutLoadWAVFile ÝÕ ÝÐÙÔÕÝÐ Ò ÑØÑÛØÞâÕÚÕ DLL openal32.dll) English: Entry point into procedure alutLoadWAVFile not found in dll library openal32.dll $ which openal32.dll/usr/local/bin/openal32.dll [EMAIL PROTECTED] /cygdrive/s/flightgear/fgdev9.9$ ls -l /usr/local/bin/openal32.dll-rwxr-xr-x 1 °ÔÜØÝØáâàÐâÞà ¾âáãâáâÒãÕâ 480468 Apr 30 2004 /usr/local/bin/openal32.dll [EMAIL PROTECTED] /cygdrive/s/flightgear/fgdev9.9$ Thank you! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use safari
Arthur and Vassilii, Even though I couldn't fix it, I'm glad I got smarter minds to think about it! 8-) OK, is there a way to get sensible-browser at compile time? Is this a link know to the OS or something? is it callable or does it need to be read on Debian somewhere? this is also wrong because "sensible-browser" should be used instead. Nice catch, not sure how to fix it though. Is there a standard path length limit? Is it queryable from some C call? Also the WIN32 section in src/GUI/gui_funcs.cxx with the 1024-long hardcoded buffers can be a crash trigger when the buffer overflows for somebody with a long enough path... OK, now I understand what you meant by just using open by itself. I didn't know you could do that, thanks! In the macflightgear binary I've been passing "--browser-app=open" to fgfs. This opens the url in the default browser. For me that's Firefox. Yes, even though I don't use xcode much (too complicated for my tiny brain 8-)), I'd like to have the projects for reference. I use the command line to make fg and run a graphical x window front end (DDD) to gdb. I don't do either very often or very well. 8-( Macflightgear is hosted on sourceforge? By the way Xcode projects you can use to build PLIB, Simgear, and FlightGear are available now. I've polished them up so they should be ready. If you're interested I'll commit them to the macflightgear cvs Actually, I can't test this (my wife is using the Mac as a telephone 8-( ), but your fix would need to go in two places: src/Main/options.cxx and src/GUI/gui_funcs.cxx (in void helpCb). I think that one might be the actual OS Application Help menu Help menu item and one the flightgear gui menu Help menu Help menu item (but I can't test this right now and could be wrong). Could you possibly do this additional patch also? I'm not sure when I'll get use of the Mac again. Then again, with arthritis I don't sleep much! 8-) Also, is it a problem that the rc to the call to start the browser isn't checked before the mkDialog call (leading to possibly inaccurate messages that the browser has been started when in fact it failed to do so) as mentioned in my previous message? Thanks for all your help and suggestions! Ima . ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Which aircraft to include in v0.9.9?
Oliver, Thank you for finding this online, I was very interested in reading it when Georg mentioned it (thanks to Georg also)! Here is the online version of this review: http://www.linux-user.de/ausgabe/2005/11/070-flightgear/ Best Regards, Oliver C. If someone needs translation into another language, you might try to translate the web page using google translation. http:// www.google.com/language_tools?hl=en The english language version is here: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Which aircraft to include in v0.9.9?
Ima Sudonim wrote: http://translate.google.com/translate?u=http%3A%2F%2Fwww.linux- user.de%2Fausgabe%2F2005%2F11%2F070-flightgear%2Flangpair=de% 7Cenhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools Oh yeah: flies are still an expensive pleasure :-) Martin. Martin, I agree, flies are still and expensive pleasure.. but delicious! 8-) I also liked the fact that google can't seem to translate Flugsimulationen, which as a non-German speaker, I can only assume means flight simulation or nuclear reactor, one of the two! grin Isn't machine translation wonderful? BabbleFish and Systran (used by Mac OS X Sherlock) is similar to google from examples I've seen. ImTranslator.com isn't too bad, but it's only free for less than 1000 words. 8-( I have a friend that used to send things to my wife and me translated from English using some online translation tool into the language we speak at home. Unfortunately, we usually couldn't understand his translations, until he actually explained what he was trying to say. But english is an ESPECIALLY ambiguous language, and machine translation (MT) gender, case endings and noun phrase/verb agreement were almost never right even on the translations that were at least semantically similar. Compared to what MT was just a few years ago, they didn't seem to do a bad job in most parts. But then again, I don't speak German! 8-) Best regards, Ima Sorry for the broken link, try: http://translate.google.com/translate?u=http://www.linux-user.de/ ausgabe/2005/11/070-flightgear/langpair=de% enhl=ensafe=offie=UTF-8oe=UTF-8prev=%2Flanguage_tools if my email program doesn't mess with it! I. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use safari
With this change, FlightGear on Mac OS X launches the mac os x Safari browser instead of netscape (w/o this change, the browser won't launch without netscape installed, and netscape isn't one of the installed mac os x browsers). thank you Ima Index: FlightGear/src/Main/options.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,v retrieving revision 1.73 diff -u -r1.73 options.cxx --- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58 - 1.73 +++ FlightGear/src/Main/options.cxx 9 Nov 2005 01:53:53 - @@ -172,7 +172,11 @@ fgSetString(/sim/control-mode, joystick); fgSetBool(/sim/auto-coordination, false); #if !defined(WIN32) +#if defined (__APPLE__) +fgSetString(/sim/startup/browser-app, safari); +#else fgSetString(/sim/startup/browser-app, netscape); +#endif #else fgSetString(/sim/startup/browser-app, webrun.bat); #endif ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use safari
Arthur and James, Yes, I agree it's silly, but currently help was broken on my two mac systems (giving a log message that netscape couldn't be found), followed by a dialog that my browser was started. It's really important to me to have browser-based help work on 0.9.9... I forgot that it was broken until now. (I know I had this working at one point, and thought I still did as I was building with a modified options.cxx. I was wrong). I promise to pay much more attention next time or at least be conscious when I try these things Unfortunately, my fix doesn't work. I think it should have been the following diff, but as neither diff is working, don't apply them to cvs please. I can't get this options.cxx change working on Mac OS X, I have to use the option --browser-app=open /Applications/Safari.app when starting flightgear. Any idea where else /sim/startup/browser-app is set or what (if anything) is overwriting it? Never mind about the cvs update. It wouldn't break anything even if applied, because it didn't work anyway. 8-( It looks like the mac browser exec actually belongs in gui/ gui_funcs.cxx. If I modify void helpCb (puObject *) (line 238) to read: string help_app = open /Applications/Safari.app ;//fgGetString (/sim/startup/browser-app); Safari starts up fine and opens help so this is the spot Arthur would need to pop his code into, I guess. It would be nice if the return code from the system call or ShellExecute could be checked before mkDialog is called. It's adding insult to injury when your browser hasn't started, but the dialog says it has 8-( I'm still a little confused as to where /sim/startup/browser-app is being set, as it doesn't seem to be in main/options.cxx as I expected. I will leave this to much wiser heads than my own. Sorry for the trouble. Some days it doesn't pay to get out of bed in the morning... 8-( I'll happily wait for arthur to fix it. Thanks to Arthur and James and all the rest... Ima Index: FlightGear/src/Main/options.cxx === RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,v retrieving revision 1.73 diff -u -r1.73 options.cxx --- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58 - 1.73 +++ FlightGear/src/Main/options.cxx 12 Nov 2005 02:41:34 - @@ -172,7 +172,11 @@ fgSetString(/sim/control-mode, joystick); fgSetBool(/sim/auto-coordination, false); #if !defined(WIN32) +#ifdef __APPLE__ +fgSetString(/sim/startup/browser-app, open /Applications/ Safari.app); +#else fgSetString(/sim/startup/browser-app, netscape); +#endif #else fgSetString(/sim/startup/browser-app, webrun.bat); #endif ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] OT: FYI, mac os x developers, xcode 2.2 has been released
According to apple developer connection (ADC) news, Apple's xcode 2.2 has been released. It would be nice to know that the new fixes haven't broken FlightGear... It is an 834 MB disk image update for mac os x 10.4.x. Download Newly Released Xcode 2.2 Today Latest tools make building universal binaries even easier. All Apple Developer Connection members can download the newly released Xcode 2.2 at no cost from the ADC Member Site. Basic ADC memberships are free, and permit downloading development tools and updates. ADC members can download from http://insideapple.apple.com/redir/ 303569/452_100/1ef0a2707706d7cd11214f98ad642f06 Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear v0.9.9-pre2
Ampere, A bit off topic: does anyone have success in compiling FlightGear and related libaries using GCC-4.0? I have only one problem, building src/FlightGear/src/Instrumentation/ od_gauge.cxx. I mentioned it in october here: http://mail.flightgear.org/pipermail/flightgear-devel/2005-October/ 039393.html the workaround is to build just od_gauge.cxx with -fpermissive. I am using: ima% gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) Copyright (C) 2005 Free Software Foundation, Inc. The problem still occurs with latest CVS. Alex, I guess you're not seeing this problem with 4.0.3? Nice to know it's been fixed! (assuming it's not a private patch) 8-) Now if only apple would update to 4.0.3... best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Buildings ?????
Next on the list are the Nat. Cathedral, Basilica of the Immaculate Conception, Mormon Temple, Pentagon and then the Mall. Not sure what timetable I'm looking at though. If you can think of any other big visible structures that you would like to see (sorry, I'm not tackling the bridges yet, there's issues with the VMAP data I don't want to deal with) let me know. No promises though. Josh, Thanks for your interest on building up a more recognizable washingon, DC! On my wishlist for baltimore: martin state airport, harbor place, bethlehem steel, the hitachi cranes of the dundalk, locust point clinton st. ? marine terminals, maybe the usfg building or md national bank building downtown. One of the largest churches in the us is on a hill in baltimore (an old shopping mall) off cedonia road, Ravens or Oriole stadium, the maryland science center On my wishlist for dc: (in addition to yours): GAI (montgomery county airpark), the college park airport RFK stadium, georgetown/howard universities -- nothing against american or george washington universities, I just don't know how recognizable they'd be), the naval observatory, the power plant in alexandria, the national theater, the kennedy center, the watergate, the national zoo, RIO center (exit 9 off I-270) is probably nicely visable from the air also There's also sugarloaf mountain or great falls, md or great falls, va. Georgetown park or chevy chase pavillion might be good markers, too, but maybe when we modal american shopping malls 8-) tysons corner (the malls) might help find dulles airport visually grin the georgetown and dalecarlia sp? reservoirs might help avoid the restricted area around the us vice presidents house (at the naval observatory) anything at all, esp. if it's on jeppesen plates or the baltimore or washington sectional or terminal area charts. oh, well, I can dream, can't I? Probably accurately displaying the borders of parks and forested areas could help with VFR, no? (this is not to imply that the borders are not accurate, I don't know but it might be worth looking into) I don't know what your schedule is, but it's probably moving a lot faster than mine will be. My schedule is remarkably unreliable 8-(. I hope that eventually I will be able to do some of this... ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] building plib, simgear and flightgear without scripts using make
Hi, I had originally been building plib, simgear and flightgear with a variety of build scripts. These scripts were hard to maintain, and I often found cross platform incompatibilities when I tried to use a script written for one os or shell on another os or different shell. I've been working on ways to improve cross platform building of plib, simgear and flightgear for a while now using make to handle the top level build (at the moment I've got Cygwin and Mac OS X), both with OS changes and with directory changes just for my personal use. I've got a (moderately flexible) makefile (gpled) that I'd like to offer perhaps for inclusion via the faq or in developer information or flightgear wiki (makefile attached). To avoid naming conflicts, I've named it makefile.ima. Build with make -f makefile.ima or rename it to makefile or Makefile. See the makefile for targets, some are: make co -- checks out plib, simgear and flightgear from cvs make allnoinstall -- checks out and builds plib, simgear and flightgear make all (or make with no arguments) -- checks out, builds and installs plib, simgear and flightgear cvs passwords are assumed to be in .cvspass. You can force cvs login by giving CVSLOGIN=1 as an argument to make. The makefile itself goes in BUILDDIR (see below), and make is run from the BUILDDIR directory. Please make sure that the install variable in your environment is set correctly for your os, I think that linux requires a -c option, where mac os x requires -C and cygwin -p in order to not install a file that is no different from the one already installed. This will avoid unnecessary rebuilds of dependencies. I am no makefile expert, but I hope that someone might find this helpful. Perhaps the makefile would help users trying to build their own source from CVS who are new to cvs and the unix build process. The build structure is similar to D(arrell) W(alliser)'s as that's the flightgear build process that I started with. The makefile assumes BUILDDIR and CONFIGPREFIX to be set to a valid directory for the build, a toplevel directory which contains src/lib/bin/include for plib, simgear and flightgear. Please see the makefile for documentation on both the directory hierarchy and these and other variables. I appreciate any and all comments. I'm sure the makefile's got lots of problems, but I offer the makefile as a first draft of something that might eventually be useful. Thank you! Best regards, Ima makefile.ima Description: Binary data ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Buildings ?????
Oh, DC scenery, one of the many things i'd like to do if I ever get around to it (health permitting) 8-) I even got a gps to plot buildings' locations... just was never able to do anything. Back at least 5 years ago when I was flying XPl*ne, I could fly off 33 (?) at DCA and overfly a beautifully rendered pentagon and rosslyn/ key bridge. Since I was 'flying' an a-10 warthog, I'd take it up to martin state outside baltimore where there's an airguard a-10 unit. I think that the capital beltway (495) and 270/70 were there, but the potomac and roosevelt island would allow even the slowest to recognize where they are, right? 8-) I think there's a white house and capital also in that scenery, but I never went that way -- flight restrictions 8-) -- even then! Perhaps the signs script that's been discussed previously on flightgear-devel would help your customers identify the local scenery also. I might have added a Washington, DC scenery package to xpla*e. I must have, right?, because FlightGear and XPla*e share the same scenery, don't they? Jeppesen charts (KDCA arrivals) mention the american legion bridge (about 10 dme from kdca), chain bridge (around 6 dme), key bridge and roosevelt bridge (around 3 dme), then arlington, george mason and rochambeau. from the south, you'd seee the woodrow wilson bridge, a power plant and a masonic temple. Don't forget the Washington, DC Metropolitan Area Special Flight Rules Area, the area around thurmont (camp david) is also restricted... you'd get a lot more from the washington sectional aeronautical chart and the VFR terminal area chart Baltimore-Washinton, available at your local airpark 8-) Is it possible for an end user to add xpla*e washington, DC scenery into flightgear (if the license agreement permits). What steps would be involved? PLEASE make your scenery changes available to others. I'd be very grateful. thanks! ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Buildings ?????
Ima Sudonim wrote: Oh, DC scenery, one of the many things i'd like to do if I ever get around to it (health permitting) 8-) I even got a gps to plot buildings' locations... just was never able to do anything. For what ever it's worth, Google maps seems to do a surprisingly good job of giving up lat/lon coordinates of objects. You have to be a little careful of the way urls get cached and delayed in a web environment, but if you get a link to the current image, you can easily read the lat/lon coordinates out of the link. Just click on the object to make sure it is centered. I'll give google a try then With a hand held gps, you aren't going to ever get to stand at the center of the roof (well maybe rarely) so google has a lot of advantages I was planning on walking the perimeter of the buildings, but with arthritis walking isn't really my thing. 8-( Or perhaps getting the lat/long of one or two corners of a building and then trying to extrapolate orientation and wall sizes from public information. Your way is much better! and might even be more accurate than doing the surveying yourself manually. (The wording of that last phrase didn't come out very well on my first attempt, but I think the final edit is slightly less ambiguous.) :-) surveying oneself manually -- I think I got your meaning but it sounds illegal in a Southern state 8-) Ima Curt. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] build break with some .cpp to .cxx renames
I have co'ed all plib/simgear/flightgear files from CVS a few minutes ago. I am running autogen.sh and configure before flightgear. However I am still getting a build break on the renamed files make[3]: *** No rule to make target `multiplaymgr.cpp', needed by `multiplaymgr.o'. Stop. make: *** No rule to make target `tiny_xdr.cpp', needed by `tiny_xdr.o'. Stop. They both build if I create symbolic links with the old names as follows: ln -s tiny_xdr.cxx tiny_xdr.cpp ln -s multiplaymgr.cxx multiplaymgr.cpp source='multiplaymgr.cxx' object='multiplaymgr.o' libtool=no \ depfile='.deps/multiplaymgr.Po' tmpdepfile='.deps/multiplaymgr.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src - I/Users/ima/Desktop/FlightGear/fgdev9.9/include -g -O2 -D_REENTRANT - c -o multiplaymgr.o `test -f 'multiplaymgr.cxx' || echo './'`multiplaymgr.cxx source='tiny_xdr.cxx' object='tiny_xdr.o' libtool=no \ depfile='.deps/tiny_xdr.Po' tmpdepfile='.deps/tiny_xdr.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src - I/Users/ima/Desktop/FlightGear/fgdev9.9/include -g -O2 -D_REENTRANT - c -o tiny_xdr.o `test -f 'tiny_xdr.cxx' || echo './'`tiny_xdr.cxx the MultiPlayer Makefile has the following: libMultiPlayer_a_SOURCES = multiplaymgr.cxx multiplaymgr.hxx mpplayer.cxx mpplayer.hxx m pmessages.hxx tiny_xdr.cxx tiny_xdr.hxx Any ideas what's going wrong? I am using Mac os x 10.4 and gcc 4.0.0 Thanks! Ima In this repspect the following files have been renamed in src/ Multiplayer: tiny_xdr.[ch]pp has become tiny_xdr.[ch]xx multiplaymgr.[ch]pp has become multiplaymgr.[ch]xx ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] build break with some .cpp to .cxx renames
Erik, Thanks! Based on your advice, I did: ls *.cpp multiplaymgr.cpptiny_xdr.cpp rm *.cpp to remove the links I'd created then I removed the files you mentioned with: rm -f ./deps/tiny_xdr.Po rm -f ./deps/multiplaymgr.Po rerunning make in src/FlightGear/src/MultiPlayer then worked with no problems. A general make of all of flightgear also worked with no problems. Thanks, again! Ima make[3]: *** No rule to make target `multiplaymgr.cpp', needed by `multiplaymgr.o'. Stop. make: *** No rule to make target `tiny_xdr.cpp', needed by `tiny_xdr.o'. Stop. Yes, I noticed that too. It's a gcc dependency problem. In the Multiplayer directory s a hidden directory called .deps which contains a file called tiny_xdr.tpO (or something like that). You could edit that file and replace every instance of hpp by hxx and every instance of cpp by cxx and run make again. You could also remove the .deps directory (or run make clean) and run autogen.sh and configure again. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [Flightgear-cvslogs] CVS:FlightGear/src/ATCAIEntity.cxx, 1.12,
Vivian Meazza wrote: Vivian and Erik, I did not have any problems building (unmodified CVS co) yesterday about 19:30 gmt on recent cygwin on win2k sp3, except that src/flightgear/utils/GPSsmooth/gps.cxx and and MIDG-II.cxx both require Dave's #ifdef HAVE_CONFIG_H # include config.h #endif fix before the includes in order to build. Sorry don't have a diff (doing from memory, but I think that's right)... It is entirely possible that the fault lies in the cvs version that I have here, but I think I have the correct HEAD version. It looks like your src/AIModels/AIFlightPlanCreate.cxx isn't up to date. You might want to run cvs up -PdAC AIFlightPlanCreate.cxx I am using gcc 3.4.4, if that makes a difference Thanks! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Lee Elliott leee at spatial.freeserve.co.uk Wed Oct 19 22:00:29 CDT 2005 Previous message: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Thursday 20 Oct 2005 03:31, Ima Sudonim wrote: On Thursday 20 Oct 2005 01:10, Ima Sudonim wrote: Hi, Someone else had mentioned something similar recently, but I can't find the post in flightgear-devel. I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Thanks! Ima Have you found this with several different aircraft or have you only tried a single type so far? If it only happens with a specific aircraft, which one is it? LeeE I was using the default cessna (didn't give --aircraft= option) (it's the chase view w/o yaw option, where the problem occurs in all instances with reverse view). DOES happen with default cessna, sopwithCamel, spitfireIIa, 747-100, ufo, Citation-II, A380, shuttle (gave a 'failed to load aircraft from, falling back to glider.ac' message, ornithopter (BTW, the ornithopter is already moving forward when fg starts, unlike the other airplane models), bell206 DOESN'T happen with A-10cl (my personal favorite) 8-) or A-10fl (there is no chase view w/o yaw option) Hope this helps! Thanks! Ima Heh ;) I don't mind top or bottom replies but sticking them in the middle throws me a bit. Anyway... I can't find any problems here - cvs a day or two old - I tried just calling fgfs with no params, to get the C-172, and could scroll backwards and forwards through the views ok. Cycled forward to chase w/o yaw, cycled backwards from it - no problems. Then tried both the A-10s, because you mention that they had no chase view w/o view and had no problems there either, including the chase view w/o yaw. Do you get a 'Drop View' with the A-10s? The Drop view should be the 'last' view on the A-10s, before you end up back in the Cockpit and should come after the chase view w/o yaw. Do you get both the chase view w/o yaw and drop view on the A-10s? LeeE Lee, thank you for your interest and suggestions... Sorry, I tend to put the answer right by the question, less chance of forgetting to answer something... 8-( There is NO chase view on my A10s -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, drop view and then back to cockpit view -- NO chase view w/o yaw. I am using latest cvs. Calling flightgear with no --aircraft param, I see the problem: the views are -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, chase view wo yaw, THEN helicopter view (again, note NOT cockpit view), but if I reverse from the 2nd helicopter view, I DO get cockpit view as I would have expected, then backing up again, the screen is labled chase view wo yaw, but is really just cockpit view. Except for the first time, there is NO cockpit view moving forward with 'v', moving backward, I see cockpit view where it belongs, but 'V' stops working with a screen labelled chase view wo yaw, but that looks like cockpit view. Using --aircraft=Citation-II, I get the following views: cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, chase view wo yaw, THEN helicopter view (again, note NOT cockpit view), but if I reverse from the 2nd helicopter view, I DO get cockpit view as I would have expected, then backing up again, the screen is labled chase view wo yaw, but is really just cockpit view. Except for the first time, there is NO cockpit view moving forward with 'v', moving backward, I see cockpit view where it belongs, but 'V' stops working with a screen labelled chase view wo yaw, but that looks like cockpit view. In other words, going forward with 'v', the views are: CV, HV, CVA, CV, TV, TVLF, CVWOY, HV, CVA, CV, TV, TVLF, CVWOY, HV, CVA, CV, etc. going back with 'V' on a broken aircraft here, I'd get: CVA, HV, CVWOY (stuck at this point and 'V' doesn't work anymore until I move forward with 'v' first) The a-10s don't have CVWOY, cycling backwards or forwards, I get: CV, HV, CVA, CV, TV, TVLF, DV, CV, HV, CVA, CV, TV, TVLF, DV, CV, HV, CVA, CV, etc. So, the broken aircraft have chase view wo yaw instead of drop view and don't display the 2nd or more cockpit views going forward (after CVWOY and before helicopter view) with 'v', but will display cockpit view with 'V' (backwards), but 'V' stops working when you get to the CVWAY view, until you move
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X, fixed (somewhat)
If I trash my preferences.xml file and go back to the default, I now get a view cycle of: cockpit view, helicopter view, chase view, tower view, tower view look from, chase view wo yaw 'v' and 'V' both work fine with the Citation-II and the default aircraft. The only difference between the two preferences files is the following diff: diff preferences.xml preferences.xml.IMA 187a188,209 nameChase View Above/name typelookat/type config from-model type=boolfalse/from-model from-model-idx type=int0/from-model-idx eye-lat-deg-path/position/latitude-deg/eye-lat-deg-path eye-lon-deg-path/position/longitude-deg/eye-lon-deg-path eye-alt-ft-path/position/altitude-ft/eye-alt-ft-path eye-heading-deg-path/orientation/heading-deg/eye-heading- deg-path at-model type=booltrue/at-model at-model-idx type=int0/at-model-idx ground-level-nearplane-m type=double0.5f/ground-level- nearplane-m x-offset-m type=double4400/x-offset-m y-offset-m type=double0/y-offset-m z-offset-m type=double-1/z-offset-m /config /view view I don't know why it makes a difference, but it does. Darn, I really liked that Chase View Above 8-( Could anyone suggest a new Chase View Above that doesn't break the view cycle via the keyboard? I find it's good for orienting myself while flying... Sorry for the false alarm. If changing views via 'v' or 'V' stop working, please check your views in data/preferences.xml! Thanks again! Ima [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Lee Elliott leee at spatial.freeserve.co.uk Wed Oct 19 22:00:29 CDT 2005 Previous message: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Thursday 20 Oct 2005 03:31, Ima Sudonim wrote: On Thursday 20 Oct 2005 01:10, Ima Sudonim wrote: Hi, Someone else had mentioned something similar recently, but I can't find the post in flightgear-devel. I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Thanks! Ima Have you found this with several different aircraft or have you only tried a single type so far? If it only happens with a specific aircraft, which one is it? LeeE I was using the default cessna (didn't give --aircraft= option) (it's the chase view w/o yaw option, where the problem occurs in all instances with reverse view). DOES happen with default cessna, sopwithCamel, spitfireIIa, 747-100, ufo, Citation-II, A380, shuttle (gave a 'failed to load aircraft from, falling back to glider.ac' message, ornithopter (BTW, the ornithopter is already moving forward when fg starts, unlike the other airplane models), bell206 DOESN'T happen with A-10cl (my personal favorite) 8-) or A-10fl (there is no chase view w/o yaw option) Hope this helps! Thanks! Ima Heh ;) I don't mind top or bottom replies but sticking them in the middle throws me a bit. Anyway... I can't find any problems here - cvs a day or two old - I tried just calling fgfs with no params, to get the C-172, and could scroll backwards and forwards through the views ok. Cycled forward to chase w/o yaw, cycled backwards from it - no problems. Then tried both the A-10s, because you mention that they had no chase view w/o view and had no problems there either, including the chase view w/o yaw. Do you get a 'Drop View' with the A-10s? The Drop view should be the 'last' view on the A-10s, before you end up back in the Cockpit and should come after the chase view w/o yaw. Do you get both the chase view w/o yaw and drop view on the A-10s? LeeE Lee, thank you for your interest and suggestions... Sorry, I tend to put the answer right by the question, less chance of forgetting to answer something... 8-( There is NO chase view on my A10s -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, drop view and then back to cockpit view -- NO chase view w/o yaw. I am using latest cvs. Calling flightgear with no --aircraft param, I see the problem: the views are -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, chase view wo yaw, THEN helicopter view (again, note NOT cockpit view), but if I reverse from the 2nd helicopter view, I DO get cockpit view as I would have expected, then backing up again, the screen is labled chase view wo yaw, but is really just cockpit view. Except for the first time, there is NO cockpit view moving forward with 'v
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X
Hi, Someone else had mentioned something similar recently, but I can't find the post in flightgear-devel. I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Thanks! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X
On Thursday 20 Oct 2005 01:10, Ima Sudonim wrote: Hi, Someone else had mentioned something similar recently, but I can't find the post in flightgear-devel. I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Thanks! Ima I was using the default cessna (didn't give --aircraft= option) (it's the chase view w/o yaw option, where the problem occurs in all instances with reverse view). DOES happen with default cessna, sopwithCamel, spitfireIIa, 747-100, ufo, Citation-II, A380, shuttle (gave a 'failed to load aircraft from, falling back to glider.ac' message, ornithopter (BTW, the ornithopter is already moving forward when fg starts, unlike the other airplane models), bell206 DOESN'T happen with A-10cl (my personal favorite) 8-) or A-10fl (there is no chase view w/o yaw option) Hope this helps! Thanks! Ima Have you found this with several different aircraft or have you only tried a single type so far? If it only happens with a specific aircraft, which one is it? LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] build break with cygwin and gcc 3.4.4in FlightGear approach.cxx
Georg and Vivian, Thank you, going back to gcc 3.3 (for C and C++) using the Cygwin setup program 'fixed' the cygwin problems I was having... plib, simgear and flightgear from latest cvs build with no problems. Thanks to Kevin Jones, also. 8-) Ima Georg Vollnhals wrote when I tried to build a CVS version of FlightGear I had a *lot* of trouble and errors. Many developers of this list tried to help me but the break-through was an advice of *KEVIN JONES* not to use gcc 3.4.4 (what I had done until then). I followed his detailled instructions as he was just writing a tutorial/manual about building FlightGear 0.9.8/FlightGear CVS under Cygwin and all went fine. Absolute not problems with the build when using gcc 3.3.3 !!! Try it! Kevin will publish his tutorial/manual soon and I hope he is not angry about my answer. But he helped me so much with his advice at a time where I already had given up my trials because I would not show up here with another ask for help and all further hints did not work. So to repeat it, the key-advice for me was to go back to gcc 3.3.3! Thank you once again, Kevin Jones :-) And I hope it will help you too, Ima. Regards Georg Ima Sudonim schrieb: Hi, I am having a problem building flightgear on cygwin (cygwin updated last friday). I am using cvs from this morning. The GCC is cygming 3.4.4 Any ideas what's wrong or how to fix it? I was about to say that gcc 3.4.4 works here - then I remembered that it doesn't - MIDG-II.cxx continues no fail with: MIDG-II.o:MIDG-II.cxx:(.text+0x1067): undefined reference to `SGFile::SGFile(std ::basic_stringchar, std::char_traitschar, std::allocatorchar const)' followed by a series of similar errors. It has been suggested here that it is a SimGear problem, but I have updated and recompliled SimGear several times since I first reported this error. I have fixed the error by removing the offending file from the makefile. FG then compiles perfectly. FlighGear-cvs has failed to compile here under Cygwin/gcc 3.4.4 with a series of different errors almost continuously since 10 Aug. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] build break with cygwin and gcc 3.4.4 in FlightGear approach.cxx
Hi,
I am having a problem building flightgear on cygwin (cygwin updated
last friday).
I am using cvs from this morning. The GCC is cygming 3.4.4
Any ideas what's wrong or how to fix it? I've googled the error and
seen a variety of 'error: expected unqualified-id before 'some
token' token' with cygwin and gcc 3.4.x, but haven't seen anything
that applies to flightgear's build of approach.cxx...
thanks!
Ima
Here's the build log:
if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../
src -I/cygdrive/s/flightgear/fgdev9.9/include -I/usr
/local/include -g -O2 -D_REENTRANT -MT approach.o -MD -MP -MF .deps/
approach.Tpo \
-c -o approach.o `test -f 'approach.cxx' || echo './'`approach.cxx; \
then mv .deps/approach.Tpo .deps/approach.Po; \
else rm -f .deps/approach.Tpo; exit 1; \
fi
In file included from ../../src/Main/globals.hxx:28,
from ../../src/Main/fg_props.hxx:14,
from approach.hxx:34,
from approach.cxx:21:
../../src/Include/config.h:194:1: warning: WIN32 redefined
In file included from /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../
include/w32api/windows.h:48,
from /cygdrive/s/flightgear/fgdev9.9/include/plib/
ul.h:113,
from /cygdrive/s/flightgear/fgdev9.9/include/plib/
sg.h:29,
from /cygdrive/s/flightgear/fgdev9.9/include/
simgear/constants.h:44,
from /cygdrive/s/flightgear/fgdev9.9/include/
simgear/timing/geocoord.h:48,
from /cygdrive/s/flightgear/fgdev9.9/include/
simgear/timing/timezone.h:33,
from /cygdrive/s/flightgear/fgdev9.9/include/
simgear/timing/sg_time.hxx:45,
from approach.hxx:31,
from approach.cxx:21:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/windef.h:
29:1: warning: this is the location of the previou
s definition
In file included from /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/
fstream:840,
from ATCVoice.hxx:27,
from ATC.hxx:34,
from approach.hxx:54,
from approach.cxx:21:
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/fstream.tcc: In
member function `virtual typename std::basic_filebuf
_CharT, _Traits::int_type std::basic_filebuf_CharT,
_Traits::underflow()':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/fstream.tcc:277:
error: expected unqualified-id before '(' token
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/fstream.tcc: In
member function `virtual std::streamsize std::basic_f
ilebuf_CharT, _Traits::xsputn(const _CharT*, std::streamsize)':
/usr/lib/gcc/i686-pc-cygwin/3.4.4/include/c++/bits/fstream.tcc:585:
error: expected unqualified-id before '(' token
make[2]: *** [approach.o] Error 1
make[2]: Leaving directory `/cygdrive/s/flightgear/fgdev9.9/src/
FlightGear/src/ATC'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/cygdrive/s/flightgear/fgdev9.9/src/
FlightGear/src'
make: *** [install-recursive] Error 1
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] FG build break on mac os x (using gcc 4.0) building od_gauge.cxx
Hello, all FG build break on mac os x (10.4.2) (using gcc 4.0) building od_gauge.cxx: gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) % make source='od_gauge.cxx' object='od_gauge.o' libtool=no \ depfile='.deps/od_gauge.Po' tmpdepfile='.deps/od_gauge.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src - I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT - c -o od_gauge.o `test -f 'od_gauge.cxx' || echo './'`od_gauge.cxx /Users/ima/Desktop/FlightGear/fgdev9.8/include/simgear/structure/ event_mgr.hxx:54: error: declaration does not declare anything make: *** [od_gauge.o] Error 1 [Four-Computer:flightgear/src/instrumentation] ima% sudo gcc_select 3.3 Password: Default compiler has been set to: gcc version 3.3 20030304 (Apple Computer, Inc. build 1809) [Four-Computer:flightgear/src/instrumentation] ima% make source='od_gauge.cxx' object='od_gauge.o' libtool=no \ depfile='.deps/od_gauge.Po' tmpdepfile='.deps/od_gauge.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src - I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT - c -o od_gauge.o `test -f 'od_gauge.cxx' || echo './'`od_gauge.cxx In file included from ../../src/Main/globals.hxx:34, from od_gauge.cxx:29: /Users/ima/Desktop/FlightGear/fgdev9.8/include/simgear/structure/ event_mgr.hxx:54: warning: declaration does not declare anything Either switching to gcc 3.3 (where this is a warning, as shown above -- but requiring a complete rebuild) or building this file with - fpermissive (shown below) will allow a successful build g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src - I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT - c -o od_gauge.o -fpermissive `test -f 'od_gauge.cxx' || echo './'`od_gauge.cxx /Users/ima/Desktop/FlightGear/fgdev9.8/include/simgear/structure/ event_mgr.hxx:54: warning: declaration does not declare anything Perhaps this is related to a known compiler problem? http://gcc.gnu.org/ml/gcc-bugs/2004-12/msg02476.html This 'error' started appearing only in the last few days and only seems to affect this one fg file... Any ideas on what might have gone wrong or how to properly fix it? 8-) Thanks! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] problem with signs program, convert: command not found
Melchior, The new signs program, it's great! However, I'm noticing a problem on a mac os x system that I reinstalled recently. I downloaded new scripts this morning, when I install them in data and run signs (either from data/local/signs or from a copy of signs copied to bin, I get a series of error messages like this: creating: cache/A/KJFK_John_F_Kennedy_Intl.rgb sh: line 1: convert: command not found I had this working before the reinstall of my system. My question is: is the convert command new? (if so, do you know where I can get source (or binary version for mac os x (10.4)))? I don't know why it worked previously, maybe I had a convert command installed on the old install of the os but I can't seem to find it now. Thanks for your help! BTW, the signs are VERY cool, and it's especially nice that they're so extensible easily. I did notice that when I scroll thru fgfs to get to the top down view that I only see red lines appearing (i.e., the tops of the signs) instead of the signs as the signs are still vertical. Can the script be changed to display signs horizontal when this top-down view is used (Hit 'v' six times to get to this view)? Thanks for giving us all a very cool feature! ... and thanks for all your work on FlightGear! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Cygwin break on latest CVS build, Norman's fix works, needs 2 more changes to alc.h
There are 3 problems preventing the successfull build of simgear on my system, one in alctypes.h, and two in alc.h. Vivian mentioned the problem with alctypes.h back in february, 2005. Norman suggested a fix here: http://baron.flightgear.org/pipermail/flightgear-devel/2005-February/034682.html Norman's fix: changing !defined(_WIN32) to !defined(WIN32) Norman's fix solves the alctypes.h problem on my Cygwin system. Could someone please make this change in CVS to alctypes.h? The file is in include/al. This fixes the `soundmgr_openal.cxx problem. A problem then occurs with building xmlsound.cxx. The same fix given above needs to be also added to line 13 of alc.h Also line 20 of alc.h must be changed to: #if defined (_MSC_VER) || defined(WIN32) Could someone please also make these two changes in CVS to alc.h? With these changes, simgear builds OK on my system. Sorry it's taken so long to figure this out. Thanks to Norman and Vivian for pointing this out in the first place. Thanks! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Running Flightgear on Mac OS X
Felix, Erik put into CVS a few hours ago a simgear/sound fix that will fix your problem. You will still see a white box on a black background, but this time it will eventually end with one of the fg startup pictures being shown. The problem was an infinite loop specific to mac os x that only showed up (I think) with gcc 3.3 and greater compilers (which is in the latest dev tools for mac os x) I think. Earlier compilers didn't seem to have this problem (at least for me they didn't 8-)). You can see which version of the compiler you have with gcc --version Mine is: gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1671) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I don't know why it's taking so long to put up a picture on the white box. It will need looking into on one of my better days (darned weather)! 8-) It would definitely be calmer for users (at least THIS user) to see a picture on the splash screen as soon as possible after the white box (or hold displaying the white box until the picture is ready, but then users might think FlightGear is not responding). Perhaps someone could figure out how to display a text message like loading FlightGear-required components. Please wait. in the white box until the picture is ready for display. (All the pictures are cool, but I especially like the triplane picture, BTW). Thanks to Eric for putting this in, and thanks to all the developers for the great flightsim AND for supporting Mac OS X! TTFN (ta-ta for now) Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] hang on mac os x with latest simgear/fg source + 3.3 gcc
There is a hang in isnan() during fg start if simgear is built using
gcc 3.3 compiler (which I installed about two months back) on mac os x.
Due to a variety of issues (mostly the weather 8-) ), I've not been
able to look at this problem until recently, but I've got a fix for it
that I'll give below.
Under gdb, breaking into the hang I have:
No bindings for joystick 9
Joystick 9 not found
^C
Program received signal SIGINT, Interrupt.
isnan(double) (r=0) at soundmgr_openal.cxx:40
40 inline int (isnan)(double r) { return isnan(r); }
(gdb) Quit
(gdb) Quit
(gdb) bt
#0 isnan(double) (r=0) at soundmgr_openal.cxx:40
#1 0x00316ccc in SGSoundMgr::set_source_pos_all(float*)
(this=0x1457cd50, pos=0xb440) at soundmgr_openal.cxx:40
#2 0x4e50 in fgMainLoop() () at ../../src/Main/globals.hxx:290
#3 0x87521e18 in -[GLUTApplication run] ()
#4 0x8753bd28 in glutMainLoop ()
#5 0x75b8 in fgMainInit(int, char**) (argc=1, argv=0x5c39ec) at
main.cxx:958
#6 0x31e0 in main (argc=1, argv=0x15fd5e00) at bootstrap.cxx:192
(gdb)
Program received signal SIGINT, Interrupt.
isnan(double) (r=0) at soundmgr_openal.cxx:40
40 inline int (isnan)(double r) { return isnan(r); }
(gdb) stepi
40 inline int (isnan)(double r) { return isnan(r); }
(gdb) u isnan
isnan(double) (r=0) at soundmgr_openal.cxx:40
40 inline int (isnan)(double r) { return isnan(r); }
(gdb)
---
The fix is to modify src/simgear/simgear/sound/soundmgr_openal.cxx as
follows:
The original (1.16) reads:
#if defined (__APPLE__)
// any C++ header file undefines isinf and isnan
// so this should be included before iostream
inline int (isinf)(double r) { return isinf(r); }
inline int (isnan)(double r) { return isnan(r); }
#endif
the fix is to replace the above with:
#if defined (__APPLE__)
# ifdef __GNUCC__
#if __GNUCC__ == 3
# if __GNUC_MINOR = 3
#include math.h
# endif
#endif
# else
// any C++ header file undefines isinf and isnan
// so this should be included before iostream
inline int (isinf)(double r) { return isinf(r); }
inline int (isnan)(double r) { return isnan(r); }
# endif
#endif
Looks like the undefining of isnan, at least, is fixed using gcc 3.3 on
mac os x. Could someone please check this fix into CVS?
Thanks!
Ima
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Mac joysticks + Mac OS X build errors
Erik Thank you VERY much! The simgear change gets me further along but still breaks as None and True are not defined. g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -DGLX_GLXEXT_PROTOTYPES -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o extensions.o `test -f 'extensions.cxx' || echo './'`extensions.cxx source='RenderTexture.cpp' object='RenderTexture.o' libtool=no \ depfile='.deps/RenderTexture.Po' tmpdepfile='.deps/RenderTexture.TPo' \ depmode=gcc3 /bin/sh ../../depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -DGLX_GLXEXT_PROTOTYPES -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo './'`RenderTexture.cpp RenderTexture.cpp: In constructor `RenderTexture::RenderTexture(const char*)': RenderTexture.cpp:163: error: `None' undeclared (first use this function) RenderTexture.cpp:163: error: (Each undeclared identifier is reported only once for each function it appears in.) RenderTexture.cpp: In member function `bool RenderTexture::_Invalidate()': RenderTexture.cpp:582: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp:588: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp: In member function `bool RenderTexture::Resize(int, int)': RenderTexture.cpp:729: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp:731: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp: In member function `void RenderTexture::_ParseModeString(const char*, std::vectorint, std::allocatorint , std::vectorint, std::allocatorint )': RenderTexture.cpp:1274: error: `True' undeclared (first use this function) RenderTexture.cpp: In member function `bool RenderTexture::_InitializeTextures()': RenderTexture.cpp:1825: warning: invalid conversion from `unsigned int*' to ` GLuint*' RenderTexture.cpp:1936: warning: invalid conversion from `unsigned int*' to ` GLuint*' make[2]: *** [RenderTexture.o] Error 1 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 makesg done I added the following to the top of RenderTexture.cpp: #ifdef __APPLE__ # ifndef None # define None false # endif # ifndef True # define True true # endif #endif Maybe the above should go elsewhere such as compiler.h? It gets me past the build errors. My above changes throw off the line numbers, but then I get the following warnings: g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -DGLX_GLXEXT_PROTOTYPES -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo './'`RenderTexture.cpp RenderTexture.cpp: In member function `bool RenderTexture::_Invalidate()': RenderTexture.cpp:591: warning: invalid conversion from `unsigned int*' to ` const GLuint*' Removed by: glDeleteTextures(1, (const GLuint*) _iTextureID); RenderTexture.cpp:597: warning: invalid conversion from `unsigned int*' to ` const GLuint*' Removed by: glDeleteTextures(1, (const GLuint*) _iDepthTextureID); RenderTexture.cpp: In member function `bool RenderTexture::Resize(int, int)': RenderTexture.cpp:738: warning: invalid conversion from `unsigned int*' to ` const GLuint*' Removed by: glDeleteTextures(1, (const GLuint*) _iTextureID); RenderTexture.cpp:740: warning: invalid conversion from `unsigned int*' to ` const GLuint*' Removed by: glDeleteTextures(1, (const GLuint*) _iDepthTextureID); RenderTexture.cpp: In member function `bool RenderTexture::_InitializeTextures()': RenderTexture.cpp:1834: warning: invalid conversion from `unsigned int*' to ` GLuint*' Removed by: glGenTextures(1, (GLuint*) _iTextureID); RenderTexture.cpp:1945: warning: invalid conversion from `unsigned int*' to ` GLuint*' Removed by: glGenTextures(1, (GLuint*) _iDepthTextureID); The above changes allow me to build RenderTexture.cpp with no errors or warnings. I should have considered that normalmap.cxx required that one piece of simgear that I couldn't build. 8-( Sorry for complaining about a non-problem... Thanks for the js correction and information also! I'll now work on building fg... Thanks again! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Mac joysticks + Mac OS X build errors
Erik, Thanks! FG builds on mac os X.3 with no problems now... Ima Ima wrote: Erik Thank you VERY much! The simgear change gets me further along but still breaks as None and True are not defined. snip fixes The above changes allow me to build RenderTexture.cpp with no errors or warnings. These changes have been committed now. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] SG and FG build breaks on mac os x.3 (10.3)
Various mac os x specific build breaks with Saturday 5 february 2005 cvs source. Flightgear: The src/input Makefile needs: base_LIBS = -framework IOKit -framework CoreFoundation to successfully build fgjs and js_demo on mac os x.3 (10.3) also: /utils/modeller g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o normalmap.o `test -f 'normalmap.cxx' || echo './'`normalmap.cxx normalmap.cxx: In function `int main(int, char**)': normalmap.cxx:82: error: `err_str' undeclared (first use this function) normalmap.cxx:82: error: (Each undeclared identifier is reported only once for each function it appears in.) normalmap.cxx:98: error: `make_normalmap' undeclared (first use this function) normalmap.cxx:99: error: `write_texture' undeclared (first use this function) make[2]: *** [normalmap.o] Error 1 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 SimGear: g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -DGLX_GLXEXT_PROTOTYPES -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo './'`RenderTexture.cpp In file included from /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ QD.framework/Headers/QD.h:42, from /System/Library/Frameworks/ApplicationServices.framework/Headers/ ApplicationServices.h:30, from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24, from /System/Library/Frameworks/AGL.framework/Headers/agl.h:23, from ../../simgear/screen/RenderTexture.h:56, from RenderTexture.cpp:58: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ QD.framework/Headers/Quickdraw.h:262: error: conflicting types for `struct Cursor' /usr/include/X11/X.h:108: error: previous declaration as `typedef XID Cursor' /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ QD.framework/Headers/Quickdraw.h:267: error: conflicting types for `typedef struct Cursor Cursor' /usr/include/X11/X.h:108: error: previous declaration as `typedef XID Cursor' RenderTexture.cpp: In member function `bool RenderTexture::_Invalidate()': RenderTexture.cpp:582: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp:588: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp: In member function `bool RenderTexture::Resize(int, int)': RenderTexture.cpp:729: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp:731: warning: invalid conversion from `unsigned int*' to ` const GLuint*' RenderTexture.cpp: In member function `bool RenderTexture::_InitializeTextures()': RenderTexture.cpp:1825: warning: invalid conversion from `unsigned int*' to ` GLuint*' RenderTexture.cpp:1936: warning: invalid conversion from `unsigned int*' to ` GLuint*' make[2]: *** [RenderTexture.o] Error 1 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 FYI, Thank you! ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Mac os x simgear build break with RenderTexture.cpp
When I went to do a full build of simgear January 27th, I am having a problem with the build of RenderTexture.cpp. I have been unable to download newer source since then due to a network problem that breaks CVS on my local network. Mac OS X doesn't generally support glx.h If someone has X11 developer sources installed on mac os x, the glx file exists on: /usr/X11R6/include/GL but I don't think that I should be using that GLX file as I am NOT building a version of FG for X, but rather for native mac os x. Does anyone have any suggestions for how to build simgear/screen without requiring GLX? (I tried explicitly giving --without-x during configure but it didn't seem to help). The first error message is: g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -DGLX_GLXEXT_PROTOTYPES -I/Users/ima/Desktop/FlightGear/fgdev9.8/include -g -O2 -D_REENTRANT -c -o RenderTexture.o `test -f 'RenderTexture.cpp' || echo './'`RenderTexture.cpp In file included from RenderTexture.cpp:58: ../../simgear/screen/RenderTexture.h:56:20: OpenGL/glx.h: No such file or directory .. followed by these errors In file included from RenderTexture.cpp:58: ../../simgear/screen/RenderTexture.h:342: error: 'GLXContext' is used as a type, but is not defined as a type. ../../simgear/screen/RenderTexture.h:343: error: 'GLXPbuffer' is used as a type, but is not defined as a type. ../../simgear/screen/RenderTexture.h:345: error: 'GLXDrawable' is used as a type, but is not defined as a type. ../../simgear/screen/RenderTexture.h:346: error: 'GLXContext' is used as a type, but is not defined as a type. RenderTexture.cpp: In constructor `RenderTexture::RenderTexture(const char*)': RenderTexture.cpp:127: error: class `RenderTexture' does not have any field named `_hGLContext' RenderTexture.cpp:128: error: class `RenderTexture' does not have any field named `_hPBuffer' .. and so on Sorry, I seem especially clueless lately. 8-( TIA for any help! Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Announce: FlightGear-0.9.8-pre1 and SimGear-0.3.8-pre1
FYI: Thanks to Innis Cunningham, I found a few non-portable pathnames in FlightGear thatI would like to fix before the next release. I'll do my best to fix these before the next release, but I may need a day or two. Cheers, Durk Just a reminder that some of us running BSD-clones (Mac OS X) have case-insensitive file systems. I think that CygWin has the same issue -- someone fixed some problems in the base package related to this not too long ago with case-insensitive file conflicts. In other words the file names 'atlas' and 'ATLAS' resolve to the same file on Mac OS X with HFS+ file system: ima% cat tmp one ima% cat TMP two ima% cat tmp two I know of no problems with the betas regarding this, however. Thank you! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] re:Mac OS X related install command concern during FG (+ dep) builds
The configure script log contains the following: checking for a BSD-compatible install... /usr/bin/install -c Perhaps it needs to first check for /usr/bin/install -C and use that instead if available? While using -c doesn't force a complete rebuild, it changes enough dependencies to rebuild a lot which it really shouldn't need to, especially FlightGear. Thanks! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Please use SG_GL constants to include GL include files for portability
One more mac os x fix needed for flightgear (all files using GL includes for FlightGear or SimGear should now use #include simgear/compiler.h followed by #include SG_GL_H #include SG_GLU_H #include SG_GLUT_H #include SG_GLEX_H (defined in compiler.h) as required. This will ensure that the necessary OpenGL or GLUT file is included in a portable fashion. (Apple broke portability with non-standard OpenGL include directory names) Currently Cockpit/hud_rwy.cxx does not use the above compiler.h strategy and breaks mac os x builds the line in hud_rwy.cxx #include GL/glu.h needs to be replaced by: #include simgear/compiler.h #include SG_GLU_H Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Mac OS X related install command concern during FG (+ dep) builds
The mac os x install command has the following parameters (subset): -C Copy the file. If the target file already exists and the files are the same, then don't change the modification time of the tar- get. -c Copy the file. This is actually the default. The -c option is only included for backwards compatibility. -p Preserve the modification time. Copy the file, as if the -C (compare and copy) option is specified, except if the target file doesn't already exist or is different, then preserve the modifi- cation time of the file. -S Safe copy. Normally, install unlinks an existing target before installing the new file. With the -S flag a temporary file is used and then renamed to be the target. The reason this is safer is that if the copy or rename fails, the existing target is left untouched. -s install exec's the command strip(1) to strip binaries so that install can be portable over a large number of systems and binary types. -v Causes install to show when -C actually installs something. So during the plib build (no plib src changes), we get: Making install in util /bin/sh ../../mkinstalldirs /Users/ima/Desktop/FlightGear/fgdev9.6/lib /usr/bin/install -c -m 644 libplibul.a /Users/ima/Desktop/FlightGear/fgdev9.6/lib/libplibul.a ranlib /Users/ima/Desktop/FlightGear/fgdev9.6/lib/libplibul.a /bin/sh ../../mkinstalldirs /Users/ima/Desktop/FlightGear/fgdev9.6/include/plib /usr/bin/install -c -m 644 ul.h /Users/ima/Desktop/FlightGear/fgdev9.6/include/plib/ul.h /usr/bin/install -c -m 644 ulRTTI.h /Users/ima/Desktop/FlightGear/fgdev9.6/include/plib/ulRTTI.h Making install in js /bin/sh ../../mkinstalldirs /Users/ima/Desktop/FlightGear/fgdev9.6/lib /usr/bin/install -c -m 644 libplibjs.a /Users/ima/Desktop/FlightGear/fgdev9.6/lib/libplibjs.a ranlib /Users/ima/Desktop/FlightGear/fgdev9.6/lib/libplibjs.a /bin/sh ../../mkinstalldirs /Users/ima/Desktop/FlightGear/fgdev9.6/include/plib /usr/bin/install -c -m 644 js.h /Users/ima/Desktop/FlightGear/fgdev9.6/include/plib/js.h The plib include (and lib and so forth) directory has been updated as shown below: % ls -l include/plib total 984 -rw-r--r-- 1 ima staff 10370 21 Nov 02:05 fnt.h -rw-r--r-- 1 ima staff 3110 21 Nov 02:04 js.h -rw-r--r-- 1 ima staff227 21 Nov 02:05 net.h -rw-r--r-- 1 ima staff 6464 21 Nov 02:05 netBuffer.h -rw-r--r-- 1 ima staff 3786 21 Nov 02:05 netChannel.h -rw-r--r-- 1 ima staff 2643 21 Nov 02:05 netChat.h -rw-r--r-- 1 ima staff 6652 21 Nov 02:05 netMessage.h -rw-r--r-- 1 ima staff 2579 21 Nov 02:05 netMonitor.h -rw-r--r-- 1 ima staff 2924 21 Nov 02:05 netSocket.hll --help -rw-r--r-- 1 ima staff 2602 21 Nov 02:05 pcx.h-g group] [-m mode] -rw-r--r-- 1 ima staff 7821 21 Nov 02:05 psl.h -rw-r--r-- 1 ima staff 63489 21 Nov 02:04 pu.h[-g group] [-m mode] -rw-r--r-- 1 ima staff 25544 21 Nov 02:04 puAux.h -rw-r--r-- 1 ima staff 44 21 Nov 02:04 puAuxLocal.hrectory ... -rw-r--r-- 1 ima staff 1830 21 Nov 02:04 puFLTK.hn install -rw-r--r-- 1 ima staff 1777 21 Nov 02:04 puGLUT.h -rw-r--r-- 1 ima staff 2428 21 Nov 02:04 puNative.h -rw-r--r-- 1 ima staff 1745 21 Nov 02:04 puPW.h -rw-r--r-- 1 ima staff 1478 21 Nov 02:04 puSDL.h -rw-r--r-- 1 ima staff 3834 21 Nov 02:05 pw.h -rw-r--r-- 1 ima staff 83371 21 Nov 02:04 sg.h -rw-r--r-- 1 ima staff 19332 21 Nov 02:04 sl.h -rw-r--r-- 1 ima staff 2382 21 Nov 02:04 slPortability.h -rw-r--r-- 1 ima staff 2859 21 Nov 02:04 sm.h -rw-r--r-- 1 ima staff 82135 21 Nov 02:05 ssg.h -rw-r--r-- 1 ima staff 2450 21 Nov 02:05 ssgAux.h -rw-r--r-- 1 ima staff 8401 21 Nov 02:05 ssgKeyFlier.h -rw-r--r-- 1 ima staff 1117 21 Nov 02:05 ssgMSFSPalette.h -rw-r--r-- 1 ima staff 7558 21 Nov 02:05 ssgaBillboards.h -rw-r--r-- 1 ima staff 2015 21 Nov 02:05 ssgaFire.h -rw-r--r-- 1 ima staff 1599 21 Nov 02:05 ssgaLensFlare.h -rw-r--r-- 1 ima staff 3228 21 Nov 02:05 ssgaParticleSystem.h -rw-r--r-- 1 ima staff343 21 Nov 02:05 ssgaScreenDump.h -rw-r--r-- 1 ima staff 5971 21 Nov 02:05 ssgaShapes.h -rw-r--r-- 1 ima staff 10716 21 Nov 02:05 ssgaSky.h -rw-r--r-- 1 ima staff 1248 21 Nov 02:05 ssgaSphere.h -rw-r--r-- 1 ima staff 3603 21 Nov 02:05 ssgaWaveSystem.h -rw-r--r-- 1 ima staff 2044 21 Nov 02:05 ssgconf.h -rw-r--r-- 1 ima staff 16648 21 Nov 02:04 ul.h -rw-r--r-- 1 ima staff 12621 21 Nov 02:04 ulRTTI.h (these files are newer, but unchanged, files created during the previous 'make install' process) This forces a rebuild of simgear and (then) flightgear unnecessarily. Question 1: Should we be using '-C' instead of '-c' to not install new files to the install directories if in fact these files are no different from the ones currently there? Question
[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
[Flightgear-devel] FlightGear build break: Mac OS X
With CVS src from 2100 GMT Wednesday, 17 XI 2004, network/ATC-inputs.cxx requires #ifdef __APPLE__ #include fcntl.h #endif before: #include ATC-Inputs.hxx to build flightgear successfully. I'd appreciate it if someone with developer authority could make this small change. Otherwise constants like O_RDWR are not defined. This might be required for other BSD unix variants, I am not sure. Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur, I have built FlightGear on Mac OS X. After a LOT of trial and error building SimGear and FlightGear without the X11 SDK. Great! It seems all that needed to be done was change GL/gl.h and GL/glu.h in all the source files which contained those includes to OpenGL/*. I was really concerned why I could build without these Gl errors and you couldn't on mac os x so I did some research I have open GL headers in /System/Library/Frameworks/OpenGL.framework/Versions/A/Headers and /System/Library/Frameworks/AGL.framework/Versions/A/Headers If I do a 'grep -r GL * from ./src/flightgear/src, I get (among other things) FDM/.deps/MagicCarpet.Po: /FlightGear/fgdev9.6/include/GL/gl.h \ FDM/.deps/MagicCarpet.Po: /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \ FDM/.deps/MagicCarpet.Po:/FlightGear/fgdev9.6/include/GL/gl.h: FDM/.deps/MagicCarpet.Po:/System/Library/Frameworks/OpenGL.framework/ Headers/gl.h: FDM/.deps/UFO.Po: /FlightGear/fgdev9.6/include/GL/gl.h \ FDM/.deps/UFO.Po: /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \ FDM/.deps/UFO.Po:/FlightGear/fgdev9.6/include/GL/gl.h: FDM/.deps/UFO.Po:/System/Library/Frameworks/OpenGL.framework/Headers/ gl.h: FDM/Balloon/.deps/BalloonSim.Po: /FlightGear/fgdev9.6/include/GL/gl.h \ FDM/Balloon/.deps/BalloonSim.Po: /System/Library/Frameworks/OpenGL.framework/Headers/gl.h \ FDM/Balloon/.deps/BalloonSim.Po:/FlightGear/fgdev9.6/include/GL/gl.h: FDM/Balloon/.deps/BalloonSim.Po:/System/Library/Frameworks/ OpenGL.framework/Headers/gl.h: Ouch! It turns out I have a GL directory in fgdev9.6/include that contains: /FlightGear/fgdev9.6/include] ima% ls -l Gl total 32 -rwxrwxr-x 1 ima staff 232 14 Dec 2002 gl.h -rwxrwxr-x 1 ima staff 26 14 Dec 2002 glext.h -rwxrwxr-x 1 ima staff 24 14 Dec 2002 glu.h -rwxrwxr-x 1 ima staff 23 14 Dec 2002 glut.h Yes, they're nearly two years old! Maybe that's why I could build and you couldn't? 8-( The real headers are: [Four-Computer:frameworks/opengl.framework/headers] ima% ls -l gl* -rw-r--r-- 1 root wheel 124202 12 Sep 2003 gl.h -rw-r--r-- 1 root wheel 200923 12 Sep 2003 glext.h -rw-r--r-- 1 root wheel 294 12 Sep 2003 gliContext.h -rw-r--r-- 1 root wheel 47720 12 Sep 2003 gliDispatch.h -rw-r--r-- 1 root wheel 16259 12 Sep 2003 glu.h -rw-r--r-- 1 root wheel2597 12 Sep 2003 gluContext.h -rw-r--r-- 1 root wheel2242 12 Sep 2003 gluMacro.h The AGL headers are: ls -l /System/Library/Frameworks/AGL.framework/Versions/A/Headers total 248 -rw-r--r-- 1 root wheel 16716 13 Sep 2003 agl.h -rw-r--r-- 1 root wheel889 13 Sep 2003 aglContext.h -rw-r--r-- 1 root wheel 71046 13 Sep 2003 aglMacro.h -rw-r--r-- 1 root wheel 1244 13 Sep 2003 aglRenderers.h lrwxr-xr-x 1 root wheel 56 25 Jan 2004 gl.h - /System/Library/Frameworks/OpenGL.framework/Headers/gl.h lrwxr-xr-x 1 root wheel 64 25 Jan 2004 gliContext.h - /System/Library/Frameworks/OpenGL.framework/Headers/gliContext.h lrwxr-xr-x 1 root wheel 65 25 Jan 2004 gliDispatch.h - /System/Library/Frameworks/OpenGL.framework/Headers/gliDispatch.h -rw-r--r-- 1 root wheel 4327 13 Sep 2003 glm.h lrwxr-xr-x 1 root wheel 57 25 Jan 2004 glu.h - /System/Library/Frameworks/OpenGL.framework/Headers/glu.h When I remove this GL directory in fgdev9.6/include and rebuild, I get: 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:11:19: GL/glut.h: No such file or directory est-epsilon.c: In function `main': est-epsilon.c:15: error: `GLfloat' undeclared (first use in this function) est-epsilon.c:15: error: (Each undeclared identifier is reported only once est-epsilon.c:15: error: for each function it appears in.) est-epsilon.c:15: error: parse error before a est-epsilon.c:17: error: `a' undeclared (first use in this function) est-epsilon.c:22: error: `t' undeclared (first use in this function) make[1]: *** [est-epsilon.o] Error 1 make: *** [all-recursive] Error 1 Sound familiar? So yes, it sounds like your patch is something needed for mac os x, either that or symlinks in ./include/GL to point to the real headers 8-) Just kidding, the patch is a MUCH better idea. Chalk it up to apple having non-standard locations for the opengl header files. I don't know where I came up with the idea of creating a GL directory, but there you go, it's there so go figure... I guess I 'll be getting rid of it as soon as your patch is ready. What needs to be done is to make a patch that include GL/* on other systems but OpenGL/* on Mac OS X. I believe this would make compiling SimGear and FlightGear on Mac OS X pain less. I had to make, make clean, make again in
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur,
You've come so far, please don't give up now!
This is the last day I'm going to work on this. If I can't get it to
work today I will wait until Mac OS X 10.4 is released. (Tiger)
Curt,
Your command to find files works fine on Mac OS X.3.6, here's the
result on my system:
sudo find / -print | grep plibfnt
Password:
/FlightGear/fgdev9.6/lib/libplibfnt.a
/FlightGear/fgdev9.6/src/plib/src/fnt/libplibfnt.a
i.e. -- one built version, also copied to lib as the installed version
Arthur,
this is a plib issue. FlightGear is just the symptom. Have you tried
any of the plib sample applications to see if your installed plib is in
fact working? Just because something builds doesn't mean it works, I
speak from unfortunate personal experience. 8-)
Can anyone with plib developer authority possibly add these changes to
plib/examples?
They are required to build in Mac OS X
Changes required to build plib examples on mac os x -- start
--
To use plib installed in a non-standard directory, I needed to set:
setenv LDFLAGS -L/FlightGear/fgdev9.6/lib
setenv CPPFLAGS -I/FlightGear/fgdev9.6/include
(these are uppercase L (LDFLAGS) and uppercase I (CPPFLAGS), BTW)
before running ./configure in the ./examples direction
I then needed to modify js_demo_LDADD to add a few frameworks
js_demo_LDADD = -lplibjs -lplibul -framework IOKit -framework
CoreFoundation
in the ./examples/src/js/makefile.
I also needed to change ./examples/src/ssg/majik/makefile to add
-framework IOKit -framework CoreFoundation to the end of
majik_demo_LDADD giving
majik_demo_LDADD = -lplibjs -lplibssg -lplibsg -lplibul $(GLUT_LIBS)
$(OGL_LIBS) -framework IOKit -framework CoreFoundation
I also needed to change ./examples/src/pw/makefile to add
-framework IOKit -framework CoreFoundation -framework
ApplicationServices -framework Carbon
to pw_demo_LDFLAGS
giving
pw_demo_LDFLAGS = -framework IOKit -framework CoreFoundation -framework
ApplicationServices -framework Carbon
I added the same to pw_pui_LDFLAGS in the same file
lorenz.cxx doesn't seem to exist and broke the build
I created lorenz.cxx containing
main()
{
}
and rebuilt. No idea what this is.
--
Changes required to build plib examples on mac os x -- end
Thanks!
Ima
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Flightgear-devel Digest, Vol 19, Issue 34
On Nov 10, 2004, at 6:26 PM, Arthur wrote: Date: Wed, 10 Nov 2004 18:26:04 -0500 From: Arthur Wiebe [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII g++ -I/usr/X11R6/include -D_REENTRANT -L/fgfs/lib -o layout-test layout-test.o libGUI.a -lsgprops -lsgdebug -lsgstructure -lsgmisc -lsgxml -lplibpw -lplibpu -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 This is an OpenGL function -- perhaps a 'make clean' in ./src/plib, ./src/simgear, and ./src/flightgear followed by a rebuild would help? You might have obj module/lib conflicts as you've tried at least two build strategies, right? (--with-x and --without-x) My opengl.framework has the following info: ls -l /system/library/frameworks/opengl.framework total 32 lrwxr-xr-x 1 root wheel 24 25 Jan 2004 Headers - Versions/Current/Headers lrwxr-xr-x 1 root wheel 26 25 Jan 2004 Libraries - Versions/Current/Libraries lrwxr-xr-x 1 root wheel 23 25 Jan 2004 OpenGL - Versions/Current/OpenGL lrwxr-xr-x 1 root wheel 26 25 Jan 2004 Resources - Versions/Current/Resources drwxr-xr-x 4 root wheel 136 27 Oct 20:36 Versions drwxr-xr-x 7 root wheel 238 27 Oct 20:36 OpenGL.framework Remember I'm using Mac OS X.6, however, versus your 10.5.x Do you have any ideas or had this error yourself? Thanks! By the way, Mac OS X packages of PLIB are at http://awiebe.blogdns.net/download/PLIB/MacOSX/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Flightgear-devel Digest, Vol 19, Issue 34
Frederic, Sorry for forgetting to change the subject the first time, I'll leave it so it threads properly. ima.sudonim at verizon.net a écrit : On Nov 10, 2004, at 6:26 PM, Arthur wrote: Date: Wed, 10 Nov 2004 18:26:04 -0500 From: Arthur Wiebe artooro at gmail.com Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions flightgear-devel at flightgear.org Message-ID: ca3422f10411101526416b4791 at mail.gmail.com Content-Type: text/plain; charset=US-ASCII g++ -I/usr/X11R6/include -D_REENTRANT -L/fgfs/lib -o layout-test layout-test.o libGUI.a -lsgprops -lsgdebug -lsgstructure -lsgmisc -lsgxml -lplibpw -lplibpu -lplibfnt -lplibul -framework GLUT -framework OpenGL -framework AGL -framework Carbon -lobjc ld: Undefined symbols: fntTexFont::load(char const*, unsigned int, unsigned int) make[2]: *** [layout-test] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1 This is an OpenGL function -- perhaps a 'make clean' in ./src/plib, ./src/simgear, and ./src/flightgear followed by a rebuild would help? You might have obj module/lib conflicts as you've tried at least two build strategies, right? (--with-x and --without-x) Oops, thanks for catching this... No, no, fntTexFont::load(char const*, unsigned int, unsigned int) is a plib function, not an openGL one. It is defined as int fntTexFont::load ( const char *fname, GLenum mag, GLenum min ) in plib/src/fnt.cxx Maybe you have problems with opengl headers and have GLenum not being 'int' ? -Fred That's why I was wondering what Arthur's OpenGL framework looked like. Arthur, at some point you might want to remove all of your changes and see if a standard plib build will work for you. Whatever happened with your config.sub issue, BTW? thanks to both of you... Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear on Mac OS X
Arthur, Makefile.in isn't in CVS. It is generated by automake. GNU Automake - http://www.gnu.org/software/automake Freeware - Generates makefile.in files from makefile.am input files, as part of the official GNU coding standards and build process. Requires GNU autoconf. On Nov 11, 2004, at 9:52 AM, [EMAIL PROTECTED] wrote: are you running ./autogen.sh without an errors? Have you updated aclocal and autoconf also? I just did a make clean and a plib build from cvs and it worked fine under Mac os X (10.6). The rest of the build went ok also (simgear and flightgear) though I had a modified (flightgear) Input/input.cxx and Main/options.cxx. The FlightGear changes are for debugging some things I was looking at at one time... I'm doing a 'make clean install' for SimGear and FlightGear now from latest (1700 GMT) cvs. My plib and simgear are straight from cvs, flightgear and data are straight from cvs (no modified local copies, except for the FlightGear input.cxx and options.cxx files that I mentioned above). Ima Message: 8 Date: Thu, 11 Nov 2004 09:51:09 -0500 From: Arthur Wiebe [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII Since I was getting nowhere trying to build FG 0.9.6 I checked it out from CVS instead. After getting automake 1.9.3 I was able to run autogen.sh and configure but it seems Makefile.in is missing in CVS. configure: creating ./config.status config.status: creating Makefile config.status: error: cannot find input file: Makefile.in That seems hard to believe though although it's true. I have no Makefile.in. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: FlightGear on Mac OS X
OK, cool! So your problem (I trust) is fixed. Thank you for sticking with it and fixing your problem! Tell all your mac friends about FlightGear! Do you think you might be able to modify the mac os x docs for 0.9.6 especially with regard to updating make tools for a successful source build? I'm sure that you are not the first to be burned with this issue. I remember having problems with another open source project (not flightgear) that required me to update make tools -- the problem usually isn't obvious -- at least to me it isn't. There's one good thing, you shouldn't have to update make tools for a few years at least. 8-) In turns out that it was using an old version of aclocal (1.6.3) and the new version of automake (1.9.3) and autoconf (1.59). So I removed the old version of aclocal so it would use v1.9.3 and now it works again. Yeah, I dropped fink when I went to Mac os x.2 (Jaguar). It sounds like a great idea for open source on mac os x, but I finally decided it was more trouble than it was worth. The above is why I don't use Fink anymore. best regards, Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Building FlightGear on Mac OSX
On Nov 9th, 2004, Adam wrote: I have been trying to build FlightGear 0.96 (CVS) on a Mac, and have been using fgdev, and have followed the instructions in the FG users guide, as well as the instructions included in fgdev, but I have run into a bunch of problems. Any help that anyone can offer would be greatly appreciated. I have searched the lists and see that some others have had some of the same problems, but I have not found postings of solutions. I guess that the instructions for building on a Mac in the users guide are somewhat out of date. I am using OSX 10.3.5 and I have Xcode 1.5 installed (gcc 3.3 and gcc 2.95.2). The insructions say to use gcc 2.95, so I have started with that. I also am using tcsh as instructed (which is no longer the Mac default). First I found that by default I already had the versions of automake and autoconf that the instructions say to build, so I did not do that. (1.6.3 and 2.53 respectively) I had trouble getting plib to build, but, after a few changes, got it to compile. What problems did you have please? How did you fix them? The instructions next call for building metakit, but I assume that is now included in SimGear? metakit is not needed anymore. it was replaced by something else, I'm afraid that I can't remember what 8-( I think it's built into simgear, however, and not external. Someone please correct me if I'm wrong... Building SimGear failed with gcc 2.95. When I switched to 3.3 it got much further, but failed on testserial. I was hoping that this is not critical. So next I tried to build FlightGear itself: ./configure --prefix=$BUILDDIR --without-threads --without-x configure: error: cannot run /bin/sh ./config.sub What is your BUILDDIR value set to? It should be the path to the fg build tree (mine is /flightgear/fgdev9.6) I will be happy to try to help, health permitting -- November is shaping up to be a bad month as it's turning colder -- but please give some more info regarding the exact errors that you're hitting. You may or may not have in fact gotten past them. If plib is not built right, then all bets are off as to whether you'll succesfully build the rest. I found that the reason is that config.sub does not exist. I have config.sub in ./src/FlightGear, ./src/plib and ./src/SimGear I didn't check all of them but config.sub in src/FlightGear is a link to: lrwxrwxrwx 1 ima staff 34 19 Jun 2003 src/flightgear/config.sub - /usr/share/automake-1.6/config.sub are you sure you've got automake installed right? This is NOT something that seems to be touched on every build... My src/FlightGear file has the following timestamp inside it: timestamp='2002-07-03' Shouldn't autogen.sh create this file? Did I do something wrong? (I see that someone else had the same problem and posted to the mailing list, but I could not find a response). So, where I think I stand is: I have plib, I think that I have SimGear? I have downloaded and installed OpenAL and I can't get FG itself to even start to compile. Thanks, -- Adam Here are my build scripts (I build from the command line, I think that others on the list have FG building from XCode but I haven't done this: cat makeplib.sh makesg.sh makefg.sh cd $BUILDDIR/src/plib ./autogen.sh ./configure --prefix=$BUILDDIR make install cd $BUILDDIR/src/SimGear ./autogen.sh ./configure --prefix=$BUILDDIR make install cd $BUILDDIR/src/FlightGear ./autogen.sh ./configure --prefix=$BUILDDIR --with-threads --without-x make install echo 'make install' done My GCC version is: gcc --version gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495) Copyright (C) 2002 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I am using mac os x 10.3.6, but did build with 10.5 in the past. I last built plib, simgear and flightgear from CVS on 11/5/04 and had no problems. I am using automake 1.6.3 and autoconf 2.57 Hope this helps. Welcome to the project, FlightGear is a great Mac OS X compatible flight sim. I haven't used X Plane in years even. 8-) This is a great list, with a lot of skilled and helpful people on it... Ima PS -- if you use .sh scripts with tcsh, you'll need to run child scripts via the 'source' command in order to properly pass the environment (including BUILDDIR to the child processes) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: FlightGear on Mac OS X
Arthur I'm glad plib built for you. I only put plib and other flightgear files in a local tree and use --prefix so configure can find them. Also that way, I don't have to worry about old versions of plib that might be on my system somewhere. if you use --prefix with a non-system directory, you can avoid having to use sudo make install for library installation also. Lots of people on the list have run into problems related to old(er) versions of libraries on their systems in multiple paths. I'm sure that I ran into this one before I started using --prefix On Nov 10, 2004, at 2:49 PM, Arthur wrote: Date: Wed, 10 Nov 2004 14:49:32 -0500 From: Arthur Wiebe [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Re: FlightGear on Mac OS X To: FlightGear developers discussions [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII Well... I got simgear configured. Before I didn't specify --prefix for plib or simgear. Now I made a directory called fgfs in / and install plib there and then specified that plib was installed there when configuring simgear and used the same prefix for simgear. Now it worked. This leads me to thinking it was a crazy permissions problem! Well at least it works now and I will be making a Mac OS X installer package for plib 1.8.3 and posting it online for other people like me. Next step is to get simgear and flightgear to compile. I guess you'll hear from me again soon. good luck! Use the same --prefix for plib, simgear and flightgear. Is everything building OK now? Remember you can't mix and match release and CVS versions, either release plib, simgear and flightgear source OR CVS plib, simgear, flightgear source. There is also talk on the list recently about file name collisions on case preserving but not case significant file systems (like cygwin and mac os x). You'll see this when you're downloading the data from cvs under mac os x, if you're using HFS+ as opposed to a *nix file system on your Mac with a few files unless they've been fixed already. Anyway you want CVS plib to have Olivier's great joystick fixes anyway. I'm not sure they're in a release yet. I use the CVS source tree, which a few times a year gets into a non-buildable state for a day or two but is not usually a problem. I don't have Mac os X installs for anything, but one of the other Mac people (Jonathan, perhaps?) had created a Mac os X cocoa executable for FGFS. I don't recall if they had an app for installation, however. I think it was just drag and drop. I don't know if this app has been updated. I'm assuming you no longer need ./lib/libplibXXX and ./include/plib sent to you? 8-) Have fun and please let the list know how it goes. Provided you've got the dependencies installed, the Mac OS X build goes just like any other *nix clone 8-). Hopefully, you'll have no build problems once you're using --prefix. Just remember to build flightgear using ./configure --without-x unless you want to use X11 on mac os x (which is NOT installed by default). There, I think that's all the mac related screwups, I've done 8-) Enjoy the world's best Mac OS X opensource flightsim... Now if someone would just do Washington, DC scenery for flightgear. I used to have a nice DC add-on for XPlane... Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: ..bo!, was: [Flightgear-devel] Back online
Arnt, Wow! OT: Is this the color PDA version of flight gear? 8-) Remember playing lunar lander on hard copy terminals? Imagine playing FG at 30 frames a second. How long would it take to print out 1 second of flight I wonder on a printer terminal using a similar system (without the color, of course)? ..http://sam.zoy.org/projects/libcaca/caca-sabre.png scary enough? ;-) I wonder if I can find a plib/simgear/fg-compatible set of compilers to generate code for my cell phone... Wouldn't THAT be nice! LOVE the graphics! Really takes me back to the dark ages... 8-) Ima Who will go back to lurking now... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Bypass FG Physics and Draw
Does this mean that we would have the ability to save and load flight data so as to reproduce, say, a taxi, take off, pattern and landing at KSFO or another airport automatically (i.e., as a demo or as a training exercise). Perhaps a short flight around the SF area also showing off the new scenery? Could we ship such flights around scenic areas (Mount Ranier, Crater Lake, the Grand Canyon) for new users in the base package or as downloadables off of flightgear.org? How big would such files be? How much data needs to be kept, how much can be calculated on the fly? Do weather conditions need to be saved also? Would flights around scenic areas be done better as flight plans with waypoints or tied into this new playback method somehow? Can this playback tool be used as a training method for new simulator pilots? If we are not saving a real recorded flight, perhaps we can use a similar method to extract either entire flights or the last XX number of seconds of a flight to save to disk for later replay? MS FlightSimulator has an extensive tutorial that involves pre-saved flights which the users can break into at certain points in the flights. How difficult would it be to add something similar to FG and where would one begin (if no one is already working on something like this). Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Flightgear-devel anyone read Polish
Finally, something I can help with! 8-) In much of the world (Poland included) you pay per impulse (about 3 minutes) even for a local call. So downloading can be expensive if you use dialup. They've got 10 copies for sale, buy now for 30 PLN (polish zloties) around 9 USD. A rough translation (2nd have of the page after the auction specifics) below, quoted text is the original Polish: Welcome to my auction I am presenting FlightGear an Ultra realistic flight simulator. Why spend more than 200 zl (about 50 usd or so) for this product, which you can have for much less when flying emotions are the same. The realism of the game permits one to learn the secrets of (plane) flight -- preserving realistic flight physics and control of the plane, there are a lot of planes to chose from. The game offers the possibility of flying practically over the entire globe (see below) FlightGear is a game which is 100% free. You may download it from the internet. You need to download more than 90 mb at once from the internet and there are a lot of extras also. The price which I sell this game for is a sum paid as I downloaded and prepared the game for you. Upon paying to my bank account, I will pay for free shipping. If you buy from me, you get: The game on 1 cd Instructions in English (pdf on the cd) Instalation instructions and Fast Start in Polish Maps of the usa (partial) and Poland and areas to fly in (on the cd) All in a boxed DVD case Witam na mojej aukcji. Przedstawiam FlightGear Ultra realistyczny symulator lotu. Po co wydawa ponad 200z za produkt, ktry mona mie za o wiele nisz cen i do tego emocje z latania s identyczne. Realizm gry pozwala na poznanie tajnikw lotu samolotem z zachowaniem bardzo realistycznej fizyki lotu oraz obsugi samolotu. a jest ich do wyboru pokana ilo. Do tego gra oferuj moliwo latania praktycznie na caej kuli ziemskiej ( o tym niej). FlightGear to gra ktra jest w 100% darmowa. Moesz j scign z internetu, Tylko e scignicie ponad 90Mb na raz z internetu to nie lada wyczyn a do tego dochodz rne inne dodatki. Cena, za ktr sprzedaj t gr to suma dziki ktrej j scignoem i przygotowaem te gr dla Ciebie, Przy w pacie na konto przesyka gratis . Jeli kupisz u mnie t gr, dostaniesz : * Gra na jednym 1CD * Instrukcja w wersji angielskiej (PDF na pycie) * Instrukcja instalacji oraz szybkiego startu gry w jez. Polskim * Mapy USA(cze), Polski i okolic do latania (na pycie) * wszystko w pudeku DVD case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Fix for build break with New AIBase.cxx (mac os x and cygwin)
The fix is attached, could someone please check it into CVS if it is appropriate? I am attempting to build source from 16:00 GMT under Mac OS X.3 with compiler gcc --version gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495) Copyright (C) 2002 Free Software Foundation, Inc. I am getting the following build break building flightgear. I have also downloaded new plib and simgear and they build with no problems, and with no warnings even in simgear/props. But when I try to use the downloaded source to build fg, I get the following build break: g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/Users/ima/Desktop/FlightGear/fgdev9.4/include -g -O2 -D_REENTRANT -c -o AIBase.o `test -f 'AIBase.cxx' || echo './'`AIBase.cxx AIBase.cxx: In member function `virtual void FGAIBase::bind()': AIBase.cxx:122: error: no matching function for call to ` SGRawValueMethodsFGAIBase, double::SGRawValueMethods(FGAIBase, unknown type, unknown type)' /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 391: error: candidates are: SGRawValueMethodsFGAIBase, double::SGRawValueMethods(const SGRawValueMethodsFGAIBase, double) /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 396: error: SGRawValueMethodsC, T::SGRawValueMethods(C, T (C::*)() const = 0, void (C::*)(T) = 0) [with C = FGAIBase, T = double] AIBase.cxx:127: error: no matching function for call to ` SGRawValueMethodsFGAIBase, double::SGRawValueMethods(FGAIBase, unknown type, unknown type)' /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 391: error: candidates are: SGRawValueMethodsFGAIBase, double::SGRawValueMethods(const SGRawValueMethodsFGAIBase, double) /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 396: error: SGRawValueMethodsC, T::SGRawValueMethods(C, T (C::*)() const = 0, void (C::*)(T) = 0) [with C = FGAIBase, T = double] AIBase.cxx:131: error: no matching function for call to ` SGRawValueMethodsFGAIBase, double::SGRawValueMethods(FGAIBase, unknown type, unknown type)' /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 391: error: candidates are: SGRawValueMethodsFGAIBase, double::SGRawValueMethods(const SGRawValueMethodsFGAIBase, double) /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 396: error: SGRawValueMethodsC, T::SGRawValueMethods(C, T (C::*)() const = 0, void (C::*)(T) = 0) [with C = FGAIBase, T = double] AIBase.cxx:135: error: no matching function for call to ` SGRawValueMethodsFGAIBase, double::SGRawValueMethods(FGAIBase, unknown type, unknown type)' /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 391: error: candidates are: SGRawValueMethodsFGAIBase, double::SGRawValueMethods(const SGRawValueMethodsFGAIBase, double) /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 396: error: SGRawValueMethodsC, T::SGRawValueMethods(C, T (C::*)() const = 0, void (C::*)(T) = 0) [with C = FGAIBase, T = double] AIBase.cxx:151: error: no matching function for call to ` SGRawValueMethodsFGAIBase, bool::SGRawValueMethods(FGAIBase, unknown type)' /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 391: error: candidates are: SGRawValueMethodsFGAIBase, bool::SGRawValueMethods(const SGRawValueMethodsFGAIBase, bool) /Users/ima/Desktop/FlightGear/fgdev9.4/include/simgear/props/props.hxx: 396: error: SGRawValueMethodsC, T::SGRawValueMethods(C, T (C::*)() const = 0, void (C::*)(T) = 0) [with C = FGAIBase, T = bool] make[2]: *** [AIBase.o] Error 1 make[1]: *** [install-recursive] Error 1 make: *** [install-recursive] Error 1 'make install' done These resolve to the following aimodal/AIBase.cxx source lines: props-tie(velocities/vertical-speed-fps, SGRawValueMethodsFGAIBase,double(*this, FGAIBase::_getVS_fps, FGAIBase::_setVS_fps)); 122 props-tie(position/altitude-ft, SGRawValueMethodsFGAIBase,double(*this, FGAIBase::_getAltitude, FGAIBase::_setAltitude)); 126 props-tie(position/latitude-deg, SGRawValueMethodsFGAIBase,double(*this, FGAIBase::_getLatitude, FGAIBase::_setLatitude)); 131 props-tie(position/longitude-deg, SGRawValueMethodsFGAIBase,double(*this, FGAIBase::_getLongitude, FGAIBase::_setLongitude)); 135 props-tie(controls/lighting/nav-lights, SGRawValueMethodsFGAIBase,bool(*this, _isNight)); 151 The following changes fix the problem on
[Flightgear-devel] re: Fix for build break with New AIBase.cxx (mac os x and cygwin)
Oops! Forgot 4 important things. Try this one instead:
AIBase.cxx
Description: Binary data
(as follows):
void FGAIBase::bind() {
double (FGAIBase::*pgVS_fps) () const;
void (FGAIBase::*psVS_fps) ( double );
double (FGAIBase::*pga) () const ;
void (FGAIBase::*psa) ( double ) ;
double (FGAIBase::*pgLat) () const ;
void (FGAIBase::*psLat) ( double ) ;
double (FGAIBase::*pgLong) () const ;
void (FGAIBase::*psLong) ( double ) ;
bool (FGAIBase::*piN) () const;
pgVS_fps = FGAIBase::_getVS_fps ;
psVS_fps = FGAIBase::_setVS_fps ;
pga = FGAIBase::_getAltitude ;
psa = FGAIBase::_setAltitude ;
pgLat = FGAIBase::_getLatitude ;
psLat = FGAIBase::_setLatitude ;
pgLong = FGAIBase::_getLongitude ;
psLong = FGAIBase::_setLongitude ;
piN = FGAIBase::_isNight ;
props-tie(id, SGRawValuePointerint(id));
props-tie(velocities/true-airspeed-kt,
SGRawValuePointerdouble(speed));
props-tie(velocities/vertical-speed-fps,
SGRawValueMethodsFGAIBase,double(*this,
pgVS_fps,
psVS_fps));
props-tie(position/altitude-ft,
SGRawValueMethodsFGAIBase,double(*this,
pga,
psa ));
props-tie(position/latitude-deg,
SGRawValueMethodsFGAIBase,double(*this,
pgLat,
psLat));
props-tie(position/longitude-deg,
SGRawValueMethodsFGAIBase,double(*this,
pgLong,
psLong ));
props-tie(orientation/pitch-deg,
SGRawValuePointerdouble(pitch));
props-tie(orientation/roll-deg,
SGRawValuePointerdouble(roll));
props-tie(orientation/true-heading-deg,
SGRawValuePointerdouble(hdg));
props-tie(radar/bearing-deg,
SGRawValuePointerdouble(bearing));
props-tie(radar/elevation-deg,
SGRawValuePointerdouble(elevation));
props-tie(radar/range-nm, SGRawValuePointerdouble(range));
props-tie(radar/h-offset,
SGRawValuePointerdouble(horiz_offset));
props-tie(radar/v-offset,
SGRawValuePointerdouble(vert_offset));
props-tie(radar/x-shift, SGRawValuePointerdouble(x_shift));
props-tie(radar/y-shift, SGRawValuePointerdouble(y_shift));
props-tie(radar/rotation, SGRawValuePointerdouble(rotation));
props-tie(controls/lighting/nav-lights,
SGRawValueMethodsFGAIBase,bool(*this, piN));
props-setBoolValue(controls/lighting/beacon, true);
props-setBoolValue(controls/lighting/strobe, true);
}
Sorry for the trouble!
Ima___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] two questions about joysticks and flightgear
js_demo returns the following values for my MacAlly joystick on mac os x 10.3.3 JS.0 Axis 0: Ailerons (-0.5 to +0.4) Axis 1: Elevator (-0.5 to +0.5) Axis 2: Throttle (-1 to +0.0) Axis 3: Horiz. Hat (-1.0 to +1.0) Axis 4: Vert. Hat (-1.0 to +1.0) Q1: How can I use the above information to figure out what values should go in my xml file? I've been looking at data/Docs/README.Joystick.html, but I am probably missing something obvious. How can I calculate what the factor should be: when I move the stick, it only moves about 1/8th of the way down the HUD even when I'm yanking the stick all of the way back/forward/whatever. Changing the factor to 5, 20, 100 doesn't seem to change anything for me. Also the throttle can only change between 50% and 100% throttle via the joystick, nothing I change in the XML file seems to have any effect. Q2: Is there documentation on the Nasal information? What needs to be done to use nasal to control the joystick as shown below (from the default joystick)? Is this the official way to go now for joysticks? axis n=2 descThrottle/desc binding commandnasal/command scriptcontrols.throttleAxis()/script /binding /axis I am using the following .xml file for my sort-of working joystick: ?xml version=1.0? !-- Setup for a MacALLY USB iStick joystick with one stick, one wheel, one digital hat, and four buttons. Layout: Axis 0: ailerons Axis 1: elevator Axis 2: throttle Hat: Axes 3 and 4 Button 0: brakes (front button) Button 1: center rudder (side button) Button 2: trim up Button 3: trim down -- PropertyList nameMacAlly USB Joystick /name axis n=0 descAileron/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/aileron/property offset type=double0.0/offset factor type=double1.0/factor !-- 1.0 -- /binding /axis axis n=1 descElevator/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/elevator/property offset type=double0.0/offset factor type=double1.0/factor /binding /axis axis n=2 descThrottle/desc binding commandproperty-scale/command property/controls/flight/engines/engine[3]/throttle/property offset type=double-1.0/offset !-- -1.0 -- factor type=double-0.5/factor !-- -0.5 -- /binding /axis axis n=3 descRudder/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/rudder/property offset type=double0.0/offset !-- -1.0 -- factor type=double1.0/factor !-- -0.5 -- /binding /axis !-- axis n=0 descAileron/desc binding commandproperty-scale/command property/controls/flight/aileron/property squared type=booltrue/squared /binding /axis axis n=1 descElevator/desc binding commandproperty-scale/command property/controls/flight/elevator/property factor type=double-1.0/factor squared type=booltrue/squared /binding /axis axis n=2 descThrottle/desc binding commandnasal/command scriptcontrols.throttleAxis()/script /binding /axis -- button n=0 descBrakes/desc binding commandproperty-assign/command property/controls/gear/wheel[0]/brake/property value type=double1.0/value /binding binding commandproperty-assign/command property/controls/gear/wheel[1]/brake/property value type=double1.0/value /binding binding commandproperty-assign/command property/controls/gear/wheel[2]/brake/property value type=double1.0/value /binding mod-up binding commandproperty-assign/command property/controls/gear/wheel[0]/brake/property value type=double0.0/value /binding binding commandproperty-assign/command property/controls/gear/wheel[1]/brake/property value type=double0.0/value /binding binding commandproperty-assign/command property/controls/gear/wheel[2]/brake/property value type=double0.0/value /binding /mod-up /button button n=1 descElevator trimup/desc repeatabletrue/repeatable binding commandproperty-adjust/command property/controls/flight/flaps/property step type=double0.001/step /binding /button button n=2 descCenter rudder/desc binding commandproperty-assign/command property/controls/flight/rudder/property value type=double0.0/value /binding /button button n=3 descElevator trim down/desc repeatabletrue/repeatable binding commandproperty-adjust/command property/controls/flight/elevator-trim/property step type=double0.001/step /binding /button /PropertyList !-- end of MAUSBJS.xml --
[Flightgear-devel] re: two questions about joysticks and flightgear
ima.sudonim wrote: Axis 0: Ailerons (-0.5 to +0.4) Axis 1: Elevator (-0.5 to +0.5) Axis 2: Throttle (-1 to +0.0) These three all indicate what appears to be a calibration error. Calibration error? Is this a problem internal to the joystick? In the way plib or fg processes the joystick info? By convention, all axes have always reported between -1 and 1. OK, so calibration error means that the axis range is not between -1 and 1, if I am understanding correctly. And that's why I thought that offset +0.5, factor +2.0 should work for the throttle And that offset +0.0, factor +2.0 should work for Ailerons and Elevator, but it doesn't seem to work that way. It makes no change to how flightgear seems to be using the joystick. Here's the new axes values from the xml file (the comments contain what fgjs suggested): axis n=0 descAileron/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/aileron/property offset type=double+0.0/offset !-- 0.0 -- factor type=double+2.0/factor !-- 1.0 -- /binding /axis axis n=1 descElevator/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/elevator/property offset type=double+0.0/offset!-- 0.0 -- factor type=double2.0/factor !-- 1.0 -- /binding /axis axis n=2 descThrottle/desc binding commandproperty-scale/command property/controls/engines/engine/throttle/property offset type=double+0.5/offset !-- -1.0 -- factor type=double+2.0/factor !-- -0.5 -- /binding This joystick is still not working properly. 8-( Q2: Is there documentation on the Nasal information? What needs to be done to use nasal to control the joystick as shown below (from the default joystick)? Is this the official way to go now for joysticks? There isn't much written documentation for the input system specifically (Nasal documentation in general is at http://plausible.org/nasal and http://plausible.org/nasal/flightgear.html). For the most part, you can simply copy what you see in other joystick files. Great! I'll look into the nasal info that you mention. Thank you! Ima Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] re: two questions about joysticks and flightgear
Andy, thanks, I'll see if I can get support from Apple. Actually my usb joystick HAS calibration both horizontal and vertical, but it simply sets the middle point of the handle. It is two dials (much like the throttle axes), and I've centered the stick using the HUD's indicators. ima.sudonim wrote: Calibration error? Is this a problem internal to the joystick? In the way plib or fg processes the joystick info? It is a problem with your joystick. Analog sticks have, since the beginning of time, varied widely in the voltages they report to the gameport. So DOS games always had a calibrate joystick option to figure out what dynamic range really is. Modern drivers still have this option, although I haven't personally seen a USB stick that required any calibration (others swear they have, though). The bottom line is that this is a driver/OS issue. While you can fix it in FlightGear by mucking with the XML, you really shouldn't have to. But if I CAN fix it with XML, why isn't the XML code in the file being accepted and having any effect in FG? What part of FG/SG processes the xml file and sets the properties for the joystick? When I browse FG internal properties for the joystick, it has the following for: /input/joysticks/js/axis/binding/ command[0] = 'property-scale' (unspecified) property[0] = '/controls/flight/aileron' (unspecified) squared[0] = 'true' (bool) /input/joysticks/js/axis[1]/binding/ command[0] = 'property-scale' (unspecified) factor[0] = '-1.00' (double) property[0] = '/controls/flight/elevator' (unspecified) squared[0] = 'true' (bool) /input/joysticks/js/axis[2]/binding/ command[0] = 'nasal' (unspecified) script[0] = 'controls.throttleAxis()' (unspecified) So why is the above nothing like the XML file which reads: axis n=0 descAileron/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/aileron/property offset type=double+0.0/offset!-- 0.0 -- factor type=double+2.0/factor!-- 1.0 -- /binding /axis axis n=1 descElevator/desc dead-band type=double0.02/dead-band binding commandproperty-scale/command property/controls/flight/elevator/property offset type=double+0.0/offset!-- 0.0 -- factor type=double2.0/factor !-- 1.0 -- /binding /axis axis n=2 descThrottle/desc binding commandproperty-scale/command property/controls/engines/engine/throttle/property offset type=double+0.5/offset !-- -1.0 -- factor type=double+2.0/factor !-- -0.5 -- /binding And why is the rudder axis missing? I'm sure that I'm missing something obvious here, but I just can't see it! Argh! It is the job of the operating system to tell you what the physical position of the stick is in correct units. Hunt for a joystick preferences or control applet somewhere. I can't find prefs or applet for the joystick nor even a generic one for usb (using mac os x (10.3)). Nuts, ANOTHER usb problem 8-) Thanks, Ima Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] re: two questions about joysticks and flightgear
ima.sudonim wrote: So why is the above nothing like the XML file which reads: [...] And why is the rudder axis missing? I'm sure that I'm missing something obvious here, but I just can't see it! Argh! As an immediate guess, I'd say it's because you're editing the wrong XML file. Eureka! I wasn't editing the wrong XML file, I was giving it the wrong joystick name! The name needed to be MacALLY USB Joystick . I had of course MacAlly USB Joystick . User error! 8-( Of course, js_demo was telling me the right name, I just ignored it for some reason. I had to swap the throttle and elevator axes to get them the way that I want, but things are working much better now! Even the hats are working (thanks, Olivier!)... The name matching is a little tricky: it needs to match very tricky 8-) exactly, otherwise you end up with the default joystick.xml file (which, suspiciously, lacks a rudder definition). You are SO RIGHT! That WAS the default joystick.xml file being loaded... I would have never guessed so I'm very glad you told me grin Your comments on joystick name case and your comments on needing to convert raw joystick axis values to a -1 to 1 value on an axis was what I needed to get this working. Thanks very much! Ima Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Mac OS Joysticks -- n_mac sounds good to me + js questions
Just a question : what about MacOS ? do they support joysticks ? Mac OS X supports joysticks from 10.2 on. There are also tools like Gamepad Companion from CarvWare and USB Overdrive X that allow you to map keys to joystick controls off topic altert BTW, here's a (year old) review of flightgear on the Mac: http://www.macobserver.com/tip/2003/05/25.1.shtml end off topic alert However, I have been having problems with joysticks under Mac OS X.2 and X.3 I use js_demo from plib and fgjs to verify the joystick, check the joystick name and so forth. I update the appropriate xml files for the joystick(s) in question FG used to show which joysticks it was attempting to match (and which it matched) for all joysticks/rudder pedals etc. upon startup. With all the log file changes, that's no longer displayed by default. How can I turn it on again? Is there particular documentation for logging on certain things (like joysticks found) to the console 8-) without getting everything logged? Now there can be DOZENS of issues here (many of them USER issues 8-( ), but at a minimum it would be nice to see exactly which joystick flightgear is using (and what it thinks the axes are and buttons are) at FG loadtime on the console IMHO. The joystick I'm trying to get it to use is: MacALLY USB Joystick -- yes, PLIB found the extra space so I'm giving it for the matching routine below in name. Perhaps that doesn't need to be done anymore? js_demo shows: got input element... button got input element... button got input element... button got input element... button got input element... axis got input element... axis got input element... hat got input element... axis When I pull back on the stick, js_demo reads Ax:1 +0.4 When I push forward on the stick, js_demo reads Ax: 1 -0.5 Joystick to left gives: Ax: 0 -0.5 Joystick to right gives: Ax: 0 +0.4 The throttle wheel rolled all the way forward gives Ax: 2 -1.0 The throttle wheel rolled all the way back gives Ax: 2 +0.0 Can someone help me translate these values to power and factor types below? In any case, I don't think flightgear is in fact finding my joystick even though plib seems to recognize it as it's name is not show up in the joysticks property list. BTW, I know that having the throttle wheel used to control the rudder is a bit strange, but mac powerbook keyboards don't seem to work very well often for certain flightgear keyboard combination, and some of my favorite airports have that runway in a tunnel problem and I crash a lot if i don't stay perfectly centered (in fairness, I crash a lot even when I do stay centered). Even as it is, the throttle as elevator control only seems to work for left elevator to center -- no right elevator, but again I'm not sure if FG is in fact using the joystick that I think it is. Perhaps because PLIB only sees the throttle wheel in the -1 to 0 range? I would dearly like to have an n_mac section for those axes/buttons that are os dependent, if any. BTW does PLIB support hats, js_demo shows it but doesn't seem to allow anything on the hat to be set to a joystick value. It's entirely possible (even likely) that I'm doing something wrong however. (I know there is a PLIB list and will take it there if this is too off topic for FG) I'd like to also be able to flip views with the hat on the joystick in a perfect world. Does anyone have any experience setting up hats with other joysticks? Lastly, should js modifications go into plib or into fg somewhere? MacALLY USB Joystick.xml file PropertyList nameMacAlly USB Joystick /name axis n=0 descAileron/desc binding commandproperty-scale/command property/controls/flight/aileron/property power type=double6/power /binding /axis axis n=1 descElevator/desc binding commandproperty-scale/command property/controls/flight/elevator/property factor type=double1.0/factor power type=double6/power /binding /axis axis n=2 descRudder/desc low repeatable type=booltrue/repeatable binding commandproperty-adjust/command property/controls/flight/rudder/property step type=double-0.01/step /binding /low high repeatable type=booltrue/repeatable binding commandproperty-adjust/command property/controls/flight/rudder/property step type=double0.01/step /binding /high /axis button n=0 descBrakes/desc binding commandproperty-assign/command property/controls/gear/wheel[0]/brake/property value type=double1.0/value /binding binding commandproperty-assign/command property/controls/gear/wheel[1]/brake/property value type=double1.0/value /binding binding commandproperty-assign/command property/controls/gear/wheel[2]/brake/property value type=double1.0/value /binding mod-up binding commandproperty-assign/command property/controls/gear/wheel[0]/brake/property value type=double0.0/value /binding binding
Re: [Flightgear-devel] isnan()
Mac OS X has You need to include math.h, and link with the standard C library -- libc (-lc) int isinf(double); int isnan(double); int isnanf(float); Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Multiplayer Server RFC -- Current Status
OK, while I'm an avowed lurker, I find that this thread has even more possibilities While I certainly want realistic flight performance of A/C to be the priority (I hope to learn to fly a real plane someday -- probably in my next life 8-( -- and I'd love it if my FG experience could translate to the real world), there ARE non-violent (or at least non-aggressive) reasons for having weapons in FG a) How about an asteroids or missile command-type simulation? These were great games, it would be interesting to tie them into a great simulation like fg. You're defending the Earth, KSFO, whatever from asteriods, missiles, what have you. Maybe even dive bombing pink flamingos, perhaps... (You're the groundskeeper and hate the cleanup after the flamingos leave... No flamingos are actually hurt of course! 8-)) Also for those with frame-rate problems, maybe a Game graphics mode that models everything in the sim fast but not necessarilly prettily. b) How about a game of tag (catch me if you can) with aircraft? (Maybe chasing a small remote control thing or a UFO) (could be weapons or without -- what about paintball or something?) c) Maybe we could create mythological 'aircraft' -- griffons, dragons, etc. and fly them or go after them Or weaponless: Or something like orienteering (follow the path) or even a scavenger hunt (find all the things on this list by flying over it), where there could be a moderator/designer setting things up, possibly real-time If missiles are out, perhaps we can shoot arrows. I don't mean to belittle anyone's beliefs, I'm pro-peace (realistically speaking, who could be pro-war, Genghis Khan?), and think the concept of spending billions on weaponry when children are starving all over the world and dying daily due to lack of imunizations for preventable diseases poor judgment to say the least... Don't even get me started on the atomic/nuclear weapons thing... OK off my soap box. Great sim, hope to help with developing it someday. I love it if we had some name or information in the scenery that could be popped up over, say, a building/landmark when it is visible in the distance. Crater Lake, Berlin wall, Sears tower, RFK stadium, etc. Some of us aren't used to looking at the world from above ground level. There's an MS flightsim add-on that does this, I don't recall the name, landmark, maybe? I'll go back to lurking now Ima An earlier thread mentioned some other things including a Reno race course based game. That would be very interesting. I tend to be in the non-weapons camp. There may be some (not myself) who find it offensive to even have source code included that discusses in weapon terms, so it might be wise to bring up an RFC thread on that when the time comes. It seems to me that generic the FDM and AI functions that have been discussed here could serve as an underlying layer for the type of things that both John and Lee mentioned. Perhaps these specific applications like a Reno race game, search and rescue, and combat features could be handled as seperate pluginable projects that run on top of a multi user simulation layer that has all the capabilities including Jon Berndt's child FDM concept. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Question about dc
Thanks, David, Martin, Erik, Jim and everyone who responded. Looks like I'm having one of those weeks/months/years. 8-) OK, Shift-2 selects magneto for the second engine. Shift-1 the first. Shift-g is lower the gear. dc3 is working fine and is a very nice plane! Next time I promise to re-read the documentation! 8-) Most embarrassingly, I seem to now recall discussions on this list about the very magneto/gear topic not too long ago. I wouldn't mind having no long term memory if I could at least have some short term memory in its place! 8-) Ima David Culp wrote: Even using 2, spacebar only the first engine ever starts... Are you using shift-2? That selects the second engine. Also, try shift-G to raise the wheels. shift+G is lowering the landing gear. g is raising the gear. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] How was I able to fly underground?
I was flying with the fokker50 around dc. I attempted to land when suddenly I was underground and still flying. (The buildings where visible above me, the hud altitude info between -600 and -200 depending). I have a ppm file showing a screenshot, but it's 1.4 mb. Please email me if for any reason you'd like to see it. I don't have a convenient web server right now 8-( or i'd leave a link. The potomac was showing up as brownish muck, until I attempted to land when I went through it into blue sky. At least I THINK that's what happened. Using new scenery from Friday as noted in my previous append from yesterday. Very cool, even if unintentional. All these buildings in the sky, was that Star Trek, Star Wars or both? 8-) The new scenery is nice, btw. Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] re: how was I able to fly underground
the more I think about it, the more I like this new feature. I know it's non-realistic, but it's fun! Why not fly underneath the ground. Sometimes the shortest path is thru a mountain (euclidean geometry 2D vs. reimanian (sp?)spherical? Maybe as an option for those of us (ahem) who are still getting the landing thing worked out? Arnt wrote: On Sun, 7 Sep 2003 13:27:43 -0400, Ima Sudonim ima.sudonim at verizon.net > wrote in message 96D4E014-E158-11D7-A2A4-00039398B344 at verizon.net >: >> I was flying with the fokker50 around dc. I attempted to land when >suddenly I was underground and still flying. (The buildings where >visible above me, the hud altitude info between -600 and -200 >depending). I have a ppm file showing a screenshot, but it's 1.4 mb. .. >mail it to me off-list. Curiosity. ;-) Done, btw the screenshot doesn't show long/lat or altitude from the hud. Not sure why... Mac os x.2, plib/flightgear/simgear from 3PM GMT today (Sunday 9/7/2003). Thanks! Ima >> Please email me if for any reason you'd like to see it. I don't have a >convenient web server right now 8-( or i'd leave a link. >>The potomac was showing up as brownish muck, until I attempted to land >when I went through it into blue sky. At least I THINK that's what >happened. Using new scenery from Friday as noted in my previous >append from yesterday. >>Very cool, even if unintentional. All these buildings in the sky, was >that Star Trek, Star Wars or both? 8-) >>The new scenery is nice, btw. >>Thanks! >>Ima >>>___ >>Flightgear-devel mailing list >Flightgear-devel at flightgear.org >http://mail.flightgear.org/mailman/listinfo/flightgear-devel >___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Update on flying underground
reproducible with --aircraft=fokker50-jsbsim in gdb or without, with hud or without Drop gear with 'g' while taxiing or while stopped on the runway or while landing with gear up (once I put the landing gear up on the fokker50, I can't get them down again). Can't reproduce it with 172 or dc3 Kool feature! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Question about dc3
How does one start the second engine in the dc3? Even using 2, spacebar only the first engine ever starts... It doesn't seem to work too well on one engine. Also when starting in the air, the engines are OFF. thanks! ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Question about dc
I tried ~ but it still only seems to start the first (left) engine on the dc3... Imaa Message: 10 Date: 07 Sep 2003 22:38:17 +0100 From: Christopher S Horler [EMAIL PROTECTED] Subject: Re: [Flightgear-devel] Question about dc3 To: FlightGear developers discussions [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain From memory (it's been a few months) you do '~' (to select all engines) and then adjust the mix and hit the starter (space) I can't help you with the air start problem, although I have managed to start the a4 dropping through the sky from less than 1ft. On Sun, 2003-09-07 at 21:41, Ima Sudonim wrote: How does one start the second engine in the dc3? Even using 2, spacebar only the first engine ever starts... It doesn't seem to work too well on one engine. Also when starting in the air, the engines are OFF. thanks! ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: flying underground
HTML thing? Perhaps when I copied and pasted from http://baron.me.umn.edu/pipermail/flightgear-devel/2003-September/021038.html to try to continue the thread? My Mail program doesn't use html (os x.2 mail 1.2.5). I have in the past used outlook to post to the group (mea culpa). Now my outlook address book has [EMAIL PROTECTED] as not accepting html mail so this shouldn't be happening anymore (+ I don't use outlook much). Are you talking about my current posts (this week) or my previous ones? I will be happy to turn off the 'html' think if you can tell me what exactly you're talking about. Do you mean the outlook type of plain text followed by html text? If so, I very much agree, I can't stand that myself. I don't think I'm doing it anymore (at least I hope not! ;-) ). Sorry if I've somehow misunderstood your comments. thanks for your help! Ima On Sunday, September 7, 2003, at 07:21 PM, Arnt Karlsen wrote: On Sun, 7 Sep 2003 17:43:06 -0400, Ima Sudonim [EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]>: Arnt, Thank you. The utility is not on my system (mac os X.2) so I've downloaded the source from sourceforge and will try to build it later. ..and do turn off that html thing in your mail client while on the FG mail lists, the guys _hate_ it. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] two questions about new scenery
Hi, Like the new scenery, but two questions: i) Will the new scenery be available via terrasync? On a clean build from 9/5/03, downloaded at 3 PM GMT, I'm getting some error messages with the new w080n030 from Friday with airport=KDCA. ii) Are these messages just noise? KDCA and KBWI textures seem to look ok... Loading tile /Scenery/w080n30/w077n39/1695817 Loading deferred texture /Scenery/w080n30/w077n38/4r WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/w080n30/w077n38/4r' token = OBJECT_BASE name = 1695817.btg Loading deferred texture /Scenery/w080n30/w077n39/5r WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/w080n30/w077n39/5r' Loading deferred texture /Scenery/w080n30/w077n38/6r WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/w080n30/w077n38/6r' Loading deferred texture /Scenery/w080n30/w077n38/rest WARNING: ssgLoadTexture: Cannot determine file type for '/Scenery/w080n30/w077n38/rest' token = OBJECT name = KBWI.btg thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Question about Mac OS X, FG and latest SimGear
I am having a problem with SimGear when building flightgear. in simgear/screen/extensions.cxx I need to wrap the #ifdef lines within #ifndef __APPLE__ #ifndef WIN32 #include dlfcn.h #else #include windows.h #endif #endif //__APPLE__ Otherwise I get the message that g++ -DHAVE_CONFIG_H -I. -I. -I../../simgear -I../.. -I/Users/ima/Desktop/FlightGear/fgdev9.2/include -g -O2 -D_REENTRANT -c -o extensions.o `test -f 'extensions.cxx' || echo './'`extensions.cxx extensions.cxx:28:19: dlfcn.h: No such file or directory make[3]: *** [extensions.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all] Error 2 make: *** [all-recursive] Error 1 So I downloaded dlcompat, but I don't see dlfcn.h anywhere on my system. Is this file required now for flightgear on macos x? With the #ifdefs out of the picture, simgear builds fine, as does fg. Fink shows the following dlcompat loaded: Information about 1159 packages read in 1 seconds. i dlcompat 20021117-1 Dynamic loading compatibility library i dlcompat-shlibs 20021117-1 shared libraries for dlcompat but I still don't see dlfcn.h. Any ideas what I'm doing wrong? Using mac os x (10.2) with developer tools and plib/simgear and fg/data of Thursday 17:00 GMT. I'd rather not separate my local source from the cvs servers any more than absolutely necessary thanks, Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] problem with a10cl-yasim -- elevator trim error at start
I get the following with --aircraft=a10cl-yasim (a10wl-yasim works fine), YASim SOLUTION FAILURE: Insufficient elevator to trim for approach leave NewTgtAirportInit() I am using base package, flightgear and simgear from about 12 noon gmt Other aircraft (checked 747, a4, sopwithCamel) seem to be ok. Changing altitude doesn't have any effect, the problem still occurs Any ideas why this is suddently appearing? I am using keyboard only, no rudder pedals or joystick. Mac OS X 10.2.4 The plane worked fine a few days ago. Any yasim gurus know how to debug this? Thanks! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] problem with a10cl-yasim -- elevator trim error at start
David, thanks, that fixed it! The a10's a great plane, big engines with a lot of power when not loaded, a good trainer for those of us who don't know what their doing. 8-) The model might not be realistic (I wouldn't know 8-)), but it's fun. Good to have it back! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] EXC_BAD_ACCESS in modified FGFS (on mac os x)
Are there any ways to test MALLOC/NEW within flightgear looking for bad pointer manipulation or allocation problems? (NOT in CVS but local modifications) Is there a way to increase the size of the stack given to fgfs in Mac OS X? I heard of a ulimit command but my machine (10.2.4) doesn't seem to have this. Unsure if stack growing into the heap or vice versa is the problem here. This is a modified version of flightgear of a friend with a mixture of C++ and C pointer manipulation. Any suggestions on how to begin debugging this? They're currently doing the cout/asm (trap) route. The problem seems specific to memory allocation, some local (stack), some via new. He swears that he isn't deleting anything twice. Problem usually occurs soon after the procedure is called and returns (in a call or object allocation immediately following this proc). The pointer work steps through a buffer got from handleBufferRead() (netBufferChannel) I want to stress again the problem is not in cvs code. With the changes commented out, fg comes up fine. Thanks, Ima Program received signal EXC_BAD_ACCESS, Could not access memory. 0x900042c8 in free_list_remove_ptr () (gdb) bt #0 0x900042c8 in free_list_remove_ptr () #1 0x90004cec in szone_malloc () #2 0x90004a64 in malloc_zone_malloc () #3 0x0038ad10 in __builtin_new () #4 0x002ce230 in SGPropertyNode::getChild (this=0xd02b050, name=0xdab0b40 wind-speed-kt, index=0, create=218281072) at props.cxx:871 #5 0x002cce18 in find_node (current=0xd02b050, [EMAIL PROTECTED], position=2, create=true) at props.cxx:305 #6 0x002cce28 in find_node (current=0xb9f1d40, [EMAIL PROTECTED], position=1, create=true) at props.cxx:306 #7 0x002d15ac in SGPropertyNode::getNode (this=0xb9f1d40, relative_path=0x3a9ad8 /environment/wind-speed-kt, create=true) at props.cxx:1725 #8 0x002d1d90 in SGPropertyNode::tie (this=0x4318010, relative_path=0xdf34ae0 , [EMAIL PROTECTED], useDefault=true) at props.cxx:1993 #9 0x002a19dc in FGEnvironmentMgr::bind (this=0x4355100) at ../../src/Main/fg_props.hxx:498 #10 0x000225a8 in fgInitSubsystems () at fg_init.cxx:1595 #11 0x5f38 in fgIdleFunction () at main.cxx:1316 #12 0x94fc13c0 in -[GLUTApplication run] () #13 0x94fd9830 in glutMainLoop () #14 0x8b08 in fgMainInit (argc=2, argv=0xb008) at main.cxx:1725 #15 0x8c80 in main (argc=2, argv=0xb158) at main.cxx:1817 #16 0x1f7c in _start (argc=2, argv=0xb158, envp=0xb164) at /SourceCache/Csu/Csu-45/crt.c:267 #17 0x1dfc in start () ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] James/Darrell: plib macos x 10.2 -- SL and JS
James, Sorry, your PLIB JS fixes are working great. I also had the -framework problems, but forget I'd updated the makefile to fix them so a new config.ac would be nice eventually but I so far am remembering to update things. I also needed to make the changes for flightgear (fgfs and js_demo/fgjs makefile). Darrell, while the new PLIB with JS fixes is working great, sound is breaking up with the cvs SL. I take it that I still need to run with your SL code from your mac x build kit. I seem to have accidentally erased your sl.tar.gz changes for macos x. Is there someplace to get them separately, or should I download your macos x build changes file again? Are there any plib sl changes recently that might have hit your sl code? thanks to both of you for great work! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Question about METAR updates
Is it possible to use a metar file to give flightgear the current weather conditions for the world. Are there special setup or options required to set this up? Are there any mac os x compatible apps (java probably ok, too) to download metar info periodically (from http://weather.noaa.gov/weather/metar.shtml ) so that flightgear can (possibly) use it? Thanks, Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] OT: question about Atlas build - missing files on MacOS X
I can't find any information on building Atlas from CVS to use with
flightgear. I've modified configure.ac to get past autogen.sh and
configure. I have the following build problems.
LoadPng.o: Where/what is png.h
MapMaker.o: What is dirent.h? The problem is the uint parts of this
struct
struct dirent {
u_int32_t d_fileno; /* file number of entry */
u_int16_t d_reclen; /* length of this record */
u_int8_t d_type; /* file type, see below */
u_int8_t d_namlen; /* length of string in d_name */
#ifdef _POSIX_SOURCE
char d_name[255 + 1]; /* name must be no longer than this */
#else
#define MAXNAMLEN 255
char d_name[MAXNAMLEN + 1]; /* name must be no longer than this */
#endif
};
OutputGL.o: where's all this stuff defined?
I am using MacOS 10.3 with 12/2002 dev tools, gcc 2.95, latest plib, fg
from cvs, simgear is recent
thank you, Ima
make all-recursive
Making all in data
make[2]: Nothing to be done for `all'.
source='LoadPng.cxx' object='LoadPng.o' libtool=no \
depfile='.deps/LoadPng.Po' tmpdepfile='.deps/LoadPng.TPo' \
depmode=gcc /bin/sh ../depcomp \
g++ -DHAVE_CONFIG_H -I. -I. -I/Desktop/FlightGear/fgdev9.1/include
-DFGBASE_DIR=\/Desktop/FlightGear/fgfsbase\ -g -O2 -c -o LoadPng.o
`test -f 'LoadPng.cxx' || echo './'`LoadPng.cxx
LoadPng.cxx:24: png.h: No such file or directory
make[2]: *** [LoadPng.o] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
g++ -DHAVE_CONFIG_H -I. -I. -I/Desktop/FlightGear/fgdev9.1/include
-DFGBASE_DIR=\/Desktop/FlightGear/fgfsbase\ -g -O2 -c -o MapMaker.o
`test -f 'MapMaker.cxx' || echo './'`MapMaker.cxx
In file included from /usr/include/dirent.h:64,
from MapMaker.cxx:24:
/usr/include/sys/dirent.h:73: syntax error before `;'
/usr/include/sys/dirent.h:74: syntax error before `;'
/usr/include/sys/dirent.h:75: syntax error before `;'
/usr/include/sys/dirent.h:76: syntax error before `;'
make: *** [MapMaker.o] Error 1
[:src/atlas/src] root# make ./MapPS.o
[:src/atlas/src] root# make ./OutputGL.o
source='OutputGL.cxx' object='OutputGL.o' libtool=no \
depfile='.deps/OutputGL.Po' tmpdepfile='.deps/OutputGL.TPo' \
depmode=gcc /bin/sh ../depcomp \
g++ -DHAVE_CONFIG_H -I. -I. -I/Desktop/FlightGear/fgdev9.1/include
-DFGBASE_DIR=\/Desktop/FlightGear/fgfsbase\ -g -O2 -c -o OutputGL.o
`test -f 'OutputGL.cxx' || echo './'`OutputGL.cxx
OutputGL.cxx: In method `void OutputGL::closeOutput()':
OutputGL.cxx:76: `png_structp' undeclared (first use this function)
OutputGL.cxx:76: (Each undeclared identifier is reported only once
OutputGL.cxx:76: for each function it appears in.)
OutputGL.cxx:76: parse error before `='
OutputGL.cxx:78: `png_ptr' undeclared (first use this function)
OutputGL.cxx:81: `png_infop' undeclared (first use this function)
OutputGL.cxx:81: parse error before `='
OutputGL.cxx:82: `info_ptr' undeclared (first use this function)
OutputGL.cxx:84: `png_infopp' undeclared (first use this function)
OutputGL.cxx:84: parse error before `0'
OutputGL.cxx:88: implicit declaration of function `int setjmp(...)'
OutputGL.cxx:89: implicit declaration of function `int
png_destroy_write_struct(...)'
OutputGL.cxx:94: implicit declaration of function `int png_init_io(...)'
OutputGL.cxx:95: `PNG_COLOR_TYPE_RGB' undeclared (first use this
function)
OutputGL.cxx:96: `PNG_INTERLACE_NONE' undeclared (first use this
function)
OutputGL.cxx:96: `PNG_COMPRESSION_TYPE_DEFAULT' undeclared (first use
this function)
OutputGL.cxx:97: `PNG_FILTER_TYPE_DEFAULT' undeclared (first use this
function)
OutputGL.cxx:97: implicit declaration of function `int
png_set_IHDR(...)'
OutputGL.cxx:98: implicit declaration of function `int
png_write_info(...)'
OutputGL.cxx:100: `png_byte' undeclared (first use this function)
OutputGL.cxx:100: `row_pointers' undeclared (first use this function)
OutputGL.cxx:100: parse error before `*'
OutputGL.cxx:102: parse error before `)'
OutputGL.cxx:106: implicit declaration of function `int
png_write_image(...)'
OutputGL.cxx:110: implicit declaration of function `int
png_write_end(...)'
make: *** [OutputGL.o] Error 1
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Question about Mac os X 10.2 fg development
Is the new version of PLIB required or optional for the fg source downloaded from cvs by the latest changes? Are there any changes to the SL directory that are required by flightgear? Also, does anyone know where I can find Atlas (specifically the atlas viewer) binaries to work with fg? Or whether I can use the opengl and GLUT support in macos x 10.2 with atlas source from atlas.sourceforge.net? The atlas configure script can't seem to find it and I don't know how to point it in the right direction (building from the command line using gcc 2.95) Thanks, Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] question about vfr add-on
I recently saw an ad for ez-landmark. It has a database listing significant scenery objects that can be used to identify landmarks for VFR inFS 2k2. There is more information available at: http://www.abacuspub.com/ezlandmark/ How difficult would it be to add something similar to FlightGear? Is anyone considering such a thing already? It sounds like a useful tool. Thanks! Ima
[Flightgear-devel] Norman and others: what code editors do ya'll recommend
I have found a nice command line AND X programming editor called WPE/XWPE (Window Programming Environment) on sunsite. It has its faults, but is quite nice overall, with build integration and editing via error message. Still looking for other programming editors (corporate or open source) that you might recommend. Only caveat is I'm looking for one that supports Macos X or X Window (or both, in a perfect world). Thank you! Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] Norman and others: what code editors do ya'll recommend
On Thursday, June 20, 2002, at 01:19 PM, ima sudonim wrote: I got VIM (that's a GREAT tutorial that came with), joe (a wordstar klone -- I used to use Borland sidekick tsr to do my compiles so I don't have to memorize the commands at least), nedit give errors: NEdit: Locale not supported by C library. NEdit: Using C locale instead. NEdit: Can't open display X is screwed up, giving: [localhost:plib_examples-1.4.1/src/js] root# startx -quartz XFree86 Version 4.1.0 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 2001 If the server is older than 6-12 months, or if your hardware is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/FAQ) Operating System: Darwin Display mode: IOKit Fatal server error: Failed to connect as window server! Quit the Mac OS X window server or use the -quartz option. OsVendorFatalError AbortDDX Quitting XDarwin... giving up. xinit: No such file or directory (errno 2): unable to connect to X server xinit: No such process (errno 3): Server error. [localhost:plib_examples-1.4.1/src/js] root# Using BBEDIT lite but also unsure if it can do the compile error/edit thing... Slickedit BSD version won't install on macos x, they're not making a macos x version at this time. None of these afaik alow me to jump right into an edit session from a compiler error or warning msg. Am I missing something in my setup or is there a magic keypress in these editors to do this? TIA, ima I'd like to have something that I could set up to do my compiles, go from errors straight to an editing session at the point of error. Find in file like grep or the ability to call an external command like grep would be great too. It would either have to be open source, or macos x compatible to work for me. A powerful c-like macro editor would be a plus... 8-) I've heard of something called joe, but think that it requires a library that I can't get on macos x. Any other suggestions? I would really recommend Project Builder, which I would expect that you already have installed. There is an effort ongoing to try to get FlightGear to build natively under Project Builder, bit I have been having some problems with my hand-build projects (more talented people than I are working on getting the autoconfig to generate the project files). You could try using Project Builder's legacy interface and see if it fits the bill. http://developer.apple.com/techpubs/macosx/Darwin/PortingUNIX/compiling/Building_Le_ect_Builder. html The link is out of date, i think, but I'll look into it. I haven't given it a try, but I may be doing so. Some questions I have concerning the legacy interface is that I cannot generate Frameworks or .app wrappers, unless the underlying makefile does so. Jonathan Polley ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Norman and others: what code editors do ya'll recommend
I really have to learn to type eventually 8-( --- Norman, I'm glad that you brought that up (it was my next question): What code editors do people recommend using? I can sort-of use vi, the one time I started emacs, I couldn't exit the darn thing. I'm evaluating a lite version of bb edit, but I don't mind command line type apps (used to use slick edit for dos on another os 8-)). I'd like to have something that I could set up to do my compiles, go from errors straight to an editing session at the point of error. Find in file like grep or the ability to call an external command like grep would be great too. It would either have to be open source, or macos x compatible to work for me. A powerful c-like macro editor would be a plus... 8-) I've heard of something called joe, but think that it requires a library that I can't get on macos x. Any other suggestions? TIA, Ima Check your editor's help file for 'multi-file grep' or 'multi-file search' IMHO this is an indispensible editor feature for developing 'large' projects and most 'good' code editors have this feature builtin so you don't have to resort to using commandline tools directly. Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] more problems with --aircraft and joystick on macos
./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=dc3-yasim ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=wrightFlyer1903-v1-nl-uiuc ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=a4-yasim ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=747-uiuc ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=x24b ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=c182 ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=c310 ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination --aircraft=ufo ./fly.sh --airport-id=KDCA --enable-anti-alias-hud --enable-auto-coordination fly is a script that runs bin/fgfs with the appropriate --fg-root x15,x24b seem to work, couldn't fly via keyboard, change views, activate hud, did nothing but climb c182 works well c310, shuttle seem to work, couldn't fly via keyboard ufo is cool, managed to get it off of the ground c172 seems to work, couldn't fly via keyboard 747-yasim, dc3-yasim, wrightFlyer1903-v1-nl-uiuc, 747-uiuc, beech99-uiuc HANG (wait mouse pointer that never goes anywhere, menus don't work, Esc doesn't quit app) I found an app called BroadbandOptimizer for Macos X that I installed. It enabled me to get some of the above planes working by tweeking my OS's performance. Until I used this, nothing worked! The joystick issue seems a macos xthing. I've tried two joysticks (one of which works 8-) on macos 9), and neither do anything on macos X. Macos X's HIDManager seems totally screwed up. 1) Does anyone out there know how to get a usb joystick working on macos X? Any other HIDManagers for macos x out there? Any flight joysticks (with twisting rudder on stick or separate rudder/throttle control) that work on macos x? That have their own drivers? 2) Any hints on how to fly without a joystick? Neither mouse nor keyboard seems to be working for me 8-) Even with --enable-auto-coordination. I've checked the faq, but as soon as the plane gets airborn it wobbles from one said to the other. BTW, cool anti-crash feature, but how can I disable it? 8-D TIA Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] more problems with --aircraft and joystick on macos
ima sudonim [EMAIL PROTECTED] said: 1) Does anyone out there know how to get a usb joystick working on macos X? Any other HIDManagers for macos x out there? Any flight joysticks (with twisting rudder on stick or separate rudder/throttle control) that work on macos x? That have their own drivers? I don't know the answer. If you don't get any response here you might try contacting the guy at usboverdrive.com as I'm sure he can tell you. OK, I'll give that a try, thanks... 2) Any hints on how to fly without a joystick? Neither mouse nor keyboard seems to be working for me 8-) The joystick is easiest. I'd give the mouse second. If you right click until the cross hair cursor shows up (which indicates the mouse is now controlling the flight) then moving the mouse forward/back will control the elevator and left/right the ailerons. You'll need to right click again to get back to the mouse arrow back for menu mode. OK, the right button click (ctrl click on mac os) seems MUCH easier to work with. I actually got up to 900 ft (somehow) before loosing control and crashing. Even with --enable-auto-coordination. I've checked the faq, but as soon as the plane gets airborn it wobbles from one said to the other. Which aircraft are you seeing this with? The only time I've seen real wobbles in that mode is when attempting to apply a lot of rudder while it is enabled. Use the property picker (View Menu, Properties option) and look under controls to see if something is holding the rudder on you (the rudder value should be 0 at startup). Rudder on taxi is 0.28500, rudder-trim 0v. Once we're airborne these values aren't changing. Maybe once I can figure out the rudder controls via mouse and keyboard this will get easier... The c310, among others. I'll start the engines, turn both throttles up to full and accelerate (to redline, actually). Once it starts to hop, I hit down arrow to bring the elevator up, and the c310 starts wobbling as soon as it leaves the ground. Maybe I just need to give some sort of right rudder to compensate for the propellers (or figure out a jet that works on my system 8-)) Any easy to fly jets that you could recommend (the 747s arent working on my system). Incidentally, is there a common denominator to the planes that I can get working or to those that I can't? Basically, c172, ufo, c310, c182 work -- are these all JSB x15,x24b seem to work, couldn't fly via keyboard, change views, activate hud, planes did nothing but climb -- don't remember what model these use 747-yasim, dc3-yasim, wrightFlyer1903-v1-nl-uiuc, 747-uiuc, beech99-uiuc HANG with wait cursor, no keyboard response -- is this a uiuc/yasim problem on my system? BTW, cool anti-crash feature, but how can I disable it? 8-D Stay in the air? ;-) Highly unlikely, given my performance thus far 8-( Cool game, lousy pilot! Wasn't it George Carlin who said that he wasn't afraid to fly, just afraid of the unscheduled stops (i.e, crashes). Thank you! Ima Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] failed to untie property w. --aircraft-id=a4-yasim +CVS question
Hi, am trying to use the new a4-sound.xml file, but when I start fsgs with --aircraft-id=a4-yasim, I get the following errors: CG: -6.1, -0.0, 0.5 Failed to untie property /consumables/fuel/tank[0]/level-gal_us Failed to untie property /consumables/fuel/tank[1]/level-gal_us Failed to untie property /engines/engine[0]/fuel-flow-gph Failed to untie property /engines/engine[0]/rpm Failed to untie property /engines/engine[0]/mp-osi Failed to untie property /engines/engine[0]/egt-degf This hangs my CLI (until I kill fsgs process). Didn't save the orginal XML file so I don't know if this problem is related to the new on. FG question: did I not install something necessary for the a4? Can I extract just the original a4-sound.xml file using cvs? what is the command syntax to do this pls? thanks! CVS question: can I extract all flightgear files (cvs -z3 checkout flightgear) and then tell cvs to extract specific files or directories so that any modifications previously made are overwritten/ignored? I don't want to blast makefiles or such I might have modified but might want to overwrite just src/flightgear/src/main for example. thanks! I know that I could delete the changed files (the cvs log shows M by them), but I'm hoping that there's an easier way. Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] joystick not seen on macos x
I am using macos 10.1.5 and a saitek x45 usb joystick. The joystick is getting power (lights up), but neither fgfs joystick tool (fgjs or js_demo) sees it nor does fgfs when it starts up. How does one set up a joystick on macos to work with flightgear? I've read the faq and the joystick support page but they don't mention mac os x Barring that, how can I use a mouse to climb, etc. Under macos 9, there was a delay problem with this joystick of two seconds or more, but it doesn't look like os x or flightgear are seeing it at all. Anyone familiar with human interface device setup on mac os x or BSD that can advice? TIA Ima ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] joystick not seen on mac os X
I'm a pseudonym wrote: I am using macos 10.1.5 and a saitek x45 usb joystick. The joystick is getting power (lights up), but neither fgfs joystick tool (fgjs or js_demo) sees it nor does fgfs when it starts up. How does one set up a joystick on macos to work with flightgear? Have you verified that the joystick actually works with Mac OS X? I have one of these controllers (which are otherwise fantastic gadgets), and under Linux it requires a special parameter to be set when the kernel module is compiled. Apparently, they respond too slowly to be considered compliant USB devices; the tweak increases the driver timeout delay. Saitek ships a custom windows driver that presumably does the same thing. They actually have a big yellow sticker on the plug warning you not to plug it in without installing the driver first. If you do, windows will (apparently) detect it incorrectly as a normal HID device and never be able to recover to the correct driver without a reinstall long tirade elided Yeah, saitek claims mac compatibility on the box, but doesn't give any drivers. They say it's apple's problem. The apple support reps just think that Saitek's nuts. I'll see if I can get 10.2 if and when it's out to see if that helps. Can you use the joystick correctly in other Mac applications? Beyond that, I know squat about the Mac or BSD USB subsystems; sorry. :) No, doesn't work at all. Not even in XPlane under X, where at least under macos 9 it was recognized. I'm not sure if os X's usb support is working nor how to test it. Tia, Ima Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] problem with --airport-id=KDCA
Hi, Way cool app, ya'll, but I'm having some problems with airport ids. Attempting to run ./fgfs with any --airport-id option causes errors as shown below. The runway information is bad, I'm guessing. I am using base 7.11.pre1 (the only one supported by the latest cvs sources that I dled). Downloaded everything from CVS again and recompiled. Am still getting the same error. I'm new at this and am unsure how to even begin. I've tried KJFK, KDCA (washington, DC) and others to the same effect. If I use the default airport (KSFO), things start OK: *KSFO info is: NewAirportInit KSFO Attempting to set starting position from runway code KSFO heading 270 Runway 01L heading = 27.7 diff = 117.7 Runway -01L heading = 207.7 diff = 62.3 Runway 01R heading = 27.71 diff = 117.71 Runway -01R heading = 207.71 diff = 62.29 Runway 10L heading = 117.9 diff = 152.1 Runway -10L heading = 297.9 diff = 27.9 Runway 10R heading = 117.9 diff = 152.1 Runway -10R heading = 297.9 diff = 27.9 closest runway = 10L + 180 runway = -122.375, 37.6211 length = 1808.99 heading = 117.9 Position for KSFO is (-122.357, 37.6135) new heading is 297.9 Searching for airport code = KSFO idx = 11133 Position for KSFO is (-122.375, 37.619) *KDCA info is: NewAirportInit kdca Attempting to set starting position from runway code kdca heading 270 closest runway = + 0 runway = 278224, 5.39338e-315 length = 8.89328e-315 heading = 180 Position for kdca is (277864, 4.52183e-05) new heading is 2.96439e-321 Searching for airport code = kdca idx = 9802 Position for kdca is (-77.0377, 38.8521) What am I doing wrong? TIA BTW, how do I build a debug version of FGFS and how can I load a source file to examine in GDB. 8-) Thanks! Ima vv- some log information related to kdca [localhost:fgdev/src/flightgear] root# src/main/fgfs --airport-id=kdca Using Mac OS X hack for initializing C++ stdio... FlightGear: Version 0.7.11pre1 Built with GNU C++ version 2.95 Scanning for root: command line fg_root = /Users/joeh/Desktop/FlightGear/fgdev/lib/base Reading global preferences Finished Reading global preferences Reading default aircraft: c172 from /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Aircraft/c172-set.xml Processing command line arguments Finished command line arguments Opening a window: 800x600 Rage 128 OpenGL Engine Max texture size = 1024 Depth buffer bits = 16 NewAirportInit kdca Attempting to set starting position from runway code kdca heading 270 closest runway = + 0 runway = 278224, 5.39338e-315 length = 8.89328e-315 heading = 180 Position for kdca is (277864, 4.52183e-05) new heading is 2.96439e-321 Searching for airport code = kdca idx = 9802 Position for kdca is (-77.0377, 38.8521) Initializing Time Current greenwich mean time = Wed Jun 12 23:44:42 2002 Current local time = Wed Jun 12 19:44:42 2002 snip Panel visible = 0 Loading deferred texture Tile not found (Ok if initializing) Attempting to schedule tiles for bogus latitude and longitude. This is a FATAL error. Exiting! scheduling needed tiles for 277864 4.52183e-05 load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery Loading tile /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037376 Tile not found (Ok if initializing) load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery Loading tile /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037384 Refreshing timestamps for 277864 0.0625 Attempting to schedule tiles for bogus latitude and longitude. This is a FATAL error. Exiting! scheduling needed tiles for 277864 4.52183e-05 Tile not found (Ok if initializing) load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery Loading tile /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060s10/w056s01/2037369 Updating light parameters. Sun angle = 117.739 ambient = 0.15 diffuse = 0 sky = 0.09 Tile not found (Ok if initializing) load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery Loading tile /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037385 My gunzipped default.apt airport information has KDCA as A KDCA 38.852087 -077.037712 16 CYN Washington National runways.mk4 has (around KDCA, unsure what the file's structure is): KDCA No airports except the default work for me. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Problem with --airport-id=KDCA
Well, duh, after trying uppercase airport identifiers, I see that you are absolutely right -- they work fine. However, I must confess that it seems inconsistent. According to the log, part of the startup processing is able to correctly identify kdca in lower case -- note the correct position information even with LC! It looks like the airport location processing can handle lowercase, but the runway processing cannot? (Haven't checked source yet). BTW, are all airport identifiers A-Z or 0-1? Do you think that it would be a good idea to just convert lowercase to upper for --airport-id option or is it better to just make the docs/command line help a bit clearer for this command? For the clueless outthere, myself included. 8-( Thanks also for the scenery pointer, I think that I've got the right scenery downloaded (w080n40), though I forgot to mention that, sorry! Position for kdca is (-77.0377, 38.8521) TIA, Ima * (ima sudonim) [2002.06.12 21:37]: > Way cool app, ya'll, but I'm having some problems with airport ids. > > Attempting to run ./fgfs with any --airport-id option causes errors as > shown below. > The runway information is bad, I'm guessing. I am using base 7.11.pre1 > (the only one supported by the latest cvs sources that I dled). > Downloaded everything from CVS again and recompiled. Am still getting > the same error. > > I'm new at this and am unsure how to even begin. I've tried KJFK, KDCA > (washington, DC) and others to the same effect. If I use the default > airport (KSFO), things start OK: > > *KSFO info is: > NewAirportInit KSFO > Attempting to set starting position from runway code KSFO heading 270 > Runway 01L heading = 27.7 diff = 117.7 > Runway -01L heading = 207.7 diff = 62.3 > Runway 01R heading = 27.71 diff = 117.71 > Runway -01R heading = 207.71 diff = 62.29 > Runway 10L heading = 117.9 diff = 152.1 > Runway -10L heading = 297.9 diff = 27.9 > Runway 10R heading = 117.9 diff = 152.1 > Runway -10R heading = 297.9 diff = 27.9 > closest runway = 10L + 180 > runway = -122.375, 37.6211 length = 1808.99 heading = 117.9 > Position for KSFO is (-122.357, 37.6135) new heading is 297.9 > Searching for airport code = KSFO > idx = 11133 > Position for KSFO is (-122.375, 37.619) > > *KDCA info is: > NewAirportInit kdca Note that you are not using all caps. Try running with "KDCA" like you have in the Subject. I'm not at home right now, so I can't test this. -- Cameron Moore [ My grandfather died when he was just an infant. ]
