[Flightgear-devel] A simple(but important) GIT question (Jack Mermod)
Ok, so I've been working on the harrier a lot, and would like to commit what I have so far into GIT. How do I do this? Check Six, Jack -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] weather conditions and winds aloft not working correctly..
On 19 Jul 2010, at 01:47, Jacob Burbach wrote: On a side note...is there a way to retrieve a list of airports within a certain distance of a position from nasal? Trivial from C++, unfortunately tricky from Nasal right now. This needs an extension or alternative to airportinfo(), which allows the 'range' parameter to be tuned. How urgent is the need? James -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] weather conditions and winds aloft not working correctly..
On Mon, 2010-07-19 at 08:47 +0100, James Turner wrote: On 19 Jul 2010, at 01:47, Jacob Burbach wrote: On a side note...is there a way to retrieve a list of airports within a certain distance of a position from nasal? Trivial from C++, unfortunately tricky from Nasal right now. This needs an extension or alternative to airportinfo(), which allows the 'range' parameter to be tuned. How urgent is the need? James In the long term, I'd like to see being able to also get FIXES, VOR and NDB information from Nasal based on a range (and possibly; range and heading), that could be quite useful for the increasing number of glass cockpits I think. If anyone is thinking of writing such a Nasal extension, then please also give thought to this as well. S. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel ** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ** -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Exposing data objects to Nasal
On 19 Jul 2010, at 09:04, Scott Hamilton wrote: In the long term, I'd like to see being able to also get FIXES, VOR and NDB information from Nasal based on a range (and possibly; range and heading), that could be quite useful for the increasing number of glass cockpits I think. If anyone is thinking of writing such a Nasal extension, then please also give thought to this as well. Yep, I am aware there's a whole range of data that should be exposed, and a huge amount of cockpit / FMS / GPS functions that can be moved to Nasal if that were done. The geodetical functions in Nasal could also use some love, in that case, to make navigation work in Nasal easier - basically a smarter wrapper around SGGeod and the functions in SGGeodesy. As always, the problem is time -and also the lag of me coding up new functions (which is quite easy) to a release, so that they're generally available to end-users, is quite long - yet another reason for a faster release cycle :) James -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim P-51D merge request
On Sun, 11 Jul 2010, Hal V. Engel wrote: This is a large merge that is a significant enhancement to the existing P-51D but it is still a work in progress and much remains to be done. At the moment I am not able to spend much time working on this but it is far enough along that I think it belongs in the FG mainline so that it can be tested against 2.1 and hopefully released with 2.1. I intend to keep working on this as time permits and my intention is to eventually make this the most complete and most accurate model in the FlightGear hanger. Hi Hal, Lovely aircraft! One thing I discovered after a few botched landings is that the crash detection system doesn't set /sim/crashed. I think it ought to since that is the standard crash indicator in FlightGear. It is easy to add as the following diff shows: index 312f0ce..bd2e03f 100644 --- a/Aircraft/p51d/Systems/crash-detect.xml +++ b/Aircraft/p51d/Systems/crash-detect.xml @@ -56,6 +56,7 @@ output/sim/freeze/clock/output output/sim/freeze/main/output output/controls/engines/engine[0]/cutoff/output +output/sim/crashed/output /switch /channel It is also easy to update the merge request - I have tried it on some of mine. PS. For those who want to try the p51d before the merge request is accepted and aren't that familiar with git here are the steps to get Hal's branch: git fetch git://gitorious.org/~hvengel/fg/hvengels-fgdata-p51d-jsbsim.git master:hvengel/p51d-jsbsim git merge hvengel/p51d-jsbsim If you have push access to fgdata it might be advisable to create a separate branch for this so that you don't accidentally push these changes. (As far as I have checked they don't interfere with anything - but if we want to keep the gitorious merge request function functional it might be better if whoever merges this contribution use that procedure instead). Btw. local finger trouble with git can easily be adjusted using git rebase, see this very useful site for more information: http://www-cs-students.stanford.edu/~blynn/gitmagic/ch05.html Take care NOT to change published commits, though. DS. Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Christian Menge has invited you to Dropbox
We're excited to let you know that Christian Menge has invited you to Dropbox! Christian Menge has been using Dropbox to sync and share files online and across computers, and thought you might want it too. Visit http://www.dropbox.com/link/20.yLWfrz5Uk6/NjI1NDU1ODk0Nw to get started. - The Dropbox Team To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/702538ee6594/flightgear-devel%40lists.sourceforge.net-- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] weather conditions and winds aloft not working correctly..
On Mon, Jul 19, 2010 at 3:47 AM, James Turner ja...@bugless.co.uk wrote: On 19 Jul 2010, at 01:47, Jacob Burbach wrote: On a side note...is there a way to retrieve a list of airports within a certain distance of a position from nasal? Trivial from C++, unfortunately tricky from Nasal right now. This needs an extension or alternative to airportinfo(), which allows the 'range' parameter to be tuned. How urgent is the need? James It's not very urgent for me personally as what I'm doing can be done a different way, but it could be quite useful in a number of situations though. -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Exposing data objects to Nasal
On 19/07/10 11:06, James Turner wrote: On 19 Jul 2010, at 09:04, Scott Hamilton wrote: In the long term, I'd like to see being able to also get FIXES, VOR and NDB information from Nasal based on a range (and possibly; range and heading), that could be quite useful for the increasing number of glass cockpits I think. If anyone is thinking of writing such a Nasal extension, then please also give thought to this as well. Yep, I am aware there's a whole range of data that should be exposed, and a huge amount of cockpit / FMS / GPS functions that can be moved to Nasal if that were done. The geodetical functions in Nasal could also use some love, in that case, to make navigation work in Nasal easier - basically a smarter wrapper around SGGeod and the functions in SGGeodesy. As always, the problem is time -and also the lag of me coding up new functions (which is quite easy) to a release, so that they're generally available to end-users, is quite long - yet another reason for a faster release cycle :) James Does any of this look like it could be part of a GSoC project for next year? Anybody care to write a very brief synopsis of where this fits, what benefits we'd get from fixing it and a vague stab in the dark about expected timescales for a Comp Sci undergraduate or similar to accomplish? Also if we fix this, what other areas does this open up? Remember however if this becomes a GSoC project, not a line of code will be written before May 2011 ;-( Best Regards Willie -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am not sure if this is my issue or not, but I appear to be having
troubles since this push.
I pulled a fresh simgear and flightgear from gitorious this morning,
compiled and installed. I verified that this simgear was the only one
on the system.
Result:
dante:~/Desktop/Source_Code/Flightgear/flightgear$ fgfs
Cannot find specified aircraft: c172p
Config option parsing failed ...
Environment vars:
FG_HOME=/home/lance/Desktop/Source_Code/Flightgear
FG_ROOT=/home/lance/Desktop/Source_Code/Flightgear/fgdata
FG_SCENERY=/home/lance/.fgfs/Scenery:/home/lance/Desktop/Source_Code/Flightgear/Scenery/
The c172p directory (and all others) are in ${FG_ROOT}/Aircraft/
It doesn't matter what options I use to fgfs, it dies in exactly the
same way every time.
Cheers,
lance
On 17/07/10 07:46 AM, James Turner wrote:
I've pushed some changes to the aircraft search code, including the
--show-aircraft option. We're no longer using PLIB ulDir to traverse
directory structures (a couple more steps on the road to kill off PLIB),
and aircraft searching is a unified code path - previously the actual
--aircraft option and --show-aircraft used unrelated code paths.
You will need an up-to-date SimGear (which includes the new
simgear::Dir helper), and please let me know if you see any problems
with aircraft -set loading; they're going to be apparent very quickly,
since locating the -set.xml file happens really early in the startup
process.
James
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
- --
Lance Levsen,
Catprint Computing
Tel: (306) 493-2278
Cell: (306) 230-8783
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxEjfYACgkQWSOc2vLaechHnQCfVEIEdIepjFSAWWTq4BdAFVjF
t6gAoNp9OJYunUSKaIOTKDRPWXSo75cj
=W9OL
-END PGP SIGNATURE-
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim P-51D merge request
On Monday 19 July 2010 03:11:04 am Anders Gidenstam wrote: On Sun, 11 Jul 2010, Hal V. Engel wrote: This is a large merge that is a significant enhancement to the existing P-51D but it is still a work in progress and much remains to be done. At the moment I am not able to spend much time working on this but it is far enough along that I think it belongs in the FG mainline so that it can be tested against 2.1 and hopefully released with 2.1. I intend to keep working on this as time permits and my intention is to eventually make this the most complete and most accurate model in the FlightGear hanger. Hi Hal, Lovely aircraft! One thing I discovered after a few botched landings is that the crash detection system doesn't set /sim/crashed. I think it ought to since that is the standard crash indicator in FlightGear. It is easy to add as the following diff shows: index 312f0ce..bd2e03f 100644 --- a/Aircraft/p51d/Systems/crash-detect.xml +++ b/Aircraft/p51d/Systems/crash-detect.xml @@ -56,6 +56,7 @@ output/sim/freeze/clock/output output/sim/freeze/main/output output/controls/engines/engine[0]/cutoff/output +output/sim/crashed/output /switch /channel It is also easy to update the merge request - I have tried it on some of mine. Thanks Anders. I have made this update and it is now part of my gitorious fgdata clone and also part of the merge request. PS. For those who want to try the p51d before the merge request is accepted and aren't that familiar with git here are the steps to get Hal's branch: git fetch git://gitorious.org/~hvengel/fg/hvengels-fgdata-p51d-jsbsim.git master:hvengel/p51d-jsbsim git merge hvengel/p51d-jsbsim I would encourage others to test this since any feedback I get will be used for additional improvements. The model does some unusual things that push the limits of JSBSim particularly the propulsion systems and related controls. There are also some things that don't work correctly because of bugs or missing features in the version of JSBSim that is part of FG but that have been (presumably) fixed in JSBSim CVS. These include: Fuel tank switching is currently broken and the engine will only run on tank[0] (left internal wing tank). The engine gage cluster(s) give wrong oil pressure, oil temperature and coolant temperature numbers. JSBSim has some fixes related to this that do not totally fix this but are none the less improvements. The tail wheel is currently always locked to the rudder. On the real P-51 series the tail wheel would swivel if the stick is forward of neutral but lock with the stick back. JSBSim CVS has a fix that will allow for this to be correctly modeled and it should only take a fairly simple fcs_function to implement. Are there any plans to update JSBSim in FG GIT? If you have push access to fgdata it might be advisable to create a separate branch for this so that you don't accidentally push these changes. (As far as I have checked they don't interfere with anything - but if we want to keep the gitorious merge request function functional it might be better if whoever merges this contribution use that procedure instead). Having this pushed into a branch of the main FG repository for later merging into the FG mainline would be fine by me. This will allow wider testing and also allow others to work on this branch. On the forums I had an exchange with another P-51D developer who has his own copy that he is working on. For the most part we are working on different things (he is adding livery support and a bombable enabled AI model - I am working on improving the FDM, the cockpit, controls and the overall weapons systems) although there is some overlap (both have machine guns and are bombable). The other developer expressed an interest in using GIT to get his work into the FG mainline and I think his work would be a good adjunct to the update I am proposing. But it was also apparent that he had no idea how to go about doing this. There was a poll on the forums asking users what they thought was the area in FG that needed the most work and by far the item with the most votes was improving the existing models. The more that can be done to encourage collaboration on and contributions to the existing models the better it will be for dealing with this apparent shortcoming. It would be really helpful to users thinking about working on an existing model to have documentation on how to go about this process. I have worked as a developer on other open source projects as well as commercial systems so I had a pretty good idea how to go about this but many users do not have this kind of background and have no idea how to get started. Btw. local finger trouble with git can easily be adjusted using git rebase, see this very useful site for more information: http://www-cs-students.stanford.edu/~blynn/gitmagic/ch05.html
Re: [Flightgear-devel] aircraft search
On 19 Jul 2010, at 18:40, Lance Levsen wrote:
Result:
dante:~/Desktop/Source_Code/Flightgear/flightgear$ fgfs
Cannot find specified aircraft: c172p
Config option parsing failed ...
Environment vars:
FG_HOME=/home/lance/Desktop/Source_Code/Flightgear
FG_ROOT=/home/lance/Desktop/Source_Code/Flightgear/fgdata
FG_SCENERY=/home/lance/.fgfs/Scenery:/home/lance/Desktop/Source_Code/Flightgear/Scenery/
The c172p directory (and all others) are in ${FG_ROOT}/Aircraft/
It doesn't matter what options I use to fgfs, it dies in exactly the
same way every time.
Does it work if you specify --aircraft=c172p explicitly?
how about other aircraft?
what does --show-aircraft list?
I wonder if I have a bug picking up the default value
James
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Same, same. Sorry. :) I have a .fgfsrc which sets the b1900d as
default. However, I also specified it on the cmdline.
dante:~$ fgfs --show-aircraft
Cannot find specified aircraft: b1900d
Config option parsing failed ...
dante:~$ fgfs --aircraft=b1900d
Cannot find specified aircraft: b1900d
Config option parsing failed ...
dante:~$ fgfs --aircraft=777-200ER
Cannot find specified aircraft: 777-200ER
Config option parsing failed ...
dante:~$ fgfs --help
Cannot find specified aircraft: b1900d
Config option parsing failed ...
All options command line options fail in the same way. (That's a
little worrying actually.)
Cheers,
lance
On 19/07/10 01:55 PM, James Turner wrote:
On 19 Jul 2010, at 18:40, Lance Levsen wrote:
Result:
dante:~/Desktop/Source_Code/Flightgear/flightgear$ fgfs
Cannot find specified aircraft: c172p
Config option parsing failed ...
Environment vars:
FG_HOME=/home/lance/Desktop/Source_Code/Flightgear
FG_ROOT=/home/lance/Desktop/Source_Code/Flightgear/fgdata
FG_SCENERY=/home/lance/.fgfs/Scenery:/home/lance/Desktop/Source_Code/Flightgear/Scenery/
The c172p directory (and all others) are in ${FG_ROOT}/Aircraft/
It doesn't matter what options I use to fgfs, it dies in exactly the
same way every time.
Does it work if you specify --aircraft=c172p explicitly?
how about other aircraft?
what does --show-aircraft list?
I wonder if I have a bug picking up the default value
James
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
- --
Lance Levsen,
Catprint Computing
Tel: (306) 493-2278
Cell: (306) 230-8783
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkxEr8YACgkQWSOc2vLaecj5JwCeKGttEqjjmk4x/OeD7W8rNBCP
Q8oAoNrpRWAi1JijXx6Cq5UqXmkpl0/8
=y2jz
-END PGP SIGNATURE-
--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] autopilot stage names
I'm posting in haste so I apologize if I'm missing something, but was there a recent change to the autopilot system that now ignores stages if they have the same name tag as a previous stage? Previously this wasn't the case, but if it's a new addition, it could possible break some configurations that aren't expecting this. Also, in the autopilot dialog box, something is now forcing the altitude to zero no matter what I change it to? Previously I could step the target altitude up and down in 100' increments using the up and down arrow keys and no matter what I do, the altitude is forced back to zero? Any ideas? This is with the Rascal110 model. Thanks, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim P-51D merge request
On Mon, 19 Jul 2010, Hal V. Engel wrote: Are there any plans to update JSBSim in FG GIT? Hi again, Erik did that just a few days ago (on the 16th) :) Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] aircraft search
On 19 Jul 2010, at 21:04, Lance Levsen wrote: Same, same. Sorry. :) I have a .fgfsrc which sets the b1900d as default. However, I also specified it on the cmdline. dante:~$ fgfs --show-aircraft Cannot find specified aircraft: b1900d Config option parsing failed ... dante:~$ fgfs --aircraft=b1900d Cannot find specified aircraft: b1900d Config option parsing failed ... dante:~$ fgfs --aircraft=777-200ER Cannot find specified aircraft: 777-200ER Config option parsing failed ... dante:~$ fgfs --help Cannot find specified aircraft: b1900d Config option parsing failed ... All options command line options fail in the same way. (That's a little worrying actually.) Unfortunately that's due to how the --aircraft option is parsed - *before* most of the config files are loaded. You're on Unix, I infer from the paths you posted earlier ... hmm. Can you email me your .fgfsrc? James -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
