[Flightgear-devel] [PATCH V2] fg: update gitignore
Update .gitignore to ignore another build result V2: Ignore the install_manifest too. --- .gitignore |2 ++ 1 file changed, 2 insertions(+) diff --git a/.gitignore b/.gitignore index 8a18462..1524d4c 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,5 @@ CTestTestfile.cmake .kdev4 *.kdev4 *.pyc +src/FDM/YASim/yasim-proptest +install_manifest.txt -- 1.7.10.4 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] fg: update gitignore
Update .gitignore to ignore another build result --- .gitignore |1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 8a18462..d8d0fd4 100644 --- a/.gitignore +++ b/.gitignore @@ -15,3 +15,4 @@ CTestTestfile.cmake .kdev4 *.kdev4 *.pyc +src/FDM/YASim/yasim-proptest -- 1.7.10.4 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [PATCH] simgear: update .gitignore to include all current build results
simgear build off /next was leaving a bunch of untracked and unignored files lying around. most of these are new binaries, but some are intermediate files generated during the build. updates .gitignore to ignore all of them. --- .gitignore | 16 1 file changed, 16 insertions(+) diff --git a/.gitignore b/.gitignore index a6fdabb..1a8431a 100644 --- a/.gitignore +++ b/.gitignore @@ -13,3 +13,19 @@ CTestTestfile.cmake install_manifest.txt build* Build +DartConfiguration.tcl +simgear/environment/test_metar +simgear/io/httpget +simgear/io/test_binobj +simgear/io/test_http +simgear/io/test_sock +simgear/magvar/test_magvar +simgear/math/geometry_test +simgear/math/math_test +simgear/misc/test_path +simgear/misc/test_strings +simgear/misc/test_tabbed_values +simgear/props/test_propertyObject +simgear/props/test_props +simgear/scene/tgdb/BucketBoxTest +simgear/xml/expat_config.h -- 1.7.10.4 -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
All sounds good from here, thanks for pulling lead on this Torsten! On Fri, Jun 8, 2012 at 2:23 PM, Alexis Bory wrote: > Le 08/06/2012 20:39, Torsten Dreyer a écrit : > > Thanks for all the replies, > > > > summing all up, I end up with the following: > > > > The summer release will become v2.8.0. Rembrandt is included but > > disabled by default and announced as an experimental but cool new > feature. > > > > We keep the current selection of base package aircraft for 2.8.0. > > > > We keep last winter's aircraft commit policy (no feature freeze) for all > > aircraft but the base package's A/C selection. > > > > Is that consensus? > > Agreed on all 3 points. > > Alexis > > > > > Greetings, > > Torsten > > > > > > Am 02.06.2012 21:36, schrieb Torsten Dreyer: > >> Hi, > >> > >> in just a bit more than two weeks from now we reach June, 17th, marking > >> the first milestone for the release of next FlightGear version: the > >> "feature freeze" period. > >> > >> If you have some great and exciting new features for FlightGear on your > >> local disc but not yet pushed the gitorious repository - now is the > time! > >> > >> Two questions have to be discussed and answered until the release > >> branches get created on July, 17th: > >> > >> 1) What's the version number of the new release? > >> a) 2.8.0 > >> b) 3.0.0 > >> > >> 2) Which aircraft do we ship in the base package? > >> a) just the c172 > >> b) same as before > >> c) [name your preferred aircraft] > >> > >> 3) Should we keep last year's commit policy for aircraft during the > >> feature freeze? > >> a) yes > >> b) no > >> > >> Regards, > >> Torsten > >> > >> > >> > >> > >> > >> > >> > -- > >> Live Security Virtual Conference > >> Exclusive live event will cover all the ways today's security and > >> threat landscape has changed and how IT managers can respond. > Discussions > >> will include endpoint security, mobile security and the latest in > malware > >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > >> ___ > >> Flightgear-devel mailing list > >> Flightgear-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/flightgear-devel > >> > >> > > > > > -- > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > ___ > > Flightgear-devel mailing list > > Flightgear-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > > > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] "FlightGear developers discussions"
Thorsten > -Original Message- > From: Renk Thorsten [mailto:thorsten.i.r...@jyu.fi] > Sent: 26 May 2012 18:21 > To: FlightGear developers discussions > Subject: [Flightgear-devel] "FlightGear developers discussions" de...@lists.sourceforge.net> > > > Done. Could do with some more refinement, but it works. If you input > > speed-kt, then position updates are ignored and positions are > > calculated from input speed and pitch. Here are the patches: > > > > http://dl.dropbox.com/u/57645542/0001-SG%20Make-Models-move-with- > headi > > ng-and > > -speed.patch > > http://dl.dropbox.com/u/57645542/0001-FG-Make-models-move-with- > heading > > -and-s > > peed.patch > > http://dl.dropbox.com/u/57645542/0002-FG-Calculate-horizontal-and-vert > > ical-s > > peeds.patch > > > > Next, I'm going to allow input of vertical and horizontal speeds (fps) > > as well. > > > > Seems to have very little impact on framerate, but it involves a for > > loop (and you know how much I like those), so there are limits. > > Great - thanks! I'm travelling at the moment, so I won't be able to look into > this until a week from now, but I'll test this as soon as I am back. > > We won't need it for many clouds (usually less than 10, for pure Cirrus skies > still less than 50), so I don't see any large number coming up (of course there > may be non-weather applications...) > > > * Thorsten The patches have been moved to https://www.dropbox.com/home/Public/FG-Models-Movement They are sequential so you will need to apply each in turn FG to Flightgear SG to Simgear. I've tested as far as I am able - seem to work. I hope you can make use of them. Vivian -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
Le 08/06/2012 20:39, Torsten Dreyer a écrit : > Thanks for all the replies, > > summing all up, I end up with the following: > > The summer release will become v2.8.0. Rembrandt is included but > disabled by default and announced as an experimental but cool new feature. > > We keep the current selection of base package aircraft for 2.8.0. > > We keep last winter's aircraft commit policy (no feature freeze) for all > aircraft but the base package's A/C selection. > > Is that consensus? Agreed on all 3 points. Alexis > > Greetings, > Torsten > > > Am 02.06.2012 21:36, schrieb Torsten Dreyer: >> Hi, >> >> in just a bit more than two weeks from now we reach June, 17th, marking >> the first milestone for the release of next FlightGear version: the >> "feature freeze" period. >> >> If you have some great and exciting new features for FlightGear on your >> local disc but not yet pushed the gitorious repository - now is the time! >> >> Two questions have to be discussed and answered until the release >> branches get created on July, 17th: >> >> 1) What's the version number of the new release? >> a) 2.8.0 >> b) 3.0.0 >> >> 2) Which aircraft do we ship in the base package? >> a) just the c172 >> b) same as before >> c) [name your preferred aircraft] >> >> 3) Should we keep last year's commit policy for aircraft during the >> feature freeze? >> a) yes >> b) no >> >> Regards, >> Torsten >> >> >> >> >> >> >> -- >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> ___ >> Flightgear-devel mailing list >> Flightgear-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/flightgear-devel >> >> > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
Hi Yves, I don't think anybody has really worked on or tested switching the nav and apt database file format. As this is closely linked to a new scenery, I wouldn't want to see this change happen shortly before the feature freeze. Thanks, Torsten Am 03.06.2012 13:45, schrieb ys: > Hi Torsten > > What are the plans now for apt.dat.gz and nav.dat.gz ? Will this > prehistorical data files still be shipped with flightgear base package 2.8.0 > ? As far as I understand flightgear is ready to read the newer formats and > also the airport scenery tools are ready to use the newer formats. And there > are some tendencies to keep this data out of the base package anyway and > having a new organized data distribution (which is my favorite). > > I am still comparing 810 data with 850 data for some older airport work done > by flightgear contributors. Once this task has finished I will send converted > data to the xplane database to be integrated where it makes sense and where I > couldn't find original contributor (some airports have already been updated > meantime by xplane contributors, so it is necessary to compare every airport > and decide which one has more advanced or "better" data). > > I think it is a good choice to go for the new data format even because > contributors are asked to send their edits to robin peels xplane datacenter > since many years. Unfortunately 810 xplane data format will not be updated > anymore, so without roadmap for a change there is only the possibility to > have a own flightgear data distribution, missing huge updates from the last > couple of years probably. On the other hand some terrasynced scenery data > will be out of data sync probably for some months with the change, but I > guess this is the part which can be updated out of core release cycles and > base package anyway. > > Cheers, Yves > > > > Am 02.06.2012 um 21:36 schrieb Torsten Dreyer: > >> Hi, >> >> in just a bit more than two weeks from now we reach June, 17th, marking >> the first milestone for the release of next FlightGear version: the >> "feature freeze" period. >> >> If you have some great and exciting new features for FlightGear on your >> local disc but not yet pushed the gitorious repository - now is the time! >> >> Two questions have to be discussed and answered until the release >> branches get created on July, 17th: >> >> 1) What's the version number of the new release? >>a) 2.8.0 >>b) 3.0.0 >> >> 2) Which aircraft do we ship in the base package? >>a) just the c172 >>b) same as before >>c) [name your preferred aircraft] >> >> 3) Should we keep last year's commit policy for aircraft during the >> feature freeze? >>a) yes >>b) no >> >> Regards, >> Torsten >> >> >> >> >> >> >> -- >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> ___ >> Flightgear-devel mailing list >> Flightgear-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
Thanks for all the replies, summing all up, I end up with the following: The summer release will become v2.8.0. Rembrandt is included but disabled by default and announced as an experimental but cool new feature. We keep the current selection of base package aircraft for 2.8.0. We keep last winter's aircraft commit policy (no feature freeze) for all aircraft but the base package's A/C selection. Is that consensus? Greetings, Torsten Am 02.06.2012 21:36, schrieb Torsten Dreyer: > Hi, > > in just a bit more than two weeks from now we reach June, 17th, marking > the first milestone for the release of next FlightGear version: the > "feature freeze" period. > > If you have some great and exciting new features for FlightGear on your > local disc but not yet pushed the gitorious repository - now is the time! > > Two questions have to be discussed and answered until the release > branches get created on July, 17th: > > 1) What's the version number of the new release? > a) 2.8.0 > b) 3.0.0 > > 2) Which aircraft do we ship in the base package? > a) just the c172 > b) same as before > c) [name your preferred aircraft] > > 3) Should we keep last year's commit policy for aircraft during the > feature freeze? > a) yes > b) no > > Regards, > Torsten > > > > > > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows crash
I had a startup crash on jsbsim just after the update. A clean solved the problem -Fred - Mail original - > De: "Alan Teeder" > À: "FlightGear developers discussions" > > Envoyé: Vendredi 8 Juin 2012 19:06:50 > Objet: Re: [Flightgear-devel] Windows crash > Fred > The Jenkins build runs fine, have tested with several aircraft. > I am still using VS2008, with > fgfs-win32-VS90-3rdParty+OSG-20110911.zip from > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/old/ . > I have tried a complete clean cmake and compile with the same > results. Reverting the JSBsim update commit clears the crash, which > occurs just after “loading scenario ´nimitz_demo’” is reported, but > before “/sim/signals/fdm-initialized” is reported. > Alan > From: Frederic Bouvier > Sent: Friday, June 08, 2012 5:32 PM > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] Windows crash > Does Jenkins build exhibit that problem ? > Regards, > -Fred > - Mail original - > > De: "Alan Teeder" > > > À: "FlightGear developers discussions" > > > > > Envoyé: Vendredi 8 Juin 2012 17:51:18 > > > Objet: Re: [Flightgear-devel] Windows crash > > > From: Alan Teeder > > > Sent: Tuesday, June 05, 2012 5:28 PM > > > To: Flightgear-devel@lists.sourceforge.net > > > Subject: [Flightgear-devel] Windows crash > > > With the latest git FG is crashing whilst the splash screen is > > shown. > > I have tried with several aircraft including C172p > > > If I revert the following all runs normally. > > > “commit 642735ab18421db87a07d6841dd720fd4615bfff > > > Author: Erik Hofman > > > Date: Wed May 30 08:39:04 2012 +0200 > > > sync with JSB JSBSim CVS” > > > My configuration is MSVC 2008, 32bit build, Windows 7. > > > Unfortunately I have been unable to even start FG from a MSVC debug > > build, and the only clue I can give is that MSVC reports that the > > crash is in free.c (part of MSVC) > > > Sorry for the report > > > Alan > > > -- > > > This is not fixed by today´s patch > > > commit a237fa6a4c4de304223f36f2123a40cf51d0cf99 > > > Author: ThorstenB > > > Date: Fri Jun 8 15:13:04 2012 +0200 > > > Harald JOHNSEN: Prevent a crash during startup. > > > Alan > > > -- > > > Live Security Virtual Conference > > > Exclusive live event will cover all the ways today's security and > > > threat landscape has changed and how IT managers can respond. > > Discussions > > > will include endpoint security, mobile security and the latest in > > malware > > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > ___ > > > Flightgear-devel mailing list > > > Flightgear-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows crash
Fred The Jenkins build runs fine, have tested with several aircraft. I am still using VS2008, with fgfs-win32-VS90-3rdParty+OSG-20110911.zip from ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/old/. I have tried a complete clean cmake and compile with the same results. Reverting the JSBsim update commit clears the crash, which occurs just after “loading scenario ´nimitz_demo’” is reported, but before “/sim/signals/fdm-initialized” is reported. Alan From: Frederic Bouvier Sent: Friday, June 08, 2012 5:32 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] Windows crash Does Jenkins build exhibit that problem ? Regards, -Fred De: "Alan Teeder" À: "FlightGear developers discussions" Envoyé: Vendredi 8 Juin 2012 17:51:18 Objet: Re: [Flightgear-devel] Windows crash From: Alan Teeder Sent: Tuesday, June 05, 2012 5:28 PM To: Flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Windows crash With the latest git FG is crashing whilst the splash screen is shown. I have tried with several aircraft including C172p If I revert the following all runs normally. “commit 642735ab18421db87a07d6841dd720fd4615bfff Author: Erik Hofman Date: Wed May 30 08:39:04 2012 +0200 sync with JSB JSBSim CVS” My configuration is MSVC 2008, 32bit build, Windows 7. Unfortunately I have been unable to even start FG from a MSVC debug build, and the only clue I can give is that MSVC reports that the crash is in free.c (part of MSVC) Sorry for the report Alan -- This is not fixed by today´s patch commit a237fa6a4c4de304223f36f2123a40cf51d0cf99 Author: ThorstenB Date: Fri Jun 8 15:13:04 2012 +0200 Harald JOHNSEN: Prevent a crash during startup. Alan -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows crash
Does Jenkins build exhibit that problem ? Regards, -Fred - Mail original - > De: "Alan Teeder" > À: "FlightGear developers discussions" > > Envoyé: Vendredi 8 Juin 2012 17:51:18 > Objet: Re: [Flightgear-devel] Windows crash > From: Alan Teeder > Sent: Tuesday, June 05, 2012 5:28 PM > To: Flightgear-devel@lists.sourceforge.net > Subject: [Flightgear-devel] Windows crash > With the latest git FG is crashing whilst the splash screen is shown. > I have tried with several aircraft including C172p > If I revert the following all runs normally. > “commit 642735ab18421db87a07d6841dd720fd4615bfff > Author: Erik Hofman > Date: Wed May 30 08:39:04 2012 +0200 > sync with JSB JSBSim CVS” > My configuration is MSVC 2008, 32bit build, Windows 7. > Unfortunately I have been unable to even start FG from a MSVC debug > build, and the only clue I can give is that MSVC reports that the > crash is in free.c (part of MSVC) > Sorry for the report > Alan > -- > This is not fixed by today´s patch > commit a237fa6a4c4de304223f36f2123a40cf51d0cf99 > Author: ThorstenB > Date: Fri Jun 8 15:13:04 2012 +0200 > Harald JOHNSEN: Prevent a crash during startup. > Alan > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows crash
From: Alan Teeder Sent: Tuesday, June 05, 2012 5:28 PM To: Flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Windows crash With the latest git FG is crashing whilst the splash screen is shown. I have tried with several aircraft including C172p If I revert the following all runs normally. “commit 642735ab18421db87a07d6841dd720fd4615bfff Author: Erik Hofman Date: Wed May 30 08:39:04 2012 +0200 sync with JSB JSBSim CVS” My configuration is MSVC 2008, 32bit build, Windows 7. Unfortunately I have been unable to even start FG from a MSVC debug build, and the only clue I can give is that MSVC reports that the crash is in free.c (part of MSVC) Sorry for the report Alan -- This is not fixed by today´s patch commit a237fa6a4c4de304223f36f2123a40cf51d0cf99 Author: ThorstenB Date: Fri Jun 8 15:13:04 2012 +0200 Harald JOHNSEN: Prevent a crash during startup. Alan -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Two issues: Shader control and turbulence
> The /sim/rendering/shader-effects property has been removed since before > 2.6.0, and IIRC it was properly announced on this list. > I believe each of those properties was documented on the > wiki by Fred, and the major changes were announced on this list. I don't mean to blame anyone for lack of documentation... If it's sufficiently clear to everyone but myself how our shader-control scheme works then I'll just remove the problematic condition and be done. Thanks, * Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Two issues: Shader control and turbulence
On Friday 08 June 2012 09:53:58 Renk Thorsten wrote: > tie to some yet unknown master switch? > Who has a plan? > * Thorsten There's no master switch anymore. There's a property that's checked by some nasal to set the quality of the shaders, but there's no master switch available for effects. Regards, Emilian -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Two issues: Shader control and turbulence
On Friday 08 June 2012 09:53:58 Renk Thorsten wrote: > Issue #1: > > We finally found the reason why Heiko didn't get the lightfield scheme > properly: > > /sim/rendering/shader-effects > > > > * there's a boolean /sim/rendering/shaders/skydome which I've been using to > switch on the lightfield branch - at some point, the checkbox in the menu > might be renamed into 'atmospheric light scattering effects' or so because > it switches about 5 other shaders (clouds, rain layers, terrain, sea,...) > on as well > > * Thorsten The /sim/rendering/shader-effects property has been removed since before 2.6.0, and IIRC it was properly announced on this list. I suggest using /sim/rendering/shaders/skydome or whatever name you like as long as it's consistent between the property set by the GUI and the effects checking for it. Also check against /sim/rendering/rembrandt/enabled if you need to know if Rembrandt is running. As that was a feature in development it's properties were quite in flux. I believe each of those properties was documented on the wiki by Fred, and the major changes were announced on this list. Regards, Emilian -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
Hi, FWIIW I would opt for version 2.8 Concerning Rembrandt, it does not work on either of my 2 ATI cards - Radeon HD 2600 XT, running Ubuntu 64-bit, and Windows Vista 32-bit, and a Radeon HD 7700 series, in Windows 7 64-bit. I think I have tried all the options mentioned here... On the 2600 I usually see the corner buffer images, but no shadows. On the 7700 even no corner images, and after a certain time the card driver FAILS! I get a black screen, but thankfully it auto-recovers ;=() Oh, and I get about a 50%+ drop in frame rate... and at low viewing angles get flashing lime green over the foreground... So yes, for sure mention Rembrandt, but clearly mark it as in development ;=)) Is there a list anywhere of cards/drivers it DOES work on? If not too expensive maybe I would buy and try one ;=)) I seem to remember someone mentioning such a listing... On converting a/c, as I think someone mentioned why or how can this be done if the results can not be seen on his system! Sort of chicken and egg story... And for the 2.8 release, assume the MULTIPLE warnings will be 'removed', or suppressed, namely - Failed to create beacon for unknown runway 'KONT 26L OM' and about 28 more like this... Image "C:/FG/fgdata/Textures/Water/waves-ver10-nm.dds" uses compressed textures which cannot be supported on some systems. Please decompress this texture for improved portability. and about 6 more like this... We should not need to air this dirty washing on a release product ;=))! Regards, Geoff. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Two issues: Shader control and turbulence
Issue #1: We finally found the reason why Heiko didn't get the lightfield scheme properly: /sim/rendering/shader-effects is required to be true in skydome.eff but apparently not set any more by recent GIT, it was however leftover in my autosave, so I didn't notice anything. I can simply remove the condition, but the wider issue is: Is there anyone who has the master plan of how we want to control what shaders are on and can tell me what property switches I should use and what not? or if such a document does not exist, could we create one? Because this is driving me nuts... What I know is: * there's a boolean /sim/rendering/shaders/skydome which I've been using to switch on the lightfield branch - at some point, the checkbox in the menu might be renamed into 'atmospheric light scattering effects' or so because it switches about 5 other shaders (clouds, rain layers, terrain, sea,...) on as well * there are the float /sim/rendering/shaders/landmass , /sim/rendering/shaders/water, ... which correspond to the quality levels as selected in the shader menu * there's the boolean Rembrandt master switch /sim/rendering/rembrandt/enabled * there are switches for 3dclouds (not in the effect file) and random vegetation (in the effect file) * currently there doesn't seem to be a generic all-shaders-off-no-exceptions switch, although I thought there was the intention to have one? What do I do? Just use my own scheme to switch lightfields on when skydome is on, no other properties checked, tie skydome also to /sim/rendering/shaders/generic > 0, tie to some yet unknown master switch? Who has a plan? Issue #2: Curt recently asked me about turbulence in Advanced Weather. I haven't had the time to test recently, but I think the same magnitude-norm of turbulence is still treated in a different way by YaSim and JSBSim (I noted that a while ago). I'm not saying any of these is wrong, but I'd like a situation in which the same magnitude implies the about the same amount of shaking independent of which FDM I use, and I really shouldn't code any FDM-dependent statements into Advanced Weather. What's the current situation with turbulence? Has anyone looked into this, i.e. is it safe for me to code a bit more turbulence effects into Advanced Weather without making life for either YaSim or JSBSim very hard? * Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Hawaii regional textures merge request
On Fri, Jun 8, 2012 at 8:49 AM, Renk Thorstenwrote: > Okay, I didn't get a message that this was merged, and despite the argument > that there's need for a discussion of the regional texturing scheme there > wasn't any discussion, so can I assume the subject isn't interesting at the > moment, discontinue to try to come up with GPL compatible solutions (which is > hard...) and just continue my own texturing projects for my private > amusement? I'll look at merging this at some point during the weekend. -Stuart -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
On Fri, Jun 8, 2012 at 8:35 AM, Renk Thorsten wrote: > Personally, I'm not using it since it makes my system just a bit too slow to > enjoy and I can't really see how to port lightfield development to Rembrandt > (I guess we're not quite there yet as far as infrastructure is concerned, and > I'd have to learn a few things, but also if Rembrandt + lightfield becomes > even 20% slower than Rembrandt alone, then I can't fly it any more - > Rembrandt costs me more than 50% of my framerate ). So personally, I really > need it as optional, and I'd drop out of shader development if it weren't > because if I can't enjoy it, I somehow lose the motivation to do it. I don't think anyone is suggesting making Rembrandt anything other than optional, just like all the other graphical features we have. > I have also continuing concerns with 'converting' things to Rembrandt - do > they still work for non-Rembrandt? I know some people create optional > Rembrandt and non-Rembrandt versions. I'd ask everyone who has no problems > with Rembrandt to really be aware that there are people who can't run it on > their hardware at all and that there are others who may not want to run it > but may want to use Flightgear and their favourite planes nevertheless. Converting aircraft to Rembrandt will still mean that they work perfectly well with non-Rembrandt. Making an aircraft "Rembrandt-compatible" just involves marking transparent surfaces as such, and has no effect on the non-Rembrandt systems. Adding Rembrandt lighting similarly can be done in such a way that there is no effect on non-Rembrandt systems. The c172p provides an example of this. There are only two areas where aircraft maintainers need to be careful IIRC: - Some aircraft have textures with Ambient Occlusion baked into them. Rembrandt provides its own ambient occlusion so the textures used for a aircraft in Rembrandt should not have this included,. - Some aircraft have "shadows" as additional models. They need to be disabled when Rembrandt shadows are enabled. > Is the implication of this that Rembrandt is considered the default and > aircraft maintainers are expected to switch? When did we make this decision? > I know all people for whom Rembrandt runs well would like to see everything > converted asap, but what for these where it really means a lot of performance > drain? As mentioned above, it's not a question of "switching". Rather it's ensuring that aircraft are compatible by marking transparent surfaces. -Stuart -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Hawaii regional textures merge request
Hi Thorsten Right, it doesn't look like it is worth to have a discussion about this and it was only me pointing this out. At the end I prefer to have your nice work in the repo and it's really not up to me to block anything. I'm just interested in this discussion and I remembered a lot of post about this topic earlier in flightgear development. I would vote to merge it in as an another example of nice and working regional textures, and maybe new people interested in a new approach for scenery development will establish a real collaborative effort later, starting to discuss, design and code, bringing up new ideas and find a place to communicate. The devel-list seems to be the wrong place for such at the moment. That's why I started the devel-scenery list, but this is completely ignored too. The only working channel I see at the moment is IRC #fg_scenery. Cheers, Yves Am 08.06.2012 um 09:49 schrieb Renk Thorsten : > > Okay, I didn't get a message that this was merged, and despite the argument > that there's need for a discussion of the regional texturing scheme there > wasn't any discussion, so can I assume the subject isn't interesting at the > moment, discontinue to try to come up with GPL compatible solutions (which is > hard...) and just continue my own texturing projects for my private > amusement? > > I don't have any issues with this not being merged, I just want to know. > > * Thorsten > -- > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Hawaii regional textures merge request
Okay, I didn't get a message that this was merged, and despite the argument that there's need for a discussion of the regional texturing scheme there wasn't any discussion, so can I assume the subject isn't interesting at the moment, discontinue to try to come up with GPL compatible solutions (which is hard...) and just continue my own texturing projects for my private amusement? I don't have any issues with this not being merged, I just want to know. * Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] The next FlightGear release (summer 2012)
> 1) What's the version number of the new release? >a) 2.8.0 >b) 3.0.0 My impression is that it would be best to advertize Rembrandt as a new, exciting, but optional and stil experimental development. The reason is similar to what others have said - it seems to do really impressive things with light sources on some systems, it seems to make other systems really slow and it doesn't seem to be guaranteed to work everywhere. Personally, I'm not using it since it makes my system just a bit too slow to enjoy and I can't really see how to port lightfield development to Rembrandt (I guess we're not quite there yet as far as infrastructure is concerned, and I'd have to learn a few things, but also if Rembrandt + lightfield becomes even 20% slower than Rembrandt alone, then I can't fly it any more - Rembrandt costs me more than 50% of my framerate ). So personally, I really need it as optional, and I'd drop out of shader development if it weren't because if I can't enjoy it, I somehow lose the motivation to do it. I have also continuing concerns with 'converting' things to Rembrandt - do they still work for non-Rembrandt? I know some people create optional Rembrandt and non-Rembrandt versions. I'd ask everyone who has no problems with Rembrandt to really be aware that there are people who can't run it on their hardware at all and that there are others who may not want to run it but may want to use Flightgear and their favourite planes nevertheless. Going to a version 2.8 would really expose Rembrandt (lightfields, ...) to a larger user-base so that we can have a much better picture (via Forum response) where the issues are. I think overemphasizing exciting new features will backfire badly if there are issues. I'd really approach this with caution. > Rembrandt has been around for quite a few months now, > and the changes required to make an aircraft Rembrandt-compatible are > pretty small, even if the changes to add proper lights are more involved. > > If I was being harsh I'd suggest that the aircraft maintainers should > "man up and do it". Is the implication of this that Rembrandt is considered the default and aircraft maintainers are expected to switch? When did we make this decision? I know all people for whom Rembrandt runs well would like to see everything converted asap, but what for these where it really means a lot of performance drain? > 2) Which aircraft do we ship in the base package? >a) just the c172 >b) same as before >c) [name your preferred aircraft] I like the DR-400 JSBSim very much - I seem to remember it was offered to the repository by the PAF hangar, I'm not sure if it ended up being committed. Anyway, I think it's a great plane, both in terms of the FDM and the visuals. Otherwise I'd like to see either the IAR-80 or the P-51D. There was also some work on the DHC6 - that's also a really popular plane - we might include that. > 3) Should we keep last year's commit policy for aircraft during the > feature freeze? >a) yes >b) no I would allow to commit aircraft freely up to the last point. It doesn't make any sense to restrict new commits as long as we don't have any effort in place to control quality of the aircraft which are already committed at least to the level where we make sure they run with the new version. We always seem to distribute some non-functional aircraft with a release, and as long as that is the case, what's the point in controlling what happens to new aircraft? Last minute changes are likely to be better than the non-functionals lying around. I would perhaps make an exception for any aircraft in the base package - quality control for those should be better and there should be some time for testing them. Cheers, * Thorsten -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
