Re: [Flightgear-devel] Config defaults for Simgear
Jim Wilson wrote: This was an old issue. Just the same, I followed up and found that there was no problem building without jpeg-factory using the latest cvs (the 0.9.8 release should be the same). You might try clearing simgear and it's header files out of the installation directories, then reinstall simgear (sans the jpeg-factory) and then reconfiguring and rebuilding flightgear. The flightgear configure script checks for the presence of the header and library file for jpeg-factory and reinstalling SimGear without jpeg-factory will simply leave the old versions there. I don't recall, but there may be a make uninstall option in SimGear. The problem is that when you have installed the jpeg-factory code once there will be a file called simgear/screen/tr.h in the include directory (most ofter /usr/local/include). The configure script tests for this file whether or not to include the jpeg-factory support in FlightGear. Removing the tr.h file and running configure again should do the trick. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] link to my homepage
I hereby formally object to my name and my code contributions being dragged into potential religious conflicts, and to using them for proselytizing purposes. It's sad to see that the repeated calls for keeping political and other controversial stuff off FlightGear don't seem to apply any more. Please remove the link to my former flightgear page from http://www.flightgear.org/links.html (FlightGear: Support for joysticks with digital axes; which is quite outdated anyway) I'll happily join again, once flightgear treats all its users and developers again without distinction of any kind, such as race, colour, sex, language, *RELIGION*, political or other opinion, national or social origin, property, birth or other status. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Config defaults for Simgear
Erik Hofman said: Jim Wilson wrote: This was an old issue. Just the same, I followed up and found that there was no problem building without jpeg-factory using the latest cvs (the 0.9.8 release should be the same). You might try clearing simgear and it's header files out of the installation directories, then reinstall simgear (sans the jpeg-factory) and then reconfiguring and rebuilding flightgear. The flightgear configure script checks for the presence of the header and library file for jpeg-factory and reinstalling SimGear without jpeg-factory will simply leave the old versions there. I don't recall, but there may be a make uninstall option in SimGear. The problem is that when you have installed the jpeg-factory code once there will be a file called simgear/screen/tr.h in the include directory (most ofter /usr/local/include). The configure script tests for this file whether or not to include the jpeg-factory support in FlightGear. Removing the tr.h file and running configure again should do the trick. Thanks for looking that up. Note that it is a good idea to remove an old package completely before installing a new version, unless you are using a package manager that supports update functions. A good practice (TM). Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] EE CanberraBI8 (FAO Lee E)
On Thursday 20 January 2005 21:28, Dave Martin wrote: WOW! I don't know where you find the time or where you keep that bottomless bucket of talent but this is another gorgeous model! It seems that you will soon have covered the majority of Britains best jet-age aero-engineering heritage. Dave Martin Thanks, I'm glad you like it but there's plenty of room for improvement. You should have a look at some of the a/c that are being made for MSFS. There's a trade off between available time, skills, reference material and tiredness, but then I guess that applies to most things:) LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
On Saturday, 22 January 2005 13:01, Melchior FRANZ wrote: I hereby formally object to my name and my code contributions being dragged into potential religious conflicts, and to using them for proselytizing purposes. It's sad to see that the repeated calls for keeping political and other controversial stuff off FlightGear don't seem to apply any more. Please remove the link to my former flightgear page from http://www.flightgear.org/links.html (FlightGear: Support for joysticks with digital axes; which is quite outdated anyway) I'll happily join again, once flightgear treats all its users and developers again without distinction of any kind, such as race, colour, sex, language, *RELIGION*, political or other opinion, national or social origin, property, birth or other status. m. Is this the way things should go? Melchior is not the only person who find the current situation unacceptable. Maybe I should make a package with a file included that says : Kill all 'em Niggers and get it put up on the FlightGear site. I say pull the package in question. If the author wants to distribute it on his own site then that is fine with me but as it stands it looks like we endorse what is in that package. I'd rather upset one contributor than piss off the whole FG community. Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems building from CVS
I've just updated my source code from CVS, but the build fails with the following: Making all in Environment make[2]: Entering directory `/home/andrew/cbproject/FlightGear-0.9/source/src/Environment' if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -I/usr/local//include -g -O2 -D_REENTRANT -MT environment_mgr.o -MD -MP -MF .deps/environment_mgr.Tpo -c -o environment_mgr.o environment_mgr.cxx; \ then mv -f .deps/environment_mgr.Tpo .deps/environment_mgr.Po; else rm -f .deps/environment_mgr.Tpo; exit 1; fi In file included from environment_ctrl.hxx:50, from environment_mgr.cxx:31: fgmetar.hxx: In member function `double FGMetar::getRain() const': fgmetar.hxx:45: error: `_rain' undeclared (first use this function) fgmetar.hxx:45: error: (Each undeclared identifier is reported only once for each function it appears in.) fgmetar.hxx: In member function `double FGMetar::getHail() const': fgmetar.hxx:46: error: `_hail' undeclared (first use this function) fgmetar.hxx: In member function `double FGMetar::getSnow() const': fgmetar.hxx:47: error: `_snow' undeclared (first use this function) make[2]: *** [environment_mgr.o] Error 1 make[2]: Leaving directory `/home/andrew/cbproject/FlightGear-0.9/source/src/Environment' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/andrew/cbproject/FlightGear-0.9/source/src' make: *** [all-recursive] Error 1 It looks as though the methods getRain(), getHail() and getSnow() rely on private attributes that haven't been declared. I have tried adding them as int's, but now get the following error: Making all in Environment make[2]: Entering directory `/home/andrew/cbproject/FlightGear-0.9/source/src/Environment' if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -I/usr/local//include -g -O2 -D_REENTRANT -MT environment_ctrl.o -MD -MP -MF .deps/environment_ctrl.Tpo -c -o environment_ctrl.o environment_ctrl.cxx; \ then mv -f .deps/environment_ctrl.Tpo .deps/environment_ctrl.Po; else rm -f .deps/environment_ctrl.Tpo; exit 1; fi environment_ctrl.cxx: In constructor ` FGMetarEnvironmentCtrl::FGMetarEnvironmentCtrl()': environment_ctrl.cxx:332: error: no matching function for call to ` FGMetarEnvironmentCtrl::MetarThread::start(int)' /usr/local/include/simgear/threads/SGThread.hxx:134: error: candidates are: int SGThread::start() make[2]: *** [environment_ctrl.o] Error 1 make[2]: Leaving directory `/home/andrew/cbproject/FlightGear-0.9/source/src/Environment' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/andrew/cbproject/FlightGear-0.9/source/src' make: *** [all-recursive] Error 1 Sadly my C++ is very sketchy, so I'm struggling to get past this. However, I'll keep digging, although it would help if anyone could provide any pointers as to the likely cause. Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
Paul Surgeon wrote: On Saturday, 22 January 2005 13:01, Melchior FRANZ wrote: I hereby formally object to my name and my code contributions being dragged into potential religious conflicts, and to using them for proselytizing purposes. It's sad to see that the repeated calls for keeping political and other controversial stuff off FlightGear don't seem to apply any more. Please remove the link to my former flightgear page from http://www.flightgear.org/links.html (FlightGear: Support for joysticks with digital axes; which is quite outdated anyway) I'll happily join again, once flightgear treats all its users and developers again without distinction of any kind, such as race, colour, sex, language, *RELIGION*, political or other opinion, national or social origin, property, birth or other status. m. Is this the way things should go? Melchior is not the only person who find the current situation unacceptable. Maybe I should make a package with a file included that says : ** and get it put up on the FlightGear site. I say pull the package in question. If the author wants to distribute it on his own site then that is fine with me but as it stands it looks like we endorse what is in that package. I'd rather upset one contributor than piss off the whole FG community. Let's not lose sight of a couple facts: 1. This is all regarding the Mac OS X package. 2. The author has already agreed to make some changes to his package. 3. This package is distributed on a source forge project page registered and maintained by this same developer. 4. The objectionable file is inside the mac package. 5. No one else has volunteered to make a mac friendly package. So from this I conclude: 1. This situation should already be resolved. 2. We have nothing we can pull off flightgear.org even if we wanted to. 3. I don't own a mac, and the mac package is in a mac specific format, so I can't actually check what's going on myself. 4. If complaints are being registered by non-mac users, they can't actually see what's in the file either so their objections are likely to be a bit suspect. I could also wish a few things. 1. That we treat everyone with respect. 2. That we discuss this issue with the same civility that we manage for just about every other subject. 3. That perhaps we consider a personal email as a first attempt to resolve the issue before needlessly raising a fire storm on the mailing list. 4. Think about it, if any one of us did something inappropriate (we didn't intend the consequences, we didn't think through the ramifications of our actions enough, it seemed like a good idea at the time, etc.) wouldn't we prefer that our error be pointed out in private so we have a chance to think and rectify the problem ourselves ... rather than finding out there's a problem by a huge long tirade on the public mailing list, with all kinds of people piling on to express their outrage? In this case it turned into a feeding frenzy. Before we were done we had banned the developer from all our mailing lists. We had posted a big notice on our home page disavowing any connection to him. We had lobbied source forge to get him and all his other projects kicked off there. And we had beat him up any other number of ways on our email list. That's just great! When have we treated any other developer and contributer this way??? If he made a mistake fine, we can fix it peacefully and civilly. I think we can and *should* do a lot better. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
On Sat, 22 Jan 2005 16:43:13 +0200, Paul wrote in message [EMAIL PROTECTED]: On Saturday, 22 January 2005 13:01, Melchior FRANZ wrote: I hereby formally object to my name and my code contributions being dragged into potential religious conflicts, and to using them for proselytizing purposes. It's sad to see that the repeated calls for keeping political and other controversial stuff off FlightGear don't seem to apply any more. Please remove the link to my former flightgear page from http://www.flightgear.org/links.html (FlightGear: Support for joysticks with digital axes; which is quite outdated anyway) I'll happily join again, once flightgear treats all its users and developers again without distinction of any kind, such as race, colour, sex, language, *RELIGION*, political or other opinion, national or social origin, property, birth or other status. m. Is this the way things should go? Melchior is not the only person who find the current situation unacceptable. Maybe I should make a package with a file included that says : Kill all 'em Niggers and get it put up on the FlightGear site. I say pull the package in question. If the author wants to distribute it on his own site then that is fine with me but as it stands it looks like we endorse what is in that package. I'd rather upset one contributor than piss off the whole FG community. ..the only place where Jesusing etc is welcome IMO, is in your own .signature, _if_ it fits in 4 lines like mine. A link there is fine, if you can't cram in your opinions etc there, put those on a web server and link to it from your .signature, rather than try pass off all of the FlightGear people as Religious Righteous etc in a binary release. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
On Sat, 22 Jan 2005 16:43:13 +0200, Paul Surgeon [EMAIL PROTECTED] wrote: I say pull the package in question. If the author wants to distribute it on his own site then that is fine with me but as it stands it looks like we endorse what is in that package. I'd rather upset one contributor than piss off the whole FG community. Let's take this whole discussion offline, guys -- it has become a bit silly. All the best, David -- http://www.megginson.com/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Patch for : Input/Joysticks/Microsoft/sidewinder-force-feed-pro.xml
The rudder and throttle need swapping based on the OS just like the Sidewinder Precision Pro. Paul Index: Input/Joysticks/Microsoft/sidewinder-force-feed-pro.xml === RCS file: /var/cvs/FlightGear-0.9/data/Input/Joysticks/Microsoft/sidewinder-force-feed-pro.xml,v retrieving revision 1.3 diff -u -r1.3 sidewinder-force-feed-pro.xml --- Input/Joysticks/Microsoft/sidewinder-force-feed-pro.xml 12 Jan 2004 17:49:44 - 1.3 +++ Input/Joysticks/Microsoft/sidewinder-force-feed-pro.xml 22 Jan 2005 14:36:44 - @@ -46,8 +46,12 @@ /binding /axis - axis n=3 + axis descRudder/desc + number + unix2/unix + windows3/windows + /number binding commandproperty-scale/command property/controls/flight/rudder/property @@ -55,8 +59,12 @@ /binding /axis - axis n=2 + axis descThrottle/desc + number + unix3/unix + windows2/windows + /number binding commandproperty-scale/command property/controls/engines/engine[0]/throttle/property ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems building from CVS
Andrew Midosn a écrit : I've just updated my source code from CVS, but the build fails with the following: Update SimGear too. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems building from CVS
--- Frederic Bouvier [EMAIL PROTECTED] wrote: Update SimGear too. Yup - my poor tired brain eventually noticed that it was complaining about SimGear *not* FlightGear (doh!), so I've updated that also. I'm still getting errors relating to FGMetar, so it certainly looks as if something's broken there. I'll keep digging. Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems building from CVS
Andrew Midosn a écrit : --- Frederic Bouvier [EMAIL PROTECTED] wrote: Update SimGear too. Yup - my poor tired brain eventually noticed that it was complaining about SimGear *not* FlightGear (doh!), so I've updated that also. I'm still getting errors relating to FGMetar, so it certainly looks as if something's broken there. I'll keep digging. You configure'd --with-thread or --without-thread ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems building from CVS
Andrew Midosn a écrit : I've just updated my source code from CVS, but the build fails with the following: It looks as though the methods getRain(), getHail() and getSnow() rely on private attributes that haven't been declared. They are declared line 237-239 of simgear/environment/metar.hxx and are protected. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] FGMetar.cxx
I've fixed one problem with the FGMetar constructor, where the call to the parent class SGMetar was incorrect, but now have another problem. In the constructor the method getCAVOK() is called, although it isn't defined anywhere in either FlightGear or SimGear. Unfortunately I have no idea what this function is supposed to do. I'll try defining it as a bool in FGMetar that just returns True for the moment, but that isn't really a solution. I would really like to sort this out and feel I am contributing in a small way to the project, but I'm not sure enough of what this code is trying to do. Sorry. Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FGMetar.cxx
Andrew Midosn a écrit : I've fixed one problem with the FGMetar constructor, where the call to the parent class SGMetar was incorrect, but now have another problem. In the constructor the method getCAVOK() is called, although it isn't defined anywhere in either FlightGear or SimGear. Unfortunately I have no idea what this function is supposed to do. I'll try defining it as a bool in FGMetar that just returns True for the moment, but that isn't really a solution. getCAVOK is at line 208 of simgear/environment/metar.hxx I would really like to sort this out and feel I am contributing in a small way to the project, but I'm not sure enough of what this code is trying to do. Sorry. You really have screwed your SimGear tree, if you think it is up to date. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] YASim prop thrust
Here is my local config for the p51d yasim propeller. Most of these values are pretty much on target according to actual specifications. The problem is that it appears to not produce sufficient thrust. Is it possible that we have a flaw in the thrust calculation? Does anyone have any actual data for p51-D thrust? propeller x=-0.75 y=0 z=0 radius=1.75 mass=1690 moment=94.5 cruise-alt=21400 cruise-power=1470 cruise-speed=380 cruise-rpm=1200 gear-ratio=0.479 manual-pitch=true actionpt x=-1.25 y=0 z=0/ control-input axis=/controls/engines/engine[0]/propeller-pitch control=PROPPITCH src0=0 src1=1 dst0=0.40 dst1=0.82/ /propeller Thanks, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FGMetar.cxx
--- Frederic Bouvier [EMAIL PROTECTED] wrote: You really have screwed your SimGear tree, if you think it is up to date. And that of course was the absolute truth. Having scrapped my SimGear directory completely and started again I now have everything compiling properly. FGMetar is of course fine, and only my brain is defective. My apologies for bothering the list, and my thanks to Fred for not lobbing a virtual half-brick at the idiot who was wasting his time. :-( Regards Andrew ___ ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Terrain elevation question
Hi, I would like to experiment a little bit with adding current terrain elevation detection for AI models. Is there a function to do this, i.e. double fgGetElevation(double lat, double lon); I found that the current user location is read from /environment/ground-elevation-m but that's the elevation at the user location and not at the position of the AI plane. The reason I'm looking into this is that even at EHAM, which is quite flat there are already some very visible artifacts due to variations in ground elevation. So we'd need to address this sooner or later. Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FGMetar.cxx
On Saturday, 22 January 2005 18:09, Frederic Bouvier wrote: I would really like to sort this out and feel I am contributing in a small way to the project, but I'm not sure enough of what this code is trying to do. Sorry. You really have screwed your SimGear tree, if you think it is up to date. I think Frederic is right - your SimGear is messed up. I tried to compile FG a few minutes ago and initially got the same errors as you did. (rain, hail, snow undeclared). So I did a cvs update of SimGear compiled it, installed it and then FG compiled without any problems. I think you should start with fresh copy of SimGear. Paul ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AI piper load fix - v0.9.8a needed?
On Friday 21 January 2005 20:32, David Luff wrote: On 21/01/2005 at 20:04 Durk Talsma wrote: So time permitting I wouldn't mind having a stab at porting (some of) your code to interact with the AIModel system, it that is okay with you. As I mentioned yesterday, the taxiway code comes to mind. This approach might actually be mutually benificial, if this would free up some time for you to work on taxidraw. Eventually, we need data for the AI system, such as, taxiways and parkings/gates and taxidraw would be an ideal tool for that. Let me know what you think. Yes, in principle that's fine by me. I'd like to keep the ATC system itself in it's own directory, but I'm happy for a significant portion, or possibly all of, the AI code to move over, and for you to 'take ownership' of it. I'm not sure how far you want to go in moving it over - some of the Me neither actually. As I am moving forward, I'm trying to gather some ideas. I'm currently mainly working on splitting up the dynamic flightplan generation code, so that I can generate pushback, taxi, takeoff, climb, cruise, decend, landing, taxi, and park, sections one at the time. This code is now works, albeit at a very rough an primitive level. It's now part of FGAIFlightplan, but could logically also be part of ATC. I'm currently leaning toward having the basic route generation part of the code be part of the AIModels codebase, and traffic monitoring be part of ATC (including some code that sends instructions to the AI planes to divert from their planned routes. But, its a fine line to draw. AIAircraft are currently pretty senseless (literally: They just follow routes and don't interact very well with their environment). I'm thinking about adding a series of invisible paths sections of taxiways, and sequence each aircraft based on their position along these paths. then it would be relatively easy for each individual aircraft to determine it's distance to it's predecessor and adjust speed accordingly. stuff is very AI/ATC interaction specific, such as the logic to fly circuits, respond to ATC instructions, and alter the circuit pattern in response to the user position (in theory anyway - one of the little blighters on downwind the other day was instructed by ATC to follow me in whilst I was about 2 mile final on straight-in. At about 1 mile final he cut in front of me, and caused me to get told to go around after taking a shade too long to clear the runway!). I'll have a mull over it this w/e and have a think about where a good cut-off point might be, and what API the AIModel code will need to expose to allow the 'intelligent AI' to continue to do what it does if left in the AI/ATC branch. Certainly, taxiing and 3D model creation and management would be good candidates for moving over to AIModels initially, leaving the heuristic GA Yep. Model management is already implimentent, and taxiing would seem logical to me. generator and the circuit-flying/tower control interaction portions in the AI/ATC for now. The AIModel code would need to expose an API for the heuristic generator to call to generate appropriate traffic, and another API for the 'intelligent-flying' code to have sufficient control of the plane. Both would be possible relatively easily. There is already code to set target heading, speed, and altitude, IIRC. The only thing that would be required is some code to override FlightPlan control, but that shouldn't be too hard either. Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
On Saturday, January 22, 2005, at 09:27AM, Curtis L. Olson [EMAIL PROTECTED] wrote: Let's not lose sight of a couple facts: 1. This is all regarding the Mac OS X package. 2. The author has already agreed to make some changes to his package. 3. This package is distributed on a source forge project page registered and maintained by this same developer. 4. The objectionable file is inside the mac package. 5. No one else has volunteered to make a mac friendly package. I strongly disagree with #5 as I have been building the last two releases of the MacOS X version of FlightGear, but they haven't been picked up and moved to the FlightGear web page. Because I don't have infinite storage, Ican't keep them around forever. This is mainly becasue I was asked to include the base packages as a part of the release. If someone would be willing to take the update, I can have a version ready this afternoon. Of COURSE they can do that. They're engineers! ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
Jonathan Polley wrote: On Saturday, January 22, 2005, at 09:27AM, Curtis L. Olson [EMAIL PROTECTED] wrote: Let's not lose sight of a couple facts: 1. This is all regarding the Mac OS X package. 2. The author has already agreed to make some changes to his package. 3. This package is distributed on a source forge project page registered and maintained by this same developer. 4. The objectionable file is inside the mac package. 5. No one else has volunteered to make a mac friendly package. I strongly disagree with #5 as I have been building the last two releases of the MacOS X version of FlightGear, but they haven't been picked up and moved to the FlightGear web page. Because I don't have infinite storage, Ican't keep them around forever. This is mainly becasue I was asked to include the base packages as a part of the release. If someone would be willing to take the update, I can have a version ready this afternoon. Jonathan, What Arthur offers (as I understand) is a nice native Mac package rather than a binary executable, a base package tar ball and a pointer to google with a hint to type unix in the search box and start reading. If you or someone else can provide similar native/easy mac packaging, I'd be happy to link to it, or host it. Please if you emailed a notice of your build to the mailing list and I missed it, send me a personal note, and subsequent reminders if necessary. I have a day job, a family (wife and 2 daughters), I admin the flightgear project, I do some work on the side for a commercial flight sim company. But mostly I thow all that aside and spend the bulk of my time trying to arbitrate and resolve flame wars on our mailing list. So think naturally fall through the cracks. Please remind me if I miss something important. Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
Curtis L. Olson wrote: 4. If complaints are being registered by non-mac users, they can't actually see what's in the file either so their objections are likely to be a bit suspect. A bit of context - the first I heard about this was not on the mailing list, but when a user popped into the IRC channel to ask why he was downloading religious propaganda - that's not the view of anyone involved in the project, that's an end user, directly associating that package with us. I realise that religion is a subject that a lot of people take very seriously, but in this situation peoples beliefs really are best kept to themselves. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] link to my homepage
I hereby formally object ... It is a matter of great regret that such things could, and can, happen in the public domain community. I might try to persuade you to reconsider on the following grounds:- 1.Everyone has the right to free speech (within certain limits and the law). 2.Flightgear does not appear to espouse any religious or political viewpoint. 3.Flightgear does not appear to willingly favour any one particular cause or group of individuals. 4.Flightgear does not appear to demand any restriction to the uses of the project so long as credit is given where due. Thus from the above, it is not a position that flightgear can logically respond to. People may object to the uses that other people may put the project, but in reality, there is little or nothing the flightgear community can do along these lines other than ensure that it does not espouse such behaviour, or appear to condone such behaviour either by supporting it through links, or references. To do otherwise, might in itself amount to the very abuse that one seeks to avoid. Basically, it is not Flightgear that has transgressed on this point, and it might be considered to be regrettable that flightgear is seen to be paying a price for it. I.E. Such circumstances may well lead us to shoot ouselves in the proverbial foot. :-( The whole concept is a remarkable testament to the generosity of man, and is in the finest traditions of humanity. We come together for a common purpose, we ask not colour, race, creed or nationality. Were one to ask anything of a member to the group, it should be only sufficient that he or she, reply, I have contibuted to the flightgear comunity. -|steve|- S.Graham-Merrett ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] YASim prop thrust
Jim Wilson wrote: Here is my local config for the p51d yasim propeller. Most of these values are pretty much on target according to actual specifications. The problem is that it appears to not produce sufficient thrust. Is it possible that we have a flaw in the thrust calculation? Does anyone have any actual data for p51-D thrust? propeller x=-0.75 y=0 z=0 radius=1.75 mass=1690 moment=94.5 cruise-alt=21400 cruise-power=1470 cruise-speed=380 cruise-rpm=1200 gear-ratio=0.479 manual-pitch=true actionpt x=-1.25 y=0 z=0/ control-input axis=/controls/engines/engine[0]/propeller-pitch control=PROPPITCH src0=0 src1=1 dst0=0.40 dst1=0.82/ /propeller I think your numbers are spot on. This is the issue that we tackled just about 12 months ago in the context of the Spitfire. Andy produced some new code, but it doesn't converge properly for very similar numbers for the lower-powered Merlin that I was trying to model. That's where it's been stuck since then. Nice to get it fixed up some time soon. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
Perhaps it will be a good idea to put up a notice that says FlightGear is not responsible for the contents of external websites. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
That may a good idea. But just so you all know and so you'll hopefully calm down, the file has been removed from the distribution although there is still a note from the packager and future releases will not even have that. So please forget this whole thing, because if you don't I'll post the entire file on how to get to Heaven in this thread. :) Maybe I should anyways just in case you don't know. Well if you want to know you can just email me. On Sat, 22 Jan 2005 16:36:27 -0500, Ampere K. Hardraade [EMAIL PROTECTED] wrote: Perhaps it will be a good idea to put up a notice that says FlightGear is not responsible for the contents of external websites. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/ - http://artooro.blogspot.com (Weblog) - http://machcms.sourceforge.net (MachCMS Project) - http://acalproj.sourceforge.net (Calendar Project) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Taking a break
I'm going to be taking a short break from the FlightGear, SimGear, and TerraGear mailing lists to help me focus on finding new customers to build up my XML consulting business back up (and to do lots of real flying, of course). I'll still be using FlightGear for practice and I will keep up to date on the CVS and read the announce lists. I expect that I won't be gone long -- likely weeks, and maybe a few months at worse -- and if people have any problems with or questions about my code chunks, I'll be happy to discuss them by private mail. I'll try to devote some time to my 3-D models while I'm away, especially the Warrior and the J3 Cub. Thanks, and all the best, David -- http://www.megginson.com/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
Arthur Wiebe wrote: That may a good idea. But just so you all know and so you'll hopefully calm down, the file has been removed from the distribution although there is still a note from the packager and future releases will not even have that. Arthur, Thanks, and thanks for all your efforts to bring us a Mac OS X package. Let's give the source forge mirrors a few days to catch up. I'm going to now delete this thread from my inbox. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: link to my homepage
* Arthur Wiebe -- Saturday 22 January 2005 22:39: But just so you all know and so you'll hopefully calm down, the file has been removed from the distribution although there is still a note from the packager and future releases will not even have that. Thank you. It wasn't about you personally. Only about the attempt to hijack the work of others for spreading controversial, personal and to some even offending opinion, however reasonable and good it may seem. Peace m. :-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] link to my homepage
Curtis L. Olson wrote: I could also wish a few things. 1. That we treat everyone with respect. Yes please, with no exception!! The logical consequence would be that you (and maybe Arthur as well) give a _credible_ signal to us that you respect our faith as much as yours - instead of dividing the list menbers into the ones that share your belief and the 'inferior' ones that either share a different belief or are non-religious. Thanks - we'll expect your response in this forum, 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
[Flightgear-devel] Bugs in FlightGear when flying over the North Pole
Today i tried to fly over the geographical North Pole in FlightGear and found the following bugs. 1. There were some bugs with the scenery alignment, Just take a look at these pictures: Here we have a long ditch on the ocean floor. http://tinypic.com/view.html?pic=1fd2fq When we fly a little farther into the northern direction we have a big hole at around 88*58.502 N on the ocean floor: http://tinypic.com/view.html?pic=1fd2mt I also want to mention, that there is no ice visible at the North Pole. BTW: It would also be a good idea to have polar lights. 2. When reaching waypoint 90*00.000 N the sun plays crazy. I know, in winter it shouldn't be possible to see the sun at the North Pole at day time but because of the big hole in the ocean (see above) it was possible to see what happens with the sun. It flys around the center of my view point. This shouldn't happen, Maybe it is better to use a spherical model for the sun and stars instead of a sky dome or by making he sun the center of the 3d world (in other words using 3 coordinate systems instead of 2. One coordinate system for the sun as a center of the solar system, one planet coordinate system and one local coordinate system to avoid floating point precision problems) Is this technically possible? 3. When trying to fly straight over the North Pole (waypoint 90*00.000 N) the latitude co-ordinate freezes instead of counting backwards. And the longitude runs in a cycle trying to find the correct co-ordinate. So it was not possible to fly over the North Pole, the only thing that worked was to turn the ufo 180 degrees and fly back. Then i also have a question, what co-ordinates are used for the magnetic North Pole in FlightGear? Is this implemented? Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
