Re: [Flightgear-devel] JSBSIM Aircraft Crash at Reset
Hello, Solved my built issue: simgear and flightgear seems mismatch some links when built under the same devel directory (devel-prog-fgCVS/11-0205/flightgear and ,devel-prog-fgCVS/11-0205/simgear) since make flightgear is going on after the end; building again simgear . Well, The last FG git next version is right. Tested with a lot of JSBSim Aircraft (more and less complex) the reset feature is performing well. Thanks to Thorsten, Bertrand and others, who worked on it. 2011/2/6 ThorstenB bre...@gmail.com On 06.02.2011 15:07, Jon S. Berndt wrote: That works. Sort of. But it's trying to patch JSBSim.cxx which we no longer have in JSBSim standalone. Patch looks good and is pushed to FlightGear/next now (so our JSBSim.cxx is also updated now). Thanks Betrand! PS: I've made several reset tests, all look good now. Also, no side-effects with the previous patches were reported, so I'm also pushing the patches to FG/2.2 now (trying to remember the entire patch sequence... :) ). cheers, Thorsten -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Best regards, Henri, aka Alva Official grtux hangar maintainer -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Incorrect conversion used for lbs to gallon of fuel
Hello, Beware that version, break the tanks system of Boeing 314 Here the Nasal error Nasal runtime error: vector index 7 out of bounds (size: 7) at /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314-fuel.nas, line 79 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314-fuel.nas, line 70 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314-fuel.nas, line 59 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314-fuel.nas, line 19 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314.nas, line 92 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314.nas, line 111 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314.nas, line 17 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Aircraft/Boeing314/Nasal/Boeing314.nas, line 125 called from: /wrklvm/FlightGear/FlightGear_CVS/data/Nasal/globals.nas, line 100 My previous version didn't Revision: 133cfbfa7f4ec62ddc97bd93d4a50fec81b52362 2011/2/6 Hal V. Engel hven...@gmail.com On Sunday, February 06, 2011 01:13:28 PM Torsten Dreyer wrote: I have checked your code and it breaks the previous behaviour for JSBSim. Your code is overwriting JSBSim values during initialization, I would rather do it the other way around and make JSBSim overwrite FlightGear default values. Especially because the capacity of all the tanks is now set to zero instead of using the FDM model definition. Enclosed is a patch that restores the normal behaviour : fuel capacity, level and density are set after the values defined in the aircraft JSBSim XML definition. Ouch - that was my bad. I only initialized JSBSim properties from FlightGear properties which didn't work if tanks are only defined within the JSBSim config file. Your patch turns this the other way round. I tried to combine both versions and set JSBSim properties from FlightGear properties if they exist and create the FlightGear properties from JSBSim properties if not. Looks good for me with the p51d-jsbsim, the c172p and the SenecaII. Thanks for the fast bug-report and the solution! Torsten Did you test the P-51D drop tanks to make sure these work OK? The unusual thing it does is to prevent the drop tank contents from being non-zero unless the tank is currently in place. This is to prevent the pilot from using the Equipment -- Fuel and Payload menu to put fuel into a non-existant drop tank. This should be tested just to make sure it is still working. Hal -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Best regards, Henri, aka Alva Official grtux hangar maintainer -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] io configs
On Mon, Feb 7, 2011 at 1:11 AM, Harry Campigli wrote: All. With out modifying the code, is there a way do define IO commands in the preference.xml file rather than the command line? I suspect not but hopefully I am wrong. To explain, in a set up where multiple machines with differing io configs , pick up their startup command line and preference files from a single machine, it would avoid having to edit so many start files. Only other option I see is to write a shell script to build the unique start command files then fire up FG each time. The way I've done this in the past is to create a unique ~/.fgfsrc file for each machine that contains the individual IO command line options and the individual view parameter options. (I was running under linux ... in my case I setup auto-login and automatically started up the software too, so when the machine was powered on, it came up running the FlightGear software automatically.) Regards, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] io configs
Hi Curt, Thanks for that, being one to give it a go, this arvo I put wrote a small generic shell script that starts up fg on each machine. It just reads 2 files of a server, one unique for that machine, the other for all machines. Its build the fgfs command line then issues it. I figured the FG IO streams were built via simgear right at init rather than later on the property tree. For info I have the machines all running TWM under ubuntu on thumb sticks. So each install is identical with configs and scenery by nfs from the server, next step is to move them into a a ram file system image which loads and boots from the stick or pxe. Although not Flightgear, you don't remember how you set up the auto logon, thats rather looked down on in unix circles and I have not found any answers to that question around the net. Thats my next problem to address. regard Harry On Mon, Feb 7, 2011 at 8:40 PM, Curtis Olson curtol...@gmail.com wrote: On Mon, Feb 7, 2011 at 1:11 AM, Harry Campigli wrote: All. With out modifying the code, is there a way do define IO commands in the preference.xml file rather than the command line? I suspect not but hopefully I am wrong. To explain, in a set up where multiple machines with differing io configs , pick up their startup command line and preference files from a single machine, it would avoid having to edit so many start files. Only other option I see is to write a shell script to build the unique start command files then fire up FG each time. The way I've done this in the past is to create a unique ~/.fgfsrc file for each machine that contains the individual IO command line options and the individual view parameter options. (I was running under linux ... in my case I setup auto-login and automatically started up the software too, so when the machine was powered on, it came up running the FlightGear software automatically.) Regards, Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] io configs
On Mon, Feb 7, 2011 at 9:06 AM, Harry Campigli wrote: Although not Flightgear, you don't remember how you set up the auto logon, thats rather looked down on in unix circles and I have not found any answers to that question around the net. Thats my next problem to address. I was setup here to run Fedora + gnome. The autologin, and auto-program start mechanism I used is gnome specific. For TWM, I'm not sure. I guess it depends on what login manager you are using and how things are setup. Are you starting up X11 and using xdm? Then you probably want to dig through the xdm configs. Wow it's been a long time since I fiddled with configuration xdm ... probably well over 10 years. Otherwise perhaps another option (untested) would be to not start a login manager automaticallly and just startup X11 from an /etc/init.d/ script (maybe by calling startx). For auto starting programs once X11 is running and a user session is active ... that's within the domain of the window manager (TWM) and I don't think I've ever used that in ernest. Long ago, I used fvwm which was the bloat-ware fancy window manager of the day (now we have gnome/kde which are nice but give a new definition to bloatware.) There are probably easier ways to do this and harder ways to do this ... and I'd probably lean toward adding something to /etc/init.d/ but maybe there's a better mechanism already there if you googled and did some research? Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://www.flightgear.org/blogs/category/curt/http://www.flightgear.org/blogs/category/personal/curt/ -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN
Hello, devel-members, I am getting ( randomly ) the following messages Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..) nan nan nan nan nan nan segment ignored.. Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..) nan nan nan nan nan nan segment ignored.. Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..) nan nan nan nan nan nan segment ignored.. PT_vs_hpt: ran out of layers for h=nan PT_vs_hpt: ran out of layers for h=nan Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN I would like to know, which feature, within flightgear is using Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0]. I do not try to access that property, so i guess it is an internal (automated ?) process Your answer could help me to debug the model i am working on ( http://www.flightgear.org/forums/viewtopic.php?f=4t=10992 ) OR Is it only a known bug ? Thanks -- Best regards, Henri, aka Alva Official grtux hangar maintainer -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN
On Mon, Feb 7, 2011 at 6:38 PM, henri orange hohora...@gmail.com wrote: Hello, devel-members, I am getting ( randomly ) the following messages Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..) nan nan nan nan nan nan segment ignored.. Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..) nan nan nan nan nan nan segment ignored.. Warning: invalid line segment passed to IntersectVisitor::addLineSegment(..) nan nan nan nan nan nan segment ignored.. PT_vs_hpt: ran out of layers for h=nan PT_vs_hpt: ran out of layers for h=nan Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN I would like to know, which feature, within flightgear is using Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0]. I do not try to access that property, so i guess it is an internal (automated ?) process That is already the end of the problem chain. Somewhere NaN is creeping into the system and propagates to various parts. Finding what uses z-accel-fps_sec, while possible, will not help you in troubleshooting the root cause. You might want to try using a debugger and running with the command line option --enable-fpe. -- Csaba/Jester -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Nasal getprop: property /accelerations[0]/pilot[0]/z-accel-fps_sec[0] is NaN
On Mon, Feb 7, 2011 at 6:59 PM, Csaba Halász csaba.hal...@gmail.com wrote: That is already the end of the problem chain. Somewhere NaN is creeping into the system and propagates to various parts. Finding what uses z-accel-fps_sec, while possible, will not help you in troubleshooting the root cause. It might have something to do with the relocation to a mooring position. I had some hint of NaN when that happened near KSFO, but had no problems at EHAM (which doesn't have a mooring position). -- Csaba/Jester -- The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear at LinuxTag and FSWeekend need
Torsten Dreyer wrote: Oh - and thanks for the first 150$, received today! Another $20 USD today, many thanks ! In summary this already makes almost one of the two additional monitors we planned to buy. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear at LinuxTag and FSWeekend need
Martin Spott wrote: Another $20 USD today, many thanks ! Today we recieved even more, $50 US plus 50 Euros - but now I'll stop announcing every donation ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] fg command arguments
Is there a way to specify multiple preference.xml files in the data directory? Running a multi-core machine and need to run three instances of fg, each with a different view with the camera specified in the xml file, but don't want to run extra copies of the cameras in the slaves; just the camera pertinent to the desired view. A REALLY ugly way would be to create three data repositories, but that would be the absolute last when everything else has failed option. Looked over the all the options but nothing other than setting the fg-root path to the directory or scenery. Maybe just write some code in options to add that as a command argument with a default to preferences.xml John -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg command arguments
I think what your looking for is the --config option, it allows you to load arbitrary xml config files. So just create a separate xml for each camera definition and then use the --config option to load the appropriate one for that instance of fgfs. cheers! --Jacob -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg command arguments
I think what your looking for is the --config option, it allows you to load arbitrary xml config files. So just create a separate xml for each camera definition and then use the --config option to load the appropriate one for that instance of fgfs. cheers! --Jacob Thanks, that sounds like what I'm looking for. Question? does it default to the fg_root directory, the local directory where the fgfs script runs, or is the full path required. Also is the .xml file extension required? Regards John -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] fg command arguments
I think what your looking for is the --config option, it allows you to load arbitrary xml config files. So just create a separate xml for each camera definition and then use the --config option to load the appropriate one for that instance of fgfs. cheers! --Jacob OK! disregard the questions, got it working. Only comment, placement seems to be important, needs to run after all the other stuff Thanks again John -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
