Re: [Flightgear-devel] Multiheaded video cards?
On Wed, 03 Nov 2004 23:07:01 -0800 Dale E. Edmons [EMAIL PROTECTED] wrote: Chris Metzler wrote: What I can tell you, though, is that DRI and OpenGL support for Matrox cards under Linux sucks rocks. First of all, Matrox' drivers are open, and their proprietary HAL module doesn't really buy you anything, so No real arguments here, but there is useable code for the card in the native X11. Sure; it's just broken. The DRI project people agree that it's broken; they just don't have anybody that can fix it right now (or, rather, didn't as of late summer. things may have changed). for just a taste. There's a lot more there too. Personally, I had constant hard lockups requiring a full system reset, with lots of DMA idle timeout messages to my X log, whenever I tried flightgear for very long with the Matrox card. From other messages in the Matrox Sounds like the ASUS (junk!) motherboard I had. My 1GHz athalon on its ASUS board sits collecting dust (it doesn't even do that very well). The G450 I have is very robust as is the code. I run Debian Linux without a single lockup in over a year now. Hmmm, well, yes, this is with an Athlon (XP 2000+) on an Asus a7v333. However, the exact problem I encountered with the Matrox drivers has been reported by several other people on e.g. the X.org and DRI project bugzillas, and they weren't running Asus motherboards. And when I dumped the G550 for a GF4 Ti4600, I never had another problem. I would only get the DMA idle timeout lockups on very intensive OpenGL stuff. fgfs would routinely do it, tuxracer would rarely do it, glxgears would never ever do it. If there were support for the Matrox X11 drivers, I would have been happy to patch the drivers with diagnostics and fail some more and collect info. But since they're not supported by either Matrox or the X/DRI folks, I just couldn't rationalize sticking with it. -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear pgp8dXBSisVl7.pgp Description: PGP signature ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Plea for help: geometry/trigonometry problem
On Wed, Nov 03, 2004 at 04:02:19PM -0600, Jon S Berndt wrote: -atan2(-phi,theta) This looks *very* strange. An arc tangent of a quotient of angles?? Although it works out dimension-wise, I've never seen a quotient of angles in any formula. Cheers -Gerhard -- Gerhard Wesp o o Tel.: +41 (0) 43 5347636 Bachtobelstrasse 56 | http://www.cosy.sbg.ac.at/~gwesp/ CH-8045 Zuerich \_/ See homepage for email address! ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] autopilot error ?
Hello, with the default c172 I see this error: Reading autopilot configuration from /home/mas/CVS/FlightGear/data/Aircraft/c172p/Systems/KAP140.xml Unknown top level section: filter Detected an internal inconsistancy in the autopilot configuration. See earlier errors for details. Deleting a sample JSBSim startup complete [ the End ] I believe this was introduced about 20 days ago. Can anyone confirm ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] ATI 9200 Direct Rendering problem on Linux
Ampere K. Hardraade wrote: Section Device Identifier Generic Video Card Driver radeon EndSection This is not very much, although it _might_ work. You'd be better done with adding a BusID and a Screen. Ampere K. Hardraade wrote: If I keep the radeon in the driver section, the config file isn't read at all. Therefore, I changed it back to ati. This shouldn't make any difference. Did you enable glx and dri in the Module-section ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] autopilot error ?
On Thursday 04 November 2004 12:21, Martin Spott wrote: Hello, with the default c172 I see this error: Reading autopilot configuration from /home/mas/CVS/FlightGear/data/Aircraft/c172p/Systems/KAP140.xml Unknown top level section: filter Detected an internal inconsistancy in the autopilot configuration. See earlier errors for details. Do you have the latest CVS? Filters were added to xmlauto.*xx mid October: http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008703.html The KAP140 autopilot was updated a couple of days later: http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008753.html So if you have a recent build it should recognize the filter tag in autopilot configurations. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] autopilot error ?
Roy Vegard Ovesen wrote: Do you have the latest CVS? Filters were added to xmlauto.*xx mid October: http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008703.html That's it. I already removed anything with '*kap140*' in the filename and pulled a fresh version from CVS. After I did the same with the 'xmlauto*' files as well I managed to build a binary that doesn't crash. Thanks, Martin. P.S.: I always find it interesting that it is not sufficient to maintain a source tree with 'cvs update' -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Plea for help: geometry/trigonometry problem
-atan2(-phi,theta) This looks *very* strange. An arc tangent of a quotient of angles?? Although it works out dimension-wise, I've never seen a quotient of angles in any formula. Cheers -Gerhard Think of them as distances, really. It was meant to be the X and Y component of the rotated Z axis projected along the XY plane. Think of the angles in radians and project the unit vector components. Maybe it's not correct, I did it very quick, but qualitatively it seemed to work, and quantitatively it seemed correct for the few angles I checked. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] autopilot error ?
On Thursday 04 November 2004 15:21, Martin Spott wrote: Roy Vegard Ovesen wrote: Do you have the latest CVS? Filters were added to xmlauto.*xx mid October: http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008 703.html That's it. I already removed anything with '*kap140*' in the filename and pulled a fresh version from CVS. After I did the same with the 'xmlauto*' files as well I managed to build a binary that doesn't crash. So... problem solved, or? Thanks, Martin. P.S.: I always find it interesting that it is not sufficient to maintain a source tree with 'cvs update' I have used 'cvs -z3 up -dPA' with great success when I update. -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: autopilot error ?
* Roy Vegard Ovesen -- Thursday 04 November 2004 16:53: I have used 'cvs -z3 up -dPA' with great success when I update. ... and I still hope that when people write things like that, they actually mean, that they created a ~/.cvsrc file and put the options there $ cat ~/.cvsrc cvs -z3 -q diff -up update -dP checkout -P rdiff -u and then really only use $ cvs up or, in this case $ cvs up -A m. :-} ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Screen to cartesian co-ords?
On Thursday, 4 November 2004 22:02, Aaron Wilson wrote: Paul, NeHe has a good example of how to convert the screen coordinates into OpenGL coordinates. http://nehe.gamedev.net/data/articles/article.asp?article=13 Aaron I found that article very helpful. The part I don't understand is how the glReadPixels get's the winZ co-ordinate. I mean I'm looking at a wireframe ellipsoid from an odd angle - how does it know how to return the Z co-ordinate of the surface of the ellisoid? Surely I have to tell it where the surface is so that it knows how to intercept the surface and not try to pick a point into infinity (in front of and behind my cursor)? That is what is not explained anywhere I look. Paul ___ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Screen to cartesian co-ords?
Paul Surgeon writes: On Thursday, 4 November 2004 22:02, Aaron Wilson wrote: Paul, NeHe has a good example of how to convert the screen coordinates into OpenGL coordinates. http://nehe.gamedev.net/data/articles/article.asp?article=13 Aaron I found that article very helpful. The part I don't understand is how the glReadPixels get's the winZ co-ordinate. I mean I'm looking at a wireframe ellipsoid from an odd angle - how does it know how to return the Z co-ordinate of the surface of the ellisoid? Surely I have to tell it where the surface is so that it knows how to intercept the surface and not try to pick a point into infinity (in front of and behind my cursor)? That is what is not explained anywhere I look. If you have enabled DepthBuffer operations in OpenGL the rasterizing process keeps track of the depth component of each pixel in the ZBuffer. Note this won't work to well with wireframe and that the Z component is the distance from the eyepoint = For an example that does this using SSG PPE keeps track of the position for a 3d Cursor $PPE_SRC / src / viewer / ppeViewerDraw.cxx / ppeViewer::update_3D_cursor() Note I am quite swamped with work and won't have time to explain the PPE code but you have the source :-) http://prettypoly.sourceforge.net/ Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Flight Test Results for Magnetic Dip
On Wed, 3 Nov 2004 20:21:15 -0500, David Megginson [EMAIL PROTECTED] wrote: Obviously, when the dip is over 70 degrees, it doesn't take a steep turn to cause this effect. The question is, does the compass hang up (i.e. bind and refuse to turn), or does it swing around? If it hangs up, that would explain why I haven't noticed the effect. Any comments from other pilots on the list, especially those who fly north of 40 in North America? I was one a short cross-country this afternoon just before the wet snow and ice pellets came in. On my way into the airport about 15 nm back, I realized that I was almost exactly on a 270 degM heading, so I tried some quick (too fast to show up on radar) left and right banks. In a left 20 degree bank, the magnetic compass does, in fact, reverse, but not all the way to 90 -- in my case, it swung south/east as far as 120 deg. It's kind-of cool, actually, to be able to observe magnetic dip directly that way -- flying west and banked 20 degrees left, the magnetic flow towards the pole was actually off my *left* elbow! All the best, David -- http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] autopilot error ?
Roy Vegard Ovesen wrote: So... problem solved, or? Yep - thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: autopilot error ?
On Thursday 04 November 2004 17:12, Melchior FRANZ wrote: * Roy Vegard Ovesen -- Thursday 04 November 2004 16:53: I have used 'cvs -z3 up -dPA' with great success when I update. ... and I still hope that when people write things like that, they actually mean, that they created a ~/.cvsrc file and put the options there $ cat ~/.cvsrc cvs -z3 -q diff -up update -dP checkout -P rdiff -u and then really only use $ cvs up or, in this case $ cvs up -A m. :-} Now I do, thanks! :-] -- Roy Vegard Ovesen ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AI carrier
Hi all, I want to share a few impressions from my first landing on the nimitz. The carrier still does not move, but the wires are working with a demo implementation in JSBSim. Pics from the replay: http://na.uni-tuebingen.de/~frohlich/carrier/ :) More will come soon! Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Screen to cartesian co-ords?
Thanks, that makes a lot more sense to me now. I'll see what I can glean from the PPE code. On Thursday, 4 November 2004 23:06, Norman Vine wrote: RE: [Flightgear-devel] Screen to cartesian co-ords? If you have enabled DepthBuffer operations in OpenGL the rasterizing process keeps track of the depth component of each pixel in the ZBuffer. Note this won't work to well with wireframe and that the Z component is the distance from the eyepoint = For an example that does this using SSG PPE keeps track of the position for a 3d Cursor $PPE_SRC / src / viewer / ppeViewerDraw.cxx / ppeViewer::update_3D_cursor() Note I am quite swamped with work and won't have time to explain the PPE code but you have the source :-) http://prettypoly.sourceforge.net/ Norman ___ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
