Re: [Flightgear-devel] Re: Windsock Model
WillyB wrote: > > Here's a screenshot if anyone cares to have a look. > http://24.121.17.106/fgfs/scenery/fgfs-windsock.png I always found that there is something odd visually with the winsock. It seems that the normals are inside and not outside. David, do you still have the blender model ? If you can't fix it, could you send it to me ? -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Windsock Model
Whoops! I didn't see this post until after I posted the last one... Feet NOT Meters ... duh :/ So it was there all along, just a few 1000 feet under the ground! Thanks Melchior Here's a screenshot if anyone cares to have a look. http://24.121.17.106/fgfs/scenery/fgfs-windsock.png Many thanks for the help here Melchior Re's WillyB On Thursday 19 June 2003 16:35, Melchior FRANZ wrote: > * WillyB -- Friday 20 June 2003 00:59: > >1042.34 > > ^^ ^^ > > elevation-ft is in =feet=. Try this: > > 3420 > > m. > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ 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 #else #include #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
Re: [Flightgear-devel] Re: Windsock Model
Ok... I made a my_preferences.xml in the data dir. On the command line: /home/willyb/Games/FG/runfg-9.2.sh --config=/home/willyb/Games/FG-0.9.2/data/my_preferences.xml -- excerpt from console -- log-level Initializing scenery subsystem Adding model Windsock KIGM Loading stars from /home/willyb/Games/FG-0.9.2/data/Astro/stars Loaded 850 stars initializing cloud layers -- end excerpt -- so from that I can see that it's reading my_preferences.xml But it doesn't show up :/ Not sure what to do now except ask again. this I doubt matters.. my scenery dir is not anywhere near the data dir.. I use an .sh script to load fgfs and it gives the peremeters for --fg-root=/where/fg-data/directory/is --fg-scenery=/where/scenery/is I'll try some other stuff also while I wait to see a reply Re's WillyB On Thursday 19 June 2003 16:10, Melchior FRANZ wrote: > * WillyB -- Friday 20 June 2003 00:59: > > you said 'personal preferences.xml' > > $ fgfs --config=/your/personal/preferences.xml > > or > > $ cat ~/.fgfsrc > --config=/your/personal/preferences.xml > > $ fgfs > > > (mine is called ~/.fgfs/preferences.xml. I have some other > personal fgfs config stuff in the hidden ~/.fgfs/ dir as well.) > > m. > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: Windsock Model
* WillyB -- Friday 20 June 2003 00:59: >1042.34 ^^ ^^ elevation-ft is in =feet=. Try this: 3420 m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: Windsock Model
* WillyB -- Friday 20 June 2003 00:59: > you said 'personal preferences.xml' $ fgfs --config=/your/personal/preferences.xml or $ cat ~/.fgfsrc --config=/your/personal/preferences.xml $ fgfs (mine is called ~/.fgfs/preferences.xml. I have some other personal fgfs config stuff in the hidden ~/.fgfs/ dir as well.) m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Windsock Model
Hmmm... you said 'personal preferences.xml' I put it in just 'preferences.xml' at the very end, (which could be my problem now) like this: Windsock KIGM Models/Airport/windsock.xml -113.9351 35.2580 1042.34 ## this part is the end of the file.. I didn't put any PropertyList tags in at all... as they are already there. That didn't work.. when I put the model itself in the stg file: (I copied windsock.ac and windsock.rgb to the dir the stg file is in) OBJECT_STATIC windsock.ac -113.9351 35.2580 1042.34 90 It shows up where I expected it to show up. It's getting lost somewhere. I don't have a personal preferences.xml and am assuming that it will work in the regular preferences.xml - which is probably where I'm going wrong. On Thursday 19 June 2003 14:03, Melchior FRANZ wrote: > * WillyB -- Thursday 19 June 2003 22:49: > > Do I place a property=/Models/Airport/windsock.xml somewhere in the > > options.xml or preferences.xml ? > > You put it in your personal preferences.xml file, like so: > > > > > Windsock KSFO > Models/Airport/windsock.xml > -122.3606 > 37.6136 > 0 > > > > > m. > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Mac OS X binary is up
http://homepage.mac.com/walisser/.cv/walisser/Public/FlightGear/fgfs- 0.9.2-06.19.03.gz-link.gz ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Windsock Model
Thanks Melchior... I 'almost' tried something similar to that! I think I was confusing it beyond it's confusion factor and then not dividing by 3.65 brain cells ;) Re's WillyB On Thursday 19 June 2003 14:03, Melchior FRANZ wrote: > * WillyB -- Thursday 19 June 2003 22:49: > > Do I place a property=/Models/Airport/windsock.xml somewhere in the > > options.xml or preferences.xml ? > > You put it in your personal preferences.xml file, like so: > > > > > Windsock KSFO > Models/Airport/windsock.xml > -122.3606 > 37.6136 > 0 > > > > > m. > > ___ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: Windsock Model
* WillyB -- Thursday 19 June 2003 22:49: > Do I place a property=/Models/Airport/windsock.xml somewhere in the > options.xml or preferences.xml ? You put it in your personal preferences.xml file, like so: Windsock KSFO Models/Airport/windsock.xml -122.3606 37.6136 0 m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Windsock Model
I asked this on the Users list, probably the wrong one to be asking on ;) Or maybe it's already been answered somewhere but I didn't see it In the 0.9.2 release there is a windsock model with an xml file included... /FG-0.9.2/data/Models/Airport/windsock.ac /FG-0.9.2/data/Models/Airport/windsock.rgb /FG-0.9.2/data/Models/Airport/windsock.xml When I turn on the --wind or the --random-wind I can't really tell from inside the sim where the wind is coming from exactly, and know that a windsock will help with this. Do I place a property=/Models/Airport/windsock.xml somewhere in the options.xml or preferences.xml ? Like maybe in this section of preferences.xml ? I have not been able to get the windsock to work at all as far as making it turn with the wind, I can get it to show up by putting it in the stg file and dir that file is in, but no idea how to make the xml for it do what it's made to do. Any help or insight will be appreciated :) TIA Re's WillyB ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: [PATCH] Instruments/hsi.xml: unbreak it :-)
* Melchior FRANZ -- Thursday 19 June 2003 20:07: > The reported breakage of the hsi was caused by wrong lower limits. The patch does not fix the "heading bug". If you lock the AP on heading, it doesn't head to the bug. The hsi2.xml uses /instrumentation/heading-indicator/indicated-heading-deg instead of /orientation/heading-magnetic-deg, and works better. Both, however, do not yield exact behavior, though. Even the hsi2 is slightly off. Ideas? m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
re: [Flightgear-devel] [PATCH] Instruments/markerbeacon.xml: fix outer marker control light
Melchior FRANZ writes: > I guess that everyone has wondered about the outer marker control > light already. It has been on since 2003/03/09. Didn't blink since > then. :-) I saw my marker lights (on my KMA 24 audio panel) flash for the first time when I was flying down to NYC on Monday: we don't use OMI markers at all in Canada. I was overflying Albany at 7500 feet, and I saw first the O and then the M markers light up, one after the other (I also pushed the button to listen to the audio), just for fun. Canada got rid of markers a while ago and now uses an NDB instead of an outer marker as the FAF for ILS approaches: that has several advantages, including the ability to navigate directly to the IAF/FAF, the ability to see how close you are to intercepting the LOC (and whether you're being vectored too tight), and the ability to allow NDB approaches when the LOC goes U/S (as happened with the LOC/BC 25 approach in Ottawa last week: I wonder how the Boeing and Airbus drivers felt tuning into the ATIS and hearing "approach NDB 25"). 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
[Flightgear-devel] [PATCH] Instruments/hsi.xml: unbreak it :-)
The reported breakage of the hsi was caused by wrong lower limits. m. Index: hsi.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/Instruments/hsi.xml,v retrieving revision 1.8 diff -u -p -r1.8 hsi.xml --- hsi.xml 9 Mar 2003 03:41:48 - 1.8 +++ hsi.xml 19 Jun 2003 18:04:33 - @@ -93,14 +93,14 @@ Started 24-7-01 by Timothy Gale rotation /orientation/heading-magnetic-deg -0.0 -360 +-360.0 +360.0 -1.0 rotation /radios/nav[0]/radials/selected-deg -0.0 +-360.0 360.0 1.0 @@ -158,14 +158,14 @@ Started 24-7-01 by Timothy Gale rotation /orientation/heading-magnetic-deg - 0.0 - 360 + -360.0 + 360.0 -1.0 rotation /radios/nav[0]/radials/selected-deg - 0.0 + -360.0 360.0 1.0 @@ -187,15 +187,15 @@ Started 24-7-01 by Timothy Gale rotation /orientation/heading-magnetic-deg -0.0 -360 +-360.0 +360.0 -1.0 rotation /radios/nav[0]/radials/selected-deg -0.0 -360 +-360.0 +360.0 1.0 @@ -223,10 +223,9 @@ Started 24-7-01 by Timothy Gale rotation - /radios/kr-87/outputs/needle-deg - -360 - 360 + -360.0 + 360.0 x-shift ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] c310-{electrical,ifr-set}.xml: fix adf/dme forc310{,-ifr,-3d}
I'm not sure if I connected adf and dme to the correct bus, but it's time that c310s have them working. There was a temporary workaround in c310-ifr-set.xml, but not for the c310-3d (= c310u3a-3d), the plain c310 and eventually others. m. Index: c310-ifr-set.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/c310-ifr-set.xml,v retrieving revision 1.5 diff -u -p -r1.5 c310-ifr-set.xml --- c310-ifr-set.xml20 Apr 2003 10:05:20 - 1.5 +++ c310-ifr-set.xml19 Jun 2003 17:20:29 - @@ -14,13 +14,6 @@ March 2002 Jim Wilson, [EMAIL PROTECTED] - - - - Aircraft/c172/c172-electrical.xml - - - Cessna 310 with IFR panel Index: c310/c310-electrical.xml === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/c310/c310-electrical.xml,v retrieving revision 1.4 diff -u -p -r1.4 c310-electrical.xml --- c310/c310-electrical.xml1 Apr 2003 15:46:52 - 1.4 +++ c310/c310-electrical.xml19 Jun 2003 17:20:29 - @@ -72,6 +72,8 @@ Instrument Power /systems/electrical/outputs/instr-ignition-switch +/systems/electrical/outputs/adf +/systems/electrical/outputs/dme ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] Instruments/markerbeacon.xml: fix outer marker control light
I guess that everyone has wondered about the outer marker control light already. It has been on since 2003/03/09. Didn't blink since then. :-) m. diff -u -p -r1.2 markerbeacon.xml --- markerbeacon.xml9 Mar 2003 03:41:48 - 1.2 +++ markerbeacon.xml19 Jun 2003 16:43:02 - @@ -45,11 +45,11 @@ properties' values. lamp switch + +/radios/marker-beacon/outer + on - - /radios/marker-beacon/outer - Aircraft/Instruments/Textures/led.rgb 0.5 0.75 ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] Instruments/hsi2.xml: fix path
diff -u -p -r1.5 hsi2.xml --- hsi2.xml20 Apr 2003 10:05:20 - 1.5 +++ hsi2.xml19 Jun 2003 15:54:27 - @@ -115,7 +115,7 @@ Started 24-7-01 by Timothy Gale switch - + FROM flag ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
Hi Jim unfortunately that is what I meant. cheers Innis Jim Wilson wrote Currently this won't work with 2D panels, if that is what you meant. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel _ Get mobile Hotmail. Go to http://ninemsn.com.au/mobilecentral/signup.asp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] larcsim multiply-defined global var
Yeah, it's the old multiply-defined global problem again. Here's the quick fix (just extern'd one of the definitions): http://homepage.mac.com/walisser/downloads/flightgearlarcsim.diff ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] unsupported extensions on Mac
It turns out that there is a better way to fix it. Apple supports the ARB version of point parameters: GL_ARB_point_parameters. I think it takes the same arguments, but to different function names, and uses different constant names (though in actuality, they have the same value). http://oss.sgi.com/projects/ogl-sample/registry/ARB/point_parameters.txt Here's a new patch, that takes this into account: http://homepage.mac.com/walisser/downloads/flightgearpointparams2.diff I didn't notice any change with or without this extension enabled (can we get a screen shot up of what the runway lights are supposed to look like?). I don't know if it's being used incorrectly or if it is unsupported somehow in the hardware (GL_ARB_point_paramters is reported in the extensions string, btw). On Thursday, June 19, 2003, at 09:12 AM, [EMAIL PROTECTED] wrote: Darrell Walisser wrote: The point parameters extensions are unsupported in Apple's GL stack. The fix I've chosen is #ifdef GL_SGIS_point_parameters // do stuff here #endif Although I don't like to fix it this way (if all was correct this wouldn't be necessary because it adds another compile time option while extensions should be able to be runtime options only) I put it in CVS because this weekend I'll be quite busy as it stands now and I like to get CVS in a workable state again. Thanks for the help Darrell. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] buildings and textures and blender2.25
Jim Wilson wrote: > Shading is done per object (normals generated on the fly). If you > need a square edge, split the adjacent sides into individual objects. > For example on the P-51D and AFAIK Lee's models, the blunt edges of > the control surfaces (e.g. flaps, ailerons) are separate objects. That reminds me. One of the things I need to think about porting over into plib* is some code I wrote that automatically splits vertices at sharp edges. It was a royal pain to get right, but it actually works quite well for arbitrary meshes. Right now, it works on a very different mesh representation than plib uses, and I'm not sure what the best way to integrate it would be. Andy * My game project is slowing down, and I'm actually looking for a job again.** ** The difficulty of which is proving to be a real shock. The last time I was in the market was 1998 in San Francisco, when you had to actually screen your calls to avoid talking to recruiters. Portland in 2003 isn't nearly as forgiving... -- 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] glass cockpit
David Culp <[EMAIL PROTECTED]> said: > > 1). Does anyone know what the two "feather wing like" icons are supposed to > > indicate and what they do if/when they move (look to each side of the 15 > > degree pitch line in the second picture)? > > The pitch limit symbols in the 737 are only visible when the flaps are not up. > They indicate the pitch that would cause stick-shaker activation. > > > 3). And does the MAG mode in the Boeings behave like the whiskey compass in > > the Cessnas? That is, should it be snagging up when in a 30 degree bank or > > should it pretty much work in a turn? > > No. It displays heading accurately. And, as John pointed out, everything else > works too. For instance, make sure you use: > /velocities/vertical-speed-fps, converted to fpm, rather than > /instrumentation/vertical-speed-indicator/indicated-speed-fpm for the > vertical speed indication. Yes, I got that one wrong too. How about the backup instrumentation? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
Tim Jelliffe <[EMAIL PROTECTED]> said: > 1). Does anyone know what the two "feather wing like" icons are supposed > to indicate and what they do if/when they move (look to each side of the > 15 degree pitch line in the second picture)? > > They also adjust depending on the situation. So when at altitude and > high speed, they may only be a few degrees above the horizon, so they > aren't always at the 15 degrees or whatever. Someone correct me if > that's wrong, but I seem to remember this from a jumpseat ride a while > ago. In fact, if you look at > http://www.airliners.net/open.file/123982/L/ > this is a 717, and the lines are blue, but you can just see them just > above the horizon. Yes. It'd be great if someone wanted to start working on an FMC subsystem. What I'm doing here is just display level, working with the data we already have. > Is the stuff you are doing in any way related to OpenGC? For example > could their gauges be used straight on to the panel? Just wondering > Well, I did borrowed the rose from a screenshot of OpenGC. Other than that, OpenGC is actually a much more powerful application that I'm not attempting to emulate. I've only looked at the code a little, and haven't set it up, but IIRC the digital display textures are generated dynamically. What I'm doing here is a lot simpler (gimp and ac3d). That said, there will be an engine display, and fortunately the 747 one looks easier to do this way than the one in OpenGC. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
> 1). Does anyone know what the two "feather wing like" icons are supposed to > indicate and what they do if/when they move (look to each side of the 15 > degree pitch line in the second picture)? The pitch limit symbols in the 737 are only visible when the flaps are not up. They indicate the pitch that would cause stick-shaker activation. > 3). And does the MAG mode in the Boeings behave like the whiskey compass in > the Cessnas? That is, should it be snagging up when in a 30 degree bank or > should it pretty much work in a turn? No. It displays heading accurately. And, as John pointed out, everything else works too. For instance, make sure you use: /velocities/vertical-speed-fps, converted to fpm, rather than /instrumentation/vertical-speed-indicator/indicated-speed-fpm for the vertical speed indication. Dave Culp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
paul mccann <[EMAIL PROTECTED]> said: > Jim looks great, just like the real thing. Coming from someone who would know, that's good to hear...thanks! > 1. they are ptich limit bars or symbol, you will get to stick shaker or > stall if you pitch up to them. Ah ok. We might have to hold off on animating those. I take it the FMC calculates their position. Is that true? > 2. On the 737 the dg or compass has 7 modes > 1. nav (full)/ looks like hsi but really showing track not heading > and relation to stored route not vor or ils info > 2. vor ils (full)/ looks like regular hsi and acts like one, plus > shows magnetic heading > 3. nav (expanded)/ same as above but you only see half the compass > 4. vor ils (expanded) " " > 5. map /this mode shows cours line and little triagle which is the > aircraft, also shows track not magnetic heading. > 6. center map same as above but full compass rose. > 7. plan /static map Initially I'll probably just do the vor ils. The rest will depend on an FMC subsystem being coded. > 3. Compass does not behave like wiskey compass. Its getting signals > from ring laser gyro and irs. So it does not drift turn wrong way or > display any of those things. That's easy to model! It's the errors that are the most challenging. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
Innis Cunningham <[EMAIL PROTECTED]> said: > Thanks Jim looks great. Thanks! > You wouldn't like to share the secrets of the xml code you use to get the > compass rose to part show and the speed and altitude strips to work.Is it > just that the strips are hidden under other layers or is there some little > secret you have found.MATE! LOL > The xml is 3D Model animation xml. There are some modifications to the animation code for sliding textures around that aren't quite complete yet. If I can clean up a few things I'll submit the latest changes to that. Currently this won't work with 2D panels, if that is what you meant. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
Thanks Jim looks great. You wouldn't like to share the secrets of the xml code you use to get the compass rose to part show and the speed and altitude strips to work.Is it just that the strips are hidden under other layers or is there some little secret you have found.MATE! LOL Cheers Innis Jim Wilson wrote >Here's a rough start on the PFD for the Boeing 747-400: http://www.spiderbark.com/fgfs/pfd01.png http://www.spiderbark.com/fgfs/pfd02.png _ Hotmail is now available on Australian mobile phones. Go to http://ninemsn.com.au/mobilecentral/signup.asp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New buildings models
David Megginson writes: > We don't distinguish between buildings and terrain, so this would also > cause the plane to fall throught he surface of the earth when taxiing. In plib you can mark flag objects for inclusion/exclusion from the intersection test. However, I don't know if the flightgear hit code honors that flag? Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org 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] is it me or hsi
Hi Paul The panel I have the instrument on is a 737 panel I am working on.If you say things are working fine on the 9.2 binaries version I will have a fly and see what happens.I fly (test) mostly in the old CVS version I have which is at least 3 weeks old.Because I can do development work in there and if I break somthing it does not matter.Why dont I up date I hear you say.Well I have seen that things have been a little unsetled in the CVS area lately.So I am woking on the theory "If it an't F***ed don't fix it"Once I have time to spare I will update but for the time being I would just like to get a reasonable panel up for the 737. Thanks for the heads up. Cheers Innis paul mccann wrote Oh ok, but I am some what confused now because I updated from cvs last night after reading your message, and do not get the error your talking about. You did the following fgfs --aircraft=c310-ifr , and you still get this? If so are using cvs version or 9.2? In either case its in the xml instrument files not the c code. You could also try the hi-res 172 panel which has the best hsi, and see if that works. Paul ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel _ Get mobile Hotmail. Go to http://ninemsn.com.au/mobilecentral/signup.asp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] [PATCH] unsupported extensions on Mac OS X
Darrell Walisser wrote: The point parameters extensions are unsupported in Apple's GL stack. The fix I've chosen is #ifdef GL_SGIS_point_parameters // do stuff here #endif Although I don't like to fix it this way (if all was correct this wouldn't be necessary because it adds another compile time option while extensions should be able to be runtime options only) I put it in CVS because this weekend I'll be quite busy as it stands now and I like to get CVS in a workable state again. Thanks for the help Darrell. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] glass cockpit
Hi Jim, 1). Does anyone know what the two "feather wing like" icons are supposed to indicate and what they do if/when they move (look to each side of the 15 degree pitch line in the second picture)? They also adjust depending on the situation. So when at altitude and high speed, they may only be a few degrees above the horizon, so they aren’t always at the 15 degrees or whatever. Someone correct me if that’s wrong, but I seem to remember this from a jumpseat ride a while ago. In fact, if you look at http://www.airliners.net/open.file/123982/L/ this is a 717, and the lines are blue, but you can just see them just above the horizon. Is the stuff you are doing in any way related to OpenGC? For example could their gauges be used straight on to the panel? Just wondering Tim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Extensions
Darrell Walisser wrote:
Here's a patch to simgear that implements gl function pointer lookup:
Frederic Bouvier wrote:
the patch below is required for MSVC
Could you add these definitions to extensions.hxx :
#define GL_POINT_SIZE_MIN_EXT 0x8126
#define GL_DISTANCE_ATTENUATION_EXT 0x8129
Thanks for bearing with me guys.
This is a really needed change, and I know from personal experience
("porting" FlightGear to IRIX) things can get frustrating sometimes.
These are all in CVS now.
Thanks again!
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
- Original Message - From: "paul mccann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 18, 2003 10:07 PM Subject: [Flightgear-devel] glass cockpit > Jim looks great, just like the real thing. > > 1. they are ptich limit bars or symbol, you will get to stick shaker or > stall if you pitch up to them. > > 2. On the 737 the dg or compass has 7 modes > 1. nav (full)/ looks like hsi but really showing track not heading > and relation to stored route not vor or ils info > 2. vor ils (full)/ looks like regular hsi and acts like one, plus > shows magnetic heading > 3. nav (expanded)/ same as above but you only see half the compass > 4. vor ils (expanded) " " > 5. map /this mode shows cours line and little triagle which is the > aircraft, also shows track not magnetic heading. > 6. center map same as above but full compass rose. > 7. plan /static map > Take a peek at www.first-day.org/jpgs for some examples. These are designed for a full size flight deck sim so some of the detail may not be possible. Also don't forget the five overlays for weather, airports, vortacs, waypoints, and route ETAs on the ND > 3. Compass does not behave like wiskey compass. Its getting signals > from ring laser gyro and irs. So it does not drift turn wrong way or > display any of those things. > Same is true for A/S, altitude, vvi, etc. Everything goes thru an air data computer that handles all those messy errors/lags you have to worry about in lighter equipment. Regards JW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
