[Flightgear-devel] 3D audio and single channel wav files (Was: SBSim: Crash at reset)
On Sat, 2011-02-05 at 02:25 +0100, Arnt Karlsen wrote: ..relevant to the 747-400 is: failed to load sound buffer:Failed to load wav file: Unsupported mode within an otherwise usable file type at /home/arnt/FG-git/install/fgfs/bin/../fgdata//Aircraft/747-400/Sounds/FGOS_FlapXtndWClick.wav You get this when the WAV file has more than one channel. Remember that 3d sound sources have no way to handle stereo sounds so single channel audio is only supported by all of the 3d audio rendering engines. Erik -- 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] 3D audio and single channel wav files (Was: SBSim: Crash at reset)
On Sat, 05 Feb 2011 10:12:33 +0100, Erik wrote in message 1296897153.1587.1.camel@Raptor: On Sat, 2011-02-05 at 02:25 +0100, Arnt Karlsen wrote: ..relevant to the 747-400 is: failed to load sound buffer:Failed to load wav file: Unsupported mode within an otherwise usable file type at /home/arnt/FG-git/install/fgfs/bin/../fgdata//Aircraft/747-400/Sounds/FGOS_FlapXtndWClick.wav You get this when the WAV file has more than one channel. Remember that 3d sound sources have no way to handle stereo sounds so single channel audio is only supported by all of the 3d audio rendering engines. Erik ..hum. Maybe use one .wav for each 3d audio rendering engine until we have a unified audio model? ..saw an article years back of a microphone mount, modeled after the human head, with the 2 microphones where we have eardrums. Add a coupla wee headset cameras, one for each ear cup, and we can automate building audio models from the videos. ;o) ..with human ear auditory canal style audio vectors, we need to orient these vectors, and the videos tells us when, how and where the pilot points his head and his auditory canals, which tells us exactly what he hears, and which tells us exactly how FG should sound when we simulate doing the same moves in FG cockpits. ..these fancy -5.1, -7.1 etc systems merely add more new data to the model builds, e.g. microphones in gloves, boots, pockets to pick up stick, pedal, seat etc vibrations, so we can get e.g. the P-51D's radiator duct dive howl right by borrowing pocket and headset etc space from air show pilots, we don't wanna add to their workload or worries, so our payloads needs to be of the lightweight fire-up-'n-forget kind. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- 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] JSBSIM Aircraft Crash at Reset
Hello, devel-members Again starting the topic ( was oriented to an other direction ) To resume what i was discovering: With at least two official jsbsim models 747-400 p51d I am getting a segmentation error at reset. I don't say these models are wrong, i say there is somewhere, in jsbsim during init, something wrong ( since i can notice the issue with many others jsbsim models ) My first reaction was is it just me ?. I gave you the Backtrace when i got it. The airport altitude seems to modify the system reaction. The more the Airport is at low altitude, the more i get the chance to win the crash. However sometime, everything is right. Thanks for an answer on that specific topic -- 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] JSBSIM Aircraft Crash at Reset
On Sat, 2011-02-05 at 13:00 +0100, henri orange wrote: Hello, devel-members Again starting the topic ( was oriented to an other direction ) To resume what i was discovering: With at least two official jsbsim models 747-400 p51d I am getting a segmentation error at reset. It is important to know what version of FlightGear you are using, FlighGear-2.0. the git branch for FlightGear-2.2 or the developers branch for FlightGear. FlightGear-2.2 has not yet been updated with the new JSBSim reset code. Erik -- 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] JSBSIM Aircraft Crash at Reset
Hi, Erik Sorry for the question is there somewhere a specific fg2.2 source ? I am using the git version with git pull, though i don't understand the meaning of it, it does work and give me an update. I thought it was the fg devel version. with fgfs --version i get FlightGear version: 2.2.0 Revision: 133cfbfa7f4ec62ddc97bd93d4a50fec81b52362 Build-Id: none FG_ROOT=/wrklvm/FlightGear/FlightGear_CVS/data FG_HOME=/home/alva/.fgfs FG_SCENERY=/wrklvm/FlightGear/FlightGear_CVS/data/Scenery:/wrklvm/FlightGear/FlightGear_CVS/data/Scenery/Terrain:/wrklvm/FlightGear/FlightGear_CVS/data/Scenery/Objects: SimGear version: 2.2.0 PLIB version: 185 about aircraft models, i do use that link http://mapserver.flightgear.org/git/?p=fgdata;a=tree;f=Aircraft click on snapshot 2011/2/5 Erik Hofman e...@ehofman.com On Sat, 2011-02-05 at 13:00 +0100, henri orange wrote: Hello, devel-members Again starting the topic ( was oriented to an other direction ) To resume what i was discovering: With at least two official jsbsim models 747-400 p51d I am getting a segmentation error at reset. It is important to know what version of FlightGear you are using, FlighGear-2.0. the git branch for FlightGear-2.2 or the developers branch for FlightGear. FlightGear-2.2 has not yet been updated with the new JSBSim reset code. Erik -- 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] JSBSIM Aircraft Crash at Reset
On Sat, 2011-02-05 at 13:31 +0100, henri orange wrote: Hi, Erik Sorry for the question is there somewhere a specific fg2.2 source ? I am using the git version with git pull, though i don't understand the meaning of it, it does work and give me an update. I thought it was the fg devel version. with fgfs --version i get FlightGear version: 2.2.0 I get that too, with the developers version in git.. It looks like you are using the developers version indeed which is a pity since I had hoped this was fixed now. Erik -- 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] JSBSIM Aircraft Crash at Reset
How can I update my FlightGear development codebase (which was created a few months ago) from git so I can try to see this problem? Jon -Original Message- From: Erik Hofman [mailto:e...@ehofman.com] Sent: Saturday, February 05, 2011 6:42 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] JSBSIM Aircraft Crash at Reset On Sat, 2011-02-05 at 13:31 +0100, henri orange wrote: Hi, Erik Sorry for the question is there somewhere a specific fg2.2 source ? I am using the git version with git pull, though i don't understand the meaning of it, it does work and give me an update. I thought it was the fg devel version. with fgfs --version i get FlightGear version: 2.2.0 I get that too, with the developers version in git.. It looks like you are using the developers version indeed which is a pity since I had hoped this was fixed now. Erik --- --- 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] JSBSIM Aircraft Crash at Reset
On Sat, 5 Feb 2011, Jon S. Berndt wrote: How can I update my FlightGear development codebase (which was created a few months ago) from git so I can try to see this problem? Hi Jon, Do you have local any changes on your branch? If not a simple: git pull should do the right thing. git pull will also work if you have committed local changes but will make your local history messy (and the official history too if your changes are ever merged back into the official history). If you don't care about the messyness of your local history read no further than point 1 below and use git pull without hesitation :) If you do have changes you want to keep I'd recommend using git rebase to keep them on top of the official work: 1. First commit your changes to your local branch. git status- show you what files you have modified. git add file1 file2 etc - adds the files you want to commit git commit- creates a commit with the changes you have added. 2. Fetch the latest stuff from the main repository. git fetch 3. Rebase your local branch on top of the latest official state. For the FlightGear and SimGear sources this would be git rebase origin/next For fgdata it is git rebase origin/master 4. If you get conflicts you can drop your local conflicting commit by git rebase --skip or resolve the conflicts, git add the changed files and continue the rebase with git rebase --continue (Use of git status is needed here to see which files are in conflict). As an additional safe-guard you may create a name for your previous work before you rebase so that you can easily recover it if the rebase goes bad. Assuming your branch is called my-branch the following command creates a back-up point: git branch my-branch.20110205 my-branch Win32 git works well from Windows powershell, btw. Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- 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] JSBSIM Aircraft Crash at Reset
Jon, There are also a couple other option if you don't want to compile the source from scratch yourself. (BTW, thanks for the nice git summary Anders. Git is very easy to use if all you want to do is track the development repository.) You can get precompiled binaries of the most recent git code at the following link. But it requires some work to grab other pieces and put them in the right place on your machine. It's still a little DIY: http://flightgear.simpits.org:8080/ Another option is to download a full installer than includes the prebuilt windows binary and the entire data package and several aircraft. That is available at the following link: Make sure to grab the most recent Setup FlightGear vMMDD.exe http://mirrors.ibiblio.org/pub/mirrors/flightgear/ftp/Win32/ That said, I don't know if these prebuilt versions demonstrate the bug or not? Curt. On Sat, Feb 5, 2011 at 8:14 AM, Anders Gidenstam anders-...@gidenstam.orgwrote: On Sat, 5 Feb 2011, Jon S. Berndt wrote: How can I update my FlightGear development codebase (which was created a few months ago) from git so I can try to see this problem? Hi Jon, Do you have local any changes on your branch? If not a simple: git pull should do the right thing. git pull will also work if you have committed local changes but will make your local history messy (and the official history too if your changes are ever merged back into the official history). If you don't care about the messyness of your local history read no further than point 1 below and use git pull without hesitation :) If you do have changes you want to keep I'd recommend using git rebase to keep them on top of the official work: 1. First commit your changes to your local branch. git status- show you what files you have modified. git add file1 file2 etc - adds the files you want to commit git commit- creates a commit with the changes you have added. 2. Fetch the latest stuff from the main repository. git fetch 3. Rebase your local branch on top of the latest official state. For the FlightGear and SimGear sources this would be git rebase origin/next For fgdata it is git rebase origin/master 4. If you get conflicts you can drop your local conflicting commit by git rebase --skip or resolve the conflicts, git add the changed files and continue the rebase with git rebase --continue (Use of git status is needed here to see which files are in conflict). As an additional safe-guard you may create a name for your previous work before you rebase so that you can easily recover it if the rebase goes bad. Assuming your branch is called my-branch the following command creates a back-up point: git branch my-branch.20110205 my-branch Win32 git works well from Windows powershell, btw. Cheers, Anders -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/ -- 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 -- 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] JSBSIM Aircraft Crash at Reset
Hi, probably spotted the cause for the reported reset crash: it's the same as already reported before - targeted by this earlier patch: http://www.gitorious.org/fg/flightgear/commit/287cc74965e11ff3888117a9d9b88ed2bdbb9252 This patch unties all JSBSim properties prior to reset. However, it's not quite sufficient and misses some JSBSim properties. Problem is that JSBSim can also tie properties outside the /fdm/jsbsim branch - using property paths which can be configured in aircraft-specific configuration files. For example, the configuration of the 747 (in Systems/failures.xml) causes JSBSim to bind the following additional properties: /accelerations/pilot-gdamped /controls/fuel/fuel-to-remain /sim/model/pushback/target-speed-fps /autopilot/autobrake/left-brake-output /autopilot/autobrake/right-brake-output These properties aren't untied by the earlier patch - so still result in trouble. I'm currently testing a different patch for the same issue: instead of untieing all properties below the /fdm/jsbsim (only), I added a list to JSBSim's FGPropertyManagager, so it keeps track of all the properties it has actually bound. It can then use this list to untie all its properties - no mattere where these are located in the property tree. This patch seems to fix the issue for me. I'll do a few more tests and (hopefully :) ) propose this a new patch... 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
Re: [Flightgear-devel] JSBSIM Aircraft Crash at Reset
On Sat, 5 Feb 2011 15:14:42 +0100 (CET), Anders wrote in message pine.lnx.4.64.1102051501090.3...@sleipner.gidenstam.se: On Sat, 5 Feb 2011, Jon S. Berndt wrote: How can I update my FlightGear development codebase (which was created a few months ago) from git so I can try to see this problem? Hi Jon, Do you have local any changes on your branch? If not a simple: git pull should do the right thing. git pull will also work if you have committed local changes but will make your local history messy (and the official history too if your changes are ever merged back into the official history). If you don't care about the messyness of your local history read no further than point 1 below and use git pull without hesitation :) If you do have changes you want to keep I'd recommend using git rebase to keep them on top of the official work: 1. First commit your changes to your local branch. git status- show you what files you have modified. git add file1 file2 etc - adds the files you want to commit git commit- creates a commit with the changes you have added. ..git commit -m 'to add an hopefully helpful reminder message of why etc you did this commit' 2. Fetch the latest stuff from the main repository. git fetch 3. Rebase your local branch on top of the latest official state. For the FlightGear and SimGear sources this would be git rebase origin/next For fgdata it is git rebase origin/master 4. If you get conflicts you can drop your local conflicting commit by git rebase --skip or resolve the conflicts, git add the changed files and continue the rebase with git rebase --continue (Use of git status is needed here to see which files are in conflict). As an additional safe-guard you may create a name for your previous work before you rebase so that you can easily recover it if the rebase goes bad. Assuming your branch is called my-branch the following command creates a back-up point: git branch my-branch.20110205 my-branch Win32 git works well from Windows powershell, btw. Cheers, Anders -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...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. -- 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] JSBSIM Aircraft Crash at Reset
Hi, Thorsten, May be i can confirm your feeling. I was looking at the old Catalina official gpl version. It can start at the right mooring place on water, when there is one, close to the Airport we want to start from ( for instance KSFO, with Mooring place at Treasure Island, Pan Am base at San Francisco). To do so, there is a nice script ( from the Boeing314) which re_init FG sitting the Aircraft at the right defined place. It is a reset. That specific process is longer working with that old existing Catalina version (though outdated). However, there is a lot of jsbsim error red message due to the new jsbsim property control process I have just experimented a modified version, by removing these message error with some minor update. I get things working right, ONLY, i don't try to remove the error red message due to internal flightgear property. for instance if i keep on, these messages: FGPropertyManager::GetNode() No node found for /systems/electrical/outputs/instrument-lights In condition: /systems/electrical/outputs/instrument-lights gt 27. Unknown property /systems/electrical/outputs/instrument-lights referenced. Creating property. Check usage. FGPropertyManager::GetNode() No node found for /instrumentation/lights/blinker-kinemat-out In condition: /instrumentation/lights/blinker-kinemat-out == 0. Unknown property /instrumentation/lights/blinker-kinemat-out referenced. Creating property. Check usage. FGPropertyManager::GetNode() No node found for /systems/electrical/outputs/landing-light In condition: /systems/electrical/outputs/landing-light gt 27. Unknown property /systems/electrical/outputs/landing-light referenced. Creating property. Check usage. FGPropertyManager::GetNode() No node found for /sim/model/waterbombing In condition: /sim/model/waterbombing == 1. Unknown property /sim/model/waterbombing referenced. Creating property. Check usage. The reset to moorage place is working. If, i attend to remove these messages, the reset to moorage place, crash. 2011/2/5 ThorstenB bre...@gmail.com Hi, probably spotted the cause for the reported reset crash: it's the same as already reported before - targeted by this earlier patch: http://www.gitorious.org/fg/flightgear/commit/287cc74965e11ff3888117a9d9b88ed2bdbb9252 This patch unties all JSBSim properties prior to reset. However, it's not quite sufficient and misses some JSBSim properties. Problem is that JSBSim can also tie properties outside the /fdm/jsbsim branch - using property paths which can be configured in aircraft-specific configuration files. For example, the configuration of the 747 (in Systems/failures.xml) causes JSBSim to bind the following additional properties: /accelerations/pilot-gdamped /controls/fuel/fuel-to-remain /sim/model/pushback/target-speed-fps /autopilot/autobrake/left-brake-output /autopilot/autobrake/right-brake-output These properties aren't untied by the earlier patch - so still result in trouble. I'm currently testing a different patch for the same issue: instead of untieing all properties below the /fdm/jsbsim (only), I added a list to JSBSim's FGPropertyManagager, so it keeps track of all the properties it has actually bound. It can then use this list to untie all its properties - no mattere where these are located in the property tree. This patch seems to fix the issue for me. I'll do a few more tests and (hopefully :) ) propose this a new patch... 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] JSBSIM Aircraft Crash at Reset
From: ThorstenB [mailto:bre...@gmail.com] Hi, probably spotted the cause for the reported reset crash: it's the same as already reported before - targeted by this earlier patch: http://www.gitorious.org/fg/flightgear/commit/287cc74965e11ff3888117a9d 9b88ed2bdbb9252 This patch unties all JSBSim properties prior to reset. However, it's not quite sufficient and misses some JSBSim properties. Problem is that JSBSim can also tie properties outside the /fdm/jsbsim branch - using property paths which can be configured in aircraft-specific configuration files. ... I'm currently testing a different patch for the same issue: instead of untieing all properties below the /fdm/jsbsim (only), I added a list to JSBSim's FGPropertyManagager, so it keeps track of all the properties it has actually bound. It can then use this list to untie all its properties - no mattere where these are located in the property tree. This patch seems to fix the issue for me. I'll do a few more tests and (hopefully :) ) propose this a new patch... cheers, Thorsten I thought we already had something like this in JSBSim - I thought I had added such a feature already, myself, actually, but maybe I just dreamed it. ;-) I'll have to go back and look at the [JSBSim] code again. I'd like to figure out how to make resetting work better from the API - more naturally and without having to reload the aircraft model. This would be useful for both the JSBSim standalone executable and for any larger simulation framework that incorporates JSBSim. Jon www.JSBSim.org www.facebook.com/jsbsim -- 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] JSBSIM Aircraft Crash at Reset
I'll have to go back and look at the [JSBSim] code again. I'd like to figure out how to make resetting work better from the API - more naturally and without having to reload the aircraft model. This would be useful for both the JSBSim standalone executable and for any larger simulation framework that incorporates JSBSim. There was a discussion on the jsbsim mailing list back in april 2009, but I think it somehow stalled without a solution: http://sourceforge.net/mailarchive/message.php?msg_id=22186590 Torsten -- 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] JSBSIM Aircraft Crash at Reset
On 05.02.2011 16:21, ThorstenB wrote: I'm currently testing a different patch for the same issue: instead of untieing all properties below the /fdm/jsbsim (only), I added a list to JSBSim's FGPropertyManagager, so it keeps track of all the properties it has actually bound. It can then use this list to untie all its properties - no mattere where these are located in the property tree. New patch pushed to flightgear/next: http://www.gitorious.org/fg/flightgear/commit/ad8d46ba648263630b8777c53f852b75cad7ecdd This will be overwritten by the next JSBSim update, however it's a short-term fix and candidate for our pending 2.2 release. So, please test if you still see reset issues with JSBSim aircraft. If we find it's an improvement (maybe/hopefully the final fix for this issue), then we'll be pushing this to the 2.2 branch also. But remember, none of the reset fixes is part of the 2.2 branch just yet. The long term fix needs to be part of the JSBSim repository of course. Jon, Erik: please check if you want to use this patch or have some other solution to the problem. 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
Re: [Flightgear-devel] JSBSIM Aircraft Crash at Reset
, I get an error at build screen-dump.cxx:(.text+0x276): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgmisc.a(PathOptions.o): In function `simgear::makeOptionsFromPath(SGPath const)': PathOptions.cxx:(.text+0x49): undefined reference to `osgDB::Options::Options(osgDB::Options const, osg::CopyOp const)' /usr/local/lib/libsgstructure.a(commands.o): In function `global constructors keyed to _ZN12SGCommandMgrC2Ev': commands.cxx:(.text+0x597): undefined reference to `OpenThreads::Mutex::Mutex(OpenThreads::Mutex::MutexType)' /usr/local/lib/libsgenvironment.a(precipitation.o): In function `SGPrecipitation::SGPrecipitation()': precipitation.cxx:(.text+0x686): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgenvironment.a(precipitation.o): In function `SGPrecipitation::build()': precipitation.cxx:(.text+0x82c): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgenvironment.a(precipitation.o): In function `SGPrecipitation::~SGPrecipitation()': precipitation.cxx:(.text._ZN15SGPrecipitationD2Ev[_ZN15SGPrecipitationD5Ev]+0x46): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgenvironment.a(precipitation.o): In function `SGPrecipitation::~SGPrecipitation()': precipitation.cxx:(.text._ZN15SGPrecipitationD0Ev[_ZN15SGPrecipitationD5Ev]+0x56): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgenvironment.a(precipitation.o): In function `osg::ref_ptrosgParticle::PrecipitationEffect::~ref_ptr()': precipitation.cxx:(.text._ZN3osg7ref_ptrIN11osgParticle19PrecipitationEffectEED2Ev[_ZN3osg7ref_ptrIN11osgParticle19PrecipitationEffectEED5Ev]+0x36): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgenvironment.a(precipitation.o):precipitation.cxx:(.text._ZN3osg7ref_ptrINS_8ClipNodeEED2Ev[_ZN3osg7ref_ptrINS_8ClipNodeEED5Ev]+0x36): more undefined references to `osg::Referenced::signalObserversAndDelete(bool, bool) const' follow collect2: ld a retourné 1 code d'état d'exécution make[2]: *** [fgfs] Erreur 1 make[2]: quittant le répertoire « /wrk3lv/00LIEN-DEVEL/devel-prog-fgCVS/11-0205/flightgear/src/Main » make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le répertoire « /wrk3lv/00LIEN-DEVEL/devel-prog-fgCVS/11-0205/flightgear/src » make: *** [all-recursive] Erreur 1 OSG 2.9.10 which was right with a previous fg git version 2011/2/5 ThorstenB bre...@gmail.com On 05.02.2011 16:21, ThorstenB wrote: I'm currently testing a different patch for the same issue: instead of untieing all properties below the /fdm/jsbsim (only), I added a list to JSBSim's FGPropertyManagager, so it keeps track of all the properties it has actually bound. It can then use this list to untie all its properties - no mattere where these are located in the property tree. New patch pushed to flightgear/next: http://www.gitorious.org/fg/flightgear/commit/ad8d46ba648263630b8777c53f852b75cad7ecdd This will be overwritten by the next JSBSim update, however it's a short-term fix and candidate for our pending 2.2 release. So, please test if you still see reset issues with JSBSim aircraft. If we find it's an improvement (maybe/hopefully the final fix for this issue), then we'll be pushing this to the 2.2 branch also. But remember, none of the reset fixes is part of the 2.2 branch just yet. The long term fix needs to be part of the JSBSim repository of course. Jon, Erik: please check if you want to use this patch or have some other solution to the problem. 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] JSBSIM Aircraft Crash at Reset
On 05.02.2011 18:54, henri orange wrote: , I get an error at build screen-dump.cxx:(.text+0x276): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgmisc.a(PathOptions.o): In function `simgear::makeOptionsFromPath(SGPath const)': You're having some local problem with mismatching osg header files and libraries. Probably compiled against osg 2.8.3 or 2.9.11 include files - and tried to link against 2.9.10 libraries (or vice versa). Or maybe the osg libraries are missing altogether. You were using FG commit 133cfbfa7f4ec62ddc97bd93d4a50fec81b52362 before (previous email). There were only two git updates since then - none affected any osg interface, neither any makefile. 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
[Flightgear-devel] git clone -l question and observations
Here locally I made a local clone of the fgdata repository using git clone -l fgdata fgdata-wip. That seemed to work as advertised. I noticed that the only branch available in the new local clone fgdata-wip is the branch that is active in fgdata at the time the clone is made that's good to know. It doesn't make a complete clone of ever branch, not even the master. I noticed that if I do a git pull inside fgdata-wip it *seems* to merge in changes from the original fgdata respository (master branch) ... I'm not 100% confident in that, I need to try it a few more times after some remote updates get pushed to the central repository. I don't know if all the changes to fgdata/master are brought over, or just the ones that I'm merged to fgdata/wip after doing a git pull in fgdata/master. (Isn't this fun, anyone still with me here?) :-) At least if I update the branch wip branch in the oringal fgdata repository, the changes seemed to get brought over to fgdata-wip when I do a pull there. Now here's my question. If I make a change inside the cloned wip branch of the cloned repository fgdata-wip and then commit it. I don't see it show up in the wip branch of the original fgdata respository. It occurred to me that maybe I need to do a git push to send the changes over to the original repository, but I get an error that is a lot of git-ese that's way over my head. What's the best way to keep my fgdata/wip branch in sync with my fgdata-clone/wip branch? Is there a way? Thanks, 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] FlightGear at LinuxTag and FSWeekend need your help
As many of you might be aware of, a group of FlightGear enthusiasts have been presenting FlightGear at FSWeekend in Lelystad(NL) and LinuxTag in Berlin(DE) over the last years. Our presentation and the equipment list has grown with each show with every single item being donated by the beforementioned enthusiasts. For the next show in Berlin, we would like to have a box of give-away 3D- glasses at hand, we need two additional monitors to complete the setup for our Thomas-Krenn-Server with eight equal displays and our projector needs a new light-bulb. To get everything set and to be able to present FlightGear at it's best for the next years, Curt, Martin and I established a PayPal account and we decided to ask for donations. If you think, we do a good job at presenting and promoting FlightGear and if you want to support us in having the best booth during the show, please consider donating a few Euros, Dollars, Pounds, Crowns, Yen, Francs, Afghanis, Dinars, Pesos or whatever your currency might be to donati...@flightgear.org using PayPal. All donations will be used for the sole purpose of adding to or maintaining the equipment used at the shows. Donations are not tax deductable yet - this might change at some time in the future. Thanks for your support and for making FlightGear the best free flight simulator on earth. Torsten -- 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] JSBSIM Aircraft Crash at Reset
Hi, built OSG 2.9.10 again , and built Simgear Flightgear again gives the same error. Then, since OSG 2.9.11, is available. I have just built osg 2.9.11, Unfortunately simgear built against it, gives the following error mv -f .deps/CheckSceneryVisitor.Tpo .deps/CheckSceneryVisitor.Po g++ -DHAVE_CONFIG_H -I. -I../../../simgear -I../../.. -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT ConditionNode.o -MD -MP -MF .deps/ConditionNode.Tpo -c -o ConditionNode.o ConditionNode.cxx mv -f .deps/ConditionNode.Tpo .deps/ConditionNode.Po g++ -DHAVE_CONFIG_H -I. -I../../../simgear -I../../.. -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT SGClipGroup.o -MD -MP -MF .deps/SGClipGroup.Tpo -c -o SGClipGroup.o SGClipGroup.cxx mv -f .deps/SGClipGroup.Tpo .deps/SGClipGroup.Po g++ -DHAVE_CONFIG_H -I. -I../../../simgear -I../../.. -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT SGInteractionAnimation.o -MD -MP -MF .deps/SGInteractionAnimation.Tpo -c -o SGInteractionAnimation.o SGInteractionAnimation.cxx mv -f .deps/SGInteractionAnimation.Tpo .deps/SGInteractionAnimation.Po g++ -DHAVE_CONFIG_H -I. -I../../../simgear -I../../.. -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT SGMaterialAnimation.o -MD -MP -MF .deps/SGMaterialAnimation.Tpo -c -o SGMaterialAnimation.o SGMaterialAnimation.cxx mv -f .deps/SGMaterialAnimation.Tpo .deps/SGMaterialAnimation.Po g++ -DHAVE_CONFIG_H -I. -I../../../simgear -I../../.. -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT SGOffsetTransform.o -MD -MP -MF .deps/SGOffsetTransform.Tpo -c -o SGOffsetTransform.o SGOffsetTransform.cxx mv -f .deps/SGOffsetTransform.Tpo .deps/SGOffsetTransform.Po g++ -DHAVE_CONFIG_H -I. -I../../../simgear -I../../.. -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT SGPagedLOD.o -MD -MP -MF .deps/SGPagedLOD.Tpo -c -o SGPagedLOD.o SGPagedLOD.cxx SGPagedLOD.cxx: In member function ‘virtual void simgear::SGPagedLOD::forceLoad(osgDB::DatabasePager*, osg::FrameStamp*)’: SGPagedLOD.cxx:73:52: erreur: no matching function for call to ‘osgDB::DatabasePager::requestNodeFile(const std::string, simgear::SGPagedLOD* const, double, osg::FrameStamp*, osg::ref_ptrosg::Referenced, osgDB::Options*)’ /usr/local/include/osgDB/DatabasePager:73:22: note: candidate is: virtual void osgDB::DatabasePager::requestNodeFile(const std::string, osg::NodePath, float, const osg::FrameStamp*, osg::ref_ptrosg::Referenced, const osg::Referenced*) make[4]: *** [SGPagedLOD.o] Erreur 1 make[4]: quittant le répertoire « /wrk3lv/00LIEN-DEVEL/devel-prog-fgCVS/11-0205/simgear/simgear/scene/model » make[3]: *** [all-recursive] Erreur 1 make[3]: quittant le répertoire « /wrk3lv/00LIEN-DEVEL/devel-prog-fgCVS/11-0205/simgear/simgear/scene » What is the matter ? 2011/2/5 ThorstenB bre...@gmail.com On 05.02.2011 18:54, henri orange wrote: , I get an error at build screen-dump.cxx:(.text+0x276): undefined reference to `osg::Referenced::signalObserversAndDelete(bool, bool) const' /usr/local/lib/libsgmisc.a(PathOptions.o): In function `simgear::makeOptionsFromPath(SGPath const)': You're having some local problem with mismatching osg header files and libraries. Probably compiled against osg 2.8.3 or 2.9.11 include files - and tried to link against 2.9.10 libraries (or vice versa). Or maybe the osg libraries are missing altogether. You were using FG commit 133cfbfa7f4ec62ddc97bd93d4a50fec81b52362 before (previous email). There were only two git updates since then - none affected any osg interface, neither any makefile. 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] JSBSIM Aircraft Crash at Reset
On Sun, Feb 6, 2011 at 12:45 AM, henri orange hohora...@gmail.com wrote: Hi, built OSG 2.9.10 again , and built Simgear Flightgear again gives the same error. Then, since OSG 2.9.11, is available. I have just built osg 2.9.11, Unfortunately simgear built against it, gives the following error What is the matter ? Current OSG is unfortunately incompatible with FG. Note, this is a compilation error, as it should be. Your earlier error with 2.9.10 was a linker error, which may mean you are not linking against all the required libraries. You have cut off the actual linker command line, so I can't tell. Have you re-run autogen.sh and configure too? -- 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] JSBSIM Aircraft Crash at Reset
Hi, Csaba Yes against OSG 2.9.10, i did built simgear flightgear from cleaned source ( copied from Git) Which mean: autogen.sh configure make sudo make install . don't bother , thanks for the answer. i will wait for a better stable version osg compatible. 2011/2/6 Csaba Halász csaba.hal...@gmail.com On Sun, Feb 6, 2011 at 12:45 AM, henri orange hohora...@gmail.com wrote: Hi, built OSG 2.9.10 again , and built Simgear Flightgear again gives the same error. Then, since OSG 2.9.11, is available. I have just built osg 2.9.11, Unfortunately simgear built against it, gives the following error What is the matter ? Current OSG is unfortunately incompatible with FG. Note, this is a compilation error, as it should be. Your earlier error with 2.9.10 was a linker error, which may mean you are not linking against all the required libraries. You have cut off the actual linker command line, so I can't tell. Have you re-run autogen.sh and configure too? -- 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 -- 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
