RE: [Flightgear-devel] Re: [BUG] Hunter noise UV face singularity
Melchior FRANZ Sent: 03 March 2004 23:39 To: [EMAIL PROTECTED] Subject: [Flightgear-devel] Re: [BUG] Hunter noise UV face singularity * Lee Elliott -- Wednesday 03 March 2004 19:56: There were a couple of redundant vertices (easily missed) and a couple of polys that were being triangulated less than optimally but the model looks fine in FG on my system - neither the two extra vertices or the triangulation problems were apparent at all. I'm talking about the degenerated UV mapping faces. Not about duplicated vertices or bogus triangulation or something. I can't remember what package Vivian used to create it - Blender or AC3D - Vivian? She uses AC3D. HE :-) Vivian, Vyvyan = male Vivien, Vivienne etc = female A common error. Sorry if there's any misunderstanding Vivian Meazza ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [BUG] Hunter noise UV face singularity
* Vivian Meazza -- Thursday 04 March 2004 09:44: * Melchior FRANZ * Lee Elliott -- Wednesday 03 March 2004 19:56: Vivian? She uses AC3D. HE :-) Vivian, Vyvyan = male Oops ... well. Then take it as a little revenge, as you started all your private emails with Hi Franz, although Franz is my last name and Melchior my first. ;-) Sorry m. PS: Do you know the Nikita story? ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [BUG] Hunter noise UV face singularity
* Vivian Meazza -- Thursday 04 March 2004 09:44: Vivian, Vyvyan = male Bah ... you were kidding, weren't you? http://images.google.com/images?q=vivian m. :-P ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: [BUG] Hunter noise UV face singularity
On Thu, 2004-03-04 at 00:57, Melchior FRANZ wrote: * Vivian Meazza -- Thursday 04 March 2004 09:44: Vivian, Vyvyan = male Bah ... you were kidding, weren't you? http://images.google.com/images?q=vivian m. :-P Watch the BBC's 80's comedy, the Young Ones, the punk was called Vivian...Don't think I would have dared to call him female, he wore Doc Martens... http://www.bbc.co.uk/comedy/guide/articles/y/youngonesthe_1299003473.shtml No offense intended. We're kinda going off topic though... Matt ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: [BUG] Hunter noise UV face singularity
Melchior wrote -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Melchior FRANZ Sent: 04 March 2004 08:58 To: [EMAIL PROTECTED] Subject: [Flightgear-devel] Re: [BUG] Hunter noise UV face singularity * Vivian Meazza -- Thursday 04 March 2004 09:44: Vivian, Vyvyan = male Bah ... you were kidding, weren't you? http://images.google.com/images?q=vivian m. :-P Well, if they all insist on spelling their names wrong ... But I'm not changing mine to Vivienne, and I'm not going to suggest that Viv Richards does either (see http://www.google.co.uk/search?sourceid=navclientie=UTF-8oe=UTF-8q=vivian +richards) or Sir Vivian Fuchs (see http://www.google.co.uk/search?sourceid=navclientie=UTF-8oe=UTF-8q=vivian +fuchs) It's the bane of my life Cheers Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] crash in FGAIPlane::Update(double)
This should now be fixed. Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] New joystick configuration.
Hi all, I have done a new joystick definition for my hardware. This is the thrustmaster top gun afterburner USB (what a name!) throttle/stick combination. I took the great Cyborg-Gold-3d-USB.xml configuration and adjusted it to the thrustmaster axis and button definitions, the global layout is the same. The most notable customization is the throttle, which has two raster positions. One marked with 'idle' and one marked with 'afterburner'. I have made the throttle values scale between 0 and 0.98 between the idle and afterburner raster. In a small area around the raster there is a deadband like zone. Above the abterburner raster, it scales the throttle up to the value of 1, which then will give afterburning. Aditionaly the /controls/engines/engine*/augumentation value is set to true in this afterburning area. Attached is small diff to incorporate the joystick into the global configuration and the joystick configuration itself. In the hope that it might be useful: could someone apply this to the cvs tree please? Greetings Mathias -- Mathias Frhlich, email: [EMAIL PROTECTED] ? Input/Joysticks/ThrustMaster/Top-Gun-Afterburner.xml Index: joysticks.xml === RCS file: /var/cvs/FlightGear-0.9/data/joysticks.xml,v retrieving revision 1.25 diff -u -r1.25 joysticks.xml --- a/joysticks.xml 5 Jan 2004 20:48:00 - 1.25 +++ b/joysticks.xml 4 Mar 2004 10:04:46 - @@ -43,6 +43,7 @@ !-- ThrustMaster devices -- js-named include=Input/Joysticks/ThrustMaster/FCS.xml/ js-named include=Input/Joysticks/ThrustMaster/Attack-Throttle.xml/ + js-named include=Input/Joysticks/ThrustMaster/Top-Gun-Afterburner.xml/ !-- Lew Engineering RCJOY device for various RC transmitters. http://www.leweng.com -- js-named include=Input/Joysticks/LewEngineering/RC-transmitter-hitecLaser4.xml/ ?xml version=1.0? !-- $Id$ Bindings for THRUSTMASTER Top Gun Afterburner stick/throttle combination. This file is based on the Cyborg-Gold-3d-USB configuration file. So it provides maximum compatibility. ___ Layout ___ axis 0: aileron axis 1: elevator axis 2: rudder axis 3: throttle no modifier F3 F4 F3+F4 ~~ button 0 (trigger): brakes parking brake speed brake thrust revers. button 1 (top middle): flaps upgear up previous view * button 2 (front right): reset view dir tail wheel lock cockpit viewreset all trim button 3 (top right):flaps down gear down next view * button 4 (thr. down/back): brakes left * zoom out* button 5 (thr. middle/back): brakes right* zoom in * button 6 (thr. upper/back): modifier 0 / button 7 (thr. front): modifier 1 / hat left (axis5):look left leaner mixture aileron trimrudder trim hat right (axis5): look right richer mixture aileron trimrudder trim hat back (axis6):look down dec prop pitch elevator trim * hat forward (axis6): look up inc prop pitch elevator trim * F3 and F4 are used like Shift, Control, or Alternate on computer keyboards. For example: press F3 and keep holding it down while pressing the fire button/trigger - toggle parking brake Also this configurations will make use of the raster positions on the throttle. The idle position and below is really zero thrust command. Positions bewteen idle and afterburner will scale the thrust value between 0 and 0.98 and thus provides military power for jet engines. The afterburner raster will really turn on afterburning. Also to avoid additional deadband values in the linux kernel to the deadband values configured here in flightgear. You may need to issue the following command before starting flightgear: jscal -s 7,1,0,-5,5,4194304,4194304,1,0,-5,5,4194304,4194304,1,0,-5,5,4194304,4194304,1,0,128,128,4194304,4194304,1,0,112,142,5534751,5534751,1,0,0,0,536870912,536870912,1,0,0,0,536870912,536870912 /dev/input/js0 This will also avoid the useless deadband area in the middle of the throttle position. Also this will make the raster positions of the throttle match the programmed values here. ___ Customization If you want to change some (or all) of the bindings, the recommended way is to copy this file to your home directory, make your changes there, and include it from your personal preferences.xml file. Use the tags js-named n=100 and /js-named around the definitions, but within
Re: [Flightgear-devel] New joystick configuration.
Mathias Fröhlich wrote: Hi all, I have done a new joystick definition for my hardware. This is the thrustmaster top gun afterburner USB (what a name!) throttle/stick combination. It's committed. Thanks! Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [Fwd: [Fwd: Joystick XML for Logitech Extreme 3D Pro]]
William Earnest wrote: Original Message Subject: Joystick XML for Logitech Extreme 3D Pro Date: Sun, 29 Feb 2004 00:53:32 +0100 From: Johan Walles [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi! Here's a joystick configuration file for a Logitech Extreme 3D Pro. It's based on wingman-extreme-digital-3d-win.xml and has the same features. The only difference is that I've re-mapped the different functions to buttons that better match the layout of this joystick, and I had to change the numbers for the different axes (sp?) as well. This is also committed now. Thanks. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New joystick configuration.
On Donnerstag, 4. März 2004 11:37, Erik Hofman wrote: It's committed. Thanks! Oops, very fast! Thanks! Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New joystick configuration.
Mathias Fröhlich wrote: On Donnerstag, 4. März 2004 11:37, Erik Hofman wrote: It's committed. Thanks! Oops, very fast! It made me realize there was another joystick configuration file that needed to be committed. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: New joystick configuration.
* Melchior FRANZ -- Thursday 04 March 2004 11:54:
I doubt that this code will work (line 273):
patch attached
m.
Index: Top-Gun-Afterburner.xml
===
RCS file: /var/cvs/FlightGear-0.9/data/Input/Joysticks/ThrustMaster/Top-Gun-Afterburner.xml,v
retrieving revision 1.1
diff -u -p -r1.1 Top-Gun-Afterburner.xml
--- a/Top-Gun-Afterburner.xml 4 Mar 2004 10:37:44 - 1.1
+++ b/Top-Gun-Afterburner.xml 4 Mar 2004 11:08:19 -
@@ -270,7 +270,8 @@
twlock = !getprop(/controls/gear/tailwheel-lock);
setprop(/controls/gear/tailwheel-lock, twlock);
if (twlock) {
- rection Hat --} else {
+ gui.popupTip(Tail Wheel UNLOCKED);
+ } else {
gui.popupTip(Tail Wheel LOCKED);
}
} elsif (mod == 2) {
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: New joystick configuration.
On Donnerstag, 4. März 2004 11:54, Melchior FRANZ wrote:
* Mathias Fröhlich -- Thursday 04 March 2004 11:30:
Attached is small diff to incorporate the joystick into the global
configuration and the joystick configuration itself.
I doubt that this code will work (line 273):
if (twlock) {
rection Hat --} else {
gui.popupTip(Tail Wheel LOCKED);
}
You are totaly right. Thanks.
Fix attached.
Eric, could you cvs once more?
Greetings
Mathias
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
--- Top-Gun-Afterburner.xml.orig 2004-03-03 23:36:32.0 +0100
+++ Top-Gun-Afterburner.xml 2004-03-04 12:07:59.0 +0100
@@ -270,7 +270,8 @@
twlock = !getprop(/controls/gear/tailwheel-lock);
setprop(/controls/gear/tailwheel-lock, twlock);
if (twlock) {
- rection Hat --} else {
+ gui.popupTip(Tail Wheel UNLOCKED);
+ } else {
gui.popupTip(Tail Wheel LOCKED);
}
} elsif (mod == 2) {
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC readability
On 3/3/04 at 7:08 PM Jorge Van Hemelryck wrote: On Wed, 03 Mar 2004 11:06:57 + David Luff wrote: I can think of a number of improvements. The first, and one which would also help the voice output, is that many of the airport names pulled automatically from the DAFIF are far too long - for instance Metropolitan Oakland International Tower should almost certainly be simply Oakland Tower. I'll go through these and try to manually change as many as possible to what seems right - in fact I'll run a script to remove International from all of them. Some of them are tricky though - should Brisbane Archerfield be Brisbane Tower or Archerfield Tower. I'm guessing the latter since there's also a Brisbane International. What about Burbank Glendale Pasadena - that could be any of the three! If real life pilots, or those who otherwise know definately, could send me corrections for their favourite airports that would be great. There would be a double benefit here - less length of message to read, and less of it going off the edge of the screen. Hi David, Actually, what pilots are supposed to do, at least in France, is use the part of the name that is written in bold face on the charts (national ones). On Jeppesen IFR charts, it looks like we're supposed to use the name written in slightly larger characters, at the top of the chart, above the rest of the name of the airport. That should work most of the time. Ah, excellent idea. I see that tower names are on the taxiway diagrams on AOPA's website, which covers a large number of US airports. Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Authentic DC-3 Sounds
Jim Wilson wrote: Cleaning up my harddrive I came across a package I downloaded a while back but never really looked at closely. It is a directory of sound files recorded and edited for use with MSFS. They are very good quality recordings made aboard a real DC-3: I recorded these GREAT sounds from my many DC-3 flights inside and outside our own DC-3 (N763A) using 3 microphones and then putting them through an equalizer in a sound studio before converting them to WAV files for simmers. They are THE BEST !! It is hoped you enjoy them. The author has released them unconditionally, other than the request that his name is mentioned, so they would of course be eligible for inclusion in FlightGear. At the moment I'm pretty tied up with other things. There are maybe two dozen small files, quite a bit of detail. Anyone interested in taking this and configuring them for our DC-3? If so I'll pass them along. This is from about a year ago ... Jim did anything ever come of this? Would be a cool addition to the FG DC-3. Regards, Curt. -- Curtis Olson Intelligent Vehicles Lab 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] Authentic DC-3 Sounds
Curtis L. Olson wrote: There are maybe two dozen small files, quite a bit of detail. Anyone interested in taking this and configuring them for our DC-3? If so I'll pass them along. This is from about a year ago ... Jim did anything ever come of this? Would be a cool addition to the FG DC-3. Sure is. Maybe I should free some time otherwise. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Authentic DC-3 Sounds
Curtis L. Olson said: Jim Wilson wrote: Cleaning up my harddrive I came across a package I downloaded a while back but never really looked at closely. It is a directory of sound files recorded and edited for use with MSFS. They are very good quality recordings made aboard a real DC-3: I recorded these GREAT sounds from my many DC-3 flights inside and outside our own DC-3 (N763A) using 3 microphones and then putting them through an equalizer in a sound studio before converting them to WAV files for simmers. They are THE BEST !! It is hoped you enjoy them. The author has released them unconditionally, other than the request that his name is mentioned, so they would of course be eligible for inclusion in FlightGear. At the moment I'm pretty tied up with other things. There are maybe two dozen small files, quite a bit of detail. Anyone interested in taking this and configuring them for our DC-3? If so I'll pass them along. This is from about a year ago ... Jim did anything ever come of this? Would be a cool addition to the FG DC-3. Actually I did pass those along to someone who was working on a DC3 cockpit at the time and then later dropped it. If anyone is interested let me know and I'll send a link. They are pretty good samples. Almost all are 8-bit already. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] 2D EFIS Instrument
On Fri 27. February 2004 14:23, you wrote: Roy Vegard Ovesen wrote: Basically you would move the texture offsets rather than the surface itself. Is this possible with 2D instruments too? As the original author of the 2D instrument code, I *strongly* advise against building 2D instruments. Since I switched to an all 3D panel in the plane I'm working on, my framerate has gone from 10-15 fps to 20-30 fps (admittedly on a low-end card), even with larger textures. I think that the only thing missing from the 3D animation code now is text, and that should be easy to add. We'll need to support the 2D code for a while because there are so many existing instruments that use it, but it's a serious mistake to start a new 2D instrument at this point. The 2D code still requires 3D rendering (since the instruments appear in a 3D scene graph), so there are no gains, but I'm guessing that the texture stacking for 2D instruments causes OpenGL state changes that are expensive, at least with my graphics card (GeForce2Go). The finest solution will be, If someone write loader for 2d instruments which converts them on fly to 3d instruments. every information is already in xml and what you only need to add is z-coordinate which you can simply increment on every layer. The most advantage of 2D instrument is that you can compute coordinates with more than one pixel precision. If all you have for ac files is blender uv editor... Regards, Madr -- Martin Dressler e-mail: [EMAIL PROTECTED] http://www.musicabona.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] A load of YASim engine stuff
David Megginson writes: For the record, I fly lean of peak, wide-open throttle regularly in cruise -- my engine runs cooler, I burn a lot less gas to produce the same power (about 8.5 gph instead of 10 gph), my spark plugs don't foul, and the risk of CO poisoning virtually vanishes, so there's not much to dislike about it. From a non-pilot engineer's point of view this makes perfect sense. At wide-open throttle you've reduced the pumping losses, and by running lean of peak you increase the engine's thermal efficiency. The key is not to go so lean that combustion becomes unstable. This is effectively how diesel engines are controlled (without the lean combustion stability limits inherent in homogenous-charge gasoline engines), and is one of the reasons why they are more efficient than their gasoline cousins. Diesels are much more popular in private cars in Europe than in the States - my wife drives a small, 1.4litre diesel hatchback, and this is regarded as perfectly normal. Of course, it's possible that my perception of the States as diesel-hating gasoline guzzlers is out of date by now! The reason for the lack of lean-burn cruise in most current automotive gasoline engines is entirely due to emissions regulations. Of the three main pollutants legislated against, two (unburned hydrocarbons [HC] and CO) must be oxidised (to H2O and CO2) and one (NOx) must be reduced (to N2). Running the engine at a stoichiometric (just the correct amount of oxygen for complete combustion) air-fuel ratio and using a 3-way catalyst allows an order of magnitude reduction of these pollutants post catalyst. Running lean and trying to reduce NOx in an oxygen rich exhaust stream has been likened to drying one's washing in a rainstorm. An effective lean NOx trap is one of the 'holy grails' of aftertreatment engineering, and would probably allow an immediate reduction of at least 10% in fuel consumption from new gasoline engines calibrated for lean cruise if available, and probably more in the future since lean-burn stability would inevitably receive more design focus. I'm not entirely sure what the current and future legislative landscape looks like as far as general aviation is concerned - are you likely to face emissions regulations in the near future? I'm pretty sure they're starting on the bikers now. Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New joystick configuration.
Matthias Frohlich wrote: I have done a new joystick definition for my hardware. This is the thrustmaster top gun afterburner USB (what a name!) throttle/stick combination. Wow, that's some significant Nasal hackery. Very cool. :) When inline scripts get that elaborate, it's probably a good idea to split them out into a CyborgGold3DUSB.nas file which would presumably be easier to maintain. You could, for example, store the current joystick mode as a module-scoped Nasal variable and not have to worry about getting it out of the property system. Some stuff, like the differential brake handling and afterburner range mapping, could even go into controls.nas for other sticks to use. The afterburner handling would obviously have to be configurable though. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: New joystick configuration.
* Andy Ross -- Thursday 04 March 2004 21:26: Wow, that's some significant Nasal hackery. Very cool. :) Yes. I like it a lot. While it looks quite intimidating at first, it's quite easy to remember. Makes the joystick very powerful. When inline scripts get that elaborate, it's probably a good idea to split them out into a CyborgGold3DUSB.nas file which would presumably be easier to maintain. It's probably a border case, but I still like it better inline. Having the nasal code external would mean to have to keep track of both files and to open both when editing etc. The only thing that I miss is vim's syntax highlighting. Some stuff, like the differential brake handling and afterburner range mapping, could even go into controls.nas for other sticks to use. I'm not sure if the differential brake handling is desirable. It doesn't feel any better than crude binary (0/1) braking. I've discussed this with Mathias today, and I'd like to hear Dave's and Josh's opinion. One has to interval-brake in any case, and the interpolate method may be smoother, but it is also less responsive and, before all, it lags behind after releasing. Of course, one could make releases faster, but is it still(?) superior to the keyboard method then? m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] More YASim engine stuff: chilly exhaust
I've just added an EGT (exhaust gas temperature) gauge to the pa28-161 model, and it showed up another YASim engine issue (apologies to Andy for posting only about the problems -- the model flies beautifully for the most part). With the engine running at full blast, YASim sets /engines/engine[0]/egt-degf to about 58 degF, or 14.5 degC, while the outside air temperature is 14.3 degC. That's one cool exhaust. I don't know exactly how hot the EGT should be, but I know that it's hotter than that. My plane is heated by a shroud around the muffler, and even the heating duct on my floor, a long way from the shroud, is extremely hot to the touch. I'm guessing that we should be seeing exhaust gas temperatures at least around 250-350 degF, but I have no solid basis for that guess right now. Is there perhaps just a conversion error in YASim somewhere? All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Authentic DC-3 Sounds
Jim Wilson wrote: Actually I did pass those along to someone who was working on a DC3 cockpit at the time and then later dropped it. If anyone is interested let me know and I'll send a link. They are pretty good samples. Almost all are 8-bit already. If you sent them over I'll free some time take a look at them. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] More YASim engine stuff: chilly exhaust
David Megginson wrote: (apologies to Andy for posting only about the problems -- the model flies beautifully for the most part). Don't be silly. I can't fix that. With the engine running at full blast, YASim sets /engines/engine[0]/egt-degf to about 58 degF, or 14.5 degC, while the outside air temperature is 14.3 degC. That's one cool exhaust. Heh, yeah, that sounds wrong. YASim comes up with an exhaust pressure via some thermodynamic prestidigitation that I remember being really (heh, really) proud of when I wrote it. I'm sure I must have convinced myself that it was working before I let my ego loose. Maybe something has broken since, or there's a conversion issue that never got fixed. Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Stackdump
I've just had FlightGear stackdump after about 15min of flight with the default Cessna in the Bay Area under gdb with the following backtrace: (gdb) bt #0 0x083d8936 in ssgVtxTable::draw() () #1 0x083c3a13 in ssgLeaf::cull(sgFrustum*, float (*) [4], int) () #2 0x083c10e5 in ssgBranch::cull(sgFrustum*, float (*) [4], int) () #3 0x083c10e5 in ssgBranch::cull(sgFrustum*, float (*) [4], int) () #4 0x083d1d6e in ssgRangeSelector::cull(sgFrustum*, float (*) [4], int) () #5 0x083d00b6 in ssgTransform::cull(sgFrustum*, float (*) [4], int) () #6 0x083c10e5 in ssgBranch::cull(sgFrustum*, float (*) [4], int) () #7 0x083c10e5 in ssgBranch::cull(sgFrustum*, float (*) [4], int) () #8 0x083c2226 in ssgContext::cull(ssgRoot*) () #9 0x083bea96 in ssgCullAndDraw(ssgRoot*) () #10 0x080547e6 in fgRenderFrame() () at main.cxx:651 #11 0x080560d6 in fgMainLoop () at main.cxx:1217 #12 0x4009be2e in __glutRegisterEventParser () from /usr/lib/libglut.so.3 #13 0x4009c4db in glutMainLoop () from /usr/lib/libglut.so.3 #14 0x08058323 in fgMainInit(int, char**) (argc=2, argv=0xbae4) at main.cxx:1706 #15 0x080527fa in main (argc=2, argv=0xbae4) at bootstrap.cxx:139 I'll keep it open for half an hour or so in case anyone with an idea of what's going on has any suggestions for variables to look at, but this seems to be repeatable (hence the run under gdb). Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: Stackdump
* David Luff -- Thursday 04 March 2004 22:27: I've just had FlightGear stackdump after about 15min of flight with the default Cessna in the Bay Area under gdb with the following backtrace: Doesn't look familiar, although I've got a couple of core dumps lately. (I'm *never* running fgfs outside gdb since two weeks! If my nvidia driver encounters a crash/abort, I have to reboot! Doesn't release the keyboard and I have no network here.) You should be able to store the core-dump for later. No need to wait: (gdb) apropos core ... gcore -- Save a core file with the current state of the debugged process generate-core-file -- Save a core file with the current state of the debugged process m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ATC readability
On Wed, 3 Mar 2004 22:43, [EMAIL PROTECTED] wrote: From: David Luff I can think of a number of improvements. The first, and one which would also help the voice output, is that many of the airport names pulled automatically from the DAFIF are far too long - for instance Metropolitan Oakland International Tower should almost certainly be simply Oakland Tower. I'll go through these and try to manually change as many as possible to what seems right - in fact I'll run a script to remove International from all of them. Some of them are tricky though - should Brisbane Archerfield be Brisbane Tower or Archerfield Tower. I'm guessing the latter since there's also a Brisbane International. What about Burbank Glendale Pasadena - For Australia, you are right. At Melbourne we have: A YMEN -37.729331 144.902436 282 CYN Melbourne Essendon A YMML -37.665503 144.836555 434 CYN Melbourne Intl A YMMB -37.977134 145.10045250 CYN Melbourne Moorabbin They are respectively, Essendon Tower/Ground etc, Melbourne Tower, Moorabbin Tower. It can get a little tricky though, Hobart has: A YMHB -42.836161 147.51177513 CYY Hobart A YCBG -42.827514 147.47703367 CYY Hobart Cambridge which would be Hobart Tower and Cambridge Tower, so you can't rely on the 'International' being present for the major airport. Nick ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Question on Solaris 9 stops on xml part and base pak will not untar on a SUN box
Greetings, I have 2 problems, one with the tar file and the other with the program stopping on the XML. I have a SUN ultra2 2200 3D creator with Solaris 9, Open GL 1.2.3 and have installed the ready to run Flightgear 0.9.3 with the base pak. I start it up and a Xwindow appears with a picture of the Flightgear title and a airplane. The command tool window stops on the xml part of the electrical system of a 172 or any other aircraft I pick. It seems like the XML part has a problem. -- Initializing Interpolator for /usr/local/FlightGear/Navaids/range.high Reading electrical system model from /usr/local/FlightGear/Aircraft/c172/c172-electrical.xml -- One other thing, When I downloaded the base pack fgfs-base-0.9.3.tar I tried the gz and the bz2 file and kept getting a checksum error when I tried to untar the file. --- x FlightGear-0.9.3/data/Docs/source/FlightGearSchool/pics/start.jpg.gz, 64937 bytes, 127 tape blocks x FlightGear-0.9.3/data/Docs/source/FlightGearSchool/pics/chap_basics_fundament, 0 bytes, 0 tape blocks tar: directory checksum error I had to use my PC with the bz2 uncompress utility and that seemed to work but did give an error. I then zipped up the dir from the pc and ftped the zip file over and unzipped it on the SUN box. Does any one have any ideas on what I am doing wrong? Thanks Andy ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New joystick configuration.
On Donnerstag, 4. März 2004 21:26, Andy Ross wrote: Wow, that's some significant Nasal hackery. Very cool. :) Cool to have nasal ;) When inline scripts get that elaborate, it's probably a good idea to split them out into a CyborgGold3DUSB.nas file which would presumably be easier to maintain. You could, for example, store the current joystick mode as a module-scoped Nasal variable and not have to worry about getting it out of the property system. This is desirable if many joysticks use the same configurations. How many joysticks are nasal based to that degree? And how many of them could live with a similar configuration? Hmm, I think that at least the hat functions make much sense for many joysticks the way they are implemented and grouped together. Some stuff, like the differential brake handling and afterburner range mapping, could even go into controls.nas for other sticks to use. The afterburner handling would obviously have to be configurable though. Yep. Would be ok for me. Additionaly to the throttle afterburning stuff I, thought about an engine switch on/off below that idle raster position. Also I can think of arresting the parking brake if the throttle is below that idle position. I believe that the jostick is default configured like this if you use it under windows together with other sims. The downside would be that for a throttle without such rasters like mine has, it would be desirable to check if you have afterburning and according to that, either use the full range of the throttle for normal thrust or behave like my nasal stuff in the other case. But for the raster positions this is not a good idea, just because these rasters are too heavy to do fine regulations in the area of them. So I would prefer for my hardware to behave the same regardless of an installed afterburner. In summary, I think that if someone has compact readable code providing these configurable features this would be perfectly ok. If it blows up too much more likely not. Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Question on Solaris 9 stops on xml part and base
Murray wrote: I start it up and a Xwindow appears with a picture of the Flightgear title and a airplane. The command tool window stops on the xml part of the electrical system of a 172 or any other aircraft I pick. It seems like the XML part has a problem. [...] One other thing, When I downloaded the base pack fgfs-base-0.9.3.tar I tried the gz and the bz2 file and kept getting a checksum error when I tried to untar the file. I assume the latter is the reason for the first one. Please verify if the base package file size is correct. I assume your base package is incomplete: crimson: 8:46:10 /archive/Mirrors/ftp.flightgear.org/Shared uname -a SunOS crimson 5.8 Generic_108528-27 sun4u sparc SUNW,UltraSPARC-IIi-Engine crimson: 8:46:15 /archive/Mirrors/ftp.flightgear.org/Shared md5sum fgfs-base-0.9.3* 3717ddd1ad3aa35df6b458a878835c8e fgfs-base-0.9.3.tar.bz2 ac58d5a0b7fc67060892773d98d994e2 fgfs-base-0.9.3.tar.gz Curt, would it be feasible to let MD5 checksums accompany large download packages on the ftp-server ? Martin. P.S.: and _please_ avoid this silly HTML in your EMail. -- 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
