Re: [Flightgear-devel] AH-1 Merge Request
Hi, My development of the Bell AH-1W Cobra is far enough along where I feel it is time to commit it to GIT, especially in time for the new release. I use GIT, but I don't know enough about it to commit it myself. If somebody could commit it for me that would be really great. Screenshot: http://img585.imageshack.us/img585/5017/cobra5.png Download: http://jackmermod.yolasite.com/resources/AH-1%2012-12-10.zip The archive Jack has provided contains a Red Bull livery which is based on the RB logo as trademarked by Red Bull, Austria. Unless it is clear that distributing this trademarked item is legal I propose not to include the livery into FlightGear GIT. Otherwise legal action against FlightGear could be filed. A clarification is currently ongoing. Details start here: http://www.flightgear.org/forums/viewtopic.php?f=4t=10130start=195#p113224 Jack had been involved in this debate. Oliver -- 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] Simgear and OSG out of sync?
I've checked in fixes for this change in osgDB:DatabasePager to the SimGear and FlightGear next and releases/2.2.0 branches. Part of the delay resulted from the fact that the Open Scene Graph change introduced a new bug; I have waited until my patch for that was accepted in OSG to avoid a situation where people could compile with OSG SVN and then crash immediately. So, You need to have revision 12170 or later of OSG SVN in order to run fgfs from the release and next branches. Otherwise you should use OSG 2.8.3 or 2.9.10. I will not conditionalize code in fgfs based on individual revisions of OSG SVN; if you are using OSG SVN, then you are, by definition, living on the bleeding edge. By the way, I committed the changes to releases/2.2.0 and then merged that branch into next. This is the way fixes should move between the two branches. Please don't commit a fix to next and then cherry-pick it to the release branch. It is very messy to have the same change committed on several different branches. Tim On Sun, Jan 16, 2011 at 12:43 PM, James Turner zakal...@mac.com wrote: On 16 Jan 2011, at 10:56, fiers...@zonnet.nl wrote: When I saw this, I removed all sources for OSG and Simgear and restarted with a fresh git clone, but the error remains. I searched the forums and noticed someone else has the same problem with a completely freshly cloned git version. Did I miss something that causes this in the past few weeks? OSG SVN made an API change to Paged LOD, no one yet updated FG to work with it. While some developers do track OSG SVN, that's a slightly ambitious goal for everyone - personally I stick with the most recent developer release of OSG (2.9.9 or 2.9.10 at the moment, depending on who you ask) I believe for this paerticular change Tim Moore has a fix pending, but each such change (not associated with a version release) requires additional configure/cmake complexity to check for the changed API - as was done for CullSettings, for example. James -- Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl ___ 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
[Flightgear-devel] [ANN] tyre smoke system
Seeing all the creative mess people created when trying to use tyre smoke, I have decided to add a little helper class to aircraft.nas, named tyresmoke_system. I also tweaked the existing tyresmoke class a little, but it should still be backward compatible. To use the new tyresmoke_system, all you need to do is replace your previous nasal code with a single call as follows: aircraft.tyresmoke_system.new(0, 1, 2, 3, 4); Pass the appropriate gear indices as arguments. Nothing else is needed, updates are managed automatically. I am not really happy with the physical model either, but I focused on the nasal side for now. Please report any bugs, regressions or comments. -- Cheers, Csaba/Jester -- 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] memory usage
I have noticed that after about an hour of hanging around at KSFO in an ufo on MP, FG's memory went steadily up and eventually reached 2.7GiB. Similarly, during the TGA event at the weekend, memory usage was above 2GiB by the end of the ~5 hour flight. Looks like we may be leaking memory. Anybody else have similar experience? I am using current GIT on 64 bit linux with AI traffic, traffic manager and replay turned off. -- Csaba/Jester -- 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] FlightGear Video Contest
Hi, just in case your are not following the forum and like to create FlightGear videos, this one is for you: http://flightgear.org/forums/viewtopic.php?f=19t=11059 Torsten -- 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] Simgear and OSG out of sync?
2011/2/15 Tim Moore timoor...@gmail.com: I've checked in fixes for this change in osgDB:DatabasePager to the SimGear and FlightGear next and releases/2.2.0 branches. Part of the delay resulted from the fact that the Open Scene Graph change introduced a new bug; I have waited until my patch for that was accepted in OSG to avoid a situation where people could compile with OSG SVN and then crash immediately. So, You need to have revision 12170 or later of OSG SVN in order to run fgfs from the release and next branches. Otherwise you should use OSG 2.8.3 or 2.9.10. I will not conditionalize code in fgfs based on individual revisions of OSG SVN; if you are using OSG SVN, then you are, by definition, living on the bleeding edge. Hi Tim, Your commit broke SimGear for me (using OSG 2.8.1). I have attached a tiny patch that restores the ability to compile the last SG git revision with OSG 2.8.1 Could you please review it and apply it if it makes sense ? Thanks. Bertrand. diff --git a/simgear/scene/model/SGPagedLOD.hxx b/simgear/scene/model/SGPagedLOD.hxx index a9e55d9..4e25931 100644 --- a/simgear/scene/model/SGPagedLOD.hxx +++ b/simgear/scene/model/SGPagedLOD.hxx @@ -72,7 +72,7 @@ public: protected: virtual ~SGPagedLOD(); -#if SG_PAGEDLOD_HAS_OPTIONS +#if !SG_PAGEDLOD_HAS_OPTIONS osg::ref_ptrosgDB::ReaderWriter::Options _readerWriterOptions; #endif }; -- 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] AH-1 Merge Request
Hi, The Red Bull livery has been removed from this release. Download: http://jackmermod.bplaced.net/Files/cobra21511.zip I find it ridiculous and a bit immature how Oliver people whine about a simple logo. If Oliver really cared about preventing fictitious lawsuits as he claims to, he would concentrate his efforts on the several red bull logos that are already in our database. If this thread is further interfered with, I will be forced to result to more forceful methods of having my work committed, or I may very well change the license back to the CC license and our community will have missed out on a very high quality aircraft. Regards, Jack -- 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] ..IP and litigation risks, was: AH-1 Merge Request
On Tue, 15 Feb 2011 16:50:36 -0800, Jack wrote in message 72e5b800-d213-466d-bf46-c3d33d4ae...@gmail.com: Hi, The Red Bull livery has been removed from this release. Download: http://jackmermod.bplaced.net/Files/cobra21511.zip I find it ridiculous and a bit immature how Oliver people whine about a simple logo. If Oliver really cared about preventing fictitious lawsuits as he claims to, he would concentrate his efforts on the several red bull logos that are already in our database. .._where_? If this thread is further interfered with, I will be forced to result to more forceful methods of having my work committed, or I may very well change the license back to the CC license and our community will have missed out on a very high quality aircraft. Regards, Jack ..as you may know, we're not Big Blue, and Big Blue is still here: http://www.groklaw.net/staticpages/index.php?page=20031016162215566 ..in 18 days, this _bullshit_ case celebrates its 8'th year in US Courts. All it takes, is Big Money and Air Show Quality Litigation. ..the reason Big Blue survives, is it still _has_ Big Money. ..now, imagine where _we_ would have been if tSCOG _had_ a case against Big Blue. You would have had to pay tSCOG US $1499 (or whatever it was) for every thread in your cpu. They were targeting GPL code, and the GPL itself, as anti-American. ..even as we celebrate the approaching conclusion of: http://www.groklaw.net/article.php?story=20110215183557939 in http://www.groklaw.net/staticpages/index.php?page=20040319041857760 it is _just_ a side show. http://groklaw.net/ has waaay more. -- ..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 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] Simgear and OSG out of sync?
- Bertrand Coconnier a écrit : 2011/2/15 Tim Moore timoor...@gmail.com: I've checked in fixes for this change in osgDB:DatabasePager to the SimGear and FlightGear next and releases/2.2.0 branches. Part of the delay resulted from the fact that the Open Scene Graph change introduced a new bug; I have waited until my patch for that was accepted in OSG to avoid a situation where people could compile with OSG SVN and then crash immediately. So, You need to have revision 12170 or later of OSG SVN in order to run fgfs from the release and next branches. Otherwise you should use OSG 2.8.3 or 2.9.10. I will not conditionalize code in fgfs based on individual revisions of OSG SVN; if you are using OSG SVN, then you are, by definition, living on the bleeding edge. Hi Tim, Your commit broke SimGear for me (using OSG 2.8.1). I have attached a tiny patch that restores the ability to compile the last SG git revision with OSG 2.8.1 Could you please review it and apply it if it makes sense ? Your patch doesn't work for OSG = 2.9 because _readerWriterOptions is unconditionally used in SGPagedLOD.cxx Regards, -Fred -- Frédéric Bouvier http://www.youtube.com/user/fgfred64 Videos -- 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
