Re: [Flightgear-devel] c172r-yasim solution error
Hi, On Donnerstag 19 Mai 2005 04:45, Jon Berndt wrote: We do have vUVWdot, which is body frame. We also have Tb2l, which is a transformation matrix that goes from body to local. This is where it gets hazy for me, too, and I have to sit and think about it, but since the body frame is rotating wrt to the local frame, I think there is an acceleration due to the rotation, as well, so one cannot simply transform from body axes to local frame. We can do this, it will just take some thinking. And, yes, Mathias is the expert, here. This is where it gets a little hazy for me, too, but IIRC, vVeldot = vUVWdot*Tb2l + vPQR*vUVW If that's not right, it's something like that, and I know we can calculate it. But, I'll really be surprised if it's not being calculated somewhere already. Ok, At first I need to know how this local frame is meant. What I have found from the code is that it is meant to be the *geodetic* horizontal local frame. But is is meant to be fixed at the aircraft and thus rotates due to the aircrafts velocity or is it fixed at the earth and relocated for every frame to display? Or the other question is: what is that hud element meant to display? I cannot yet make sense of that. Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: Re : Re: [Flightgear-devel] visual freeze
On Donnerstag 19 Mai 2005 08:59, BONNEVILLE David wrote: Thanks Mathias. I guess there is no solution for the moment ? Any idea ? Nothing in my mind for that. Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] SimGear Build Problem under MacOS X
Jonathan Polley wrote: It seems as if MacOS X does not have isnan(), or at least by default. There is a fix for this in cloud.cxx also. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear0.9.8 Segmentationfault coredumpedPlease Help!
-Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel- [EMAIL PROTECTED] On Behalf Of YENEW T KASSAYE Sent: 19 May 2005 23:04 To: FlightGear developers discussions Subject: RE: [Flightgear-devel] FlightGear0.9.8 Segmentationfault coredumpedPlease Help! Thanks Vivan, I made the corrections. No change. I do want to mention that when I am compiling simgear,it gives me errors about openAL not being loaded. I defeated this problem by placing AL and GL in /cygwin/include instead of /usr/local/include. Would this create a problem? I think you ought to get it all to compile in the advised locations. A possible cause of problems is multiple versions of AL and GL. Make sure that you only have one version of each. What are your errors in compiling SimGear with OpenAl in the 'correct' location? A possible way forward is to start over - uninstall Cygwin, and start from there. Download and install compatible versions of plib, OpenAl (our variant) etc, and rebuild. Tedious, but probably quicker than chasing down files in obscure directories. I also uninstalled the X11 package from cygwin. Hmm ... this was a problem in the past, but I think it shouldn't be needed now This allowed simgear to compile. But I still have the seg. dump after I compile and run fgfs from cygwin. Still stuck! It brings up the intro screen and never puts you in the cockpit. I do have the already compiled executable downloaded from flightgear.org and it works fine on this machine. I ran fgrun from cygwin and it works. But I need to be able to compile because I am modifying the hud to feed in SEP data. Keep trying, it definitely does work. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Colditz Glider
On Fri, 2005-05-20 at 02:37, Josh Babcock wrote: I'll see what more I can deduce tonight. Steve Didn't get anything much done, sadly, but I have taken a look at your fuselage images, Josh. Nice work! Just an update. http://jrbabcock.home.comcast.net/flightgear/colditz/colditz1.jpg http://jrbabcock.home.comcast.net/flightgear/colditz/colditz2.jpg One small observation. It's hard to be sure, but I think the photos of the glider replica show that the riser forming the back of the pilot's seat is also the centre bolting-on point for the wings, and therefore comes to a narrow flat-top under the wing, not to a sharp point as you've modelled it. Looks like P.Reid's drawing (body_glider_plans.htm) shows it like that too. It would also seem that the wing overhangs forward of the top-of- the-seat bolt-on point too. This is where I assume the passenger was squashed in. He gets a bit of side-to-side view in there, but not much. He wouldn't see much at night anyway. Other opinions may differ of course. Annoyingly, the photos from the 1999 flight on the 'fiddler's green' site don't really have enough detail in that area to be sure of anything. Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Colditz Glider
Steve Hosgood wrote: On Fri, 2005-05-20 at 02:37, Josh Babcock wrote: I'll see what more I can deduce tonight. Steve Didn't get anything much done, sadly, but I have taken a look at your fuselage images, Josh. Nice work! Just an update. http://jrbabcock.home.comcast.net/flightgear/colditz/colditz1.jpg http://jrbabcock.home.comcast.net/flightgear/colditz/colditz2.jpg One small observation. It's hard to be sure, but I think the photos of the glider replica show that the riser forming the back of the pilot's seat is also the centre bolting-on point for the wings, and therefore comes to a narrow flat-top under the wing, not to a sharp point as you've modelled it. Looks like P.Reid's drawing (body_glider_plans.htm) shows it like that too. It would also seem that the wing overhangs forward of the top-of- the-seat bolt-on point too. This is where I assume the passenger was squashed in. He gets a bit of side-to-side view in there, but not much. He wouldn't see much at night anyway. Other opinions may differ of course. Annoyingly, the photos from the 1999 flight on the 'fiddler's green' site don't really have enough detail in that area to be sure of anything. Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d You are correct. The pointy bit is there as a reference point for me to place the wing, and will be hidden once the wing goes on. It also saves a few polys :) Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Microlight
Hi. How about inserting a Microlight like the solowings Aquilla into your list of aircraft? Keep up the good work. Kind Regards Morné Fourie AFRIDATA.net Cell: +27 83 293 5893Office: +27 83 293 5893 Fax: +27 +83 281 5872Email: [EMAIL PROTECTED]___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Build Problem Under MacOS 10.4
Did you use GCC 4 or 3.3? I've been so busy that I've not even tried building FGFS on 10.4. I did try to build plib but it failed with the same type of error. And I fixed it just like you (except by making it non-static) but then a mess of other errors showed up that well... I knew nothing about.On 5/20/05, Jonathan Polley [EMAIL PROTECTED] wrote: For some reason, the c172_aero.c file in src/FDM/LaRCsim generates alink error.There is a variable, called simply 'b' that conflictswith a symbol in MacOS 10.4's OpenGL library (go figure).Withoutmaking it static (or changing its name), I get the following link error: ld: ../../src/FDM/LaRCsim/libLaRCsim.a(c172_aero.o) illegal referenceto symbol: _b defined in indirectly referenced dynamic library /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib For now, I have made the 'b' variable static and then FlightGearlinks just fine.It does not complete its initialization, but Iprobably have a messed up config file (it has been a while since Ihave build FlightGear). Jonathan Polley___Flightgear-devel mailing listFlightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://artooro.blogspot.com (Weblog)- http://sourceforge.net/users/artooro/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] c172r-yasim solution error
Mathias Fröhlich wrote: At first I need to know how this local frame is meant. What I have found from the code is that it is meant to be the *geodetic* horizontal local frame. But is is meant to be fixed at the aircraft and thus rotates due to the aircrafts velocity or is it fixed at the earth and relocated for every frame to display? For what it's worth, YASim supports this NED (north/east/down) coordinate frame for output, but doesn't use it internally. It's pretty strange IMHO, and of course has a singularity problem at the poles. If JSBSim is having trouble with it, it might be best to just junk the concept and fix the HUD code to use body coordinates. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Build Problem Under MacOS 10.4
On 20 May 2005, at 15:30, Andy Ross wrote:it is no longer legal to do this: int i; glGenTextures(1, i); Instead, you have to declare 'i' as GLint (and similarly for GLuint and so on) Are you sure? I thought the Apple compiler was still a 32 bit environment on OS/X. And in any case, PPC64 is an "LP64" ABI, which means that a plain "int" is still 32 bits, just like GLint. Really, there are no meaningful (for our purposes) systems any more where an "int" is anything but 32 bits. The size of longs and pointers is variable, but ints are pretty fixed. Umm - I am not sure about the reason for making the change, but the fact is that on Tiger, GLuint is a typedef for 'unsigned long'. Hence, the code has to be changed to use the portable names, or GCC 4.0 chokes.Next time I run into an Apple engineer, I'll ask about this.HHJames ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] c172r-yasim solution error
In a message dated 5/20/2005 2:09:17 AM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
But is is meant to be fixed at the aircraft and thus rotates due to the
aircrafts velocity or is it fixed at the earth and relocated for every frame
to display?
Or the other question is: what is that hud element meant to display?
I cannot yet make sense of that.
Hi M,
The HUD element provides a visual indicator of energy within a constant
speed climb or descent thru the use of hud_ladr.cxx:
if(energy_marker) {
if (total_vel 5.0) {
t1 = 0;
t2 = 0;
} else {
t1 = up_vel/total_vel;
t2 = asin((Vxx*Axx + Vyy*Ayy + Vzz*Azz)/(9.81*total_vel));
}
pot_slope = ((t2/3)*SGD_RADIANS_TO_DEGREES)*factor + vel_y;
The values of Vxx, Vyy, ... are called in for the JSBSim and YASim both, but
Axx, Ayy, ... are called for YAsim only, rendering the HUD element to
indicate velocity only.
As for reference plane, I'm hazy as to the effect of the frame on the
reference but would lean towards the geodedic or earth-referenced
acceleration. I
have been through the flight.cxx and .hxx files along with the
src/FDM/JSBSim.cxx and YASim.cxx and have come away with the v_dot_local,
Get_ and
Set_Accels_Local as the given terminology in the NED sections, although
these
may be in name only and not function.
To refresh the initial query; I would like to use the energy marker within
a training tool using a simple single trainer but I need 2 VOR's for
intersection identification. The PA-28 -YASim provides the energy marker and
the
c172 - JSBSim provides the avionics... hmmm...
Thanks,
Mike
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] problem with signs program, convert: command not found
Melchior, The new signs program, it's great! However, I'm noticing a problem on a mac os x system that I reinstalled recently. I downloaded new scripts this morning, when I install them in data and run signs (either from data/local/signs or from a copy of signs copied to bin, I get a series of error messages like this: creating: cache/A/KJFK_John_F_Kennedy_Intl.rgb sh: line 1: convert: command not found I had this working before the reinstall of my system. My question is: is the convert command new? (if so, do you know where I can get source (or binary version for mac os x (10.4)))? I don't know why it worked previously, maybe I had a convert command installed on the old install of the os but I can't seem to find it now. Thanks for your help! BTW, the signs are VERY cool, and it's especially nice that they're so extensible easily. I did notice that when I scroll thru fgfs to get to the top down view that I only see red lines appearing (i.e., the tops of the signs) instead of the signs as the signs are still vertical. Can the script be changed to display signs horizontal when this top-down view is used (Hit 'v' six times to get to this view)? Thanks for giving us all a very cool feature! ... and thanks for all your work on FlightGear! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Colditz Glider
I've just come across a few more details in: http://www.chicagolandglidercouncil.com/newsletter_files/CLGCNewsletterFeb02.pdf There's a comment by the pilot who flew the replica, to the effect that the glide ratio was about 18:1 That's pretty impressive! There's also a photo of the glider just off the ground on the lauch tow, and a comment that the wings were built by a Mr John Lee, who was also the pilot for the TV programme. Another comment (backing up Jon Stockill's statement) is that the glider was in the Imperial War Museum, London for a while, and was moved to their aircraft collection at Duxford (Cambridgeshire, England) later. Annoyingly, that's about 6 hours driving from here, or I'd go over there with a camera. ** Research is revealing that 99% of the info on the Colditz glider on the web is a copy of some part of someone else's page! The link mentioned above is a pleasant change from that! Here's another pleasant discovery: http://www.aae.uiuc.edu/m-selig/ads/aircraft.html This claims that the wing on the Colditz Glider is a Clark YH which is great because that's a standard wing and its lift / drag / stall characteristics are documented. Can't find much on the web, but there's some aircraft design books down in the university library that I will be interested to check out Steve ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: problem with signs program, convert: command not found
* Ima Sudonim -- Friday 20 May 2005 17:49: The new signs program, it's great! If it weren't that unhumble, I would agree. I enjoy it a lot. :-) I've meanwhile made a (simple) webpage for it, so that I don't have to announce here on the list every time I make some changes: http://members.aon.at/mfranz/flightgear/signs.html If you are going to use the new versions, it's a good idea to uninstall the old once. Not only did I change the path (signs/ instead of sign/) and the package names, but also the format: formerly I used ft (eeww), because that was what the airport data was in. Now I'm using meters. (Easy to convert in case someone has already started to make his own topographic database.) Also, I'm about to finish Germany. (Ready tomorrow.) I fixed some bugs in the Austrian database (Salzburg placed correctly), added a few villages (Fucking[1] in Upper Austria -- how could they miss it?!?, Strasswalchen, etc.), and other objects (Castle Hochosterwitz, some (non-classified) military facilities). However, I'm noticing a problem on a mac os x system that I reinstalled recently. I downloaded new scripts this morning, Oh. OK, then forget the above. This is the most recent version already. (Slightly increased performance. Yay!) when I install them in data and run signs (either from data/local/signs or from a copy of signs copied to bin, That's OK. The program doesnt' care from where it was started. I get a series of error messages like this: creating: cache/A/KJFK_John_F_Kennedy_Intl.rgb sh: line 1: convert: command not found I had this working before the reinstall of my system. My question is: is the convert command new? (if so, do you know where I can get source (or binary version for mac os x (10.4)))? No. That's part of the ImageMagick package, which can meanwhile be seen as a standard. Just install that (again), and make sure it's in the $PATH. BTW, the signs are VERY cool, and it's especially nice that they're so extensible easily. I did notice that when I scroll thru fgfs to get to the top down view that I only see red lines appearing (i.e., the tops of the signs) instead of the signs as the signs are still vertical. Red lines? On the red signs only, right? Otherwise that's a graphics card driver bug ... Can the script be changed to display signs horizontal when this top-down view is used (Hit 'v' six times to get to this view)? ... but yes, the signs do only billboard around the vertical axis. I tried it otherwise (change spherical to true in all sign[0-9]*.xml files if you want to try yourself), but this looked ugly. Yes, the signs were then visible from above. But they followed view banking, which looked ridiculous. That's a feature in the animation code or plib, and the script can't do anything about it (AFAIK). I'd rather raise the signs some more. Thanks for giving us all a very cool feature! ... and thanks for all your work on FlightGear! You are welcome. :-) m. [1] sorry for the adult content, but I didn't christian that village ;-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Build Problem Under MacOS 10.4
James Turner wrote: Umm - I am not sure about the reason for making the change, but the fact is that on Tiger, GLuint is a typedef for 'unsigned long'. Hence, the code has to be changed to use the portable names, or GCC 4.0 chokes. Hrm... that sounds like a bug in the Apple headers. The OpenGL spec requires that GLint/GLuint be exactly a 32 bit value. If Apple is defining it otherwise in an environment* where a long is 64 bits, then they need to fix their files. * Are you sure this is the case for the OS/X development environment? I was sure that it was still 32 bit, which would make a long 32 bits as well. Can you post the error you get? It should not be an error to cast a pointer to an unsigned int to a pointer to a GLuint on any 32 or 64 bit environment I am aware of. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear0.9.8 Segmentationfault coredumpedPlease Help!
Vivan, I followed your advice and started over and FightGear WORKS!!!. I had to place AL and GL in the /cygwin/include instead of /usr/local/include. If I dont do that when I run ./configure for SimGear, it errors out at the end and says openAL has to be installed. The last few lines before this error message look for openAl files and three no's appear. Thanks for your help. I am still getting the Segmentation fault core dumped when I exit FlightGear but it runs regardless. That might have not been my problem running fgfs the whole time. I am going to move on to modifiying the HUD. Wish me luck.. _Yenew -Original Message- From: [EMAIL PROTECTED] [mailto:flightgear-devel- [EMAIL PROTECTED] On Behalf Of YENEW T KASSAYE Sent: 19 May 2005 23:04 To: FlightGear developers discussions Subject: RE: [Flightgear-devel] FlightGear0.9.8 Segmentationfault coredumpedPlease Help! Thanks Vivan, I made the corrections. No change. I do want to mention that when I am compiling simgear,it gives me errors about openAL not being loaded. I defeated this problem by placing AL and GL in /cygwin/include instead of /usr/local/include. Would this create a problem? I think you ought to get it all to compile in the advised locations. A possible cause of problems is multiple versions of AL and GL. Make sure that you only have one version of each. What are your errors in compiling SimGear with OpenAl in the 'correct' location? A possible way forward is to start over - uninstall Cygwin, and start from there. Download and install compatible versions of plib, OpenAl (our variant) etc, and rebuild. Tedious, but probably quicker than chasing down files in obscure directories. I also uninstalled the X11 package from cygwin. Hmm ... this was a problem in the past, but I think it shouldn't be needed now This allowed simgear to compile. But I still have the seg. dump after I compile and run fgfs from cygwin. Still stuck! It brings up the intro screen and never puts you in the cockpit. I do have the already compiled executable downloaded from flightgear.org and it works fine on this machine. I ran fgrun from cygwin and it works. But I need to be able to compile because I am modifying the hud to feed in SEP data. Keep trying, it definitely does work. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] FlightGear0.9.8 Segmentationfault coredumpedPleaseHelp!
YENEW T KASSAYE wrote I followed your advice and started over and FightGear WORKS!!!. I had to place AL and GL in the /cygwin/include instead of /usr/local/include. If I dont do that when I run ./configure for SimGear, it errors out at the end and says openAL has to be installed. The last few lines before this error message look for openAl files and three no's appear. Hmm - I don't understand this - where is simgear and flightgear? Thanks for your help. I am still getting the Segmentation fault core dumped when I exit FlightGear but it runs regardless. That might have not been my problem running fgfs the whole time. This shouldn't happen - there's something wrong still I am going to move on to modifiying the HUD. Wish me luck.. Go for it! Regards Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] My first solo cross-country; Was: My first solo ....
Martin Spott wrote: Well, it really took a very long time for getting there ! The second half of 2004 I didn't make a single flight due to timely and/or monetary restrictions. Afterwards I had to bear almost four months of delay because we never managed to match free time and good weather for the first solo. Similar with my first solo cross-country. I chose a rather small airfield (EDKA, less than 600 m) as the destination of my first solo cross-country and my intructor decided it would be not a good idea to have bad weather for this trip. Finally I made it without the slightest difficulties and I'm very proud of this :-) The flight from EDLN to EDKA is about half an hour for each direction and the feeling on this journey was overwhelming. The most significant effect is the absence of this guy who talks too much ;-) We made several cross-country flights together and I'm really fond of my instructor, he's quite as crazy a guy as I am told to be myself. But it is always difficult to make your own opinion upon a certain situation and additionally have to figure out how the advice of your instructor matches with your own picture. Often the result of following your own decision is far better than the result of doing the splits to merge your own and your instructors ideas. There's always a certain range of valid reactions on an incident which don't necessarily match each other. Last weekend we had a trip to Denmark and I did about six and a half hours flying that weekend. Alone the trip back home was 188 minutes non-stop from EKOD to EDLN (BTW, if you ever have the chance to visit EKEL, do it - if you manage to find it ! ;-) But the simple solo trip of just half an hour per direction still was much more inspiring. Cheerio, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] c172r-yasim solution error
In a message dated 5/20/2005 12:49:29 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: Or if you really want to cheat: use the Cessna 3D model with the Piper FDM configuration. :) I think that's how this whole thing started... YASim FDM with c172 model results in a YASim solution error - insufficient elevator trim. I could start altering the geometry or moving the CG, but I was hoping NOT to upset all the previous efforts put into the model. Mike ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] c172r-yasim solution error
Mike wrote: Andy Ross wrote: Or if you really want to cheat: use the Cessna 3D model with the Piper FDM configuration. :) I think that's how this whole thing started... YASim FDM with c172 model results in a YASim solution error - insufficient elevator trim. Not the C172 model (which, for many reasons, is not going to be maintained as a YASim plane). I mean use the Cherokee model. You can use the 172 panel and graphics with another airplane's FDM configuration. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] openGC problem need help!
i am trying to run fg with openGC displays but until now i am not succeded . i am using fg under xp sp2 . i can not start fgfs in opengc communication mode i also can not launch opengc alone when i run it gives error after loading fonts in dos mode and crashes please help me Yahoo! Mail Mobile Take Yahoo! Mail with you! Check email on your mobile phone.___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] c172r-yasim solution error
Mike wrote: Could you send me some specifics on the above procedure? I'm playing around within the pa28-set.xml without much success. In your Aircraft/c172p directory, edit the c172p-set.xml file and replace these lines: flight-model archive=yjsb/flight-model aero archive=yc172p/aero with: flight-model archive=yyasim/flight-model aero archive=ypa28-161/aero I didn't test this, but it should work for a quick hack. The result will be an aircraft that looks like a Skyhawk but flies like a Warrior. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
