RE: [Flightgear-devel] Compile problem with Metakit
I have found the same problems. I think it is related to using gcc 3.2 on recent cygwin. gcc 3.2 doesn't look in /usr/local/* by default, so you need to add it manually (set CXXFLAGS and LDFLAGS appropriately). There must be a simpler and more automated solution, but my knowledge of the auto tools is insufficient to fix it. Richard. -Original Message- From: Michael Basler [mailto:[EMAIL PROTECTED]] Sent: 14 February 2003 11:01 pm To: [EMAIL PROTECTED] Subject: RE: [Flightgear-devel] Compile problem with Metakit Curt, Which version of metakit were you building? Is this still problem with the most recent versions of metakit? If not, has anyone reported this to the metakit author so this can at least get resolved in future versions? This is Metakit 2.4.3. It came with the CVS archive, maybe 14 days ago (I didn't update by purpose to avoid interference with, maybe, recent CVS version errors; the version I have build with the old GCC 2.95n base Cygwin). Maybe I should indeed try to contact the author... No one else seeing this error? Thanks, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel __ __ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk __ __ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 747 cockpit
On Saturday, February 15, 2003, at 11:19 pm, Jim Wilson wrote: The two possible options that come to mind are as follows: 1) Use the current 3D Modeling system. 2) Take code from the opengc project and change it so that it gets data directly off our property system (property paths configurable). The idea then would be to load these using Andy's panelnode code that currently loads the 2D panel into 3D cockpits. I'm thinking that these could be special 2D panel types and there could be a separate panel class (inherited from a general) for each glass display. Any comments? My plan was to add a bunch of new panel element types, though at some stage we are going to need some big chunks of custom code. For example, for the KLN-89b, the screen is essentially a 4-line, 20? character display, so I was figuring on an ncurses-like markup of fields, pages and lists, all of fixed character positions and dimensions. This will work really well for the [M]CDUs of big jets too. But even the KLN-89b has the dreaded NAV4 mode, which provides a graphical map of the flightplan, waypoints, airspace boundaries an so on. I was mentally planning to cross that bridge when I got to it, but obviously it'd be nice to share code with other similar displays. Basically, I think the currently panel method (a tree of elements we place) is essentially right model (i.e declarative, not just procedural bits of openGL). We would need quite a few custom elements in this approach, and NAV (map) displays are a special problem, but I think the other stuff is pretty doable (tapes, number fields, artificial horizon) in a tuneable way. And would also map closely to a XML-ified HUD. Indecisively, James -- The lack of planning on your part does not constitute to an emergency on mine ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
I have found the same problems. I think it is related to using gcc 3.2 on recent cygwin. Thanks, Richard, good to know it's not just my fault. gcc 3.2 doesn't look in /usr/local/* by default, so you need to add it manually (set CXXFLAGS and LDFLAGS appropriately). There must be a simpler and more automated solution, but my knowledge of the auto tools is insufficient to fix it. Curt, could you, please, fix this (shouldn't be hard for an expert, I guess...). BTW, is this a pure Cygwin problem or face GCC 3.2 based Linux distros the same problem? Thanks and regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 747 cockpit
Jim Wilson wrote: Recently I've been looking at potential solutions to doing a glass cockpit display in flightgear. The 2D panel system just doesn't provide anywhere near the functionality to do it, so I've pretty much decided that isn't an option. The two possible options that come to mind are as follows: 1) Use the current 3D Modeling system. There are two critical things that 2) Take code from the opengc project and change it so that it gets data There is a third option: use glDrawPixels to draw essentially a constantly updating texture. I have no idea about the performance penalty it involves, but it might be worht looking into. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile problem with Metakit
Michael Basler wrote: I have found the same problems. I think it is related to using gcc 3.2 on recent cygwin. Thanks, Richard, good to know it's not just my fault. gcc 3.2 doesn't look in /usr/local/* by default, so you need to add it manually (set CXXFLAGS and LDFLAGS appropriately). There must be a simpler and more automated solution, but my knowledge of the auto tools is insufficient to fix it. Curt, could you, please, fix this (shouldn't be hard for an expert, I guess...). Why should configure automatically add /usr/local/include to the search path and not (for example) /opt/include? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear on TheOpenCD
[EMAIL PROTECTED] wrote: Hello, My name is Henrik Nilsen Omma, and I am a participant in a new Open Source Project called TheOpenCD. Our aim is to create a simple to use CD distribution of Open Source software for Windows that will act as a showcase, and in that way spread the OSS message. We released our first edition in December, and we are now aiminng for a much expanded and improved version in March. We are careful to select only the best quality OSS, so that we can really impress user. As a result our CD will only include around 30 applications (whereas GNUwinII has over 100), and only 3-4 games. Flightgear has impressed us, with it's size, complexity and graphics. However there are a few minor issues which currently doesn't match our profile. There was a review in a local magazine this week, and immidiately draw attention. I think it is a good innitiative! 1. When starting the game there are lots of debugg messages, can these be removed? 2. The game and locations are installed in separate packages. This should be combined in a single and smooth install/uninstall along with as much ducumentation as possible. Can we do a collaboration on this? #1 is something we would need help with, while #2 can be done by someone in our team using InnoSetup. The first CD is already in wide circulation, but we expect much more from the second one, as it will be more mature, and we will push it harder. This patch will already remove a lot of the startup messages: http://www.a1.nl/~ehofman/fgfs/download/SimGear_remove_cout-20030217.diff David, can you apply it to SimGear? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
Erik, Why should configure automatically add /usr/local/include to the search path and not (for example) /opt/include? because Metakit and SimGear are installed there by default (withour any additional --prefix option) - at least in my case. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Compile problem with Metakit
On Mon, 17 Feb 2003 10:24:01 +0100 [EMAIL PROTECTED] (Michael Basler) wrote: I have found the same problems. I think it is related to using gcc 3.2 on recent cygwin. Thanks, Richard, good to know it's not just my fault. gcc 3.2 doesn't look in /usr/local/* by default, so you need to add it manually (set CXXFLAGS and LDFLAGS appropriately). There must be a simpler and more automated solution, but my knowledge of the auto tools is insufficient to fix it. Curt, could you, please, fix this (shouldn't be hard for an expert, I guess...). There already is a --with-metakit=DIR option to configure. Conversely you specify CPPFLAGS and LDFLAGS on the command line to configure thus: CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib ./configure Cheers, Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
Bernie, There already is a --with-metakit=DIR option to configure. Conversely you specify CPPFLAGS and LDFLAGS on the command line to configure thus: Is there a similar option to tell FlightGear where to look for the Simgear libs, as they hit the same problem? - I still would prefer having this working by default without any options. The average user just types ./configure and sits back. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
I agree. If a user sucessfully builds and installs a package to it's default location, it is reasonable to expect that subsequent ./configures would find that package. Richard -Original Message- From: Michael Basler [mailto:[EMAIL PROTECTED]] Sent: 17 February 2003 10:48 am To: [EMAIL PROTECTED] Subject: RE: [Flightgear-devel] Compile problem with Metakit Bernie, There already is a --with-metakit=DIR option to configure. Conversely you specify CPPFLAGS and LDFLAGS on the command line to configure thus: Is there a similar option to tell FlightGear where to look for the Simgear libs, as they hit the same problem? - I still would prefer having this working by default without any options. The average user just types ./configure and sits back. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel __ __ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk __ __ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Harrier GR3
I've scanned in the cockpit diagram from the GR3 from the pilots manual, and managed to hack it around to get this: http://www.stockill.org/fgfs/fgfs-screen-001.jpg If anyone wants to make use of it to produce a full 2d panel then I'll be happy to provide the files in whatever resolution/format you want to work from. I'm trying to get together the info from the manual to tweak the flight model too - I can certainly help with fuel and water tank capacities and layout, but nobody appears to have put their name to the current harrier.xml -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
Michael Basler writes: Bernie, There already is a --with-metakit=DIR option to configure. Conversely you specify CPPFLAGS and LDFLAGS on the command line to configure thus: Is there a similar option to tell FlightGear where to look for the Simgear libs, as they hit the same problem? - I still would prefer having this working by default without any options. The average user just types ./configure and sits back. Ok, looking in configure.ac, the --with-metakit=/path/to/metakit option simply adds the specified path to EXTRA_DIRS. We used to add /usr/local to EXTRA_DIRS automatically, but this was removed because it was causing problems for gcc-3.x. Question for those with gcc-3.x: does the --with-metakit=/path option also cause problems/warnings compiling? It would be *very* simple to add /usr/local back in to the list of subdirectories that are checked and added automatically. Someone needs to tell me specifically why gcc-3.x was complaining about this and what can be done about it. I can't imagine that gcc-3.x prevents you from including or linking against anything in the /usr/local tree. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 747 cockpit
James Turner [EMAIL PROTECTED] said: Basically, I think the currently panel method (a tree of elements we place) is essentially right model (i.e declarative, not just procedural bits of openGL). We would need quite a few custom elements in this approach, and NAV (map) displays are a special problem, but I think the other stuff is pretty doable (tapes, number fields, artificial horizon) in a tuneable way. And would also map closely to a XML-ified HUD. This would work to some degree. The biggest problem is that the 2D code doesn't offer an option other than placing textures on rectangular polys. This is a major problem when doing glass displays, especially the PFD. Granted it is possible to come up with scheme for specifying polys in xml, but it seems a lot easier to just draw them in a 3D drawing program. In the 3D you could basically do most anything with two layers. The bottom layer would have various shaped polys fit together like a puzzle that have dynamic texture mapping. The top layer would be small polys that had mostly rotating or sliding arrows, and text overlays. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 747 cockpit
Erik Hofman [EMAIL PROTECTED] said: There is a third option: use glDrawPixels to draw essentially a constantly updating texture. I have no idea about the performance penalty it involves, but it might be worht looking into. Erik It seems like that'd be the only way of doing gps map displays. How does atlas work? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
Curt, Ok, looking in configure.ac, the --with-metakit=/path/to/metakit option simply adds the specified path to EXTRA_DIRS. We used to add /usr/local to EXTRA_DIRS automatically, but this was removed because it was causing problems for gcc-3.x. Question for those with gcc-3.x: does the --with-metakit=/path option also cause problems/warnings compiling? This is strange, as I am using GCC 3.2 myself, and this obviously seems to require adding /usr/local to the search path. Maybe there's some difference between how Cygwin behaves and how some Linux distros behave? Notably, it might be interseting to know how RedHat Linux behaves, as Cygwin is maintained by RedHat. Anyway, if you or anyone else sends me modified configre scripts for Simgear and FlightGear both including /usr/local for searching for the Metakit and Simgear libs, resp., I could test if they work (which doesn't imply them necessarily to work on all other systems, of course). BTW, is there a similar option --with-simgear=/path/to/simgear when building FlightGear? Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 747 cockpit
Jim Wilson writes: Erik Hofman [EMAIL PROTECTED] said: There is a third option: use glDrawPixels to draw essentially a constantly updating texture. I have no idea about the performance penalty it involves, but it might be worht looking into. Erik It seems like that'd be the only way of doing gps map displays. How does atlas work? I seem to recall hearing discussions that glDrawPixels() is *excessively* slow on most platforms; to the point of making it nearly unusable for real time graphics. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Compile problem with Metakit
OK, these tests are using SimGear and FlightGear CVS snapshots from about 29th Jan, Cygwin (similar date) on W2K, gcc 3.2. When configuring SimGear: ./configure --with-metakit=/usr/local (or ./configure --with-metakit=/usr/local/lib) both fail at the MetaKit version check. I should note though that it appears to find mk4.h successfully, but it is the version check that fails. LDFLAGS=-L/usr/local/lib ./configure runs configure correctly to the end and creates all the Makefiles. Then, with a minor tweak to .../simgear/sky/Makefile to remove the clouds3d directory, SimGear builds and installs correctly. Same requirements apply to configuring FlightGear, which then builds and installs happily. No errors or warnings from gcc about /usr/local/* that I could see. Does that help? Whilst we are on the subject of gcc warnings, when building on recent Cygwin installations, you get warnings like this: In file included from hud.hxx:34, from hud_card.cxx:2: ../../src/Include/config.h:245:1: warning: WIN32 redefined In file included from /usr/include/w32api/windows.h:48, from /usr/include/plib/ul.h:102, from /usr/include/plib/sg.h:28, from hud_card.cxx:1: /usr/include/w32api/windef.h:29:1: warning: this is the location of the previous definition fairly often. The fix is to remove the definition of WIN32 from .../src/Include/config.h, but I think this is an auto generated file, so I get lost right about now when trying to fix it. Richard -Original Message- From: Curtis L. Olson [mailto:[EMAIL PROTECTED]] Sent: 17 February 2003 1:38 pm To: [EMAIL PROTECTED] Subject: RE: [Flightgear-devel] Compile problem with Metakit Michael Basler writes: Bernie, There already is a --with-metakit=DIR option to configure. Conversely you specify CPPFLAGS and LDFLAGS on the command line to configure thus: Is there a similar option to tell FlightGear where to look for the Simgear libs, as they hit the same problem? - I still would prefer having this working by default without any options. The average user just types ./configure and sits back. Ok, looking in configure.ac, the --with-metakit=/path/to/metakit option simply adds the specified path to EXTRA_DIRS. We used to add /usr/local to EXTRA_DIRS automatically, but this was removed because it was causing problems for gcc-3.x. Question for those with gcc-3.x: does the --with-metakit=/path option also cause problems/warnings compiling? It would be *very* simple to add /usr/local back in to the list of subdirectories that are checked and added automatically. Someone needs to tell me specifically why gcc-3.x was complaining about this and what can be done about it. I can't imagine that gcc-3.x prevents you from including or linking against anything in the /usr/local tree. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Boeing 747 cockpit
Curtis L. Olson wrote: I seem to recall hearing discussions that glDrawPixels() is *excessively* slow on most platforms; to the point of making it nearly unusable for real time graphics. It also ties the implementation to a particular screen resolution, which is a non-starter 3D cockpits anyway. Doing software-side rendering into a buffer for use as a texture would work, though. It's probably not too much slower than a bunch of GL_LINE's would be. Andy -- Andrew J. RossBeyond the OrdinaryPlausibility Productions Sole Proprietor Beneath the Infinite Hillsboro, OR Experience... the Plausible? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Hmmmm
We appear to have got a mention in Alan Cox's diary. Unfortunately he's taken to writing the last batch of entries in Welsh - obviously the lessons are going well... http://www.linux.org.uk/diary/ if anyone has the ability to translate. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Hmmmm
I noticed that too. Pity that Babelfish doesn't do Welsh. Could be related to DRI? Possibly? (Why didn't I take Welsh lessons when I was at University in Swansea?) Richard -Original Message- From: Jon Stockill [mailto:[EMAIL PROTECTED]] Sent: 17 February 2003 4:21 pm To: [EMAIL PROTECTED] Subject: [Flightgear-devel] H We appear to have got a mention in Alan Cox's diary. Unfortunately he's taken to writing the last batch of entries in Welsh - obviously the lessons are going well... http://www.linux.org.uk/diary/ if anyone has the ability to translate. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel __ __ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk __ __ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
On Monday, February 17, 2003, at 04:21 pm, Jon Stockill wrote: http://www.linux.org.uk/diary/ if anyone has the ability to translate. According to my native welsh friend (who also hacks the kernel, so I assume the technology is correct to): 'Too many collisions, DRI collides too much when playing Flightgear, cars colliding in front of the house' ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
Jon Stockill [EMAIL PROTECTED] said: We appear to have got a mention in Alan Cox's diary. Unfortunately he's taken to writing the last batch of entries in Welsh - obviously the lessons are going well... http://www.linux.org.uk/diary/ if anyone has the ability to translate. InterTran results: translation Too much he espouse. He is being THREE ' heartburn espouse when dw I ' heartburn play 'Flightgear' I go he is being two he one has ' heartburn espouse before the tw. He is being anyone ' heartburn blemish serious except we were we police force and ambulance I go machine fire. I looked I ' group game Scotland and Ireland. He is being game ' heartburn hand sail. He will be Ireland ' heartburn win receiving England? l appraise hard! He is being Telsa ' heartburn reach by Bristol. There is not anything train go by Bristol crookedly Swansea about Sunday now! He was she ' heartburn has tired I go anything happy. /translation Maybe we don't want to know :-) Please pass the rollaids. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: FlightGear (fwd)
And the answer is -- Forwarded message -- Date: Mon, 17 Feb 2003 11:41:01 -0500 (EST) From: Alan Cox [EMAIL PROTECTED] To: Jon Stockill [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: FlightGear thought I'd mail and ask for a translation of the entry concerning FlightGear ;) Flightgear crashes my box with a Radeon 9000 Seems to be the large textures when I buzz a city. Quite annoying really because its a really neat program. Other stuff like cube works well Alan -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
InterTran results: translation Too much he espouse. He is being THREE ' heartburn espouse when dw I ' heartburn play 'Flightgear' I go he is being two he one has ' heartburn espouse before the tw. He is being anyone ' heartburn blemish serious except we were we police force and ambulance I go machine fire. I looked I ' group game Scotland and Ireland. He is being game ' heartburn hand sail. He will be Ireland ' heartburn win receiving England? l appraise hard! He is being Telsa ' heartburn reach by Bristol. There is not anything train go by Bristol crookedly Swansea about Sunday now! He was she ' heartburn has tired I go anything happy. /translation Wow. Welsh must be a romantic language when every other word means heartburn... I love the He is being Telsa bit. What? Alan is coming to Bristol? He would be most welcome... As to DRI (Welsh for THREE!) crashing, I don't even need FlightGear to crash my computer with DRI CVS, it crashes on startup of the X server. Hmmm, maybe it's time to also install the kernel module from DRI? Andras === Major Andras e-mail: [EMAIL PROTECTED] www:http://andras.webhop.org/ === ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
According to my native welsh friend (who also hacks the kernel, so I assume the technology is correct to): 'Too many collisions, DRI collides too much when playing Flightgear, [...] This sounds quite reasonable. I got a reply from Alan on 'dri-devel': My lockup with flightgear on the 9000 with 4.2.99 based tree and a recent DRM module. I am (I suppose so) annoying the DRI people already for many months because FlightGear reliably locks up their X server built from development source tree. So I assume people start getting really interested in this issue because they don't want an XFree86-4.3.0 release with obvious bugs that get triggered by popular software Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
Martin Spott writes: I am (I suppose so) annoying the DRI people already for many months because FlightGear reliably locks up their X server built from development source tree. So I assume people start getting really interested in this issue because they don't want an XFree86-4.3.0 release with obvious bugs that get triggered by popular software Keep bugging them. :-) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
As to DRI (Welsh for THREE!) crashing, I don't even need FlightGear to crash my computer with DRI CVS, it crashes on startup of the X server. Hmmm, maybe it's time to also install the kernel module from DRI? Yep, please pick the sources from: xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/ xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/ and adjust the Makefile in your kernel tree accordingly. Or adjust 'xc/config/cf/linux.cf' to get the kernel modules built with 'make World', Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: FlightGear (fwd)
Jon Stockill wrote: And the answer is... Alan Cox wrote: Flightgear crashes my box with a Radeon 9000 Seems to be the large textures when I buzz a city. Quite annoying really because its a really neat program. Other stuff like cube works well Magnificent. Maybe now someone will look at the issue. I reported this a while back, and Keith Whitwell's response was essentially that FlightGear was too big and complicated to use as a test case. :( While of course that's true enough, it wasn't very helpful. I rather doubt he'd have said the same thing about RTCW or Unreal. Andy -- Andrew J. RossBeyond the OrdinaryPlausibility Productions Sole Proprietor Beneath the Infinite Hillsboro, OR Experience... the Plausible? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: FlightGear (fwd)
Andy Ross writes: Magnificent. Maybe now someone will look at the issue. I reported this a while back, and Keith Whitwell's response was essentially that FlightGear was too big and complicated to use as a test case. :( Keith does make a good point, simple test cases are the most ideal in terms of debugging problems, but the flip side is that you run the risk of building drivers that only work on the simple test cases. Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: FlightGear (fwd)
Curtis L. Olson writes: Keith does make a good point, simple test cases are the most ideal in terms of debugging problems, but the flip side is that you run the risk of building drivers that only work on the simple test cases. You need a simple test case that uses lots of polygons and lots of texture memory. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hmmmm
Martin Spott writes: I am (I suppose so) annoying the DRI people already for many months because FlightGear reliably locks up their X server built from development source tree. [...] Keep bugging them. :-) Hmm, it already cost me zillions of hours to do this. FlightGear is anything but a trivial test case - and DRI is not a simple object to test. So it is quite a time consuming adventure to find a reliable test case with FlightGear, to run this test against a handfull of different DRI CVS trees, against a lot of small DRI-patches floating around and to reboot the workstation after each failure :-/ I would love the ability to save the current state of my workstation and simply to resume at this point within a few seconds after a crash, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] help! new to fliight sims
Hi, i'm a student and trying to learn how to make flight sims. i am in the learning process and i was wondering if anyone of you could point me in the righ direction. i want to start by drawing dials, and horizon indicator. i dont know if flightgear has function calls to automatically do this, but could anyone point me to tutorials or code on how to start. feel free to dummy it up :)Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day
Re: [Flightgear-devel] help! new to fliight sims
Once upon a time, you were sitting and writing: Hi, i'm a student and trying to learn how to make flight sims. i am in the learning process and i was wondering if anyone of you could point me in the righ direction. i want to start by drawing dials, and horizon indicator. i dont know if flightgear has function calls to automatically do this, but could anyone point me to tutorials or code on how to start. feel free to dummy it up :) Hm... it looks like you have a long way ahead :) (but from what I know about simulations drawing panels would certainly not be my first step...). ~ ___ Elad (elady)_@__ ___ ( \ J. Yarkoni .-'`-. / ) ( \_ / (O O) \ _/ ) (`-( ) )-') ( _\ \/ /_ ) (__/ `-..-' \__) Elady for friends or Oh my God... - It's Him ! for fans (or turbofans). [EMAIL PROTECTED] | http://www.ee.bgu.ac.il/~elady | .---. ECE. BGU, Beer-Sheva,Israel ' ___ ' 972-8-6472417 84105 -' .-. '- _' '-' '_ ''-|---|/ \==][^',_m_,'^][==/ \|---|-'' \__/~\__/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] help! new to fliight sims
Elad Yarkoni writes: Once upon a time, you were sitting and writing: Hi, i'm a student and trying to learn how to make flight sims. i am in the learning process and i was wondering if anyone of you could point me in the righ direction. i want to start by drawing dials, and horizon indicator. i dont know if flightgear has function calls to automatically do this, but could anyone point me to tutorials or code on how to start. feel free to dummy it up :) Hm... it looks like you have a long way ahead :) (but from what I know about simulations drawing panels would certainly not be my first step...). Actually, drawing 2d panels is pretty straight forward, and their's lots of examples you can start with and modify. Panels are all done with .xml config files so you don't need to do any coding or recompiling to build a panel. And, you can reload the panel on the fly, so you don't even have to restart FlightGear to test your changes. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] help! new to fliight sims
Curtis L. Olson wrote: Actually, drawing 2d panels is pretty straight forward, and their's lots of examples you can start with and modify. Panels are all done with .xml config files so you don't need to do any coding or recompiling to build a panel. And, you can reload the panel on the fly, so you don't even have to restart FlightGear to test your changes. And before you notice it, some one ends up with something like this: http://home.attbi.com/~davidculp2/f16/f16-v3.jpg Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Nasl (not another scripting language)
I mentioned earlier that I had a fun toy I wanted to pawn off on you guys. Here: http://www.plausible.org/nasl Some will remember a few months back when the subject of scripting languages came up that I mentioned that someday I'd love to write my own language. Existing embeddable languages are either too limited or too large, and that I though there was a sweet spot for a small, simple language that still managed to support the standard list of features programmers have come to expect. In keeping with YASim's naming, let me present Nasl (yes, it's pronounced like you think it is). It does objects, functions (including functional programming), hash tables, vectors, strings and numbers; supports a syntax rather like Javascript; and does it all in less than 100k of ANSI C. I think it rocks*. Coming soon will be exception handling and runtime call stack inspection. To boot, the interpreter was designed to be threadsafe, although the garbage collector doesn't understand more than one context at the moment. * but then, that might be just because I've finally got to a point where I don't know about any actual bugs in it. Whether this is useful for FlightGear or not is up to you guys. I know that David has done some work with integrating PSL, which is a more limited language but probably more mature (and already available in plib). While it was intended to be small, Nasl may still seem like overkill to some. It is also frighteningly immature, which of course is why I'd *love* for you guys to play with it. I need to start working on other parts of my game first; until I have more code written, I won't have an environment in which to embed my embedded scripting language. Any work you guys do as guinea pigs before then is free testing for me. :) So anyway, take a look and tell me what you think. The quickest way to get a feel for the syntax is to read through the annotated sample file at http://www.plausible.org/nasl/sample.nas Andy -- Andrew J. RossBeyond the OrdinaryPlausibility Productions Sole Proprietor Beneath the Infinite Hillsboro, OR Experience... the Plausible? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] 2D panel texture cropping
I've been working on an ADI for the jets, based on Dave's C-172 attitude indicator and have hit a snag. Does the 2D panel code offer the ability to crop textures that would be shifted out of the bounds of the instrument? Dave Culp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel