Re: [Flightgear-devel] Version number for the upcoming release
On Monday 14 December 2009 05:46:11 Chris Wilkinson wrote: There could have been any number of better ways to express the version number, but they chose to use one that can combine more than one decimal place into what looks to a lay person like a mistyped number... not clever. Well they chose major and minor version numbers delimited by a dot, which can and is easily extended to even finer granularity by just adding another group or two. It's certainly no perfect system, but it's been adopted in practically the whole computer industry, software and hardware. So FlightGear is in fairly good company there. The chances that someone would misunderstand this universally adopted scheme are quite small if you ask me. People seem to cope with it quite well, as they do with IPv4 addresses which are usually written as four groups of numbers seperated by the same dot: 123.45.67.089 And anyway: here in Europe (except for the UK and Ireland), we don't even use a dot as decimal separator. We use the comma while the dot is used for grouping thousands. And it's the same in many other parts of the world, for example South America. So what's wrong again with using the same system that just about everyone else uses? Stefan -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Version number for the upcoming release
I don't think anything wrong with the MAJOR.MINOR.PATCHLEVEL format, I think it's fairly obvious, and is widely used. I'm not a huge fan of rolling over into double digits though, unless you started with double digits to begin with. For example 1.09 to 1.10 is logical to me, but 1.9.1 to 1.10 is not, I would expect 1.9.1 to be the newer in this case. Perhaps it is time to go to 2.0 then, in hindsight osg should have probably been 2.0 being such a major change in direction. Being 2.0 can also give some leeway to excuse the bugsI mean hey, we're in the infancy of a new major number release...of course there are flaws. :D :D cheers! --Jacob -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL verification patch)
Durk wrote: On Sunday 13 December 2009 10:16:24 pm Stuart Buchanan wrote: A clear statement would a) provide a good reference point for any further discussion outside of the community, rather than various people making different comments. b) be visible enough to Google so that anyone doing cursory research would have more chance of coming across FG if investigating FPS. As someone who has in the past done professional work with FG, I'd be happy to draft a factual statement. Agreed. If you're willing to draft such a statement, I'm happy to help in proofreading, etc. etc. Also, I've been thinking of trying to publish a statement of similar content on some of the major websites: avsim.com or flightsim.com. I think one statement can easily be used for both purposes if written appropriately. I've included my draft below. I've purposefully sought not to address any moral or value arguments but stick to the facts for a number of reasons: a) There are a variety of opinions on this list and any statement should be something that all FG developers are happy with b) I want to aviod anything that could be considered slanderous or libelous. c) I think a mature approach will gain a lot more support from external readers as opposed to an emotional response. I'd appreciate feedback, even if it is only to agree with the wording of the statement, to ensure that we have buy-in for this. -Stuart FlightGear Flight Pro Sim Statement: As many people will be aware, there is a new flight simulator product that is being heavily marketed at the moment - Flight Pro Sim. As it is very heavily based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ. FlightGear is a open-source flight simulator that was started in 2006. It is released under the GNU General Public License v2, and as such, it is free to use, modify and develop with few restrictions. It has been developed with the collaboration of a huge number of individuals over the internet over the last 12 years. FlightGear can be downloaded for free from http:// www.flightgear.org. Flight Pro Sim is a commercial product very heavily based on FlightGear. Investigation by a number of the FlightGear developers has found no difference between this and the FlightGear v1.9.1 release other than a change of name. Flight Pro Sim is in no way endorsed or supported by the core FlightGear development team. Given the extreme similarities between Flight Pro Sim and FlightGear, we would recommend that prospective buyers download FlightGear for free and satisfy themselves that Flight Pro Sim provides worthwhile value for money before purchasing it. FAQ: Q: What is the difference between FlightGear and Flight Pro Sim? A: As far as we have been able to make out, the only difference between FlightGear v1.9.1 and Flight Pro Sim is a change in name throughout the software, and the fact that you have to pay for it. Q: Is it legal for the makers of Flight Pro Sim to simply re-brand FlightGear ? A: Yes. Under the GNU GPL v2 (http://www.gnu.org/licenses/gpl-2.0.html), this is legal, provided that they distribute the source code (or make it available). Q: Is is legal to sell a copy of FlightGear, whether re-branded or not ? A: Yes. Technically, the purchaser is paying for the distribution of the software, and it reasonable to charge a fee for this. In fact, those interested in receiving a DVD containing FlightGear may do so through the main FlightGear website, and directly contribute to the project (though they may want to wait for the upcoming release in the new year). Q: Has Flight Pro Sim paid any money to FlightGear for the rights to the program ? A: No. No such payment is required, as FlightGear is open-source software. Q: Is there any relationship between the makers of Flight Pro Sim and FlightGear? A: Not that we are aware of. As far as we are aware, the makers of Flight Pro Sim are not FlightGear developers. Q: Has Flight Pro Sim contributed to the FlightGear project at all ? A: There is no evidence that the makers of Flight Pro Sim have contributed to the FlightGear project, either through code or money. They did offer to provide money ($250) for a monthly competition, but this offer has not been taken up. Q: I have purchased Flight Pro Sim. Can I get a refund ? A: That is something you will have to take up with the makers of Flight Pro Sim. We understand they offer a 60 day money-back guarantee. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net
Re: [Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL verification patch)
On 14 Dec 2009, at 11:11, Stuart Buchanan wrote: I'd appreciate feedback, even if it is only to agree with the wording of the statement, to ensure that we have buy-in for this. FlightGear is a open-source flight simulator that was started in 2006. It is released under the GNU General Public License v2, and as such, it is free to use, modify and develop with few restrictions. It has been developed with the collaboration of a huge number of individuals over the internet over the last 12 years. FlightGear can be downloaded for free from http:// www.flightgear.org. Err, 2006 1996? ... 2006 + 12 != 2009 :) Aside from that, looks good to me, especially in terms of not being libellous towards FPS, and clarifying the GPL right-to-charge-for-distribution issue. Several people from outside FG have referred to 'freeware' in the MSFS sense, and obviously have no clue about this whole 'open-source' thing. Mind you, you could make yourself very tired explaining that point in the flight-simming world :D James -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Erik wrote Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? Erik No, nothing more needs doing atm in relation to the crash on reset, and the crash on exit bugs. Both were coding errors that Linux appears to swallow, while Windows did not using MSVC9. Sound seems OK here, but has not been subject to thorough testing. Vivian -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] AI == airport, facility, and environment services
On 12/13/2009 11:29 PM, Durk Talsma wrote: FWIW, as per previous agreement, I've started investigating how much effort it is going to cost to remove the ai-code altogether. There are a few places where the existing code depends on ATCDCL functions. Isolating these shouldn't be too hard. ATIS, as currently implemented, is in the ATCDCL directory. Having some sort of ATIS is important. I don't mind if the existing code goes away, so long as the feature doesn't go away. === As previously discussed, this is part of a bigger issue, namely Airport, Facility, and Environment Services (AFES). For example: -- If two different radios are tuned to the same frequency, we want them to hear exactly the same ATIS, exactly the same IDENT codes, exactly the same ATC chatter, et cetera. Synchronizing this is not too tricky for multiple radios in a given aircraft, but gets tricker for multiple aircraft in the MP environment. -- There are other Airport/Facility features, functions, and services that require consistency, such as the choice of active runway, the decision to turn on runway lighting (including pilot-controlled lighting), the decision to reverse a reversible ILS, et cetera. These decisions affect the ATIS, AI traffic, AI ATC chatter, et cetera. -- Of course we want AI traffic itself to be consistent across the MP environment. -- The same goes for clouds and weather. If there is a wisp of scud over the middle of the airport, all aircraft in the MP environment should see the same wisp of scud. The common thread here is that there is a lot of stuff that happens outside the aircraft. FGFS began life as an aircraft simulator. Some ideas (such as generating IDENT codes from inside navradio.cxx) that made sense in a single, simple aircraft don't make sense in a complex aircraft, let alone a multiplayer environment. I don't expect all this to get sorted all at once ... but it would be nice to have some sort of strategy so that every time this-or-that piece gets upgraded it moves us closer to the goal. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Version number for the upcoming release
Hi there, The chances of people in this mailing list misunderstanding that convention are low, because by and large we're advocates of free software which is predominantly released under such numbering schemes, but I feel confident I could take that convention around the engineering office I work in and confuse a whole lot of otherwise very intelligent people. The (un)washed masses are used to titles such as 'Office 2007', 'Word 2003', and dare I say it, 'Flight Simulator 2004'. Those names give some kind of meaning, whereas Flightgear 1.9.2 to a lay person (no matter how intelligent) probably would not mean a lot. FG to me is more developer-driven than user-driven, and I would also think devs make up a significant proportion of the user base. Devs would be more likely to be using cvs than stable 1.9.1 as their daily tester/flyer. So long as cvs keeps working the way it does I cannot see any problem with keeping the scheme intact for development, but simplifying the fg name a bit for major releases, since that only happens pretty much annually. How about 'Flightgear 2010' for the next stable release? Might spark a bit more user interest in the project by having a more human name for milestone releases... Just my $0.02 worth again... Regards, Chris Wilkinson, YBBN/BNE. From: Stefan Seifert n...@detonation.org To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Sent: Mon, 14 December, 2009 6:40:32 PM Subject: Re: [Flightgear-devel] Version number for the upcoming release On Monday 14 December 2009 05:46:11 Chris Wilkinson wrote: There could have been any number of better ways to express the version number, but they chose to use one that can combine more than one decimal place into what looks to a lay person like a mistyped number... not clever. Well they chose major and minor version numbers delimited by a dot, which can and is easily extended to even finer granularity by just adding another group or two. It's certainly no perfect system, but it's been adopted in practically the whole computer industry, software and hardware. So FlightGear is in fairly good company there. The chances that someone would misunderstand this universally adopted scheme are quite small if you ask me. People seem to cope with it quite well, as they do with IPv4 addresses which are usually written as four groups of numbers seperated by the same dot: 123.45.67.089 And anyway: here in Europe (except for the UK and Ireland), we don't even use a dot as decimal separator. We use the comma while the dot is used for grouping thousands. And it's the same in many other parts of the world, for example South America. So what's wrong again with using the same system that just about everyone else uses? Stefan -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel __ See what's on at the movies in your area. Find out now: http://au.movies.yahoo.com/session-times/-- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb627aa20 (LWP 30813)]
0x0865ece2 in findcell (hr=0xeb43550, key=
{num = nan(0x567891077bfa8), ref = {ptr = {obj = 0x1077bfa8,
str = 0x1077bfa8, vec = 0x1077bfa8, hash = 0x1077bfa8, code =
0x1077bfa8, func = 0x1077bfa8, ccode = 0x1077bfa8, ghost =
0x1077bfa8}, reftag = 2146789257}}, hash=4111002719) at
../../../simgear/nasal/hash.c:67
67 if(IS_NUM(a)) return a.num == b.num;
Current language: auto; currently c
(gdb) bt
#0 0x0865ece2 in findcell (hr=0xeb43550, key=
{num = nan(0x567891077bfa8), ref = {ptr = {obj = 0x1077bfa8,
str = 0x1077bfa8, vec = 0x1077bfa8, hash = 0x1077bfa8, code =
0x1077bfa8, func = 0x1077bfa8, ccode = 0x1077bfa8, ghost =
0x1077bfa8}, reftag = 2146789257}}, hash=4111002719) at
../../../simgear/nasal/hash.c:67
#1 0x0865f35d in naHash_get (hash=value optimized out, key=
{num = nan(0x567891077bfa8), ref = {ptr = {obj = 0x1077bfa8,
str = 0x1077bfa8, vec = 0x1077bfa8, hash = 0x1077bfa8, code =
0x1077bfa8, func = 0x1077bfa8, ccode = 0x1077bfa8, ghost =
0x1077bfa8}, reftag = 2146789257}}, out=0xbfdea690) at
../../../simgear/nasal/hash.c:130
#2 0x0865be74 in naInternSymbol (sym=
{num = nan(0x567891077bfa8), ref = {ptr = {obj = 0x1077bfa8,
str = 0x1077bfa8, vec = 0x1077bfa8, hash = 0x1077bfa8, code =
0x1077bfa8, func = 0x1077bfa8, ccode = 0x1077bfa8, ghost =
0x1077bfa8}, reftag = 2146789257}}) at
../../../simgear/nasal/codegen.c:74
#3 0x086586c9 in naNewContext () at ../../../simgear/nasal/code.c:190
#4 0x084c3bbe in FGNasalSys::init (this=0xeb30d50) at
../../../src/Scripting/NasalSys.cxx:650
#5 0x0808e3f0 in fgInitSubsystems () at ../../../src/Main/fg_init.cxx:1709
#6 0x0806d0f8 in fgIdleFunction () at ../../../src/Main/main.cxx:774
#7 0x080bbec2 in fgOSMainLoop () at ../../../src/Main/fg_os_osgviewer.cxx:172
#8 0x0806d8d5 in fgMainInit (argc=10, argv=0xbfdeab04) at
../../../src/Main/main.cxx:920
#9 0x0806baef in main (argc=10, argv=0xbfdeab04) at
../../../src/Main/bootstrap.cxx:229
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Version number for the upcoming release
What if we start naming releases in addition to the normal version scheme. FlightGear 2.x.x name, name could be some continued variation on a theme or something. I think that would be a nice middle ground, we keep a meaningful versioning scheme, and also get a catchy name for everyone. I've worked on projects that have done this and it works well I think, the name usually changed for every meaningful release1.1, 1.2, .1.3...etc. cheers --Jacob -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] navaids update
Hi, I've got a question about the navaids, particularly nav.dat. Is nav.dat supposed to be updated from robin X-plane database? The french missing navaids I submited to robin ( approach locators ) are included in recent nav.dat from X-plane, and I was waiting them to come in Flightgear, but apparently we are using the version just before. here's a diff toward our current nav.dat with the missing french locators, if you find some interest in using french airports :) . jano --- fg_nav.dat 2009-12-14 11:22:24.0 +0100 +++ jjano_nav.dat 2009-12-14 11:22:02.0 +0100 @@ -1,6 +1,104 @@ I 810 Version - DAFIF data cycle 2007.09, build 20070106, metadata NavXP810. Copyright © 2007, Robin A. Peel (ro...@xsquawkbox.net). This data is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program (AptNavGNULicence.txt); if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. This product was developed using DAFIF (the Defense Aeronautical Flight Information File), a product of the US National Imagery and Mapping Agency (NIMA). NIMA requires the following warranty statements: (A) Under 10 U.S.C. 456, no civil action may be brought against the United States on the basis of the content of a navigational aid prepared or disseminated by either the former Defense Mapping Agency (DMA) or the National Imagery and Mapping Agency (NIMA). (B) The DAFIF product is provided as is, and no warranty, express or implied, including, but not limited to the implied warranties of merchantability and fitness for particular purpose or arising by statute or otherwise in law or from a course of dealing or usage in trade, is made by NIMA as to the accuracy and functioning of the product. ©: Neither NIMA nor its personnel will be liable for any claims, losses, or damages arising from or connected with the use of this product. The user agrees to hold harmless the United States National Imagery and Mapping Agency. The user's sole and exclusive remedy is to stop using the DAFIF product. +2 43.9122 002.0644528 323 250.0 AB Albi le Sequestre NDB +2 49.9762 002.80941666361 321 1500.0 ABY Albert Bray NDB +2 43.26527778 005.58638000590 366 250.0 ADC Le Castellet NDB +2 44.1505 000.6738156 400 250.0 AG Agen la Garenne NDB +2 45.7105 000.4269397 404 250.0 AGO Angouleme Brie Champniers NDB +2 44.9558 002.3680 2310 343 250.0 AR Aurillac NDB +2 47.5772 -000.1513305 292 250.0 AS Angers Marce NDB +2 45.8616 006.0205 2205 384 250.0 AT Annecy Meythet NDB +2 44.4422 004.3619676 427 250.0 AUB Aubenas Ardeche Meridionale NDB +2 46.88167000 002.92888955679 306 250.0 AV Avord NDB +2 47.9202 003.5022505 417 250.0 AX Auxerre Branches NDB +2 47.6108 002.7827528 405 250.0 BIC Briare Chatillon NDB +2 45.52027800 004.29889000 1371 299 250.0 BO Saint Etienne Boutheon NDB +2 46.2038 005.2888869 423 250.0 BOR Bourg Ceyzeriat NDB +2 42.4258 009.5375 33 369 250.0 BP Bastia Poretta NDB +2 45.6158 004.99278000 1076 388 250.0 BR Lyons Bron NDB +2 47.0175 002.2816509 375 250.0 BRG Bourges NDB +2 44.3652 -001.1288 92 358 250.0 BRS Biscarrosse Parentis NDB +2 47.2669 006.2025 1348 370 250.0 BSV Besancon la Veze +2 49.4916 002.0294377 391 250.0 BV Beauvais Tille NDB +2 44.5669 003.4691 4062 393 250.0 BX Mende Brenoux NDB +2 46.7216 004.8430656 391 250.0 CC Chalon Champforgeuil NDB +2 45.8044 003.3616 1066 367 250.0 CF Clermond Ferrand Auvergne NDB +2 49.0052 002.7402352 370 250.0 CGZ Paris Charles de Gaulle NDB +2 45.5925 005.88361100840 346 250.0 CH Chambery Aix les Bains NDB +2 48.0077 003.6961545 353 250.0 CHY Chailley NDB +2 44.38527778 001.4155951 348 250.0 CL Cahors Lalbenque NDB +2 43.2225 002.2077489 345 250.0 CS Carcassonne Salvaza NDB +2 43.5228 007.04527778 98 385 250.0 CSC Cannes Mandelieu NDB +2 41.7952 008.7241295 387 250.0 CT Ajaccio Campo dell'Oro NDB +2 48.7591 004.3188604 347
Re: [Flightgear-devel] navaids update
Salut Jean, jean pellotier wrote: Is nav.dat supposed to be updated from robin X-plane database? If nobody else is going to do that, I'll be updating the file from Robin's most current package during our pre-release phase (however this is going to be defined ). here's a diff toward our current nav.dat with the missing french locators, if you find some interest in using french airports :) . I do - been flying there several times in real life and mostly had to do visual navigation because no navaids (neither VOR's nor anything else) had been installed on my routes :-) Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
On Mon, Dec 14, 2009 at 1:11 PM, Jacob Burbach jmburb...@gmail.com wrote:
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb627aa20 (LWP 30813)]
0x0865ece2 in findcell (hr=0xeb43550, key=
{num = nan(0x567891077bfa8), ref = {ptr = {obj = 0x1077bfa8,
str = 0x1077bfa8, vec = 0x1077bfa8, hash = 0x1077bfa8, code =
0x1077bfa8, func = 0x1077bfa8, ccode = 0x1077bfa8, ghost =
0x1077bfa8}, reftag = 2146789257}}, hash=4111002719) at
../../../simgear/nasal/hash.c:67
67 if(IS_NUM(a)) return a.num == b.num;
I believe this may be a compiler bug. Can you provide a disassembly
around that line? 50 instructions in each direction should be fine I
think.
Nasal stores values in a tricky union and (on 32 bit systems) it uses
the reftag to differentiate between numbers and pointers.
The IS_NUM check is like this:
#define NASAL_REFTAG 0x7ff56789 // == 2,146,789,257 decimal
#define IS_REF(r) ((r).ref.reftag == NASAL_REFTAG)
#define IS_NUM(r) (!IS_REF(r))
Your gdb output shows that reftag is in fact equal to NASAL_REFTAG so
IS_NUM should be false and thus the comparison that raises the FPE
should not be executed. I suspect gdb generated code that at least
loads one of the values into the FPU triggering the FPE.
--
Csaba/Jester
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL
Hi Stuart, just one minor nit (aside the one wrt. the date of birth), there's a useless blank here: be downloaded for free from http:// www.flightgear.org. ^^^ Well done ! Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL verification patch)
FlightGear is a open-source flight simulator that was started in 2006. 1996. :) g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Version number for the upcoming release
On Mon, Dec 14, 2009 at 10:09 AM, Jacob Burbach jmburb...@gmail.com wrote: I'm not a huge fan of rolling over into double digits though, unless you started with double digits to begin with. For example 1.09 to 1.10 is logical to me, but 1.9.1 to 1.10 is not, I would expect 1.9.1 to be the newer in this case. Lexical sorting too, which can be a nuisance in version checks or directory listings. -- Csaba/Jester -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
Not sure what you meant about gdb generating code to cause it, I get the same error when run outside of gdb. Assembly of the function below, if you need something else let me know. 0x0865ec50 findcell+0:push %ebp 0x0865ec51 findcell+1:mov%esp,%ebp 0x0865ec53 findcell+3:push %edi 0x0865ec54 findcell+4:push %esi 0x0865ec55 findcell+5:push %ebx 0x0865ec56 findcell+6:xor%ebx,%ebx 0x0865ec58 findcell+8:sub$0x5c,%esp 0x0865ec5b findcell+11: mov0x8(%ebp),%edi 0x0865ec5e findcell+14: mov%edx,-0x38(%ebp) 0x0865ec61 findcell+17: mov0x4(%eax),%edx 0x0865ec64 findcell+20: mov%eax,-0x54(%ebp) 0x0865ec67 findcell+23: mov$0x1,%eax 0x0865ec6c findcell+28: mov%ecx,-0x34(%ebp) 0x0865ec6f findcell+31: movl $0x0,-0x4c(%ebp) 0x0865ec76 findcell+38: lea0x1(%edx),%ecx 0x0865ec79 findcell+41: shl%cl,%eax 0x0865ec7b findcell+43: sub$0x1,%eax 0x0865ec7e findcell+46: mov%eax,-0x28(%ebp) 0x0865ec81 findcell+49: mov-0x28(%ebp),%ecx 0x0865ec84 findcell+52: lea0x1(%edi,%edi,1),%eax 0x0865ec88 findcell+56: and%ecx,%eax 0x0865ec8a findcell+58: test %edx,%edx 0x0865ec8c findcell+60: mov%eax,-0x24(%ebp) 0x0865ec8f findcell+63: je 0x865eca6 findcell+86 0x0865ec91 findcell+65: mov$0x20,%ecx 0x0865ec96 findcell+70: mov%edi,%ebx 0x0865ec98 findcell+72: sub%edx,%ecx 0x0865ec9a findcell+74: shr%cl,%ebx 0x0865ec9c findcell+76: lea0x0(,%ebx,4),%esi 0x0865eca3 findcell+83: mov%esi,-0x4c(%ebp) 0x0865eca6 findcell+86: mov-0x54(%ebp),%eax 0x0865eca9 findcell+89: mov%edx,%ecx 0x0865ecab findcell+91: add$0xc,%eax 0x0865ecae findcell+94: and$0x7,%eax 0x0865ecb1 findcell+97: lea0x7(%eax),%edi 0x0865ecb4 findcell+100: and$0x8,%edi 0x0865ecb7 findcell+103: sub%eax,%edi 0x0865ecb9 findcell+105: mov$0x10,%eax 0x0865ecbe findcell+110: shl%cl,%eax 0x0865ecc0 findcell+112: lea0xc(%edi,%eax,1),%eax 0x0865ecc4 findcell+116: mov%eax,-0x2c(%ebp) 0x0865ecc7 findcell+119: mov-0x54(%ebp),%eax 0x0865ecca findcell+122: mov-0x2c(%ebp),%esi 0x0865eccd findcell+125: add-0x4c(%ebp),%eax 0x0865ecd0 findcell+128: mov%edi,-0x30(%ebp) 0x0865ecd3 findcell+131: mov(%eax,%esi,1),%eax 0x0865ecd6 findcell+134: cmp$0x,%eax 0x0865ecd9 findcell+137: je 0x865edb8 findcell+360 0x0865ecdf findcell+143: fldl -0x38(%ebp) 0x0865ece2 findcell+146: fstpl -0x48(%ebp) 0x0865ece5 findcell+149: jmp0x865ed21 findcell+209 0x0865ece7 findcell+151: nop 0x0865ece8 findcell+152: fldl -0x20(%ebp) 0x0865eceb findcell+155: fldl -0x48(%ebp) 0x0865ecee findcell+158: fucompp 0x0865ecf0 findcell+160: fnstsw %ax 0x0865ecf2 findcell+162: sahf 0x0865ecf3 findcell+163: sete %al 0x0865ecf6 findcell+166: setnp %dl 0x0865ecf9 findcell+169: and%edx,%eax 0x0865ecfb findcell+171: movzbl %al,%eax 0x0865ecfe findcell+174: test %eax,%eax 0x0865ed00 findcell+176: jne0x865edb8 findcell+360 0x0865ed06 findcell+182: mov-0x2c(%ebp),%edx 0x0865ed09 findcell+185: add-0x24(%ebp),%ebx 0x0865ed0c findcell+188: mov-0x54(%ebp),%ecx 0x0865ed0f findcell+191: and-0x28(%ebp),%ebx 0x0865ed12 findcell+194: lea(%edx,%ebx,4),%eax 0x0865ed15 findcell+197: mov(%ecx,%eax,1),%eax 0x0865ed18 findcell+200: cmp$0x,%eax 0x0865ed1b findcell+203: je 0x865edb8 findcell+360 0x0865ed21 findcell+209: cmp$0xfffe,%eax 0x0865ed24 findcell+212: je 0x865ed06 findcell+182 0x0865ed26 findcell+214: mov-0x30(%ebp),%ecx 0x0865ed29 findcell+217: shl$0x4,%eax 0x0865ed2c findcell+220: add-0x54(%ebp),%eax 0x0865ed2f findcell+223: cmpl $0x7ff56789,-0x34(%ebp) 0x0865ed36 findcell+230: mov0xc(%ecx,%eax,1),%edx 0x0865ed3a findcell+234: mov0x10(%ecx,%eax,1),%ecx 0x0865ed3e findcell+238: mov%edx,-0x20(%ebp) 0x0865ed41 findcell+241: mov%ecx,-0x1c(%ebp) 0x0865ed44 findcell+244: jne0x865ece8 findcell+152 0x0865ed46 findcell+246: mov-0x20(%ebp),%eax 0x0865ed49 findcell+249: cmp%eax,-0x38(%ebp) 0x0865ed4c findcell+252: je 0x865edb8 findcell+360 0x0865ed4e findcell+254: mov-0x38(%ebp),%edx 0x0865ed51 findcell+257: mov-0x34(%ebp),%ecx 0x0865ed54 findcell+260: mov%edx,(%esp) 0x0865ed57 findcell+263: mov%ecx,0x4(%esp) 0x0865ed5b findcell+267: call 0x8665d60 naStr_len 0x0865ed60 findcell+272: mov-0x20(%ebp),%esi 0x0865ed63 findcell+275: mov-0x1c(%ebp),%edi 0x0865ed66 findcell+278: mov%esi,(%esp) 0x0865ed69 findcell+281: mov%edi,0x4(%esp)
Re: [Flightgear-devel] GPS find nearest.
Well, since this was a GPS-related thread, I decided to post this here instead of creating another thread :-) The zkv500's Turnpoint screen works properly now. However, the navigation display won't show the distance to the waypoint. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
On Mon, Dec 14, 2009 at 3:25 PM, Jacob Burbach jmburb...@gmail.com wrote:
Not sure what you meant about gdb generating code to cause it, I get
the same error when run outside of gdb. Assembly of the function
below, if you need something else let me know.
I meant gcc, sorry :)
Thanks for the listing. Looks like the number is loaded by the code
before the IS_NUM check, but I suspect it is for passing to the equal
function (which got inlined - confusing, eh?). If it were c++ code we
could change it to a const reference ... as it is, I think we'll have
to try the const pointer route as per attached patch :(
--
Csaba/Jester
diff --git a/simgear/nasal/hash.c b/simgear/nasal/hash.c
index 1efe8fb..0aebc15 100644
--- a/simgear/nasal/hash.c
+++ b/simgear/nasal/hash.c
@@ -62,12 +62,12 @@ static unsigned int refhash(naRef key)
}
}
-static int equal(naRef a, naRef b)
+static int equal(const naRef* a, const naRef* b)
{
-if(IS_NUM(a)) return a.num == b.num;
-if(PTR(a).obj == PTR(b).obj) return 1;
-if(naStr_len(a) != naStr_len(b)) return 0;
-return memcmp(naStr_data(a), naStr_data(b), naStr_len(a)) == 0;
+if(IS_NUM(*a)) return a-num == b-num;
+if(PTR(*a).obj == PTR(*b).obj) return 1;
+if(naStr_len(*a) != naStr_len(*b)) return 0;
+return memcmp(naStr_data(*a), naStr_data(*b), naStr_len(*a)) == 0;
}
/* Returns the index of a cell that either contains a matching key, or
@@ -76,7 +76,7 @@ static int findcell(struct HashRec *hr, naRef key, unsigned int hash)
{
int i, mask = POW2(hr-lgsz+1)-1, step = (2*hash+1) mask;
for(i=HBITS(hr,hash); TAB(hr)[i] != ENT_EMPTY; i=(i+step)mask)
-if(TAB(hr)[i] != ENT_DELETED equal(key, ENTS(hr)[TAB(hr)[i]].key))
+if(TAB(hr)[i] != ENT_DELETED equal(key, ENTS(hr)[TAB(hr)[i]].key))
break;
return i;
}
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Version number for the upcoming release
Hi, On Dec 14, 2009, at 7:18 AM, James Turner wrote: One observation - the intention, at least mine and Tim's, is to move to quarterly releases, so I have no intention of 'finishing' the route manager for a particular release. (Regular release cycles take the pressure of rushing to complete a feature) Stable features will be integrated onto the 'next' branch, when they're complete (or a functionally useful subset is complete). The shaders and sound changes both fall into this category, while the route manager work is certainly not in that category yet. I vote to both quarterly release and separating stable branch from development branch. My opinion about next version number is 1.10.0 since the current FG doesn't reach the 2.0 criteria (We stil miss shadows). I would accept 1.19.0 if we agree that our effort in this year worth 10 times of minor updates. Anyway, we must not go for 2.0 unless we change the 2.0 criteria. Tat p.s. Though 1.10.0 can be confusing (or using dots is confusing), you can get used to it when you know how the versions numbers are compared. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
I applied your hash patch, but no deuce.
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb62cba20 (LWP 25297)]
0x0865f79c in findcell (hr=0x107b5490, key=
{num = nan(0x56789123dabd8), ref = {ptr = {obj = 0x123dabd8,
str = 0x123dabd8, vec = 0x123dabd8, hash = 0x123dabd8, code =
0x123dabd8, func = 0x123dabd8, ccode = 0x123dabd8, ghost =
0x123dabd8}, reftag = 2146789257}}, hash=4111002719) at
../../../simgear/nasal/hash.c:67
67 if(IS_NUM(*a)) return a-num == b-num;
Current language: auto; currently c
(gdb) bt
#0 0x0865f79c in findcell (hr=0x107b5490, key=
{num = nan(0x56789123dabd8), ref = {ptr = {obj = 0x123dabd8,
str = 0x123dabd8, vec = 0x123dabd8, hash = 0x123dabd8, code =
0x123dabd8, func = 0x123dabd8, ccode = 0x123dabd8, ghost =
0x123dabd8}, reftag = 2146789257}}, hash=4111002719) at
../../../simgear/nasal/hash.c:67
#1 0x0865fe0d in naHash_get (hash=value optimized out, key=
{num = nan(0x56789123dabd8), ref = {ptr = {obj = 0x123dabd8,
str = 0x123dabd8, vec = 0x123dabd8, hash = 0x123dabd8, code =
0x123dabd8, func = 0x123dabd8, ccode = 0x123dabd8, ghost =
0x123dabd8}, reftag = 2146789257}}, out=0xbf83b0e0) at
../../../simgear/nasal/hash.c:130
#2 0x0865c934 in naInternSymbol (sym=
{num = nan(0x56789123dabd8), ref = {ptr = {obj = 0x123dabd8,
str = 0x123dabd8, vec = 0x123dabd8, hash = 0x123dabd8, code =
0x123dabd8, func = 0x123dabd8, ccode = 0x123dabd8, ghost =
0x123dabd8}, reftag = 2146789257}}) at
../../../simgear/nasal/codegen.c:74
#3 0x08659189 in naNewContext () at ../../../simgear/nasal/code.c:190
#4 0x084c469e in FGNasalSys::init (this=0x1079e578) at
../../../src/Scripting/NasalSys.cxx:650
#5 0x0808e3f0 in fgInitSubsystems () at ../../../src/Main/fg_init.cxx:1709
#6 0x0806d0f8 in fgIdleFunction () at ../../../src/Main/main.cxx:774
#7 0x080bbf82 in fgOSMainLoop () at ../../../src/Main/fg_os_osgviewer.cxx:172
#8 0x0806d8d5 in fgMainInit (argc=10, argv=0xbf83b554) at
../../../src/Main/main.cxx:920
#9 0x0806baef in main (argc=10, argv=0xbf83b554) at
../../../src/Main/bootstrap.cxx:229
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
On Mon, Dec 14, 2009 at 4:37 PM, Jacob Burbach jmburb...@gmail.com wrote: I applied your hash patch, but no deuce. Then I have no idea why the code is loading the value. Got a new asm listing? :) -- Csaba/Jester -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
Dump of assembler code for function findcell: 0x0865f710 findcell+0:push %ebp 0x0865f711 findcell+1:mov%esp,%ebp 0x0865f713 findcell+3:push %edi 0x0865f714 findcell+4:xor%edi,%edi 0x0865f716 findcell+6:push %esi 0x0865f717 findcell+7:push %ebx 0x0865f718 findcell+8:xor%ebx,%ebx 0x0865f71a findcell+10: sub$0x4c,%esp 0x0865f71d findcell+13: mov0x4(%eax),%esi 0x0865f720 findcell+16: mov%eax,-0x38(%ebp) 0x0865f723 findcell+19: mov$0x1,%eax 0x0865f728 findcell+24: mov%ecx,-0x3c(%ebp) 0x0865f72b findcell+27: mov%edx,-0x40(%ebp) 0x0865f72e findcell+30: mov0x8(%ebp),%edx 0x0865f731 findcell+33: lea0x1(%esi),%ecx 0x0865f734 findcell+36: shl%cl,%eax 0x0865f736 findcell+38: sub$0x1,%eax 0x0865f739 findcell+41: mov%eax,-0x30(%ebp) 0x0865f73c findcell+44: mov-0x30(%ebp),%ecx 0x0865f73f findcell+47: lea0x1(%edx,%edx,1),%eax 0x0865f743 findcell+51: and%ecx,%eax 0x0865f745 findcell+53: test %esi,%esi 0x0865f747 findcell+55: mov%eax,-0x2c(%ebp) 0x0865f74a findcell+58: je 0x865f75e findcell+78 0x0865f74c findcell+60: mov$0x20,%ecx 0x0865f751 findcell+65: mov%edx,%ebx 0x0865f753 findcell+67: sub%esi,%ecx 0x0865f755 findcell+69: shr%cl,%ebx 0x0865f757 findcell+71: lea0x0(,%ebx,4),%edi 0x0865f75e findcell+78: mov-0x38(%ebp),%eax 0x0865f761 findcell+81: mov%esi,%ecx 0x0865f763 findcell+83: add$0xc,%eax 0x0865f766 findcell+86: and$0x7,%eax 0x0865f769 findcell+89: lea0x7(%eax),%edx 0x0865f76c findcell+92: and$0x8,%edx 0x0865f76f findcell+95: sub%eax,%edx 0x0865f771 findcell+97: mov$0x10,%eax 0x0865f776 findcell+102: shl%cl,%eax 0x0865f778 findcell+104: lea0xc(%edx,%eax,1),%eax 0x0865f77c findcell+108: mov%eax,-0x34(%ebp) 0x0865f77f findcell+111: mov-0x38(%ebp),%eax 0x0865f782 findcell+114: mov-0x34(%ebp),%ecx 0x0865f785 findcell+117: add%edi,%eax 0x0865f787 findcell+119: mov(%eax,%ecx,1),%eax 0x0865f78a findcell+122: cmp$0x,%eax 0x0865f78d findcell+125: je 0x865f870 findcell+352 0x0865f793 findcell+131: mov-0x3c(%ebp),%ecx 0x0865f796 findcell+134: add$0xc,%edx 0x0865f799 findcell+137: fldl -0x40(%ebp) 0x0865f79c findcell+140: fstpl -0x20(%ebp) 0x0865f79f findcell+143: mov%edx,-0x44(%ebp) 0x0865f7a2 findcell+146: mov%ecx,-0x14(%ebp) 0x0865f7a5 findcell+149: mov-0x40(%ebp),%ecx 0x0865f7a8 findcell+152: mov%ecx,-0x24(%ebp) 0x0865f7ab findcell+155: jmp0x865f7e8 findcell+216 0x0865f7ad findcell+157: lea0x0(%esi),%esi 0x0865f7b0 findcell+160: fldl (%esi) 0x0865f7b2 findcell+162: fldl -0x20(%ebp) 0x0865f7b5 findcell+165: fucompp 0x0865f7b7 findcell+167: fnstsw %ax 0x0865f7b9 findcell+169: sahf 0x0865f7ba findcell+170: sete %al 0x0865f7bd findcell+173: setnp %dl 0x0865f7c0 findcell+176: and%edx,%eax 0x0865f7c2 findcell+178: movzbl %al,%eax 0x0865f7c5 findcell+181: test %eax,%eax 0x0865f7c7 findcell+183: jne0x865f870 findcell+352 0x0865f7cd findcell+189: mov-0x34(%ebp),%ecx 0x0865f7d0 findcell+192: add-0x2c(%ebp),%ebx 0x0865f7d3 findcell+195: mov-0x38(%ebp),%edx 0x0865f7d6 findcell+198: and-0x30(%ebp),%ebx 0x0865f7d9 findcell+201: lea(%ecx,%ebx,4),%eax 0x0865f7dc findcell+204: mov(%edx,%eax,1),%eax 0x0865f7df findcell+207: cmp$0x,%eax 0x0865f7e2 findcell+210: je 0x865f870 findcell+352 0x0865f7e8 findcell+216: cmp$0xfffe,%eax 0x0865f7eb findcell+219: je 0x865f7cd findcell+189 0x0865f7ed findcell+221: mov-0x38(%ebp),%esi 0x0865f7f0 findcell+224: shl$0x4,%eax 0x0865f7f3 findcell+227: add-0x44(%ebp),%eax 0x0865f7f6 findcell+230: add%eax,%esi 0x0865f7f8 findcell+232: cmpl $0x7ff56789,-0x14(%ebp) 0x0865f7ff findcell+239: jne0x865f7b0 findcell+160 0x0865f801 findcell+241: mov-0x24(%ebp),%eax 0x0865f804 findcell+244: cmp(%esi),%eax 0x0865f806 findcell+246: je 0x865f870 findcell+352 0x0865f808 findcell+248: mov-0x40(%ebp),%edx 0x0865f80b findcell+251: mov-0x3c(%ebp),%ecx 0x0865f80e findcell+254: mov%edx,(%esp) 0x0865f811 findcell+257: mov%ecx,0x4(%esp) 0x0865f815 findcell+261: call 0x8666810 naStr_len 0x0865f81a findcell+266: mov0x4(%esi),%edi 0x0865f81d findcell+269: mov(%esi),%esi 0x0865f81f findcell+271: mov%edi,0x4(%esp) 0x0865f823 findcell+275: mov%esi,(%esp) 0x0865f826 findcell+278: mov%eax,-0x28(%ebp) 0x0865f829 findcell+281: call 0x8666810 naStr_len 0x0865f82e
Re: [Flightgear-devel] GPS find nearest.
Thank you pointing this, I haven't seen it. Here is the patch to correct the mistake. Thanks in advance to commit it. best regards seb Victhor Foster wrote : Well, since this was a GPS-related thread, I decided to post this here instead of creating another thread :-) The zkv500's Turnpoint screen works properly now. However, the navigation display won't show the distance to the waypoint. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Index: Aircraft/Instruments-3d/zkv500/MainScreens.nas === RCS file: /var/cvs/FlightGear-0.9/data/Aircraft/Instruments-3d/zkv500/MainScreens.nas,v retrieving revision 1.9 diff -r1.9 MainScreens.nas 223c223 dist * dist_conv[0][dist_unit], --- me.waypoint.getNode(distance-nm,1).getValue() * dist_conv[0][dist_unit], 227c227 me.waypoint.getNode(course-error-nm).getValue() * dist_conv[0][dist_unit], --- dist * dist_conv[0][dist_unit], -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] simgear version number now a string
The recent change which makes a string from the simgear version breaks FG configure. I don't think introducing an incompatible change to the version macro is a good idea. Erik, can you explain why you made the change? I am aware that FG's own version is a string, so I am guessing that might have been the reason. -- Cheers, Csaba/Jester -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
It is strange that I am the only one reporting this fault, but it is still there. On both my Vista laptop and the XP box it fails if run from Visual C++ 2008 with Debug - Start Debugging. On the Vista laptop it also fails if I run the release build from fgrun , but only if sound is enabled. This case is OK on the XP box. The only compilation flag that I have added to the CVS VC90 configuration is NOMINMAX. VC90 build is very out of date and quite few new files and libraries have to be added. As of today version.h is not found. I have hand built one from version.h.in, with the line #define SIMGEAR_VERSION 1.99.4. Alan -- From: Erik Hofman e...@ehofman.com Sent: Monday, December 14, 2009 9:09 AM To: FlightGear developers discussions flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] Flight Gear on Windows Alan Teeder wrote: I am no longer seeing the first two bugs which seem to have been sorted out this week, but do have a similar problem with sound. See my thread with Eric. Is this something I need to look after or is it a matter of finding the proper compile options? Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
On Fri, 11 Dec 2009 23:37:44 +0100, jean wrote in message 4b22c9b8.6050...@wanadoo.fr: Vivian Meazza a écrit : Geoff, I agree with all you have said, but would add the following: The reset bug has been sorted. The crash-on-exit bug has probably been sorted, but I haven’t had time to test it yet. I don’t see the red/orange effect you report. got something like that too on linux, but guess what? with an ati card it's related to shaders, as once i remove the shader effects, scenary is ok. depending on sun and orientation, scenery get sudenly darker, or green, or blue affecting differently far and close field. some screens: http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-005.png http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-006.png http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-024.png and an other (ati?) bug: if i have a look on the airport from obove vertically, then texture become a mess, and all is fine once shaders removed: http://janodesbois.free.fr/fg_screens/decembre09/fgfs-screen-027.png ps: and to answer to the question why have you taken an ati card? that was the only way to flight with shaders on an agp card, and so my PC can last some years more :) . using fglrx, on a debian sid with an ati radeonhd4650. ..try X.org's radeon and X.org/Novell's radeonHD too, and show us so we can compare them. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...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. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] simgear version number now a string
Csaba Halász wrote: The recent change which makes a string from the simgear version breaks FG configure. I don't think introducing an incompatible change to the version macro is a good idea. Erik, can you explain why you made the change? I am aware that FG's own version is a string, so I am guessing that might have been the reason. It was part of a patch to provide better version information when running fgfs --version I did check if it was breaking compilation of simgear. I must admit I didn't test running configure. Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] simgear version number now a string
On 12/14/2009 10:30 AM, Erik Hofman wrote: Csaba Halász wrote: The recent change which makes a string from the simgear version breaks FG configure. I don't think introducing an incompatible change to the version macro is a good idea. Erik, can you explain why you made the change? I am aware that FG's own version is a string, so I am guessing that might have been the reason. It was part of a patch to provide better version information when running fgfs --version I did check if it was breaking compilation of simgear. I must admit I didn't test running configure. I tested it. It works fine chez moi. make clean ; ./configure --lots-of-options ; make Can somebody say in more detail what the problem is? I can't even find anywhere it is used within simgear. The rationale for quoting it (and the corresponding FG version string) is simple: It is hard to do anything with the version identifier unless it is treated as a string. It's not really a version number since it is not a number. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] simgear version number now a string
On Mon, Dec 14, 2009 at 6:54 PM, John Denker j...@av8n.com wrote: I tested it. It works fine chez moi. make clean ; ./configure --lots-of-options ; make Can somebody say in more detail what the problem is? I can't even find anywhere it is used within simgear. It is used in the *flightgear* configure.ac script. FG can't find simgear anymore because it can't parse the version. Easy to fix there but maybe other projects (such as terragear or fgrun) also depend on it. It's not really a version number since it is not a number. It's a NaN! Sorry :) -- Csaba/Jester -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] simgear version number now a string
It's a NaN! Sorry :) So now we know where all these NaN errors have been coming from! ;-) -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] simgear version number now a string
On 12/14/2009 11:08 AM, Csaba Halász wrote: It is used in the *flightgear* configure.ac script. FG can't find simgear anymore because it can't parse the version. Easy to fix there but maybe other projects (such as terragear or fgrun) also depend on it. A fully-compatible fix is attached below. In the interests of consistency, would it make sense to define FLIGHTGEAR_VERSION_STRING with quotes, and change FLIGHTGEAR_VERSION to have no quotes? Now is the time to change it if we're going to change it. It's not really a version number since it is not a number. It's a NaN! Sorry :) Ew. = commit 9ea41430a4e12767c67fdd2e2799b47670c1cba0 Author: John Denker j...@av8n.com Date: Mon Dec 14 11:26:05 2009 -0700 Add SIMGEAR_VERSION_STRING (emphasis on STRING). diff --git a/simgear/version.h.in b/simgear/version.h.in index 368a4a9..dcbcf5d 100644 --- a/simgear/version.h.in +++ b/simgear/version.h.in @@ -27,6 +27,7 @@ #define SIMGEAR_VERSION @VERSION@ +#define SIMGEAR_VERSION_STRING @VERSION@ #endif // _SIMGEAR_VERSION_H commit 4423a4c867e6d87a3c5a2edff45a00788468ebd3 Author: John Denker j...@av8n.com Date: Mon Dec 14 11:27:37 2009 -0700 Use SIMGEAR_VERSION_STRING (emphasis on STRING) diff --git a/src/Main/options.cxx b/src/Main/options.cxx index c04053b..985b36a 100644 --- a/src/Main/options.cxx +++ b/src/Main/options.cxx @@ -1212,7 +1212,7 @@ fgOptVersion( const char *arg ) cerr *it; } cerr endl; -cerr SimGear version: SIMGEAR_VERSION endl; +cerr SimGear version: SIMGEAR_VERSION_STRING endl; cerr PLIB version: PLIB_VERSION endl; cerr OSG version: FG_OSG_VERSION endl; return FG_OPTIONS_EXIT; -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] simgear version number now a string
Here's another way of getting the job done.
This is tidier in the sense that it leaves simgear unchanged.
commit cd0af70c868210f46584a1e5e922364b9f2e63ce
Author: John Denker j...@av8n.com
Date: Mon Dec 14 11:50:53 2009 -0700
Print SIMGEAR_VERSION as a string, even though it doesn't come with quote
marks.
diff --git a/src/Main/options.cxx b/src/Main/options.cxx
index c04053b..a57622c 100644
--- a/src/Main/options.cxx
+++ b/src/Main/options.cxx
@@ -1199,6 +1199,8 @@ fgOptParking( const char *arg )
static int
fgOptVersion( const char *arg )
{
+#define _Quote(x) #x
+#define Quote(x) _Quote(x)
cerr FlightGear version: VERSION endl;
cerr FG_ROOT= globals-get_fg_root() endl;
cerr FG_HOME= fgGetString(/sim/fg-home) endl;
@@ -1212,10 +1214,12 @@ fgOptVersion( const char *arg )
cerr *it;
}
cerr endl;
-cerr SimGear version: SIMGEAR_VERSION endl;
+cerr SimGear version: Quote(SIMGEAR_VERSION) endl;
cerr PLIB version: PLIB_VERSION endl;
cerr OSG version: FG_OSG_VERSION endl;
return FG_OPTIONS_EXIT;
+#undef Quote
+#undef _Quote
}
static int
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Gear on Windows
Alan Teeder wrote: VC90 build is very out of date and quite few new files and libraries have to be added. Honestly try to stay away from the build files, mainly because I have no way to test them. I might completely break building for MSVC and note even know it (typo's are made easily). If anyone has proper build files I would be happy to commit them. As of today version.h is not found. I have hand built one from version.h.in, with the line #define SIMGEAR_VERSION 1.99.4. That should be fixed again, sorry for the fuzz. Erik -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement
I hate to be the one to shout about bad English, but FlightGear is either 'Free', or you can download it 'for nothing'. Please don't say 'for free'. Cheers, Vic -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL verification patch)
On Monday 14 December 2009 12:11:15 pm Stuart Buchanan wrote: I think one statement can easily be used for both purposes if written appropriately. Agreed. That's actually what I was thinking of. I'd appreciate feedback, even if it is only to agree with the wording of the statement, to ensure that we have buy-in for this. In addition to the points brought up by others, I have one suggestion for a FAQ item: From the discussion on the flight simulator network, it struck me that people (especially those with a freeware background) don't necessarily understand why we are allowing third parties to make money off of FlightGear. I guess this is already covered by the is it legal to resell FAQ item, but maybe it's worth to specifically address this question from a different perspective (i.e. that of somebody coming from a freeware background)? Cheers, Durk -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement
Thanks to everyone who's commented so far: Vic Marriott wrote: I hate to be the one to shout about bad English, but FlightGear is either 'Free', or you can download it 'for nothing'. Please don't say 'for free'. I think for nothing could have negative connotations. How about at no cost? Gene Buckle wrote: FlightGear is a open-source flight simulator that was started in 2006. 1996. :) Whoops. Martin Spott wrote: just one minor nit (aside the one wrt. the date of birth), there's a useless blank here: be downloaded for free from http:// www.flightgear.org. ^^^ Vivian wrote: ... huge number of individuals ...? We are _relatively_ few. Large number - possibly, huge number - probably not, even taking into account those that have come and gone over the years. Rather depends on your definition of huge, I suppose. Yes, huge is a bit much. I'll change it to large So, taking it all together, I've included an updated statement below. Any further comments? -Stuart FlightGear Flight Pro Sim Statement (v1.1): As many people will be aware, there is a new flight simulator product that is being heavily marketed at the moment - Flight Pro Sim. As it is very heavily based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ. FlightGear is a open-source flight simulator that was started in 1996. It is released under the GNU General Public License v2, and as such, it is free to use, modify and develop with few restrictions. It has been developed with the collaboration of a large number of individuals over the internet over the last 12 years. FlightGear can be downloaded at not cost from http://www.flightgear.org. Flight Pro Sim is a commercial product very heavily based on FlightGear. Investigation by a number of the FlightGear developers has found no difference between this and the FlightGear v1.9.1 release other than a change of name. Flight Pro Sim is in no way endorsed or supported by the core FlightGear development team. Given the extreme similarities between Flight Pro Sim and FlightGear, we would recommend that prospective buyers download FlightGear for free and satisfy themselves that Flight Pro Sim provides worthwhile value for money before purchasing it. FAQ: Q: What is the difference between FlightGear and Flight Pro Sim? A: As far as we have been able to make out, the only difference between FlightGear v1.9.1 and Flight Pro Sim is a change in name throughout the software, and the fact that you have to pay for it. Q: Is it legal for the makers of Flight Pro Sim to simply re-brand FlightGear ? A: Yes. Under the GNU GPL v2 (http://www.gnu.org/licenses/gpl-2.0.html), this is legal, provided that they distribute the source code (or make it available). Q: Is is legal to sell a copy of FlightGear, whether re-branded or not ? A: Yes. Technically, the purchaser is paying for the distribution of the software, and it reasonable to charge a fee for this. In fact, those interested in receiving a DVD containing FlightGear may do so through the main FlightGear website, and directly contribute to the project (though they may want to wait for the upcoming release in the new year). Q: Has Flight Pro Sim paid any money to FlightGear for the rights to the program ? A: No. No such payment is required, as FlightGear is open-source software. Q: Is there any relationship between the makers of Flight Pro Sim and FlightGear? A: Not that we are aware of. As far as we are aware, the makers of Flight Pro Sim are not FlightGear developers. Q: Has Flight Pro Sim contributed to the FlightGear project at all ? A: There is no evidence that the makers of Flight Pro Sim have contributed to the FlightGear project, either through code or money. They did offer to provide money ($250) for a monthly competition, but this offer has not been taken up. Q: I have purchased Flight Pro Sim. Can I get a refund ? A: That is something you will have to take up with the makers of Flight Pro Sim. We understand they offer a 60 day money-back guarantee. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL verification patch)
I think if we are deigning to say Investigation by a number of the FlightGear developers has found no difference between this and the FlightGear v1.9.1 release other than a change of name.; then I also think that after Under the GNU GPL v2 (http://www.gnu.org/licenses/gpl-2.0.html), this is legal, provided that they distribute the source code (or make it available), it's fair to mention something along the lines of Our developers and users have not conclusively determined whether or not the offer from FlightSimPro is indeed in compliance with these terms. I believe that statement sticks to the facts while expressing our stance of skepticism. Cheers, -R. (MD-Terp) Robert M. Shearman, Jr. Transit Operations Supervisor, University of Maryland Department of Transportation also known as rm...@umd.edu FlightGear Flight Pro Sim Statement: As many people will be aware, there is a new flight simulator product that is being heavily marketed at the moment - Flight Pro Sim. As it is very heavily based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ. FlightGear is a open-source flight simulator that was started in 2006. It is released under the GNU General Public License v2, and as such, it is free to use, modify and develop with few restrictions. It has been developed with the collaboration of a huge number of individuals over the internet over the last 12 years. FlightGear can be downloaded for free from http:// www.flightgear.org. Flight Pro Sim is a commercial product very heavily based on FlightGear. Investigation by a number of the FlightGear developers has found no difference between this and the FlightGear v1.9.1 release other than a change of name. Flight Pro Sim is in no way endorsed or supported by the core FlightGear development team. Given the extreme similarities between Flight Pro Sim and FlightGear, we would recommend that prospective buyers download FlightGear for free and satisfy themselves that Flight Pro Sim provides worthwhile value for money before purchasing it. FAQ: Q: What is the difference between FlightGear and Flight Pro Sim? A: As far as we have been able to make out, the only difference between FlightGear v1.9.1 and Flight Pro Sim is a change in name throughout the software, and the fact that you have to pay for it. Q: Is it legal for the makers of Flight Pro Sim to simply re-brand FlightGear ? A: Yes. Under the GNU GPL v2 (http://www.gnu.org/licenses/gpl-2.0.html), this is legal, provided that they distribute the source code (or make it available). Q: Is is legal to sell a copy of FlightGear, whether re-branded or not ? A: Yes. Technically, the purchaser is paying for the distribution of the software, and it reasonable to charge a fee for this. In fact, those interested in receiving a DVD containing FlightGear may do so through the main FlightGear website, and directly contribute to the project (though they may want to wait for the upcoming release in the new year). Q: Has Flight Pro Sim paid any money to FlightGear for the rights to the program ? A: No. No such payment is required, as FlightGear is open-source software. Q: Is there any relationship between the makers of Flight Pro Sim and FlightGear? A: Not that we are aware of. As far as we are aware, the makers of Flight Pro Sim are not FlightGear developers. Q: Has Flight Pro Sim contributed to the FlightGear project at all ? A: There is no evidence that the makers of Flight Pro Sim have contributed to the FlightGear project, either through code or money. They did offer to provide money ($250) for a monthly competition, but this offer has not been taken up. Q: I have purchased Flight Pro Sim. Can I get a refund ? A: That is something you will have to take up with the makers of Flight Pro Sim. We understand they offer a 60 day money-back guarantee. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement (was Re: FlightGear URL verification patch)
On Mon, 14 Dec 2009 22:24:23 +0100, Durk wrote in message 200912142224.24136.d.tal...@xs4all.nl: On Monday 14 December 2009 12:11:15 pm Stuart Buchanan wrote: I think one statement can easily be used for both purposes if written appropriately. Agreed. That's actually what I was thinking of. I'd appreciate feedback, even if it is only to agree with the wording of the statement, to ensure that we have buy-in for this. In addition to the points brought up by others, I have one suggestion for a FAQ item: From the discussion on the flight simulator network, it struck me that people (especially those with a freeware background) don't necessarily understand why we are allowing third parties to make money off of FlightGear. I guess this is already covered by the is it legal to resell FAQ item, but maybe it's worth to specifically address this question from a different perspective (i.e. that of somebody coming from a freeware background)? Cheers, Durk ..the freebee crowd often get their warez the same way they get their music, and may even have seen sheet music, allowing our banal sheet music is for music binaries, like what source code is for flight simulator binaries. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...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. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement
On Mon, 14 Dec 2009 21:30:50 + (GMT), Stuart wrote in message 724039.15837...@web26006.mail.ukl.yahoo.com: Q: Is it legal for the makers of Flight Pro Sim to simply re-brand FlightGear ? A: Yes. Under the GNU GPL v2 ..have you guys decide _against_ GPLv3 and GPLv2-and-later and instead decided to go GPLv2-_only_??? ..if not, FG is GPL and GPLv2-and-maybe-later. ;o) (http://www.gnu.org/licenses/gpl-2.0.html), this is legal, provided that they distribute the source code (or make it available). Q: Has Flight Pro Sim paid any money to FlightGear for the rights to the program ? A: No. No such payment is required, as FlightGear is open-source ..say is GPL software, BSD, MIT etc are also open-source. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...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. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement
On 12/14/2009 02:30 PM, Stuart Buchanan wrote in part: Q: Is is legal to sell a copy of FlightGear, whether re-branded or not ? A: Yes. Technically, the purchaser is paying for the distribution of the Since we are not lawyers here, I would shy away from answering bluntly yes to a legal question. How about something like: Q: Is is legal to sell a copy of FlightGear, whether re-branded or not ? A: Under some conditions, yes. There are legal ways of distributing the program, and also illegal ways. This FAQ expresses no opinions about the legality of any particular distribution scheme. Generally speaking, the license allows a distributor to charge any price or no price but requires the distributor to comply with a number of restrictions, including making the source code available and giving you a license to make further copies. For details, refer to http://www.gnu.org/licenses/gpl.html -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement
On Mon, 2009-12-14 at 21:30 +, Stuart Buchanan wrote: Being really really picky with English, the opening statement uses the word heavily too often; it's not good style. As a suggestion of replacement, perhaps; As many people will be aware, there is a new flight simulator product that is being heavily marketed at the moment - Flight Pro Sim. As it is almost entirely based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ. almost entirely leaves an impression that there is little difference, while not making a binding statement that we may not be able to substantiate.. And in the next paragraph; It has been developed with the collaboration of a large number of individuals for the last 12 years. though I feel over the Internet could almost be left out, it really isn't important how we collaborate, the number and length of time are the important bits here. Given the similarities between Flight Pro Sim and FlightGear, the word extreme feels like it is trying to pull emotional strings here, it could be removed without changing to meaning of the sentence. Viewing this statement in to the future, how does it feel if a legitimate commercial contributor crops up, is there anything here that would deter or prevent an engaged contributor from working with the project? I think by restating the GPL principles it has left open a contributor we would be happy to work with. S. FlightGear Flight Pro Sim Statement (v1.1): As many people will be aware, there is a new flight simulator product that is being heavily marketed at the moment - Flight Pro Sim. As it is very heavily based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ. FlightGear is a open-source flight simulator that was started in 1996. It is released under the GNU General Public License v2, and as such, it is free to use, modify and develop with few restrictions. It has been developed with the collaboration of a large number of individuals over the internet over the last 12 years. FlightGear can be downloaded at not cost from http://www.flightgear.org. Flight Pro Sim is a commercial product very heavily based on FlightGear. Investigation by a number of the FlightGear developers has found no difference between this and the FlightGear v1.9.1 release other than a change of name. Flight Pro Sim is in no way endorsed or supported by the core FlightGear development team. Given the extreme similarities between Flight Pro Sim and FlightGear, we would recommend that prospective buyers download FlightGear for free and satisfy themselves that Flight Pro Sim provides worthwhile value for money before purchasing it. FAQ: Q: What is the difference between FlightGear and Flight Pro Sim? A: As far as we have been able to make out, the only difference between FlightGear v1.9.1 and Flight Pro Sim is a change in name throughout the software, and the fact that you have to pay for it. Q: Is it legal for the makers of Flight Pro Sim to simply re-brand FlightGear ? A: Yes. Under the GNU GPL v2 (http://www.gnu.org/licenses/gpl-2.0.html), this is legal, provided that they distribute the source code (or make it available). Q: Is is legal to sell a copy of FlightGear, whether re-branded or not ? A: Yes. Technically, the purchaser is paying for the distribution of the software, and it reasonable to charge a fee for this. In fact, those interested in receiving a DVD containing FlightGear may do so through the main FlightGear website, and directly contribute to the project (though they may want to wait for the upcoming release in the new year). Q: Has Flight Pro Sim paid any money to FlightGear for the rights to the program ? A: No. No such payment is required, as FlightGear is open-source software. Q: Is there any relationship between the makers of Flight Pro Sim and FlightGear? A: Not that we are aware of. As far as we are aware, the makers of Flight Pro Sim are not FlightGear developers. Q: Has Flight Pro Sim contributed to the FlightGear project at all ? A: There is no evidence that the makers of Flight Pro Sim have contributed to the FlightGear project, either through code or money. They did offer to provide money ($250) for a monthly competition, but this offer has not been taken up. Q: I have purchased Flight Pro Sim. Can I get a refund ? A: That is something you will have to take up with the makers of Flight Pro Sim. We understand they offer a 60 day money-back guarantee. -- Return on Information:
Re: [Flightgear-devel] nan-a-palooza
Status summary: 0) I merged in Jester's nan-fixes. That was easy: git remote add -t nan-fixes jester git://gitorious.org/~jester/fg/jesters-clone.git git pull jester make I have not explicitly disabled real-weather-fetch, but it appears to be non-enabled by default. The ai-traffic remains enabled. This is the default. So here's what I observe in this state: 1) If I want to get anything done, I cannot --enable-fpe because that leads to an early FP exception, while the splash screen is still up. I cannot say whether this is due to intrinsic badness in the fglrx driver, or whether the driver is being passed unwholesome data. #include tirade about non-open-source drivers 2) It is still easy to get SEGVs or ABORTs (due to corrupt double-linked lists) when exiting from the sim. Some logs including tracebacks are here http://www.av8n.com/fly/fgfs//corrupt--21540.log http://www.av8n.com/fly/fgfs//corrupt--21628.log This appears to be about 90% reproducible chez moi. It is at least as likely to happen after after a short (30 second) simulator run as after a long (90 minute) one. 3) The good part is that I can now sit stationary on the ground, taxi, and even fly without seeing nan messages spewed on the console. This is a major improvement. I attribute this improvement to Jester's patches, since AFACT that is the only significant thing that has changed since a couple of days ago. Some seriously laborious debugging must have gone into preparing those patches. It is much appreciated. I am particularly amused by commit a3d5fda6b09e from 24 Oct 2009. It replaced 17 lines with 1 line and produced a better result. -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Flight Pro Sim Statement
2009/12/15 Scott Hamilton scott.hamil...@popplanet.biz: On Mon, 2009-12-14 at 21:30 +, Stuart Buchanan wrote: Being really really picky with English, the opening statement uses the word heavily too often; it's not good style. As a suggestion of replacement, perhaps; As many people will be aware, there is a new flight simulator product that is being heavily marketed at the moment - Flight Pro Sim. As it is almost entirely based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ. almost entirely leaves an impression that there is little difference, while not making a binding statement that we may not be able to substantiate.. And in the next paragraph; It has been developed with the collaboration of a large number of individuals for the last 12 years. though I feel over the Internet could almost be left out, it really isn't important how we collaborate, the number and length of time are the important bits here. Given the similarities between Flight Pro Sim and FlightGear, the word extreme feels like it is trying to pull emotional strings here, it could be removed without changing to meaning of the sentence. Viewing this statement in to the future, how does it feel if a legitimate commercial contributor crops up, is there anything here that would deter or prevent an engaged contributor from working with the project? I think by restating the GPL principles it has left open a contributor we would be happy to work with. (Gawd, I dislike html email.) Scott, Say you want to embed into a certified hardware for flight training,. If I was an entity that wanted to use FlightGear, I'd probably be emailing Curt for suggestions to find a developer that is willing to consult as necessary and also to consider commiting patches from the commercial entity. There are other ways to contribute to the FlightGear project. I don't think anyone would say no to improved scenery, especially around the airports/airfields. There is nothing wrong with keeping the proposal quiet (ie off list) but an apparent fork in name only is not in the spirit of the GPL. The above approach is much more transparent than what has been done in the past. Regards George -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] nan-a-palooza
On Tue, Dec 15, 2009 at 1:46 AM, John Denker j...@av8n.com wrote:
Status summary:
0) I merged in Jester's nan-fixes. That was easy:
git remote add -t nan-fixes jester
git://gitorious.org/~jester/fg/jesters-clone.git
git pull jester
make
We want GIT! We want GIT! :D
1) If I want to get anything done, I cannot --enable-fpe
because that leads to an early FP exception, while the
splash screen is still up.
That may be the nasal bug Jacob is seeing. I could reproduce it and
also made a little test case that I am gonna submit as a gcc bug
report. It is clearly accessing the double member of the union
before it has been established as valid. I have adjusted the
workaround I had posted earlier so that the bug is no longer triggered
for me. (See attachment) Also, compiling with -O3 makes it go away
here.
2) It is still easy to get SEGVs or ABORTs (due to
corrupt double-linked lists) when exiting from the
sim. Some logs including tracebacks are here
http://www.av8n.com/fly/fgfs//corrupt--21540.log
http://www.av8n.com/fly/fgfs//corrupt--21628.log
This appears to be about 90% reproducible chez moi.
It is at least as likely to happen after after a
short (30 second) simulator run as after a long
(90 minute) one.
I can confirm this as well. I have already reported two potential
issues that need to be investigated (based on valgrind reports).
Also, Tat has started a cvs bisect: so far he has bracketed the
problem between 1st of october and 1st of november, I think.
--
Csaba/Jester
diff --git a/simgear/nasal/hash.c b/simgear/nasal/hash.c
index 1efe8fb..f9683ee 100644
--- a/simgear/nasal/hash.c
+++ b/simgear/nasal/hash.c
@@ -62,28 +62,28 @@ static unsigned int refhash(naRef key)
}
}
-static int equal(naRef a, naRef b)
+static int equal(const naRef* a, const naRef* b)
{
-if(IS_NUM(a)) return a.num == b.num;
-if(PTR(a).obj == PTR(b).obj) return 1;
-if(naStr_len(a) != naStr_len(b)) return 0;
-return memcmp(naStr_data(a), naStr_data(b), naStr_len(a)) == 0;
+if(IS_NUM(*a)) return a-num == b-num;
+if(PTR(*a).obj == PTR(*b).obj) return 1;
+if(naStr_len(*a) != naStr_len(*b)) return 0;
+return memcmp(naStr_data(*a), naStr_data(*b), naStr_len(*a)) == 0;
}
/* Returns the index of a cell that either contains a matching key, or
* is the empty slot to receive a new insertion. */
-static int findcell(struct HashRec *hr, naRef key, unsigned int hash)
+static int findcell(struct HashRec *hr, const naRef* key, unsigned int hash)
{
int i, mask = POW2(hr-lgsz+1)-1, step = (2*hash+1) mask;
for(i=HBITS(hr,hash); TAB(hr)[i] != ENT_EMPTY; i=(i+step)mask)
-if(TAB(hr)[i] != ENT_DELETED equal(key, ENTS(hr)[TAB(hr)[i]].key))
+if(TAB(hr)[i] != ENT_DELETED equal(key, ENTS(hr)[TAB(hr)[i]].key))
break;
return i;
}
static void hashset(HashRec* hr, naRef key, naRef val)
{
-int ent, cell = findcell(hr, key, refhash(key));
+int ent, cell = findcell(hr, key, refhash(key));
if((ent = TAB(hr)[cell]) == ENT_EMPTY) {
ent = hr-next++;
if(ent = NCELLS(hr)) return; /* race protection, don't overrun */
@@ -127,7 +127,7 @@ int naHash_get(naRef hash, naRef key, naRef* out)
{
HashRec* hr = REC(hash);
if(hr) {
-int ent, cell = findcell(hr, key, refhash(key));
+int ent, cell = findcell(hr, key, refhash(key));
if((ent = TAB(hr)[cell]) 0) return 0;
*out = ENTS(hr)[ent].val;
return 1;
@@ -147,7 +147,7 @@ void naHash_delete(naRef hash, naRef key)
{
HashRec* hr = REC(hash);
if(hr) {
-int cell = findcell(hr, key, refhash(key));
+int cell = findcell(hr, key, refhash(key));
if(TAB(hr)[cell] = 0) {
TAB(hr)[cell] = ENT_DELETED;
if(--hr-size POW2(hr-lgsz-1))
@@ -211,7 +211,7 @@ int naiHash_tryset(naRef hash, naRef key, naRef val)
{
HashRec* hr = REC(hash);
if(hr) {
-int ent, cell = findcell(hr, key, refhash(key));
+int ent, cell = findcell(hr, key, refhash(key));
if((ent = TAB(hr)[cell]) = 0) { ENTS(hr)[ent].val = val; return 1; }
}
return 0;
--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] navaids update
Is nav.dat supposed to be updated from robin X-plane database? If nobody else is going to do that, I'll be updating the file from Robin's most current package during our pre-release phase (however this is going to be defined ). Can't the data be commited to CVS now ? pete -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] FYI: Contacting Counsel
I just wanted to drop a note I will be contacting the Software Freedom Law Center - http://www.softwarefreedom.org - on behalf of FlightGear. If you have any questions, comments or concerns please don't hesitate to email me -off the list-. Cheers John -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] NASA 3D models
Don't know if this has been mentioned before: http://www.nasa.gov/multimedia/3d_resources/3d-models-gallery.html Jon -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
