Re: [Flightgear-devel] 2.10.1
The downside is that I think it would require adding
an if()
test to the vertex shader, something I've been avoiding due to
(unfounded?)
concerns about performance.
General advice that I can find is that GLSL is designed as a linear
program:
conditionals and loops are best avoided:
From my own experience:
* conditionals on flags (say uniform int) are in general unproblematic and work
as intended
* conditionals on a varying are dangerous and only worth trying if you have an
expensive operation which you can avoid - but then they help.
Say, replacing
expensive = some_expensive_operation();
mix(cheap, expensive, x) ;
by
if (x0.0)
{
expensive = some_expensive_operation();
mix(cheap, expensive, x) ;
}
usually does help if x is zero for enough pixels/vertices. The exception to
this are texture lookups which are expensive, but must be evaluated outside of
a branch if the condition involves a varying
* nested conditionals might work for performance gain up to a depth of 2, never
any deeper - then you end up evaluating every branch
* conditionals of the form
if (x0) {do stuff();}
(...)
if (x0) {do_other_stuff();}
don't seem to be recognized as referring to the same condition - they need to
be merged into a single block to be effective for performance.
In general, I think one should stay clear of conditionals, but they have their
use for optimization as well.
* Thorsten
--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi Toshi, According Fred's comment in http://code.google.com/p/flightgear-bugs/issues/detail?id=1027#c9 those messages are output by fgrun reading the file: $fgdata/Aircraft/C130/kc130-yasim-cnf.xml thanks for the pointer! This is now fixed in fgdata. Cheers, Gijs -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On Fri, May 3, 2013 at 6:15 PM, Vivian Meazza wrote: I re-installed the Jenkins nightly Win build from yesterday – seems OK, although I have NOT done any extensive testing. I’m seeing regular crashes here from ALS and Rembrandt, but that’s nothing new. I’m getting a number of errors on start-up; they seem harmless: Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm FYI, I don't think this is related to the AAR work I've done recently, and looks like it might be aircraft specific. What aircraft are you seeing this with? I would be more concerned over the state of the data. The reinstall has partly solved the Screenshot directory issue – it now uses the default Working Directory, but the gui input is still stuck. We have a small glitch with Stuart’s latest iteration of the Random Vegetation (aka trees) with what I think is probably a mipmapping issue. I thought 2.10.1 data would be taken from 2.10.0, with commits cherry-picked? If not, I'd suggest backing out that commit from the 2.10.1 data branch, as it has a co-requisite simgear change, and as Vivian mentions still has some issues. I've been away for the last 5 days so haven't had the chance to look into the tree problem further, but have a couple of ideas. One option would be to mirror the texture rows, so instead of looking like this: ^^^ ^^^ ^^^ ^^^ It would be top-to-top and base-to-base: ^ That way is the mipmap UV isn't quite accurate, it would just include the tree-top of the texture above, rather than the base. This would certainly be less noticeable. The downside is that I think it would require adding an if() test to the vertex shader, something I've been avoiding due to (unfounded?) concerns about performance. Or I might simply change the textures to a (very) long strip, so instead of 512x128 it would be 2048x128. However that feels rather clunky, and might not make good use of GPU memory. Anyone with GPU experience care to comment? -Stuart -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi Stuart, Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm I think I've seen that with all aircraft I've flown recently. IIRC they were all non-AAR capable (as in, they had no AAR stuff in -set.xml) but I'm not near my computer, so I cannot confirm that theory. Cheers, Gijs Date: Wed, 8 May 2013 10:56:25 +0100 From: stuar...@gmail.com To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] 2.10.1 On Fri, May 3, 2013 at 6:15 PM, Vivian Meazza wrote: I re-installed the Jenkins nightly Win build from yesterday – seems OK, although I have NOT done any extensive testing. I’m seeing regular crashes here from ALS and Rembrandt, but that’s nothing new. I’m getting a number of errors on start-up; they seem harmless: Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm FYI, I don't think this is related to the AAR work I've done recently, and looks like it might be aircraft specific. What aircraft are you seeing this with? I would be more concerned over the state of the data. The reinstall has partly solved the Screenshot directory issue – it now uses the default Working Directory, but the gui input is still stuck. We have a small glitch with Stuart’s latest iteration of the Random Vegetation (aka trees) with what I think is probably a mipmapping issue. I thought 2.10.1 data would be taken from 2.10.0, with commits cherry-picked? If not, I'd suggest backing out that commit from the 2.10.1 data branch, as it has a co-requisite simgear change, and as Vivian mentions still has some issues. I've been away for the last 5 days so haven't had the chance to look into the tree problem further, but have a couple of ideas. One option would be to mirror the texture rows, so instead of looking like this: ^^^ ^^^ ^^^ ^^^ It would be top-to-top and base-to-base: ^ That way is the mipmap UV isn't quite accurate, it would just include the tree-top of the texture above, rather than the base. This would certainly be less noticeable. The downside is that I think it would require adding an if() test to the vertex shader, something I've been avoiding due to (unfounded?) concerns about performance. Or I might simply change the textures to a (very) long strip, so instead of 512x128 it would be 2048x128. However that feels rather clunky, and might not make good use of GPU memory. Anyone with GPU experience care to comment? -Stuart -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 8 May 2013, at 10:56, Stuart Buchanan stuar...@gmail.com wrote: I thought 2.10.1 data would be taken from 2.10.0, with commits cherry-picked? If not, I'd suggest backing out that commit from the 2.10.1 data branch, as it has a co-requisite simgear change, and as Vivian mentions still has some issues. The 2.10.1 data is indeed take from 2.10.0 with selective picking as you describe; I wasn't clear enough to Vivian which configuration he should be testing (the 'Window-release' build, which includes its own data) Regards, James -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Stuart From: Buchanan [mailto:stuar...@gmail.com] Sent: 08 May 2013 10:56 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] 2.10.1 On Fri, May 3, 2013 at 6:15 PM, Vivian Meazza wrote: I re-installed the Jenkins nightly Win build from yesterday - seems OK, although I have NOT done any extensive testing. I'm seeing regular crashes here from ALS and Rembrandt, but that's nothing new. I'm getting a number of errors on start-up; they seem harmless: Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm FYI, I don't think this is related to the AAR work I've done recently, and looks like it might be aircraft specific. What aircraft are you seeing this with? I would be more concerned over the state of the data. The reinstall has partly solved the Screenshot directory issue - it now uses the default Working Directory, but the gui input is still stuck. We have a small glitch with Stuart's latest iteration of the Random Vegetation (aka trees) with what I think is probably a mipmapping issue. I thought 2.10.1 data would be taken from 2.10.0, with commits cherry- picked? If not, I'd suggest backing out that commit from the 2.10.1 data branch, as it has a co-requisite simgear change, and as Vivian mentions still has some issues. I've been away for the last 5 days so haven't had the chance to look into the tree problem further, but have a couple of ideas. One option would be to mirror the texture rows, so instead of looking like this: ^^^ ^^^ ^^^ ^^^ It would be top-to-top and base-to-base: ^ That way is the mipmap UV isn't quite accurate, it would just include the tree-top of the texture above, rather than the base. This would certainly be less noticeable. The downside is that I think it would require adding an if() test to the vertex shader, something I've been avoiding due to (unfounded?) concerns about performance. Or I might simply change the textures to a (very) long strip, so instead of 512x128 it would be 2048x128. However that feels rather clunky, and might not make good use of GPU memory. Anyone with GPU experience care to comment? General advice that I can find is that GLSL is designed as a linear program: conditionals and loops are best avoided: http://stackoverflow.com/questions/2614622/tips-for-efficient-glsl-code Here's some stuff on textures. http://www.arcsynthesis.org/gltut/Texturing/Tutorial%2014.html I don't think the shape matters as much as the overall size. As I understand it, GLSL optimizes the storage. In this case new the texture would be 4 times as big. I don't think that's optimal, but on the other hand, it's not pushing the envelope. Do you use a shader analyser? I use the AMD one: http://developer.amd.com/tools-and-sdks/graphics-development/gpu-shaderanaly zer/ might help to decide which route to take HTH Vivian -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi Stuart, Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm I think I've seen that with all aircraft I've flown recently. IIRC they were all non-AAR capable (as in, they had no AAR stuff in -set.xml) but I'm not near my computer, so I cannot confirm that theory. It's even weirder than that. I see the messages in the console whenever I launch FGRun. No matter what aircraft is loaded by default (last flown plane), I always get these lines as soon as FGRun opens; so before starting fgfs. Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm Cheers, Gijs -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
If It's an FGRun problem maybe it's caused by the 3D preview code parsing the planes From: gijsr...@hotmail.com To: flightgear-devel@lists.sourceforge.net Date: Wed, 8 May 2013 20:57:33 +0200 Subject: Re: [Flightgear-devel] 2.10.1 Hi Stuart, Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm I think I've seen that with all aircraft I've flown recently. IIRC they were all non-AAR capable (as in, they had no AAR stuff in -set.xml) but I'm not near my computer, so I cannot confirm that theory. It's even weirder than that. I see the messages in the console whenever I launch FGRun. No matter what aircraft is loaded by default (last flown plane), I always get these lines as soon as FGRun opens; so before starting fgfs. Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm Cheers, Gijs -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Brandano, It's possible that it comes from FGRun, but a Nasal warning from the 3d preview code seems a bit implausible. It is recent thing, though. Vivian From: TDO Brandano [mailto:tdo_brand...@hotmail.com] Sent: 08 May 2013 22:12 To: Flightgear Devel List Subject: Re: [Flightgear-devel] 2.10.1 If It's an FGRun problem maybe it's caused by the 3D preview code parsing the planes _ From: gijsr...@hotmail.com To: flightgear-devel@lists.sourceforge.net Date: Wed, 8 May 2013 20:57:33 +0200 Subject: Re: [Flightgear-devel] 2.10.1 Hi Stuart, Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm I think I've seen that with all aircraft I've flown recently. IIRC they were all non-AAR capable (as in, they had no AAR stuff in -set.xml) but I'm not near my computer, so I cannot confirm that theory. It's even weirder than that. I see the messages in the console whenever I launch FGRun. No matter what aircraft is loaded by default (last flown plane), I always get these lines as soon as FGRun opens; so before starting fgfs. Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm Cheers, Gijs -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi, Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm According Fred's comment in http://code.google.com/p/flightgear-bugs/issues/detail?id=1027#c9 those messages are output by fgrun reading the file: $fgdata/Aircraft/C130/kc130-yasim-cnf.xml Cheers, Toshi -- Learn Graph Databases - Download FREE O'Reilly Book Graph Databases is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Am 2013-05-03 19:15, schrieb Vivian Meazza: Check your IOrules! (write to 'Z:/do-not-access' is allowed) Check your IOrules! (read from 'Z:/do-not-access' is allowed) Have you installed a recent fgdata? If so these messages should not appear. Tom -- Thomas Geymayer www.tomprogs.at / C-Forum und Tutorial: www.proggen.org Student of Computer Science @ Graz University of Technology --- Austria -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Tom -Original Message- From: Thomas Geymayer [mailto:tom...@gmail.com] Sent: 04 May 2013 08:27 To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] 2.10.1 Am 2013-05-03 19:15, schrieb Vivian Meazza: Check your IOrules! (write to 'Z:/do-not-access' is allowed) Check your IOrules! (read from 'Z:/do-not-access' is allowed) Have you installed a recent fgdata? If so these messages should not appear. Not for a couple of days, I'll update again. Vivian -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Tom -Original Message- From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: 04 May 2013 09:20 To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] 2.10.1 Tom -Original Message- From: Thomas Geymayer [mailto:tom...@gmail.com] Sent: 04 May 2013 08:27 To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] 2.10.1 Am 2013-05-03 19:15, schrieb Vivian Meazza: Check your IOrules! (write to 'Z:/do-not-access' is allowed) Check your IOrules! (read from 'Z:/do-not-access' is allowed) Have you installed a recent fgdata? If so these messages should not appear. Not for a couple of days, I'll update again. That cured it - one less alert - good Thanks Vivian -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 30 Apr 2013, at 23:22, Saikrishna Arcot saiarcot...@gmail.com wrote: Are there still any plans to release a 2.10.1? I've been very busy the past few weeks, but in theory the binaries are done and exist (on Jenkins) for Windows, Mac and Linux. After some testing, It just needs 'someone' to upload/mirror them I guess. Did any test the Windows installer from Jenkins yet? Regards, James -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
James, I re-installed the Jenkins nightly Win build from yesterday - seems OK, although I have NOT done any extensive testing. I'm seeing regular crashes here from ALS and Rembrandt, but that's nothing new. I'm getting a number of errors on start-up; they seem harmless: Failed to create alias at /controls[0]/refuelling[0]/refuelling-drogues-pos-norm [0]. Source /sim[0]/multiplay[0]/generic[0]/float[2] is already aliasing another property. Failed to set alias to /controls/refuelling/refuelling-drogues-pos-norm ALC Error (sound manager): Invalid Enum at context creation. Check your IOrules! (write to 'Z:/do-not-access' is allowed) Check your IOrules! (read from 'Z:/do-not-access' is allowed) Image D:/Git_New/my_fgdata/Textures.high/Terrain/transition1.dds uses compressed textures which cannot be supported on some systems. (about 50 times) These are all of interest to developers only: they are not something about which the user can do anything, so I would suggest that they are downgraded to warnings for the release from their current alert status. I would be more concerned over the state of the data. The reinstall has partly solved the Screenshot directory issue - it now uses the default Working Directory, but the gui input is still stuck. We have a small glitch with Stuart's latest iteration of the Random Vegetation (aka trees) with what I think is probably a mipmapping issue. Otherwise, I reckon we're good to go so far as Win 7 is concerned. I will have a look with XP later if you would like. Unless that is there's been something since last night . Vivian From: James Turner [mailto:zakal...@mac.com] Sent: 03 May 2013 12:17 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] 2.10.1 On 30 Apr 2013, at 23:22, Saikrishna Arcot saiarcot...@gmail.com wrote: Are there still any plans to release a 2.10.1? I've been very busy the past few weeks, but in theory the binaries are done and exist (on Jenkins) for Windows, Mac and Linux. After some testing, It just needs 'someone' to upload/mirror them I guess. Did any test the Windows installer from Jenkins yet? Regards, James -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] 2.10.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Are there still any plans to release a 2.10.1? - -- Saikrishna Arcot -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRgEQgAAoJEDg9nXyl50AF7k8P/jWIiA7CK7cfJEzNUD2I7dMy VAQdklKv69GFOLBqMs5sWpuKSilBguorOTfk1TY5bj7iPKNe98o4TSCY8zAfUUhQ WwVE/C7ZOLrC6+38PHQlr3PZb5HBfhCaByZsGelZ3EUL3yb3tLxvLsDOZ9lGpgAm kAYhIpSgks0ZW+nnztNo28m0LJVOnJjKzWgeEvlSiZuXFJHC/PPycs1x/gfB9nHl wjD/UD76/a6pno8W+mpLTIHWsEwCPiPxJD1cz13rlBVX6SQJFhvYg8h2eFAp1HmM m0oaTJHtkVxClyWrmiG3gc8DhmvcyyuV15xrNApGN0pZrV3hqB96Y0w5N+of8vHu lHTwRqHOe7hm0MAhOz5Pbm/fP9/7RKs5TdLSd0unJ0UpUJr/IFrRq3o3x2fTk2Ms WNeoUrvm3j/OXJkJQehOOvTXbe24GLyU+2YV2bPjS20tlK5YGyMp6RSedZNcXqys 8gSBZA2ZS2qxYRNPWbwh/NSxCG2Q1UZbRnJQfwagbGIeKFJV06V27tKWBLeMV15y orDT3KgX0R2ulKbENIKdUnmX55KHZANdSeiKIEVBeLKyGOR4cWNZDCAt/VR0mDCn /YnJxEnK3Z1L1q3x1PY0G6Pi/yBdw7hqbqT0/GMAiG0zD1zrk9lvGP1godqK06NT 0hH+AhZyrTdmRKsnY8pt =ugJd -END PGP SIGNATURE- -- Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with 2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 3 Apr 2013, at 20:42, geneb ge...@deltasoft.com wrote: It might be a good idea to create a script that will distribute the new builds to the various mirrors. That way I'm less likely to throttle the machine to 10k/sec when it hammers whatever I'm watching on Netflix at the time. :D I would prefer that too - the release builds can be uploaded to my DreamHost account, but that step is quite slow (700MB x 3). As ever, Jenkins can do 'anything', we just need to decide what is wise. In particular I don't know how mirror-ing occurs, if we uploaded to a primary which is automatically rsynced to the secondaries or what. Curt? James -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] 2.10.1
Hi, Continuing with the experimental creation of a bug fix release, Release-candidate builds for 2.10.1: http://flightgear.simpits.org:8080/job/Windows-release/ http://flightgear.simpits.org:8080/job/Linux-release/ http://flightgear.simpits.org:8080/job/Mac-release/ These are the first Windows releases produced automatically (Jenkins creates the installer) instead of via Curt, so please be on the look-out for anything I may have messed up / omitted. Based on very limited testing with my Windows VM everything seems sane and the apps run. The intention is that the quality of these builds is 'at least as good' as 2.10.0, so I would be happy for them to replace 2.10.0 on the web sites as soon as they pass a collective sanity check from people here. If you find new bugs, that's fine, but unless they are regressions since 2.10.0 (which is unlikely, hopefully) then they should not block releasing; they can be fixed in a (hypothetical!) 2.10.2 or wait until 2.12. In particular the Windows builds include the UTF-8 pathname fix which is significant for various people, I believe. Regards, James -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi James, This is great news if you are able to crank out full installers right from Jenkins. That will save me a bunch of downloading and hours of uploading for every new release candidate. Thanks, Curt. On Wed, Apr 3, 2013 at 4:34 AM, James Turner zakal...@mac.com wrote: Hi, Continuing with the experimental creation of a bug fix release, Release-candidate builds for 2.10.1: http://flightgear.simpits.org:8080/job/Windows-release/ http://flightgear.simpits.org:8080/job/Linux-release/ http://flightgear.simpits.org:8080/job/Mac-release/ These are the first Windows releases produced automatically (Jenkins creates the installer) instead of via Curt, so please be on the look-out for anything I may have messed up / omitted. Based on very limited testing with my Windows VM everything seems sane and the apps run. The intention is that the quality of these builds is 'at least as good' as 2.10.0, so I would be happy for them to replace 2.10.0 on the web sites as soon as they pass a collective sanity check from people here. If you find new bugs, that's fine, but unless they are regressions since 2.10.0 (which is unlikely, hopefully) then they should not block releasing; they can be fixed in a (hypothetical!) 2.10.2 or wait until 2.12. In particular the Windows builds include the UTF-8 pathname fix which is significant for various people, I believe. Regards, James -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ 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 -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On Wed, 3 Apr 2013, Curtis Olson wrote: Hi James, This is great news if you are able to crank out full installers right from Jenkins. That will save me a bunch of downloading and hours of uploading for every new release candidate. It might be a good idea to create a script that will distribute the new builds to the various mirrors. That way I'm less likely to throttle the machine to 10k/sec when it hammers whatever I'm watching on Netflix at the time. :D g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.diy-cockpits.org/coll - Go Collimated or Go Home. Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi James, you could also automatically seed them in BitTorrent, on a Linux box you can use btmakemetafile which I use here to generate those update packages on my tracker [1]. Roland [1]: http://mxchange.org:23456/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFcobEACgkQty+BhcbHvXiFbwCgkC4VyzAOvxEDHBQ5x+nMxtSf M1MAn3RqGl7nCEdyuWQ0kT78D/MoyHjQ =8mS8 -END PGP SIGNATURE- -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi James, you could also automatically seed them in BitTorrent, on a Linux box you can use btmakemetafile which I use here to generate those update packages on my tracker [1]. Roland [1]: http://mxchange.org:23456/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlFcobAACgkQty+BhcbHvXitIQCgvfIyXKDcl5mbKb8uXBLAfKUq /5cAn3thIyON7+u+fwH5g97iHHxExzn4 =/NXT -END PGP SIGNATURE- -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 16 Mar 2013, at 20:49, Pat pat.callah...@gmail.com wrote: what's the relationship between 2.10.0 the maint branch and 2.10.1? 2.10.1 will be released from the 2.10 branch, when I start picking commits. I'm going to bump the version files on the branch 'now' aka once I've had a cup of tea :) James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 17 Mar 2013, at 09:27, James Turner zakal...@mac.com wrote: 2.10.1 will be released from the 2.10 branch, when I start picking commits. I'm going to bump the version files on the branch 'now' aka once I've had a cup of tea :) Branches are updated, and the initial fixes I know of / were mentioned here have been merged to all three. Jenkins will get to work soon / now, though I need to do some steps on Windows to make that fully automated. What I've merged so far: - Windows non-ASCII path fix (bug 1055) - this one is quite significant - Fix for ILS not visible on the map during first run due to a caching bug - udev include guard fix - Nasal tanker heading fix from Jano - ZLT_NT mast fixes from AndersG - Saitek X52 fixes from Keiran Smith Any others suggestions are welcome. There was a change Stuart made early after the 2.10 branch, which I was considering, but I've totally forgotten what it was now, will dig through the mail archives and see if I can find it. Regards, James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 17 Mar 2013, at 10:33, James Turner zakal...@mac.com wrote: Any others suggestions are welcome. There was a change Stuart made early after the 2.10 branch, which I was considering, but I've totally forgotten what it was now, will dig through the mail archives and see if I can find it. Which I've now found and merged. James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
what's the relationship between 2.10.0 the maint branch and 2.10.1? -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi all, (2013/03/14 7:11), Frederic Bouvier wrote: With regard to the Windows release, after installing Setup Flightgear 2.10.0.3.exe on Windows XP, when launching fgrun I immediately get the following error/warning: There is no disk in the drive. Please insert a disk into drive D:. It does it upon launch of fgrun, and it will also do it later upon selection of the dhc2 aircraft. After removing all aircraft and cleaning out the fgrun preferences file, fgrun still gripes about no disk in drive D: on launch.Everything still works if one simply selects Continue, though it's a bit annoying. BTW, D: is the drive where Jenkins builds windows binaries, so it should be something like a build path configured in the generated binaries. I might find one possible reason for the issue. Aircraft/dhc2/Models/dhc2.ac includes texture D:/Git_New/my_fgdata/Aircraft/dhc2/white.png on lines 1303, 1740, 3615, 5310 and 7174, which will cause file accesses to drive D. I also checked other aircraft files from git repo, and found other three files include the path to D:/Git_New: Aircraft/Buccaneer/Models/buccaneer.ac Aircraft/Buccaneer/Models/flap.ac Aircraft/Hurricane/Models/hurricane-ver-26.ac Just for reference about how to test. Following advice in http://code.google.com/p/flightgear-bugs/issues/detail?id=284#c66 , I launched process monitor from Microsoft, watched file access of fgrun when dhc2 was selected, and then I got following results: C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2 NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2 NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\white.png NAME NOT FOUND C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\white.png Cheers, Toshi -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Just for reference about how to test. Following advice in http://code.google.com/p/flightgear-bugs/issues/detail?id=284#c66 , I launched process monitor from Microsoft, watched file access of fgrun when dhc2 was selected, and then I got following results: C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2 NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2 NAME INVALID C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\D:\Git_New\my_fgdata\Aircraft\dhc2\white.png NAME INVALID C:\Program Files\FlightGear\white.png NAME NOT FOUND C:\Program Files\FlightGear\data\Aircraft\dhc2\Models\white.png Cheers, Toshi Interesting. It appears 'someone' introduced this while making these aircraft rembrandt compatible.I'll fix the dhc-2. Syd -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Just to check, will both Flightgear and Simgear be updated to 2.10.1, or just Flightgear? Saikrishna Arcot On Wed 13 Mar 2013 08:31:40 AM CDT, James Turner wrote: Hi, As previously suggested, I am going to attempt a 2.10.1 release, to see if this improves our perceived quality. There's some bug fixes I am already aware of, including a Windows path-handling one which is quite significant. I would appreciate nominations for other bug-fixes and low-risk tweaks, to be merged to the release branches, including fgdata. Ideally give me SHAs of commits on next, which I can safely cherry pick to the release branches - if commits need editing, a merge-request would be easier for me to process. Or you can merge yourself to the release branches, providing you exercise suitable diligence :) Regards, James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi James, sounds good, even if there are only a small number (1 or more) important fixes. Would it make sense to amend our release procedure (Torsten) :-) to include a subsection on sub-release procedures. Under the hood we probably repeat most of the full release procedure, but maybe we'd want to give a defined timeline for a dot release to collect the requested patches nominations, maybe (?) push out a release candidate (?), and then a final release. We should keep it as simple as possible -- too complicated and too much work and it won't happen, but some organization and coordination and procedure may not hurt, just so we are all on the same page. Thanks, Curt. On Wed, Mar 13, 2013 at 8:31 AM, James Turner wrote: Hi, As previously suggested, I am going to attempt a 2.10.1 release, to see if this improves our perceived quality. There's some bug fixes I am already aware of, including a Windows path-handling one which is quite significant. I would appreciate nominations for other bug-fixes and low-risk tweaks, to be merged to the release branches, including fgdata. Ideally give me SHAs of commits on next, which I can safely cherry pick to the release branches - if commits need editing, a merge-request would be easier for me to process. Or you can merge yourself to the release branches, providing you exercise suitable diligence :) Regards, James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ 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 -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
So far I can think of two fixes: 0b04458e99689a30f668d1b37bce93fa55149a2b b71e703d75d19dff698b38177f319c6baa76a277 Will let you know when I find more. Gijs -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 13 Mar 2013, at 13:51, Gijs de Rooy gijsr...@hotmail.com wrote: 0b04458e99689a30f668d1b37bce93fa55149a2b b71e703d75d19dff698b38177f319c6baa76a277 You know, saying which repository, and a one line description of the fix, would really save me some typing and git calls :) James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On 13 Mar 2013, at 13:35, Saikrishna Arcot saiarcot...@gmail.com wrote: Just to check, will both Flightgear and Simgear be updated to 2.10.1, or just Flightgear? All three - simgear, flightgear and fgdata - since the fixes span all three. James -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
On Wed, Mar 13, 2013 at 9:31 AM, James Turner zakal...@mac.com wrote: Hi, As previously suggested, I am going to attempt a 2.10.1 release, to see if this improves our perceived quality. There's some bug fixes I am already aware of, including a Windows path-handling one which is quite significant. I would appreciate nominations for other bug-fixes and low-risk tweaks, to be merged to the release branches, including fgdata. Ideally give me SHAs of commits on next, which I can safely cherry pick to the release branches - if commits need editing, a merge-request would be easier for me to process. Or you can merge yourself to the release branches, providing you exercise suitable diligence :) Regards, James Howdy James, With regard to the Windows release, after installing Setup Flightgear 2.10.0.3.exe on Windows XP, when launching fgrun I immediately get the following error/warning: There is no disk in the drive. Please insert a disk into drive D:. It does it upon launch of fgrun, and it will also do it later upon selection of the dhc2 aircraft. After removing all aircraft and cleaning out the fgrun preferences file, fgrun still gripes about no disk in drive D: on launch.Everything still works if one simply selects Continue, though it's a bit annoying. I haven't seen this mentioned elsewhere, though I didn't search rigorously. If this is related to the Windows path-handling thing, then please ignore me. :) -Gary aka Buckaroo -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
Hi, - Mail original - De: Gary Neely grne...@gmail.com On Wed, Mar 13, 2013 at 9:31 AM, James Turner zakal...@mac.com wrote: Hi, As previously suggested, I am going to attempt a 2.10.1 release, to see if this improves our perceived quality. There's some bug fixes I am already aware of, including a Windows path-handling one which is quite significant. I would appreciate nominations for other bug-fixes and low-risk tweaks, to be merged to the release branches, including fgdata. Ideally give me SHAs of commits on next, which I can safely cherry pick to the release branches - if commits need editing, a merge-request would be easier for me to process. Or you can merge yourself to the release branches, providing you exercise suitable diligence :) Regards, James Howdy James, With regard to the Windows release, after installing Setup Flightgear 2.10.0.3.exe on Windows XP, when launching fgrun I immediately get the following error/warning: There is no disk in the drive. Please insert a disk into drive D:. It does it upon launch of fgrun, and it will also do it later upon selection of the dhc2 aircraft. After removing all aircraft and cleaning out the fgrun preferences file, fgrun still gripes about no disk in drive D: on launch.Everything still works if one simply selects Continue, though it's a bit annoying. I haven't seen this mentioned elsewhere, though I didn't search rigorously. If this is related to the Windows path-handling thing, then please ignore me. :) It looks like we forgot lesson learned with issue #284 :( I am fixing Jenkins right now. Regards, -Fred -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.10.1
With regard to the Windows release, after installing Setup Flightgear 2.10.0.3.exe on Windows XP, when launching fgrun I immediately get the following error/warning: There is no disk in the drive. Please insert a disk into drive D:. It does it upon launch of fgrun, and it will also do it later upon selection of the dhc2 aircraft. After removing all aircraft and cleaning out the fgrun preferences file, fgrun still gripes about no disk in drive D: on launch.Everything still works if one simply selects Continue, though it's a bit annoying. I haven't seen this mentioned elsewhere, though I didn't search rigorously. If this is related to the Windows path-handling thing, then please ignore me. :) It looks like we forgot lesson learned with issue #284 :( I am fixing Jenkins right now. After further verifications, it isn't the case. Configuration option is still there. BTW, D: is the drive where Jenkins builds windows binaries, so it should be something like a build path configured in the generated binaries. Regards, -Fred -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
