Re: [Flightgear-devel] FlightGear prerelease
On Saturday 08 December 2007 23:13, Tatsuhiro Nishioka wrote: Thanks AJ! Durk, could you apply my patch to CVS? Thanks, Tat Looks like Melchior already beat me... :-) Thanks for looking into this. Cheers, Durk - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Tatsuhiro Nishioka schrieb:
Hi,
I found kind of a hint of the cause of DList stack overflow.
After reset, the number of ssgTransform increases a lot.
so maybe this has something to do with the cause of the problem since
ssgTransform::cull calls _ssgPushMatrix and _ssgPopMatrix. these two
show DList stack overflow error.
Plus, this problem doesn't happen when --disable-ai-models is specified.
When I commented outscenarionimitz_demo/scenario from
preferences.xml,
this DL stack overflow doesn't happen even without --disable-ai-models.
So resetting carrier object in AICarrier::init() or methods called
from init() probably generates
redundant or unexpected ssgTransform objects.
I'll dive deeper tomorrow.
If any of you have any idea on what causes this, please let me know.
Best,
Tat
On Dec 8, 2007, at 2:49 AM, Tatsuhiro Nishioka wrote:
Hi Tat,
I tried your diff but my actual CVS source (did a fresh update before
applying the diff) gives some rejections.
It might be that you build the diff against an older source?
Here an example of one rejection:
*
AIBase.cxx
*
***
*** 179,185
}
From your diff:
- if (model) {
aip.init( model );
aip.setVisible(true);
invisible = false;
--- 180,188
Actual CVS:
if (model.get()) {
aip.init( model.get() );
aip.setVisible(true);
invisible = false;
}
...
Regards
Georg
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Tatsuhiro Nishioka schrieb: Hi Georg, Of course it should be rejected since you applied it to too new code. The patch is for 0.9.11-pre2 release, not for CVS head. Check out source files using -r RELEASE_0_9_11_pre2 option and apply it again. Best, Tat Hello Tat, thank you for the info. I will try later, might be this evening, due to real life work. Georg - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi Georg,
Of course it should be rejected since you applied it to too new code.
The patch is for 0.9.11-pre2 release, not for CVS head.
Check out source files using -r RELEASE_0_9_11_pre2 option and apply
it again.
Best,
Tat
On Dec 8, 2007, at 6:37 PM, Georg Vollnhals wrote:
Hi Tat,
I tried your diff but my actual CVS source (did a fresh update before
applying the diff) gives some rejections.
It might be that you build the diff against an older source?
Here an example of one rejection:
*
AIBase.cxx
*
***
*** 179,185
}
From your diff:
- if (model) {
aip.init( model );
aip.setVisible(true);
invisible = false;
--- 180,188
Actual CVS:
if (model.get()) {
aip.init( model.get() );
aip.setVisible(true);
invisible = false;
}
...
Regards
Georg
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
-
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi guys, Finally I found the cause of DList stack overflow and off-carrier aircraft problem. The cause of the first one is that aip.ssgTransform of AICarrier are unexpectedly registered on every reset in AIBase::init(). The second one is caused by ssgEntry related code in AICarrier::init(). So I made a patch for doing these process only in the first init() calls. Now, off-carrier aircraft and DList stack overflow are not feature anymore. Enclosed is the patch for solving these problems. I want you guys to test this on your platforms. I don't think this affects any other AI objects' reinit() as far as I've tested but this should be tested on many machines. If it works on some platforms, then I'll ask Durk to apply it. By the way, I've encountered that aircraft doesn't follow the movement of Nimitz while testing this patch. In this case, simply remove ~/.fgfs/autosave.xml can fix this problem. You can also fix it by changing Rendering options and exit fgfs by pressing ESC. Best, Tat On Dec 8, 2007, at 8:44 AM, Tatsuhiro Nishioka wrote: Hi, I found kind of a hint of the cause of DList stack overflow. After reset, the number of ssgTransform increases a lot. so maybe this has something to do with the cause of the problem since ssgTransform::cull calls _ssgPushMatrix and _ssgPopMatrix. these two show DList stack overflow error. Plus, this problem doesn't happen when --disable-ai-models is specified. When I commented outscenarionimitz_demo/scenario from preferences.xml, this DL stack overflow doesn't happen even without --disable-ai- models. So resetting carrier object in AICarrier::init() or methods called from init() probably generates redundant or unexpected ssgTransform objects. I'll dive deeper tomorrow. If any of you have any idea on what causes this, please let me know. Best, Tat FlightGear-DListStackOverflow.diff Description: Binary data - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Saturday 08 December 2007 09:04:18 Tatsuhiro Nishioka wrote: Finally I found the cause of DList stack overflow and off-carrier aircraft problem. Now, off-carrier aircraft and DList stack overflow are not feature anymore. If it works on some platforms, then I'll ask Durk to apply it. I'd like to report that it worked perfectly for me on Linux, and that aircraft ending up under the carrier on reset bug was very annoying indeed (especially given the risky nature of carrier ops ;-) This would be one fix well worth applying before the release - I hope it can be committed so that it gets proper testing. Cheers, AJ - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Thanks AJ! Durk, could you apply my patch to CVS? Thanks, Tat On Dec 9, 2007, at 6:48 AM, AJ MacLeod wrote: On Saturday 08 December 2007 09:04:18 Tatsuhiro Nishioka wrote: Finally I found the cause of DList stack overflow and off-carrier aircraft problem. Now, off-carrier aircraft and DList stack overflow are not feature anymore. If it works on some platforms, then I'll ask Durk to apply it. I'd like to report that it worked perfectly for me on Linux, and that aircraft ending up under the carrier on reset bug was very annoying indeed (especially given the risky nature of carrier ops ;-) This would be one fix well worth applying before the release - I hope it can be committed so that it gets proper testing. Cheers, AJ - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Tatsuhiro Nishioka -- Saturday 08 December 2007: Durk, could you apply my patch to CVS? Too late! Already committed. Thanks. :-) m. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Haha, quick work. Thanks a lot! On Dec 9, 2007, at 7:19 AM, Melchior FRANZ wrote: * Tatsuhiro Nishioka -- Saturday 08 December 2007: Durk, could you apply my patch to CVS? Too late! Already committed. Thanks. :-) m. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On ven 7 décembre 2007, Tatsuhiro Nishioka wrote: Goorg, and Melchir, Thanks for your report and opinion. On Dec 8, 2007, at 1:09 AM, Georg Vollnhals wrote: Hi Tat, tested this on OpenSUSE 10.2 86_64 with FG 9.11 Prerelease S76 Helicopter 1. DList stack overflow (snip) NEGATIVE Yes, my fingers are aching ... pressed more than 30 times SHIFT-ESC = NO problem here OK, so this is a Mac OS specific bug. 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. Don't worry, it is not only a Mac OS specific bug it is an old bug. I have it on PC with Linux Best, Tat Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Goorg, and Melchir, Thanks for your report and opinion. On Dec 8, 2007, at 1:09 AM, Georg Vollnhals wrote: Hi Tat, tested this on OpenSUSE 10.2 86_64 with FG 9.11 Prerelease S76 Helicopter 1. DList stack overflow (snip) NEGATIVE Yes, my fingers are aching ... pressed more than 30 times SHIFT-ESC = NO problem here OK, so this is a Mac OS specific bug. 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. POSITIVE Found the S76 on the water and the carrier moving away :-( Got it! On Dec 8, 2007, at 2:12 AM, Melchior FRANZ wrote: * Tatsuhiro Nishioka -- Friday 07 December 2007: 1. DList stack overflow I've seen them on other occasions in fg/plib. Haven't tried with Shift-Esc, but I think that's a plib problem. Don't think that's something we can fix before the release. It's definitely not one of bugs that people usually report. More of a Doctor, it hurts problem. :-) Haha, though I don't think it's Doctor, it hurts thing since it actually occurs on Mac OS, I understand that we can't fix it before the release. So I'm going to notice that there is a problem on sequential resets on Mac OS X in the release note if I can't find the cause of the problem by the time of the release. I'm going to trace some code that uses DList push/pop during reset. If someone already know what functions uses these on reset, please let me know. 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. I've been told that this is a ... feature. :-/ Oh... but I don't buy that idea since it's not a product made by MS :-p Anyway, I'm trying to find the cause of this issue, finding the ground elevation gets negative value when reset. I force adjusted the ground elevation value when reset on Nimitz for test, but A6M2 fell down onto the sea anyway. so that's not the real cause. I hope I can find the real cause of this soon. Best, Tat - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi there, I want to know if the bugs that I reported before are Mac OS specific or not. So I want you guys to check if the following bugs occur on your platform(s). 1. DList stack overflow When I reset fgfs by pressing Shift-ESC for several times (maybe 10 times), DList stack overflow occurs. This problem has something to do with the flying instruments problem that I posted before since the instruments start flying when DList stack overflows occur 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. If these are Mac OS specific, then I'm going to find the causes to make patches. By the way, can I have a CVS account? Thanks in advance. Tat - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi, I found kind of a hint of the cause of DList stack overflow. After reset, the number of ssgTransform increases a lot. so maybe this has something to do with the cause of the problem since ssgTransform::cull calls _ssgPushMatrix and _ssgPopMatrix. these two show DList stack overflow error. Plus, this problem doesn't happen when --disable-ai-models is specified. When I commented outscenarionimitz_demo/scenario from preferences.xml, this DL stack overflow doesn't happen even without --disable-ai-models. So resetting carrier object in AICarrier::init() or methods called from init() probably generates redundant or unexpected ssgTransform objects. I'll dive deeper tomorrow. If any of you have any idea on what causes this, please let me know. Best, Tat On Dec 8, 2007, at 2:49 AM, Tatsuhiro Nishioka wrote: Goorg, and Melchir, Thanks for your report and opinion. On Dec 8, 2007, at 1:09 AM, Georg Vollnhals wrote: Hi Tat, tested this on OpenSUSE 10.2 86_64 with FG 9.11 Prerelease S76 Helicopter 1. DList stack overflow (snip) NEGATIVE Yes, my fingers are aching ... pressed more than 30 times SHIFT-ESC = NO problem here OK, so this is a Mac OS specific bug. 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. POSITIVE Found the S76 on the water and the carrier moving away :-( Got it! On Dec 8, 2007, at 2:12 AM, Melchior FRANZ wrote: * Tatsuhiro Nishioka -- Friday 07 December 2007: 1. DList stack overflow I've seen them on other occasions in fg/plib. Haven't tried with Shift-Esc, but I think that's a plib problem. Don't think that's something we can fix before the release. It's definitely not one of bugs that people usually report. More of a Doctor, it hurts problem. :-) Haha, though I don't think it's Doctor, it hurts thing since it actually occurs on Mac OS, I understand that we can't fix it before the release. So I'm going to notice that there is a problem on sequential resets on Mac OS X in the release note if I can't find the cause of the problem by the time of the release. I'm going to trace some code that uses DList push/pop during reset. If someone already know what functions uses these on reset, please let me know. 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. I've been told that this is a ... feature. :-/ Oh... but I don't buy that idea since it's not a product made by MS :-p Anyway, I'm trying to find the cause of this issue, finding the ground elevation gets negative value when reset. I force adjusted the ground elevation value when reset on Nimitz for test, but A6M2 fell down onto the sea anyway. so that's not the real cause. I hope I can find the real cause of this soon. Best, Tat - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Tatsuhiro Nishioka wrote: Hi there, I want to know if the bugs that I reported before are Mac OS specific or not. So I want you guys to check if the following bugs occur on your platform(s). 1. DList stack overflow When I reset fgfs by pressing Shift-ESC for several times (maybe 10 times), DList stack overflow occurs. This problem has something to do with the flying instruments problem that I posted before since the instruments start flying when DList stack overflows occur Happens here too on Gentoo Linux (x64_64) but not often. 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. Happens here too. If these are Mac OS specific, then I'm going to find the causes to make patches. By the way, can I have a CVS account? Thanks in advance. Tat -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHWajMWmK6ng/aMNkRChpRAKC+MDYd0ww6Hjd8culSyDu+vm90UwCdFDAd tycH16Y1znnzE5cwaT4sOvc= =nzjR -END PGP SIGNATURE- - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Georg Vollnhals Sent: 07 December 2007 16:10 To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FlightGear prerelease ... Snip ... 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. This is a bug which we never got around to fixing, so I guess we should call it a feature now. Vivian - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Tatsuhiro Nishioka -- Friday 07 December 2007: 1. DList stack overflow I've seen them on other occasions in fg/plib. Haven't tried with Shift-Esc, but I think that's a plib problem. Don't think that's something we can fix before the release. It's definitely not one of bugs that people usually report. More of a Doctor, it hurts problem. :-) 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. I've been told that this is a ... feature. :-/ m. - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Tatsuhiro Nishioka schrieb: Hi there, I want to know if the bugs that I reported before are Mac OS specific or not. So I want you guys to check if the following bugs occur on your platform(s). Hi Tat, tested this on OpenSUSE 10.2 86_64 with FG 9.11 Prerelease S76 Helicopter 1. DList stack overflow When I reset fgfs by pressing Shift-ESC for several times (maybe 10 times), DList stack overflow occurs. This problem has something to do with the flying instruments problem that I posted before since the instruments start flying when DList stack overflows occur NEGATIVE Yes, my fingers are aching ... pressed more than 30 times SHIFT-ESC = NO problem here 2. Aircraft shows up under a carrier on reset This happens when I reset FlightGear (Shift-ESC) on Nimitz. POSITIVE Found the S76 on the water and the carrier moving away :-( Regards Georg EDDW - SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Am Dienstag, den 04.12.2007, 22:46 +0100 schrieb Melchior FRANZ: * Durk Talsma -- Tuesday 04 December 2007: data/Aircraft/737-300 \ Yes, I'd swap that with the 787. A flat panel that disappears when you look left/right is hard to bear. (Though I miss a VOR display on the 787. Need to search for that ...) data/Aircraft/A-10 \ Good choice. Very detailed, very good quality. data/Aircraft/bf109 \ Hmm ... it's well done and all, but I think it's too realistic, read: too hard to take off/land due to the very narrow gear. Well, that's how an aircraft with 1700 hp and a wing similar in size to a Cessna behaves. With any taildragger you are bound to heavy rudder usage. Especially in cross wind and a hard runway surface. The A6M2 would IMHO be a better choice (or the fw190, but I think that's not finished yet). I'm glad you like the fw190, but I won't be able to bring the fw190 up to the bf109s features (3D Cockpit, livery select, hotspots, selectable externals, engine behaviour, startup sequence, tutorials) within this short time. Unfortunatly we haven't discussed this earlier. data/Aircraft/bo105 \ Good choice, of course. Approved by a real bo105 pilot (very impressed). :-) data/Aircraft/c172 \ data/Aircraft/c172p \ use pa24 instead? But I see the pa28 further down, so ... data/Aircraft/c310 \ data/Aircraft/c310u3a \ use Seneca instead? data/Aircraft/f16 \ Totally broken! Don't ship this! The FCS winds up after a few minutes and kills you. Very frustrating. After starting fgfs, let is parked for a few minutes, then try to fly it. Good luck! (Though the HUD is nice. :-) data/Aircraft/wrightFlyer1903 \ Waste of disk space. Everyone tries it once or twice, and never again, because it's just *boring* Greetings -- Detlef Faber http://www.sol2500.net/flightgear - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On mer 5 décembre 2007, Melchior FRANZ wrote: * Jon S. Berndt -- Wednesday 05 December 2007: I believe recent enhancements and fixes in JSBSim may have fixed the F-16, but I'm not sure. Well, not in FlightGear's CVS, though it may have improved a bit. BTW: I reported that problem a least twice to Erik and once to Dave. m. Hello, The F16 was/is a wonderful Aircraft to fly. I never noticed any problem with it (but in the old time 2004 ? 2005 ?) Sure the recent JSBSim improvements will probably improve every Aircraft which are JSBSim FDM. Regarding the F16 i can notice about Mirage2000 this Models a Mirage 2000C/RDI based on the F-16A Block-32 from Erik Hofman Regarding JSBSim, we could notice, according to the list of aircraft which are proposed, a decrease of the number of aircraft which are JSBSim FDM. Don't we have to take care, and to keep a balance like it was before ? I hope that, in the future, JSBSim will not be only a stand alone system out of FlightGear Regards -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On mer 5 décembre 2007, Melchior FRANZ wrote: * Jon S. Berndt -- Wednesday 05 December 2007: I wonder if it is a platform-specific issue? Extremely unlikely. But this could play a role: my js has the centering spring deactivated. So, when I have the f16 parked, this is often with elevator and ailerons fully applied in one direction. This will make the winding-up of the PID much more obvious here. Try this: $ fgfs --aircraft=f16-3d --airport=knuq Then apply full elevator/aileron/rudder for one minute. Then start and enjoy. I you do that for two minutes, then you won't survive longer than a few seconds after lift-off. m. Ouups, this not an explanation with your problem, here i don't use any joystick , only keyboard and mouse. Regards BTW: I am too lazy to include my pedals and two joysticks which remains in in a dusty box :) -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Jon S. Berndt -- Wednesday 05 December 2007: If the F16 is broken now it should not be included. It shouldn't be hard for someone with some JSBSim insight to fix it. When I told Dave about the problem, he suggested to replace the elevator FCS part by the one of the 737, and this did indeed work. But then I noticed that the aileron has the same problem, and if I'd replace half of the f16 with 737 parts, then it wouldn't be an f16, but an f737. :-) BTW: the problem started with an JSBSim update. I reported that problem the first time on 2004/06/15. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
About f16-3d I just tried again it, flying with it 15 minutes over the Mediterranean sea from LFTH, i did not notice the problems you have. I confirm that it is a nice Model to fly, probably easier than the real one. Does it mean that the computer configuration is involved ? the FDM becoming crazy. Mine is 32 bits AMD Athlon 3200 with GPU Nvidia 7800GS (full screen 1800x1440 oversea i get more than 100 fps) Regards -- Gérard It has been a while since I flew the F-16, but as I recall, I didn't notice any problems, either. I wonder if it is a platform-specific issue? I did see the bug reports, and I thought that those concerns were addressed. Jon - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* gerard robin -- Wednesday 05 December 2007: Don't we have to take care, and to keep a balance like it was before ? You mean, we have to ship FlightGear v1.0 with as many broken aircraft as working ones, for balancing reasons? :-} m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Detlef Faber -- Wednesday 05 December 2007: Am Dienstag, den 04.12.2007, 22:46 +0100 schrieb Melchior FRANZ: Hmm ... it's well done and all, but I think it's too realistic, read: too hard to take off/land due to the very narrow gear. Well, that's how an aircraft with 1700 hp and a wing similar in size to a Cessna behaves. With any taildragger you are bound to heavy rudder usage. Especially in cross wind and a hard runway surface. You don't have to explain me that this is caused by the design of the real thing. That's what I was saying. I just think that a difficult to handle aircraft might not be ideal for the default set. But then again, the v22 isn't easy to handle, either. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Melchior FRANZ -- Wednesday 05 December 2007: my js has the centering spring deactivated. [...] Of course, I expect now someone to point out that most people don't have their springs removed, so we can ship the f16 as is. And I can't even disagree ... strongly. :-) m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Jon S. Berndt -- Wednesday 05 December 2007: I wonder if it is a platform-specific issue? Extremely unlikely. But this could play a role: my js has the centering spring deactivated. So, when I have the f16 parked, this is often with elevator and ailerons fully applied in one direction. This will make the winding-up of the PID much more obvious here. Try this: $ fgfs --aircraft=f16-3d --airport=knuq Then apply full elevator/aileron/rudder for one minute. Then start and enjoy. I you do that for two minutes, then you won't survive longer than a few seconds after lift-off. m. PS: I didn't have the spring removed when I first reported the problem in 2004. It seems better now, but it's still an ugly bug. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Jon S. Berndt -- Wednesday 05 December 2007: If the F16 is broken now it should not be included. It shouldn't be hard for someone with some JSBSim insight to fix it. When I told Dave about the problem, he suggested to replace the elevator FCS part by the one of the 737, and this did indeed work. But then I noticed that the aileron has the same problem, and if I'd replace half of the f16 with 737 parts, then it wouldn't be an f16, but an f737. :-) BTW: the problem started with an JSBSim update. I reported that problem the first time on 2004/06/15. m. I'll take another look at it today. It might be tomorrow before I can report anything. I can check for obvious problems, though at this point I won't be able to fly it in a recent version of FlightGear. There were some major changes in the past couple of years, but I thought I had eventually upgraded all of the aircraft models. I'll find out about the F-16. Jon - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On mer 5 décembre 2007, Melchior FRANZ wrote: * gerard robin -- Wednesday 05 December 2007: Don't we have to take care, and to keep a balance like it was before ? You mean, we have to ship FlightGear v1.0 with as many broken aircraft as working ones, for balancing reasons? :-} m. Broken ??? I don't understand, these aircraft are not broken. May be we don't have the same definition of it, or we can say that every aircraft are broken because not close to the real ones. Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Yes, the selection should be balanced. A representative of every class that the users would be interested in, especially well done ones (with 3D cockpit) that don't consume excessive disk space, but more importantly: download volume. And they should be flyable, too. I couldn't care less which FDMs they use. I'd have no problem if they'd all be JSBSim or all YASim. The receivers probably give a damn about the FDM. The selection is for them, not for us. And if tried to be balanced, then what about UIUC and LaRCSim? Yes, the f16 is broken. I just tried it. After a few minutes you see how the FCS is starting to misbehave. The f16 starts pulling to the right and up, etc. That's most noticeable after you had it parked for some minutes. It can become completely unflyable. I don't see use ship a broken aircraft that the authors didn't care to fix despite several bug reports. But well, I don't decide that anyway. m. Melchior, I agree with you. If the F16 is broken now it should not be included. Jon - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* gerard robin -- Wednesday 05 December 2007: On mer 5 décembre 2007, Melchior FRANZ wrote: You mean, we have to ship FlightGear v1.0 with as many broken aircraft as working ones, for balancing reasons? :-} Broken ??? I don't understand, these aircraft are not broken. That was just irony. I suggested not to include the f16 because it's broken. And you said it's wonderful and we need more JSBSim aircraft for balancing reasons. Yes, the selection should be balanced. A representative of every class that the users would be interested in, especially well done ones (with 3D cockpit) that don't consume excessive disk space, but more importantly: download volume. And they should be flyable, too. I couldn't care less which FDMs they use. I'd have no problem if they'd all be JSBSim or all YASim. The receivers probably give a damn about the FDM. The selection is for them, not for us. And if tried to be balanced, then what about UIUC and LaRCSim? Yes, the f16 is broken. I just tried it. After a few minutes you see how the FCS is starting to misbehave. The f16 starts pulling to the right and up, etc. That's most noticeable after you had it parked for some minutes. It can become completely unflyable. I don't see use ship a broken aircraft that the authors didn't care to fix despite several bug reports. But well, I don't decide that anyway. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Jon S. Berndt -- Wednesday 05 December 2007: I believe recent enhancements and fixes in JSBSim may have fixed the F-16, but I'm not sure. Well, not in FlightGear's CVS, though it may have improved a bit. BTW: I reported that problem a least twice to Erik and once to Dave. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On mer 5 décembre 2007, Melchior FRANZ wrote: * gerard robin -- Wednesday 05 December 2007: On mer 5 décembre 2007, Melchior FRANZ wrote: You mean, we have to ship FlightGear v1.0 with as many broken aircraft as working ones, for balancing reasons? :-} Broken ??? I don't understand, these aircraft are not broken. That was just irony. I suggested not to include the f16 because it's broken. And you said it's wonderful and we need more JSBSim aircraft for balancing reasons. SNIP Yes, the f16 is broken. I just tried it. After a few minutes you see how the FCS is starting to misbehave. The f16 starts pulling to the right and up, etc. That's most noticeable after you had it parked for some minutes. It can become completely unflyable. I don't see use ship a broken aircraft that the authors didn't care to fix despite several bug reports. But well, I don't decide that anyway. m. About f16-3d I just tried again it, flying with it 15 minutes over the Mediterranean sea from LFTH, i did not notice the problems you have. I confirm that it is a nice Model to fly, probably easier than the real one. Does it mean that the computer configuration is involved ? the FDM becoming crazy. Mine is 32 bits AMD Athlon 3200 with GPU Nvidia 7800GS (full screen 1800x1440 oversea i get more than 100 fps) Regards -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Thursday 22 November 2007 07:36, Durk Talsma wrote: This is a quick note to everybody: I'm planning to build an official FlightGear pre-release tonight. I did a full dress rehearsal last sunday and that all seemed to work well, but I still needed Curt's okay for a few remaining issues. In the mean time, if there are any *urgent* patches remaining please try to get them into CVS ASAP. FWIW, FlightGear/PLIB is probably in a releasable state as it is, but given the time since the last release, there may be riding a lot of expectancy on this release, so I'd like to be a little more careful and to at least one more pre-release -and should any problems arise- a second one. To follow up on this: It seems like the initial testing round went pretty well, with mostly minor problems being reported, and many of them being fixed already. I'm hoping to roll up the tar files for the release itself this weekend. I'm not sure whether we'll be able to transfer those to the main webserver instantly, as there were some problems recently. If not, I hope that John Wojnaroski can again provide some server space. In the mean time, I guess we need to make a final decision on the version number... Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/Generic \ data/Aircraft/Instruments \ data/Aircraft/Instruments-3d \ data/Aircraft/UIUC \ data/Aircraft/737-300 \ data/Aircraft/A-10 \ data/Aircraft/bf109 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation-Bravo \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/Rascal \ data/Aircraft/T38 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Cheers, Durk - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Durk Talsma -- Tuesday 04 December 2007: data/Aircraft/737-300 \ Yes, I'd swap that with the 787. A flat panel that disappears when you look left/right is hard to bear. (Though I miss a VOR display on the 787. Need to search for that ...) data/Aircraft/A-10 \ Good choice. Very detailed, very good quality. data/Aircraft/bf109 \ Hmm ... it's well done and all, but I think it's too realistic, read: too hard to take off/land due to the very narrow gear. The A6M2 would IMHO be a better choice (or the fw190, but I think that's not finished yet). data/Aircraft/bo105 \ Good choice, of course. Approved by a real bo105 pilot (very impressed). :-) data/Aircraft/c172 \ data/Aircraft/c172p \ use pa24 instead? But I see the pa28 further down, so ... data/Aircraft/c310 \ data/Aircraft/c310u3a \ use Seneca instead? data/Aircraft/f16 \ Totally broken! Don't ship this! The FCS winds up after a few minutes and kills you. Very frustrating. After starting fgfs, let is parked for a few minutes, then try to fly it. Good luck! (Though the HUD is nice. :-) data/Aircraft/wrightFlyer1903 \ Waste of disk space. Everyone tries it once or twice, and never again, because it's just *boring*. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I would suggest including the lightning instead of f16, lightning is really good quality and both are fighters. Regards, Arvid Norlander Melchior FRANZ wrote: * Durk Talsma -- Tuesday 04 December 2007: data/Aircraft/737-300 \ Yes, I'd swap that with the 787. A flat panel that disappears when you look left/right is hard to bear. (Though I miss a VOR display on the 787. Need to search for that ...) data/Aircraft/A-10 \ Good choice. Very detailed, very good quality. data/Aircraft/bf109 \ Hmm ... it's well done and all, but I think it's too realistic, read: too hard to take off/land due to the very narrow gear. The A6M2 would IMHO be a better choice (or the fw190, but I think that's not finished yet). data/Aircraft/bo105 \ Good choice, of course. Approved by a real bo105 pilot (very impressed). :-) data/Aircraft/c172 \ data/Aircraft/c172p \ use pa24 instead? But I see the pa28 further down, so ... data/Aircraft/c310 \ data/Aircraft/c310u3a \ use Seneca instead? data/Aircraft/f16 \ Totally broken! Don't ship this! The FCS winds up after a few minutes and kills you. Very frustrating. After starting fgfs, let is parked for a few minutes, then try to fly it. Good luck! (Though the HUD is nice. :-) data/Aircraft/wrightFlyer1903 \ Waste of disk space. Everyone tries it once or twice, and never again, because it's just *boring*. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVcu3WmK6ng/aMNkRCli0AKCHnb5sopm8HyMAIBFKwZiGcC1mDACgsatD gthI7NqIvTwpS3741SGKr6A= =jad0 -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Durk Talsma [EMAIL PROTECTED] schrieb: On Thursday 22 November 2007 07:36, Durk Talsma wrote: This is a quick note to everybody: I'm planning to build an official FlightGear pre-release tonight. I did a full dress rehearsal last sunday and that all seemed to work well, but I still needed Curt's okay for a few remaining issues. In the mean time, if there are any *urgent* patches remaining please try to get them into CVS ASAP. FWIW, FlightGear/PLIB is probably in a releasable state as it is, but given the time since the last release, there may be riding a lot of expectancy on this release, so I'd like to be a little more careful and to at least one more pre-release -and should any problems arise- a second one. To follow up on this: It seems like the initial testing round went pretty well, with mostly minor problems being reported, and many of them being fixed already. I'm hoping to roll up the tar files for the release itself this weekend. I'm not sure whether we'll be able to transfer those to the main webserver instantly, as there were some problems recently. If not, I hope that John Wojnaroski can again provide some server space. In the mean time, I guess we need to make a final decision on the version number... Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/Generic \ data/Aircraft/Instruments \ data/Aircraft/Instruments-3d \ data/Aircraft/UIUC \ data/Aircraft/737-300 \ data/Aircraft/A-10 \ data/Aircraft/bf109 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation-Bravo \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/Rascal \ data/Aircraft/T38 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Cheers, Durk Hi, sounds great! There is still one suggest by me for the win32-version: adding the sim-frame-throttle-thingy (that one for preventing too high fps) in preference.xml or other easy way. I see some problems with people with very good (up-todate) computers. That's something I miss on the win32 version! Regards HHS Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Durk Talsma wrote: On Thursday 22 November 2007 07:36, Durk Talsma wrote: This is a quick note to everybody: I'm planning to build an official FlightGear pre-release tonight. I did a full dress rehearsal last sunday and that all seemed to work well, but I still needed Curt's okay for a few remaining issues. In the mean time, if there are any *urgent* patches remaining please try to get them into CVS ASAP. I hope Jon Berndt will submit patches to the fgfs JSBSim code that 1. Turns off JSBSim modeling of turbulence that plays havoc with the default c172p, and 2. Removes the redundant sense from FGPropellers.cpp. Jon, you indicated #2 should be done. how hard is porting #1 from JSBSim cvs? Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/Generic \ data/Aircraft/Instruments \ data/Aircraft/Instruments-3d \ data/Aircraft/UIUC \ data/Aircraft/737-300 \ data/Aircraft/A-10 \ data/Aircraft/bf109 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ IMHO we should not include the two c310 and replace them with 1. SenecaII (great twin with lots of documentation) 2. de Havilland Beaver - Floats (shows the on-water progress this release and a great bush AC) This exchange leaves a modern light twin and adds the on-water and bush categories to fgfs. data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation-Bravo \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/Rascal \ data/Aircraft/T38 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Cheers, Durk -Dave Perry - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Durk Talsma wrote: Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/UIUC \ Ditch this - I don't think we have any UIUC aircraft in common use (though the Wright Flyer might be) data/Aircraft/c172 \ data/Aircraft/c172p \ c172p should be included as it is mentioned extensively in the docs and has basic tutorials. data/Aircraft/c310 \ data/Aircraft/c310u3a \ Much as I like the c310 - it's now very primitive compared with recent aircraft. Replace with the Seneca II. snip data/Aircraft/j3cub \ Include as a nice easy taildragger. data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ I'd suggest replacing this with a complex single, say the pa24-250. Then we have a nice progression from training to complex twin. data/Aircraft/Rascal \ Does anyone actually use this? data/Aircraft/T38 \ I'm sure that there are better jets, but I'm not familiar with them in enough detail to suggest a replacement. data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ As Melchior says - ditch as no-one uses it. I'd also suggest that we include a carrier-capable jet as well - seahawk? -Stuart ___ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* dave perry -- Tuesday 04 December 2007: 2. Removes the redundant sense from FGPropellers.cpp. Jon, you indicated #2 should be done. how hard is porting #1 from JSBSim cvs? That's already committed. 2. de Havilland Beaver - Floats (shows the on-water progress this release and a great bush AC) Oh, yes, indeed, I support that. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tuesday 04 December 2007 22:46, Melchior FRANZ wrote: data/Aircraft/wrightFlyer1903 \ Waste of disk space. Everyone tries it once or twice, and never again, because it's just *boring*. In general I agree with your suggestions. What about swapping this with the Legendary Russian AN2? I discovered that aircraft at FSWeekend, and got instantly hooked. It seems fairly complete to me and it would be a nice aircraft for the historical aircraft section. Cheers, Durk - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
* Durk Talsma -- Tuesday 04 December 2007: What about swapping this with the Legendary Russian AN2? I discovered that aircraft at FSWeekend, and got instantly hooked. It seems fairly complete to me and it would be a nice aircraft for the historical aircraft section. Yes, but ... $ du -sh bo105 V22-Osprey A-10 787 an2 3.2Mbo105 (actually smaller; I have some devel files there) 8.8MV22-Osprey 20M A-10 20M 787 47M an2-- whoops m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Durk Talsma wrote: To follow up on this: It seems like the initial testing round went pretty well, with mostly minor problems being reported, and many of them being fixed already. I'm hoping to roll up the tar files for the release itself this weekend. Is this just the final tarballs for the binary, or are you rolling up the data tarballs as well? I'd _really_ like to include a fix for the MP repeated chat, as it is unusable in it's current state and I have some enhancements as well, so a timescale for the data code-freeze would be good. I also need to coordinate with Martin Spott generating The Manual for inclusion in the release. To generate The Manual, I need a version number. To get a version number we need a decison! I think all the opinions are in, so I think Curt now needs to collate them and tell us what the result is. Of course, the opinions have been so varied that he can pretty much decide what he wants and convince us that the majority agree with him :) Finally, for those of us who have been developing exclusively on OSG for windows, it would be very useful to have a set of binaries available so we can test our aircraft on plib before the data tarball is created, and the 175 aircraft are uploaded to the website. -Stuart __ Sent from Yahoo! - the World's favourite mail http://uk.mail.yahoo.com - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Stuart Buchanan wrote: --- Durk Talsma wrote: Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/UIUC \ Ditch this - I don't think we have any UIUC aircraft in common use (though the Wright Flyer might be) Well one of the splash screens picture an UIUC aircraft iirc. snip data/Aircraft/j3cub \ Include as a nice easy taildragger. I agree data/Aircraft/Rascal \ Does anyone actually use this? Good question. data/Aircraft/T38 \ I'm sure that there are better jets, but I'm not familiar with them in enough detail to suggest a replacement. I would suggest Lightning. It is very detailed aircraft and nice looking. It is also (in my opinion) easier to fly than T38, both with mouse and with joystick. As Melchior says - ditch as no-one uses it. I'd also suggest that we include a carrier-capable jet as well - seahawk? I agree. Regards, Arvid Norlander -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHVdUSWmK6ng/aMNkRCrX6AJ0fNTFPSrDvBV4qMPG3veoIp1L2vQCfaHHg FKA0l3OgYeAfwJnQId8KmSU= =41sy -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tuesday 04 December 2007 23:27, Melchior FRANZ wrote: $ du -sh bo105 V22-Osprey A-10 787 an2 3.2Mbo105 (actually smaller; I have some devel files there) 8.8MV22-Osprey 20M A-10 20M 787 47M an2-- whoops Oh, yes that's a bit on the heavy side... D. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi, Durk Talsma schrieb am 04.12.2007 21:57: FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/Generic \ data/Aircraft/Instruments \ data/Aircraft/Instruments-3d \ data/Aircraft/UIUC \ data/Aircraft/737-300 \ data/Aircraft/A-10 \ data/Aircraft/bf109 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation-Bravo \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/Rascal \ data/Aircraft/T38 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Cheers, Durk I would like to see a glider with aero-towing-capability (bocian) in the release. Although the J3 has towing capability I would like to see the beaver in the release, too, because due to its higher mass it is much easier with tho aircraft. (I am not voting against the J3, it is a nice taildragger with minimal disk-usage.) Maik - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tue, 4 Dec 2007 21:57:00 +0100 Durk Talsma [EMAIL PROTECTED] wrote: On Thursday 22 November 2007 07:36, Durk Talsma wrote: This is a quick note to everybody: I'm planning to build an official FlightGear pre-release tonight. I did a full dress rehearsal last sunday and that all seemed to work well, but I still needed Curt's okay for a few remaining issues. In the mean time, if there are any *urgent* patches remaining please try to get them into CVS ASAP. FWIW, FlightGear/PLIB is probably in a releasable state as it is, but given the time since the last release, there may be riding a lot of expectancy on this release, so I'd like to be a little more careful and to at least one more pre-release -and should any problems arise- a second one. To follow up on this: It seems like the initial testing round went pretty well, with mostly minor problems being reported, and many of them being fixed already. I'm hoping to roll up the tar files for the release itself this weekend. I'm not sure whether we'll be able to transfer those to the main webserver instantly, as there were some problems recently. If not, I hope that John Wojnaroski can again provide some server space. In the mean time, I guess we need to make a final decision on the version number... Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/Generic \ data/Aircraft/Instruments \ data/Aircraft/Instruments-3d \ data/Aircraft/UIUC \ data/Aircraft/737-300 \ data/Aircraft/A-10 \ data/Aircraft/bf109 \ data/Aircraft/bo105 \ data/Aircraft/c172 \ data/Aircraft/c172p \ data/Aircraft/c310 \ data/Aircraft/c310u3a \ data/Aircraft/Citation-Bravo \ data/Aircraft/f16 \ data/Aircraft/j3cub \ data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ data/Aircraft/Rascal \ data/Aircraft/T38 \ data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ Cheers, Durk - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi, The Bravo's Primus 1000 system is a bit of a mess right now ... I'd feel better if it wasn't included with the release . Thanks -- SydSandy [EMAIL PROTECTED] - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On mar 4 décembre 2007, Melchior FRANZ wrote: * Durk Talsma -- Tuesday 04 December 2007: data/Aircraft/737-300 \ Yes, I'd swap that with the 787. A flat panel that disappears when you look left/right is hard to bear. (Though I miss a VOR display on the 787. Need to search for that ...) data/Aircraft/A-10 \ Good choice. Very detailed, very good quality. data/Aircraft/bf109 \ Hmm ... it's well done and all, but I think it's too realistic, read: too hard to take off/land due to the very narrow gear. The A6M2 would IMHO be a better choice (or the fw190, but I think that's not finished yet). data/Aircraft/bo105 \ Good choice, of course. Approved by a real bo105 pilot (very impressed). :-) data/Aircraft/c172 \ data/Aircraft/c172p \ use pa24 instead? But I see the pa28 further down, so ... data/Aircraft/c310 \ data/Aircraft/c310u3a \ use Seneca instead? data/Aircraft/f16 \ Totally broken! Don't ship this! The FCS winds up after a few minutes and kills you. Very frustrating. After starting fgfs, let is parked for a few minutes, then try to fly it. Good luck! (Though the HUD is nice. :-) data/Aircraft/wrightFlyer1903 \ Waste of disk space. Everyone tries it once or twice, and never again, because it's just *boring*. m. I getting surprised, What about the concorde isn't it one of the most representative ? -- Gérard http://pagesperso-orange.fr/GRTux/ Less i work, better i go - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi, The Bravo's Primus 1000 system is a bit of a mess right now ... I'd feel better if it wasn't included with the release . Thanks How about the B1900 ? Any issues. It is know as having one of the best panels. It would fill the commercial twin prop slot. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
I agree with the pa24-250 or other complex single, whether it replaces pa24 (which I also like but I agree c172p should stay in) or another. On Dec 4, 2007 3:15 PM, Stuart Buchanan [EMAIL PROTECTED] wrote: --- Durk Talsma wrote: Another question: we always have a limited number of aircraft that are in the distribution, with the rest being available as separate downloads. We like to keep the number of aircraft constant, and representative of the many types of aircraft supported by FlightGear. Is there any pressing reason to swap one aircraft for another one? IIRC, there have been some suggestions of replacing the 737 by the 787. FWIW, we currently have the following selection of aircraft (Taken from Makefile.am): data/Aircraft/UIUC \ Ditch this - I don't think we have any UIUC aircraft in common use (though the Wright Flyer might be) data/Aircraft/c172 \ data/Aircraft/c172p \ c172p should be included as it is mentioned extensively in the docs and has basic tutorials. data/Aircraft/c310 \ data/Aircraft/c310u3a \ Much as I like the c310 - it's now very primitive compared with recent aircraft. Replace with the Seneca II. snip data/Aircraft/j3cub \ Include as a nice easy taildragger. data/Aircraft/Hunter \ data/Aircraft/p51d \ data/Aircraft/pa28-161 \ I'd suggest replacing this with a complex single, say the pa24-250. Then we have a nice progression from training to complex twin. data/Aircraft/Rascal \ Does anyone actually use this? data/Aircraft/T38 \ I'm sure that there are better jets, but I'm not familiar with them in enough detail to suggest a replacement. data/Aircraft/ufo \ data/Aircraft/wrightFlyer1903 \ As Melchior says - ditch as no-one uses it. I'd also suggest that we include a carrier-capable jet as well - seahawk? -Stuart ___ Support the World Aids Awareness campaign this month with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Hans Fugal Fugal Computing - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
I'd like to see the 737 stay. Also, I believe recent enhancements and fixes in JSBSim may have fixed the F-16, but I'm not sure. Jon - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Tue, 4 Dec 2007 18:59:11 -0600 Robert Black [EMAIL PROTECTED] wrote: Hi, The Bravo's Primus 1000 system is a bit of a mess right now ... I'd feel better if it wasn't included with the release . Thanks How about the B1900 ? Any issues. It is know as having one of the best panels. It would fill the commercial twin prop slot. yes I dont have any immediate plans for that one :). As far as Carrier capable aircraft , I think the A-6E is another really well done candidate... -- SydSandy [EMAIL PROTECTED] - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
--- Stuart Buchanan wrote: Finally, for those of us who have been developing exclusively on OSG for windows, it would be very useful to have a set of binaries available so we can test our aircraft on plib before the data tarball is created, and the 175 aircraft are uploaded to the website. And, indeed a very kind person has done so: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32 Thanks! -Stuart ___ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Thursday 29 November 2007 16:34, Torsten Dreyer wrote: Am Donnerstag, 29. November 2007 14:44 schrieb Hans Fugal: Is there not a way to sanity check the cloud cache size in the plib version before going ahead and segfaulting? Like notice that it's 0 and set it to the lowest valid value. It seems that this would be a simple fix, and that there's really no excuse not to do it. Unless, of course, there is a real excuse... This should do the trick: Instead of doing nothing when setting a new value to zero, the resolution and cacheSize is set to it's default value when trying to set it to zero. It works on my copy, but maybe one of the screnegraph experts should comment this. Torsten I decided to go ahead and commit this, even though I haven't seen any further comment from a scenegraph expert. The patch seems simple enough, and preventing program crashes would make it worthwhile. If there is breakage, it seems easy enough to revert. :-) Cheers, Durk - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Jeez, Bill, 2.718281828459 makes a lot more sense. Lee Bill Galbraith wrote: *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Lee Duke *Sent:* Friday, November 30, 2007 8:14 AM *To:* FlightGear developers discussions *Subject:* Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults How about /0.x.y/ where /x/ and /y /can be variables and everyone can just choose their favorite or preferred numbers rather than filling my in box with discussions of which number comes after/ z/. Lee Okay, then I'm calling my version 0.3.14, because who doesn't love Pi? Bill - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
It seems to me that we are discussing the issue right now, but we are in danger of getting side tracked. Maybe we should put it out to a vote? We've only had a few people weigh in here, which likely means the rest of the developers don't care, or it's not a battle they think is worth fighting. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d What about 0.10.0? Richard - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
_ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Olson Sent: Friday, November 30, 2007 7:52 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults I'm just a little surpised that the version number is such a contentious issue. It seems like there are more important battles to fight. How about we at least agree to skip 0.9.11 out of sensitivity to a very large group of people. Okay, so are we going to 0.10.1 ??? Geeze, it's just a number. Bill - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Nov 30, 2007 1:23 AM, Melchior FRANZ wrote: The problem that I have/had is that you don't say it openly, when you make such a decision -- that you will call it 1.0, which aircraft it will contain etc. All we got was a cryptic hint with tongue in cheek, instead of an I will make the next release 1.0, because ... (And while you can, of course, discuss it, it's already decided.). It's only in private messages where one gets some more info. I'm just a little surpised that the version number is such a contentious issue. It seems like there are more important battles to fight. How about we at least agree to skip 0.9.11 out of sensitivity to a very large group of people. I have no problems whatsoever with commercial use (as you know from my private mails), or that it occasionally brings you projects and money. On the contrary. I welcome that. And I would understand if this is involved in the decisions to name the release 1.0. (The companies don't like it much that the version number implies that fgfs is still immature beta quality software.) I'd just like to know that/when this is the reason. Don't forget: this is *our* collective work, not only yours. And I think we deserve some basic information. The company I work with has no idea what the version number of flightgear is ... they leave all that to me and do not care. This company's customers want an FAA certified sim. They also do not care what the version number string of FlightGear is. You have constructed a problem in your imagination and then are upset with me for not coming clean on it. No. I don't even care that much, even if is seems so. For me a version 1.0 means that the software is basically feature complete. Of course it will never be finished (this would be sad -- we could all go home). And I think that lights are missing. But well, let's release it as 1.0 without lights. Fine with me. (Maybe we'd end up with 0.9.23 if we really wait for lights. Waiting for something doesn't get anything done, anyway. ;-) Well that's maybe the point. I'll be 80 years old and we'll still be at 0.9.xxx, and maybe we'll have your landing lights by then, or maybe we won't. To me a 1.0 version number means something that's not quite ready for general consumption, or we think there are major holes or major problems and are holding back. Sure we haven't finished every feature in the flight sim play book, but let's let the world know that we have something serious here. See first paragraph: I hate that we *don't* have such discussions. Or such information. Now we know at least[1]: the next release will be 1.0, and it's because you think it's high time after such a long time. OK, all questions answered. Thanks. No surprises when the release comes out. (Developers should never be surprised by the release of their own work. :-) It seems to me that we are discussing the issue right now, but we are in danger of getting side tracked. Maybe we should put it out to a vote? We've only had a few people weigh in here, which likely means the rest of the developers don't care, or it's not a battle they think is worth fighting. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Curtis Olson wrote: On Nov 30, 2007 1:23 AM, Melchior FRANZ wrote: The problem that I have/had is that you don't say it openly, when you make such a decision -- that you will call it 1.0, which aircraft it will contain etc. All we got was a cryptic hint with tongue in cheek, instead of an I will make the next release 1.0, because ... (And while you can, of course, discuss it, it's already decided.). It's only in private messages where one gets some more info. I'm just a little surpised that the version number is such a contentious issue. It seems like there are more important battles to fight. How about we at least agree to skip 0.9.11 out of sensitivity to a very large group of people. As timore said on IRC: timoore If we skip 0.9.11, then the terrorists have won I can't agree more... It is just a number and they should in my experience follow some logic: 0.9.10 - 0.10 = Ok 0.9.10 - 0.11 = Not Ok 0.9.10 - 0.9.10.1 = Ok 0.9.10 - 0.9.10.2 = Not Ok 0.9.10 - 0.9.11= Ok 0.9.10 - 1.0 = Ok (but other issues as mfranz pointed out, I agree with him about landing lights) In other words: Either: Add one to any part and reset all parts after it to 0 Or: Add an extra part, with a 0 or 1. Never : Add 2 or anything else. Regards, AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHUAvsWmK6ng/aMNkRCiYfAKCaCQTeKW/PUEXUU0/6v4ZscpY1vwCfc4cY RsDGp9dtijDdUq97hOVW4QE= =aCfd -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Nov 30, 2007 7:11 AM, AnMaster wrote: As timore said on IRC: timoore If we skip 0.9.11, then the terrorists have won Wow, I didn't realize the terrorists had such strong feelings about our next version number! :-) Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
How about /0.x.y/ where /x/ and /y /can be variables and everyone can just choose their favorite or preferred numbers rather than filling my in box with discussions of which number comes after/ z/. Lee P.S. The correct answer is /z + 1/. Richard Bytheway wrote: It seems to me that we are discussing the issue right now, but we are in danger of getting side tracked. Maybe we should put it out to a vote? We've only had a few people weigh in here, which likely means the rest of the developers don't care, or it's not a battle they think is worth fighting. Regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d What about 0.10.0? Richard - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
_ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee Duke Sent: Friday, November 30, 2007 8:14 AM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults How about 0.x.y where x and y can be variables and everyone can just choose their favorite or preferred numbers rather than filling my in box with discussions of which number comes after z. Lee Okay, then I'm calling my version 0.3.14, because who doesn't love Pi? Bill - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Anything other than 0.9.11 means both the terrorists and the tunnel vision of the USAians have triumphed. And BTW as far as most of Europe is concerned a serious terrorist outrage occured 11-9-2001 and 9-11 is just a set of numbers. This is not the place for politics however (which I am happy to debate with anyone off list) so to stop everybody getting their knickers in a twist, lets go with Bill and call it 0.3.14-pecan. When we get landing lights and all the other good stuff, then it will be worthy of being called 0.3.14-mutton. --- Best Regards Willie Fleming [EMAIL PROTECTED] - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Thu, 29 Nov 2007, Georg Vollnhals wrote: 4. 3D clouds crash Selecting 3D clouds in the rendering menu crashes FlightGear after closing the window. When used as a startup parameter FlightGear does not run. Do I remember right that this is an older problem and depending on the video-driver/card of the user system??? Hi, Check that cloud resolution and cloud cache size isn't 0 in the rendering dialogue. These are stored in autosave.xml and FG/OSG sets one of them to zero - causing FG/plib to crash when enabling 3d clouds unless one adjusts the parameter first. Cheers, Anders -- --- Anders Gidenstam mail: anders(at)gidenstam.org WWW: http://www.gidenstam.org/FlightGear/JSBSim-LTA/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Anders Gidenstam wrote: On Thu, 29 Nov 2007, Georg Vollnhals wrote: 4. 3D clouds crash Selecting 3D clouds in the rendering menu crashes FlightGear after closing the window. When used as a startup parameter FlightGear does not run. Do I remember right that this is an older problem and depending on the video-driver/card of the user system??? Hi, Check that cloud resolution and cloud cache size isn't 0 in the rendering dialogue. These are stored in autosave.xml and FG/OSG sets one of them to zero - causing FG/plib to crash when enabling 3d clouds unless one adjusts the parameter first. Why not have autosave-osg.xml and autosave-plib.xml, I changed to use that locally because of how annoying this was. IMO something like that would make sense in cvs too. At least until FG/OSG support all those values. Or simply make FG/OSG ignore the values, not overwrite them? /AnMaster Cheers, Anders -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHTrdBWmK6ng/aMNkRCnTBAJ9+4elQyYLKEw8T6TapQslmPEfbsQCgsnfd /5d/30R3Xo1aUPUp5LgEi4Y= =hADr -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Georg Vollnhals wrote: [...] 2. Triangle distorted sky also with Anthrax GUI Although using the Anthrax-GUI, the sky gets triangulated when using a submenu with (orange???) input-fields. This triangle distortion disappears immediatly after leaving the input field. Did the nVidia driver settings workaround help? (Quote from earlier mail on -devel): I brought this up in IRC and it was mentioned that this may be an NVidia. I followed AnMaster's recommendation that I enable NVidia's anti-aliasing and anisotropic filtering for all apps and that does seem to have solved the issue. The default settings for these was Application Controlled. 3. Winter textures (partially) broken (same for OSG version) As we had the first snow here the last days I wanted to use the winter-textures for a flight (--season=winter) but was disappointed as it seams to be broken. Some of the winter textures display right, other are only visible from a specific small view-angle. With another view-angle the ground has some sort of brown colour, no real texture. (It is also broken with FG/OSG CVS, here most of the textures won't display, only one or two). Is this specific to my system? Or is it broken on your system, too? Known broken, for a long time. [...] 4. Please make gstunnel menu switchable Melchiors gstunnel.nas works with the Prerelease version. This could be a very nice new feature for the new FG version if Melchior could make it switchable (on/off) by a menu entry. I remember that it helped me a lot a long, long time ago with the flightsim of those days ... What is this gstunnel thing? /AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHTriYWmK6ng/aMNkRCl29AKCh3bU1lWPmY4IswVc+/AcJmX7oJgCgq9I/ O/wYlS7YmN3jn2eZ5a2Jhqk= =oZYl -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Hans Fugal schrieb: Is there not a way to sanity check the cloud cache size in the plib version before going ahead and segfaulting? Like notice that it's 0 and set it to the lowest valid value. It seems that this would be a simple fix, and that there's really no excuse not to do it. Unless, of course, there is a real excuse... Hi Anders, Anmaster and Hans, thank you for your anwers. First, setting the texture resolution 0 did the trick. It really would be a great idea like Hans proposed to check for zero and if true, set the lowest value to avoid this ugly crash. I am pretty sure I am not the only one who did not realize that crash was caused by invalid values. This would hinder many questions in the FG forums after the new release. @Anders: The gstunnel is a visualization of the glidepath. Here is a picture: http://home.arcor.de/vollnhals-bremen/gstunnel/fgfs-screen-080.jpg Regards Georg - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Am Donnerstag, 29. November 2007 14:44 schrieb Hans Fugal:
Is there not a way to sanity check the cloud cache size in the plib
version before going ahead and segfaulting? Like notice that it's 0
and set it to the lowest valid value. It seems that this would be a
simple fix, and that there's really no excuse not to do it. Unless, of
course, there is a real excuse...
This should do the trick: Instead of doing nothing when setting a new value to
zero, the resolution and cacheSize is set to it's default value when trying
to set it to zero.
It works on my copy, but maybe one of the screnegraph experts should comment
this.
Torsten
Index: cloudfield.cxx
===
RCS file: /var/cvs/SimGear-0.3/source/simgear/scene/sky/cloudfield.cxx,v
retrieving revision 1.14.2.1
diff -u -p -r1.14.2.1 cloudfield.cxx
--- cloudfield.cxx 31 Jul 2007 01:19:11 - 1.14.2.1
+++ cloudfield.cxx 29 Nov 2007 15:18:13 -
@@ -80,6 +80,8 @@ int SGCloudField::get_CacheResolution(vo
}
void SGCloudField::set_CacheResolution(int resolutionPixels) {
+ if( resolutionPixels == 0 )
+ resolutionPixels = 64;
if(cacheResolution == resolutionPixels)
return;
cacheResolution = resolutionPixels;
@@ -97,10 +99,10 @@ int SGCloudField::get_CacheSize(void) {
void SGCloudField::set_CacheSize(int sizeKb) {
// apply in rendering option dialog
+ if( sizeKb == 0 )
+ sizeKb = 1024;
if(last_cache_size == sizeKb)
return;
- if(sizeKb == 0)
- return;
if(sizeKb)
last_cache_size = sizeKb;
if(enable3D) {
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Georg Vollnhals -- Thursday 29 November 2007: 3. Winter textures (partially) broken (same for OSG version) That was IIRC caused by Erik's texture cache, which saved several megabytes formerly wasted texture memory, which is an important improvement. He knows about the breakage of his season feature, and I assume he just hasn't had time to fix it. :-) 4. Please make gstunnel menu switchable That would be easy, but I haven't even committed it, because it has some problems: on several runways the apt.dat runways don't match the rendered airports, and it's a bit embarrassing if the glide slope tunnel doesn't end on the runway. Also, it doesn't consider wind when choosing a runway, nor does it respect ATC's choice. The latter two problems wouldn't be hard to fix, but the former is. So I'm not sure if this should be made available. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Melchior FRANZ -- Thursday 29 November 2007: That would be easy, but I haven't even committed it, because it has some problems: Oh, and it doesn't respect the true glide slope angle. It always uses 3 degree, although some have 3.5. (But then again, I'm not sure if fgfs makes a difference, so this could be consistently wrong. ;-) m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Melchior FRANZ schrieb: * Melchior FRANZ -- Thursday 29 November 2007: That would be easy, but I haven't even committed it, because it has some problems: Oh, and it doesn't respect the true glide slope angle. It always uses 3 degree, although some have 3.5. (But then again, I'm not sure if fgfs makes a difference, so this could be consistently wrong. ;-) m. Hi Melchior, I respect your arguments. Some of them I did not notice as I just was lucky when testing it, it altway matched runway and wind-direction. And I did not see it like a command flightpath display but just as a training device for people who really have no idea how to get their (bigger) aircraft landed in some realistic way. Ok, one could just use the approach lighting system to have a simple help, but these big read sqares of your gstunnel are a lot easier to use. Could you imagine to put this nasal file into the Nasal folder of the upcoming release *deactivated*, ie. named gstunnel.nas.off or something like that? I would like to present this help in the German FlightGear Forum after the 0.9.11 is out and it would only be a little step for the user to rename this file and then use this option - if wanted. Regards Georg - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Thursday 29 November 2007 20:38:15 Heiko Schulz wrote: There are some things I noticed and two suggestion: -If I check show fps - it does not appear. I have to enlarge and to downsize the window, or to reset FGF for viewing the fps Are you sure you're using the exact --geometry setting you require, and/or hiding the taskbar? If there's a taskbar on the screen for example, the bottom part of the window (with the fps display) will likely be cut off. Maybe the fullscreen option, or the game mode might help there (I'm not on Windows to check myself, but I've seen a similar thing happen on Linux desktops). Suggestions: -Because we have a wide range of aircrafts which only can fully used with OSG we should give an option for using the OSG version with the release. With MS it is easy ( download option for OSG-Binary and just changing the root), for other platforms maybe a little bit more difficult. It also brings a little preview about the features and abilities of the new scenegraph I also think that at least the two versions should be made to run happily together (i.e. by sorting the aforementioned 3d clouds / autosaved setting bug) An optional official (i.e. nicely packaged) download of FG-OSG 0.9.11 for more adventurous Windows users would be nice. - can we change the name of the new release from 0.9.11 to 0.9.12? I'm not superstitious, but it looks a little bit funny on a FLIGHTsimulation ( remember the 11. september 2001 - and the aftereffect to the aircraft industry) I would strongly disagree with that - with every respect for those who were affected by the events you mention, it's only a set of numbers (not even a date, in any recognisable format), and since 0.9.11 comes right after 0.9.10, it's only logical to use them. If we start being ridiculously over-sensitive to particular numbers we'll end up with a very odd version history indeed... Cheers, AJ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Heiko Schulz wrote: Hi, There are some things I noticed and two suggestion: -If I check show fps - it does not appear. I have to enlarge and to downsize the window, or to reset FGF for viewing the fps FPS counter show nice here but I changed preferences.xml to give me maximized window by default. - stepping clouds at certain weather What do you mean? -3D-clouds crashing - I hope we will get the sugested solution - stutters with any helicopters at the ground- lifting up is a big problem cause to the stutters. If the heli is in the air the stutters disappear and it flys smooth. I did not noticed yet on plib since some months ago, before it was only with OSG-version and it was a known bug. Yes stutters near ground with fg/plib at KSFO airport I often noticed in many aircrafts. Effect not as marked for simpler airports. Suggestions: -Because we have a wide range of aircrafts which only can fully used with OSG we should give an option for using the OSG version with the release. With MS it is easy ( download option for OSG-Binary and just changing the root), for other platforms maybe a little bit more difficult. It also brings a little preview about the features and abilities of the new scenegraph Even worse, some crash plib if they exist, even over mp. For example if you use plib and anyone connects near you with B-1B and you have B-1B in your aircraft folder, your fg will segfault. This I consider a release-blocking bug. FG/plib should ignore the aircraft instead of segfault on it. - can we change the name of the new release from 0.9.11 to 0.9.12? I'm not superstitious, but it looks a little bit funny on a FLIGHTsimulation ( remember the 11. september 2001 - and the aftereffect to the aircraft industry) No comments but I think that would be silly, it depends on your date order anyway... With the Swedish format for date (dd/mm -) it is the other way around... No one would comment on a possible future 0.11.9 I bet... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHTylSWmK6ng/aMNkRCpWFAKCegEwqQ91hxkspYdYB0jTwWoQuqACfaiZC RyLzDNqjt7w1McOexvoE+k0= =Tqv4 -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Heiko Schulz -- Thursday 29 November 2007: - stutters with any helicopters at the ground- lifting up is a big problem cause to the stutters. If the heli is in the air the stutters disappear [...] Sounds like the effect that volumetric shadows have, on any complex aircraft near ground, not just helicopters. Tim will implement a much faster method. :-) m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
I did not use any shadows- still haveing a to weak pc I remember something heard about that the cause lies into the collision detect for the ground Hopefully Tim well be soon ready- can't wait to see it! :-) regards HHS --- Melchior FRANZ [EMAIL PROTECTED] schrieb: * Heiko Schulz -- Thursday 29 November 2007: - stutters with any helicopters at the ground- lifting up is a big problem cause to the stutters. If the heli is in the air the stutters disappear [...] Sounds like the effect that volumetric shadows have, on any complex aircraft near ground, not just helicopters. Tim will implement a much faster method. :-) m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s mit dem neuen Yahoo! Mail. www.yahoo.de/mail - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Georg Vollnhals -- Thursday 29 November 2007: Could you imagine to put this nasal file into the Nasal folder of the upcoming release *deactivated*, ie. named gstunnel.nas.off or something like that? Better fix the problems that can be fixed and put it as regular file. :-) I made the script switchable (/sim/rendering/glide-slope-tunnel for now), and changed it to choose the best runway according to the wind direction and not the smallest deviation from the course. This should also better match what ATC says. Not that many use ATC, anyway. The remaining problem will hopefully go away after the next round of scenery generation. http://members.aon.at/mfranz/gstunnel.nas [2.8 kB] I just don't know where to put this in the gui. The View/Rendering Options is not the right place, as this isn't about how rendering should be done, but just about one extra feature. We don't really have a place for such settings yet. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Melchior FRANZ wrote: * Heiko Schulz -- Thursday 29 November 2007: - stutters with any helicopters at the ground- lifting up is a big problem cause to the stutters. If the heli is in the air the stutters disappear [...] Sounds like the effect that volumetric shadows have, on any complex aircraft near ground, not just helicopters. Tim will implement a much faster method. :-) That is another problem, check shadow of for example lightning in plib. The shadow is quite bad, like half of the aircraft didn't exist. The lightning is the worst example but many other exists. Best way to see lightning problems is to fly on the side and look out through side cockpit window at ground with sun almost right over head. I can make a screenshot if you want later. /AnMaster -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHTyuQWmK6ng/aMNkRCji4AJ4yJ+X7DTC7Vm6XTBbBtgdm2ltydgCgpYT6 epJoJMkbioxTv0m8jBv3Ob0= =Fc0N -END PGP SIGNATURE- - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
--- AJ MacLeod [EMAIL PROTECTED] schrieb: On Thursday 29 November 2007 20:38:15 Heiko Schulz wrote: There are some things I noticed and two suggestion: -If I check show fps - it does not appear. I have to enlarge and to downsize the window, or to reset FGF for viewing the fps Are you sure you're using the exact --geometry setting you require, and/or hiding the taskbar? If there's a taskbar on the screen for example, the bottom part of the window (with the fps display) will likely be cut off. Maybe the fullscreen option, or the game mode might help there (I'm not on Windows to check myself, but I've seen a similar thing happen on Linux desktops). Suggestions: -Because we have a wide range of aircrafts which only can fully used with OSG we should give an option for using the OSG version with the release. With MS it is easy ( download option for OSG-Binary and just changing the root), for other platforms maybe a little bit more difficult. It also brings a little preview about the features and abilities of the new scenegraph I also think that at least the two versions should be made to run happily together (i.e. by sorting the aforementioned 3d clouds / autosaved setting bug) An optional official (i.e. nicely packaged) download of FG-OSG 0.9.11 for more adventurous Windows users would be nice. - can we change the name of the new release from 0.9.11 to 0.9.12? I'm not superstitious, but it looks a little bit funny on a FLIGHTsimulation ( remember the 11. september 2001 - and the aftereffect to the aircraft industry) I would strongly disagree with that - with every respect for those who were affected by the events you mention, it's only a set of numbers (not even a date, in any recognisable format), and since 0.9.11 comes right after 0.9.10, it's only logical to use them. If we start being ridiculously over-sensitive to particular numbers we'll end up with a very odd version history indeed... Cheers, AJ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel Hi, I did use 800x600 - so no taskbar or anything cuts here. A optional package would be nice - with the aircrafts made for OSG. Regards HHS Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Nov 29, 2007 2:56 PM, AJ MacLeod wrote: I would strongly disagree with that - with every respect for those who were affected by the events you mention, it's only a set of numbers (not even a date, in any recognisable format), and since 0.9.11 comes right after 0.9.10, it's only logical to use them. If we start being ridiculously over-sensitive to particular numbers we'll end up with a very odd version history indeed... Everyone seems to agree that version numbers are an arbitrary set of numbers and the only really important thing is that each subsequent version has a higher number than all the previous versions in a branch. But then most people seem to also follow that up with very strongly held opinions about what the version number should be. As we've seen from just a few postings in this thread, there is a variety incompatible, yet strongly held opinions on the subject. I may jump in and make an executive decision on this one, and it shouldn't be a big deal because it's just an arbitrary number that is higher than the previous release. And I may attempt to piss everyone off, just to keep it fair. :-) Best regards, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On jeu 29 novembre 2007, Melchior FRANZ wrote: * Georg Vollnhals -- Thursday 29 November 2007: Could you imagine to put this nasal file into the Nasal folder of the upcoming release *deactivated*, ie. named gstunnel.nas.off or something like that? Better fix the problems that can be fixed and put it as regular file. :-) I made the script switchable (/sim/rendering/glide-slope-tunnel for now), and changed it to choose the best runway according to the wind direction and not the smallest deviation from the course. This should also better match what ATC says. Not that many use ATC, anyway. The remaining problem will hopefully go away after the next round of scenery generation. http://members.aon.at/mfranz/gstunnel.nas [2.8 kB] I just don't know where to put this in the gui. The View/Rendering Options is not the right place, as this isn't about how rendering should be done, but just about one extra feature. We don't really have a place for such settings yet. m. It is not Autopilot, however it is an help to pilot, it could be in the autopilot item Regards -- Gérard http://pagesperso-orange.fr/GRTux/ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Curtis Olson -- Thursday 29 November 2007: Everyone seems to agree that version numbers are an arbitrary set of numbers [...] No, you got that backwards. From reading the thread it was clear that people consider a sane version number more important than politics, such as avoiding 0.9.11 because of the incident. Is it your commercial interests in fgfs that make you want it be called 1.0? Did someone complain? Those who use fgfs in their FAA certified simulator? We would understand it. Here's again what I consider sorely missing for a release 1.0: landing/taxi-lights. It's weird to call a simulator 1.0 if you have to let your aircraft parked in the middle of a runway after having landed at night, because you don't see anything but a few dim light points. A daylight-only simulator doesn't deserve the 1.0. :-P m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
gerard robin schrieb: On jeu 29 novembre 2007, Melchior FRANZ wrote: * Georg Vollnhals -- Thursday 29 November 2007: Could you imagine to put this nasal file into the Nasal folder of the upcoming release *deactivated*, ie. named gstunnel.nas.off or something like that? Better fix the problems that can be fixed and put it as regular file. :-) I made the script switchable (/sim/rendering/glide-slope-tunnel for now), and changed it to choose the best runway according to the wind direction and not the smallest deviation from the course. This should also better match what ATC says. Not that many use ATC, anyway. The remaining problem will hopefully go away after the next round of scenery generation. http://members.aon.at/mfranz/gstunnel.nas [2.8 kB] I just don't know where to put this in the gui. The View/Rendering Options is not the right place, as this isn't about how rendering should be done, but just about one extra feature. We don't really have a place for such settings yet. m. It is not Autopilot, however it is an help to pilot, it could be in the autopilot item Regards Hi Melchior, hi Gérard! First to say, I made some testflights at EDDW and it works fine if I set the wind with [EMAIL PROTECTED]. Then I tried to make it easier from the startup and switch the property on with --prop:sim/rendering/glide-slope-tunnel=true. The sim starts with the tunnel visible but not the right wind direction. It seems that the early activating makes the script not seeing the winddirection. So I would ask to put a menu-entry anywhere where it fits, that might be the suggestion of Gérard or even the rendering menu-window - I think the normal user will not classify this wrong :-) Anyway, nice add-on. Georg - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
--- Melchior FRANZ [EMAIL PROTECTED] schrieb: * Curtis Olson -- Thursday 29 November 2007: Everyone seems to agree that version numbers are an arbitrary set of numbers [...] No, you got that backwards. From reading the thread it was clear that people consider a sane version number more important than politics, such as avoiding 0.9.11 because of the incident. Is it your commercial interests in fgfs that make you want it be called 1.0? Did someone complain? Those who use fgfs in their FAA certified simulator? We would understand it. Here's again what I consider sorely missing for a release 1.0: landing/taxi-lights. It's weird to call a simulator 1.0 if you have to let your aircraft parked in the middle of a runway after having landed at night, because you don't see anything but a few dim light points. A daylight-only simulator doesn't deserve the 1.0. :-P m. Hmm... How possible it is, that we have landinglights with the release after this one? Compared to x-Plane we sure other v 1.0, but with OSG there are some differences HHS Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Georg Vollnhals -- Thursday 29 November 2007: gerard robin schrieb: It is not Autopilot, however it is an help to pilot, it could be in the autopilot item Yes, maybe. * Georg Vollnhals -- Thursday 29 November 2007: First to say, I made some testflights at EDDW and it works fine if I set the wind with [EMAIL PROTECTED]. Then I tried to make it easier from the startup and switch the property on with --prop:sim/rendering/glide-slope-tunnel=true. Err ... with METAR wind, then? Yes, that might come too late. Just increase the settimer() interval. We don't need/want the tunnel right at startup, anyway. After 30 seconds or a minute would be early enough. Need to check ... So I would ask to put a menu-entry anywhere where it fits, that might be the suggestion of Gérard or even the rendering menu-window [...] Will think about it. m. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Thursday 29 November 2007 21:54:05 Curtis Olson wrote: But then most people seem to also follow that up with very strongly held opinions about what the version number should be. As we've seen from just a few postings in this thread, there is a variety incompatible, yet strongly held opinions on the subject. Most of us were merely going on the version number ALREADY set by our fickle^w honourable dict^w executive ;-) AJ - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Nov 29, 2007 4:13 PM, Melchior FRANZ wrote: No, you got that backwards. From reading the thread it was clear that people consider a sane version number more important than politics, such as avoiding 0.9.11 because of the incident. I think your message at least confirms my point that there is substantial and heartfelt disagreement on something as trivial as version numbers. Is it your commercial interests in fgfs that make you want it be called 1.0? Did someone complain? Those who use fgfs in their FAA certified simulator? We would understand it. You are taking a subtle shot at me here which I could choose to resent or choose ignore and I'll go with the latter approach. :-) There are a large and growing number of people in the world that use FlightGear for one purpose or another. If they didn't use FlightGear, they would have to purchase something else or spend time money developing something else. Do they have a commercial interest in FlightGear? It's no secret that I work with a flight simulator company (ATC Flight Sims) and help them leverage FlightGear as part of their FAA certified pilot training systems. But I see this as a huge win for everyone. And I know of *many* other companies that I am not involved with that use FlightGear, again for everyone's benefit. So if you have a problem, please state it clearly and maybe take it up with me offline with your first attempt. If you are just taking a shot at me, then I'll ignore it. :-) Here's again what I consider sorely missing for a release 1.0: landing/taxi-lights. It's weird to call a simulator 1.0 if you have to let your aircraft parked in the middle of a runway after having landed at night, because you don't see anything but a few dim light points. A daylight-only simulator doesn't deserve the 1.0. :-P How about I say it this way ... our version number system has become too tedious and ponderous. And are you suggesting that a 10 year old mature software product can't be allowed a v1.0 version number? It's never going to be perfect, and never going to have every feature that everyone wants. If I would have been smart, I would have called the very first release v1.0which is what I do now with all my other projects, and we wouldn't even be having this discussion. Let's move forward, full speed ahead! Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/ Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Melchior FRANZ schrieb: * Georg Vollnhals -- Thursday 29 November 2007: First to say, I made some testflights at EDDW and it works fine if I set the wind with [EMAIL PROTECTED]. Then I tried to make it easier from the startup and switch the property on with --prop:sim/rendering/glide-slope-tunnel=true. Err ... with METAR wind, then? Yes, that might come too late. Just increase the settimer() interval. We don't need/want the tunnel right at startup, anyway. After 30 seconds or a minute would be early enough. Need to check ... Sorry, I think I was not clear enough. The tunnel is not true up when I set both, wind and tunnel-prop: [EMAIL PROTECTED] --prop:sim/rendering/glide-slope-tunnel=true. I did not test METAR wind with the NEW gs-tunnel.nas but will do now. Georg - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
Georg Vollnhals schrieb: Melchior FRANZ schrieb: * Georg Vollnhals -- Thursday 29 November 2007: First to say, I made some testflights at EDDW and it works fine if I set the wind with [EMAIL PROTECTED]. Then I tried to make it easier from the startup and switch the property on with --prop:sim/rendering/glide-slope-tunnel=true. Err ... with METAR wind, then? Yes, that might come too late. Just increase the settimer() interval. We don't need/want the tunnel right at startup, anyway. After 30 seconds or a minute would be early enough. Need to check ... Sorry, I think I was not clear enough. The tunnel is not true up when I set both, wind and tunnel-prop: [EMAIL PROTECTED] --prop:sim/rendering/glide-slope-tunnel=true. I did not test METAR wind with the NEW gs-tunnel.nas but will do now. Georg Ok, I did it with several Airports and setting --enable-real-weather-fetch --prop:sim/rendering/glide-slope-tunnel=true. Most (German) airports worked well. LFBO METAR was ... VRB01KT ... so it was pretty understandable for me that the runway selector and the tunnel placer decided different. LOAN METAR was ... 09006KT and I found the Cessna on RW 10 and the tunnel vice versa (RW 28) Starting once again only with --enable-real-weather-fetch and activating the tunnel-prop through the FG property manager when the sim was running placed the tunnel the right way, both Cessna and tunnel RW 10. Now it is too late to increase the INTERVAL var in gs-tunnel.nas, ie. from 5 to 20 (?) and do some further tests. Will do it this late evening. Regards Georg - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
On Thursday 29 November 2007 23:25, Curtis Olson wrote: [snip...] How about I say it this way ... our version number system has become too tedious and ponderous. And are you suggesting that a 10 year old mature software product can't be allowed a v1.0 version number? It's never going to be perfect, and never going to have every feature that everyone wants. If I would have been smart, I would have called the very first release v1.0which is what I do now with all my other projects, and we wouldn't even be having this discussion. Let's move forward, full speed ahead! Curt. Almost Just a tongue-in-cheek suggestion... why not go against the flow and accept that there will never be a fault-free 'perfect' version of FG and deliberately never release a V1.00 version:) Instead, we could just start adding another version sub-subfix:) In effect, and by other s/w producers standards we would already be somewhere between versions 5 and 20, so 0.9.12.00 would be cool. Infact, I think it would be both amusing and publicity-worth to make a point of it because in reality it's true:) I think it would be a statement that most development people would recognise and appreciate and atm they are the most significant users of FG:) LeeE - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hi Durk, looking over my logs, there was quite a bit of traffic downloading the pre-release version of FG and the base files. Glad I could help. Do you want to continue with this arrangement or has Curt had a chance to setup the ftp server for you? If not I can give you ftp access and perhaps we can continue using this site as a mirror. Your call Regards John - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear Prerelease 0.9.11 some testresults
* Curtis Olson -- Friday 30 November 2007: [...] So if you have a problem, please state it clearly The problem that I have/had is that you don't say it openly, when you make such a decision -- that you will call it 1.0, which aircraft it will contain etc. All we got was a cryptic hint with tongue in cheek, instead of an I will make the next release 1.0, because ... (And while you can, of course, discuss it, it's already decided.). It's only in private messages where one gets some more info. I have no problems whatsoever with commercial use (as you know from my private mails), or that it occasionally brings you projects and money. On the contrary. I welcome that. And I would understand if this is involved in the decisions to name the release 1.0. (The companies don't like it much that the version number implies that fgfs is still immature beta quality software.) I'd just like to know that/when this is the reason. Don't forget: this is *our* collective work, not only yours. And I think we deserve some basic information. And are you suggesting that a 10 year old mature software product can't be allowed a v1.0 version number? No. I don't even care that much, even if is seems so. For me a version 1.0 means that the software is basically feature complete. Of course it will never be finished (this would be sad -- we could all go home). And I think that lights are missing. But well, let's release it as 1.0 without lights. Fine with me. (Maybe we'd end up with 0.9.23 if we really wait for lights. Waiting for something doesn't get anything done, anyway. ;-) we wouldn't even be having this discussion. See first paragraph: I hate that we *don't* have such discussions. Or such information. Now we know at least[1]: the next release will be 1.0, and it's because you think it's high time after such a long time. OK, all questions answered. Thanks. No surprises when the release comes out. (Developers should never be surprised by the release of their own work. :-) m. [1] Well, I know it from Curt since a week. - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease; RPMs available + PATCH
2007/11/27, Andy Ross [EMAIL PROTECTED]: So it's only missing #include which should be in the code. See the attachments. [...] #include math.h +#include stdlib.h +#include cstring Surely that should be string.h, no? It's just a style thing, but if you're modifying code that is already using ANSI C headers, and not Standard C++ headers, you should stay with the existing convention. It's especially weird to add one of each. :) O.K. Thanks for your hint. Ladislav. Andy - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease; RPMs available + PATCH
Hi.
I have yet another two patches to get FlightGear and Simgear
compiling with new gcc 4.3, which is stricter about missing
declarations of functions. So it's only missing #include which should
be in the code. See the attachments.
Btw. I'm building the RPMs for Fedora, Mandriva and SuSE in Build
Service (http://build.opensuse.org). So you can easily install them,
searching the FlightGear on the web page
http://software.opensuse.org/search and choose the home:lmich
repository.
Regards Ladislav.
--- src/Airports/parking.cxx
+++ src/Airports/parking.cxx
@@ -27,6 +27,7 @@
#endif
//#include algorithm
+#include stdlib.h
#include simgear/compiler.h
--- src/Airports/runwayprefs.cxx
+++ src/Airports/runwayprefs.cxx
@@ -26,6 +26,8 @@
#endif
#include math.h
+#include stdlib.h
+#include cstring
//#include algorithm
#include simgear/compiler.h
--- src/Airports/runways.cxx
+++ src/Airports/runways.cxx
@@ -27,6 +27,7 @@
#include math.h // fabs()
#include stdio.h // sprintf()
+#include stdlib.h //atoi()
#include simgear/compiler.h
#include simgear/debug/logstream.hxx
--- src/FDM/JSBSim/input_output/FGfdmSocket.cpp
+++ src/FDM/JSBSim/input_output/FGfdmSocket.cpp
@@ -37,6 +37,7 @@
INCLUDES
%%*/
+#include cstring
#include FGfdmSocket.h
namespace JSBSim {
--- src/FDM/YASim/yasim-test.cpp
+++ src/FDM/YASim/yasim-test.cpp
@@ -1,4 +1,6 @@
#include stdio.h
+#include stdlib.h
+#include cstring
#include simgear/props/props.hxx
#include simgear/xml/easyxml.hxx
--- src/Main/util.cxx
+++ src/Main/util.cxx
@@ -21,6 +21,7 @@
#include simgear/compiler.h
#include math.h
+#include stdlib.h
#include vector
SG_USING_STD(vector);
--- BUILD/SimGear-0.3.11-pre2/simgear/io/sg_file.cxx
+++ BUILD/SimGear-0.3.11-pre2/simgear/io/sg_file.cxx
@@ -21,6 +21,8 @@
// $Id: sg_file.cxx,v 1.8 2006-03-08 18:16:08 mfranz Exp $
+#include cstring
+
#include simgear/compiler.h
#include STL_STRING
--- BUILD/SimGear-0.3.11-pre2/simgear/io/sg_serial.cxx
+++ BUILD/SimGear-0.3.11-pre2/simgear/io/sg_serial.cxx
@@ -20,6 +20,8 @@
//
// $Id: sg_serial.cxx,v 1.6 2006-03-08 18:16:08 mfranz Exp $
+#include stdlib.h
+#include cstring
#include simgear/compiler.h
--- BUILD/SimGear-0.3.11-pre2/simgear/misc/strutils.cxx
+++ BUILD/SimGear-0.3.11-pre2/simgear/misc/strutils.cxx
@@ -21,6 +21,7 @@
// $Id: strutils.cxx,v 1.3 2006-03-08 18:16:08 mfranz Exp $
#include ctype.h
+#include cstring
#include strutils.hxx
namespace simgear {
--- BUILD/SimGear-0.3.11-pre2/simgear/misc/tabbed_values.cxx
+++ BUILD/SimGear-0.3.11-pre2/simgear/misc/tabbed_values.cxx
@@ -20,6 +20,8 @@
//
// $Id: tabbed_values.cxx,v 1.3 2006-03-08 18:16:08 mfranz Exp $
+#include stdlib.h
+
#include tabbed_values.hxx
#include assert.h
--- BUILD/SimGear-0.3.11-pre2/simgear/screen/RenderTexture.cpp
+++ BUILD/SimGear-0.3.11-pre2/simgear/screen/RenderTexture.cpp
@@ -46,6 +46,7 @@
* Nov. 2005, Use the simgear logging facility, Erik Hofman
* Mar. 2006, Add MAC OS X support, Alexander Powell
*/
+#include cstring
#ifdef HAVE_CONFIG_H
# include simgear_config.h
--- BUILD/SimGear-0.3.11-pre2/simgear/screen/TestRenderTexture.cpp
+++ BUILD/SimGear-0.3.11-pre2/simgear/screen/TestRenderTexture.cpp
@@ -16,6 +16,7 @@
#include assert.h
#include stdio.h
+#include stdlib.h
void Reshape(int w, int h);
--- BUILD/SimGear-0.3.11-pre2/simgear/screen/shader.cpp
+++ BUILD/SimGear-0.3.11-pre2/simgear/screen/shader.cpp
@@ -18,6 +18,9 @@
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
*/
+#include cstring
+#include stdlib.h
+
#ifdef HAVE_CONFIG_H
# include simgear_config.h
#endif
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Monday 26 November 2007 03:09, Tatsuhiro Nishioka wrote: Durk, (and more developers), could you test this patch so it can run on linux and windows properly? If so, please apply this patch. Otherwise, I'm gonna make a new patch with #ifdef __APPLE__ #endif closure not to affect other platforms. Okay, committed. Thanks. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
On Monday 26 November 2007 19:52, Tatsuhiro Nishioka wrote: Please apply this patch if you still have time before the official 0.9.11-pre2 release. Otherwise, apply this on the next release. Okay, done. Cheers, Durk - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease; RPMs available + PATCH
On Tuesday 27 November 2007 15:22, Ladislav Michnovič wrote: Hi. I have yet another two patches to get FlightGear and Simgear compiling with new gcc 4.3, which is stricter about missing declarations of functions. So it's only missing #include which should be in the code. See the attachments. Hi Ladislav, Committed. Thanks for the patches. Cheers, Durk - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease; RPMs available + PATCH
So it's only missing #include which should be in the code. See the attachments. [...] #include math.h +#include stdlib.h +#include cstring Surely that should be string.h, no? It's just a style thing, but if you're modifying code that is already using ANSI C headers, and not Standard C++ headers, you should stay with the existing convention. It's especially weird to add one of each. :) Andy - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Durk, Okay, I'll write on this issue a bit before I leave here. This bug actually has occurred since 0.9.10. When I found this bug, I sent a similar report as Hans did, and the answer was almost exactly the same as you said. So I checked if rgb file for halo was properly loaded. Then I found that somehow it was not loaded properly on Mac OS X. I was trying to find the cause of this problem by tracing around SimGear's oursun.cxx, but I only found a workaround (changing the order of adding texture paths (i.e. the order of loading rgb files). This allows Mac OS X properly load rgb file for halo... I don't know why such thing happens yet, but it works anyway. This is why I changed the order of adding texture paths in the patch that I posted yesterday. I didn't post the patch since I was not sure if this patch affects other platforms. Maybe this is a proper timing to apply the patch only if it doesn't affect other platforms. By the way, I forgot to mention that there is another bug (also since 0.9.10) that shadows are not rendered on Mac OS X. At the time SGShadowVolume::setupShadows is called for the first time, OpenGL extentions and AlphaBits/StencilBits are not properly recognized on Macs, so SGShadowVolume::init() should be (re)invoked when setupShadows() is called for the first time. Enclosed is the patch for SimGear to solve this problem. This patch doesn't affect any other platform since it is in #ifdef __APPLE__ #endif closure. Please apply this patch if you still have time before the official 0.9.11-pre2 release. Otherwise, apply this on the next release. I can help on this again when I come back (about a week later). Hans, could you help on this instead of me while I'm away? Thanks in advance, Tat On Nov 25, 2007, at 5:37 PM, Durk Talsma wrote: On Saturday 24 November 2007 22:06, Hans Fugal wrote: On OSX, for some unknown reason the sun is displayed as a square (or diamond, if you like) instead of as a circle. Unknown to me, anyway; I think the MacFlightGear folks have a patch. Here's a screenshot: http://hans.fugal.net/tmp/fg/square-sun.png In your earlier mail, you mentioned that this problem showed up relatively recently. It seems like a particular type of texture blending isn't working anymore (The sun basically consists of two textures with radially increasing alpha values that blend into to the sky, thus creating an inner and an outer halo). If you have an idea around what time this problem occurred, could you try to revert to an older revision, and try to pin point the date when this problem occurred? Also, could it be related to a video driver? I'm not seeing this problem here, so I'm a afraid I'm not much use in trying to help debugging this problem. Cheers, Durk - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel SimGear-0.3.10-shadow-MacOSX.diff Description: Binary data - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Hans,
one more report before I leave ;-)
Actually, I don't see the weather problems that you have. (I tested on
my MacBook Pro)
I chose Thunderstorm from the Weather Scenario dialog and closed it.
When I opened it again, it still says Thunderstorm. even with --
enable-real-weather-fetch option.
When I added --enable-real-weather-fetch option, the dialog says
none as you mentioned.
but when I choose METAR, then the weather changes to METER mode.
Plus, when I manually adjust the weather conditions in METER mode,
the numbers that I adjusted were still there when I open the weather
condition dialog again.
When I select METAR manually after I selected thunderstorm,
the weather is still thunderstorm even the dialog shows METAR.
In this case, I didn't add --enable-real-weather-fetch, so this
could be normal behavior.
This is what I got. Is this what you expect or not?
I also want to know the weather related behavior on other platforms.
If you don't see the same thing on your Mac, please try all the
patches that I have. these can be obtained from:
http://macflightgear.svn.sourceforge.net/viewvc/macflightgear/branches/0.9.11/patches/
FlightGear-0.9.10-MacOSX.diff is the patch for the sun gets rendered
properly as I posted before.
SimGear-0.3.10-MacOSX.diff includes the patch that I posted on the
last email on the list.
This also contains the patch for missing OpenAL on Macs. so you can
apply the patch that I enclosed on my last post instead of this
if you already have your own version of OpenAL patch.
SimGear-0.3.10-MacOSX-Splash.diff is only for PPC Macs to avoid
getting broken splash screen so you don't probably need that.
This is due to (I guess) a bug in gzlib on PPC Macs since this bug
doesn't occur on Intel Macs.
I'm very happy If you give me any feedbacks on these patches.
I'll reply when I'm back.
Hope it helps,
Tat
On Nov 26, 2007, at 12:50 PM, Hans Fugal wrote:
Hi Tat, thanks. That's the same patch that I mentioned elsewhere in
this thread. I can test on linux tomorrow but not windows.
As for the weather, I haven't tested it explicitly in linux the last
day or so, but IIRC it is not OS X specific.
On Nov 25, 2007 7:09 PM, Tatsuhiro Nishioka [EMAIL PROTECTED]
wrote:
Hans,
Why don't you try this patch for the sun problem.
This is for 0.9.10 but should work on 0.9.11-pre2.
The cause of this problem is the order of adding texture path.
Thus I changed its order so the sun gets rendered properly.
Durk, (and more developers), could you test this patch so it can run
on linux and windows properly?
If so, please apply this patch. Otherwise, I'm gonna make a new patch
with #ifdef __APPLE__ #endif closure
not to affect other platforms.
About the weather problem, let me check it later.
I'm gonna be out for a while for a business trip so I'll check that
later.
Best,
Tat
--- org/FlightGear-0.9.10/src/Main/main.cxx 2006-03-21
10:52:29.0 -0800
+++ flightgear/FlightGear/src/Main/main.cxx 2006-11-20
16:06:35.0 -0800
@@ -787,13 +787,6 @@
// TODO: move to environment mgr
thesky = new SGSky;
-SGPath texture_path(globals-get_fg_root());
-texture_path.append(Textures);
-texture_path.append(Sky);
-for (int i = 0; i FGEnvironmentMgr::MAX_CLOUD_LAYERS; i+
+) {
-SGCloudLayer * layer = new
SGCloudLayer(texture_path.str());
-thesky-add_cloud_layer(layer);
-}
SGPath sky_tex_path( globals-get_fg_root() );
sky_tex_path.append( Textures );
@@ -812,6 +805,15 @@
globals-get_ephem()-getNumStars(),
globals-get_ephem()-getStars() );
+
+SGPath texture_path(globals-get_fg_root());
+texture_path.append(Textures);
+texture_path.append(Sky);
+for (int i = 0; i FGEnvironmentMgr::MAX_CLOUD_LAYERS; i+
+) {
+SGCloudLayer * layer = new
SGCloudLayer(texture_path.str());
+thesky-add_cloud_layer(layer);
+}
+
// Initialize MagVar model
SGMagVar *magvar = new SGMagVar();
globals-set_mag( magvar );
On Nov 25, 2007, at 6:06 AM, Hans Fugal wrote:
I verified that these two do still exist. Allow me to elaborate,
though they have been reported before.
On OSX, for some unknown reason the sun is displayed as a square (or
diamond, if you like) instead of as a circle. Unknown to me,
anyway; I
think the MacFlightGear folks have a patch. Here's a screenshot:
http://hans.fugal.net/tmp/fg/square-sun.png
The weather bug is in two pieces, actually. First, when you go into
the Weather Scenario dialog, None is always selected, regardless
of
what weather is actually being used. If one is using real weather
fetch as I am, it should say METAR.
When real weather fetch is enabled, no matter what Weather Scenario
(thunderstorm, none, fair) or what conditions or clouds I set
Re: [Flightgear-devel] FlightGear prerelease
On Saturday 24 November 2007 18:39, Hans Fugal wrote: OS X Leopard (10.5) on a Macbook, gcc 4.0.1, a patched plib 1.8.4. Simgear 0.3.11-pre2 needs the following patch in order to build: Okay Done. Thanks. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear prerelease
Sorry if I mislead. To my knowledge this square sun has been the case
for a long time. The patch I was thinking of comes from the
macflightgear 0.9.10 sources. I have applied it (with a little fuzz)
to pre2 and it does solve the problem. Here it is:
--- org/FlightGear-0.9.10/src/Main/main.cxx 2006-03-21 10:52:29.0 -0
800
+++ flightgear/FlightGear/src/Main/main.cxx 2006-11-20 16:06:35.0 -0
800
@@ -787,13 +787,6 @@
// TODO: move to environment mgr
thesky = new SGSky;
-SGPath texture_path(globals-get_fg_root());
-texture_path.append(Textures);
-texture_path.append(Sky);
-for (int i = 0; i FGEnvironmentMgr::MAX_CLOUD_LAYERS; i++) {
-SGCloudLayer * layer = new SGCloudLayer(texture_path.str());
-thesky-add_cloud_layer(layer);
-}
SGPath sky_tex_path( globals-get_fg_root() );
sky_tex_path.append( Textures );
@@ -812,6 +805,15 @@
globals-get_ephem()-getNumStars(),
globals-get_ephem()-getStars() );
+
+SGPath texture_path(globals-get_fg_root());
+texture_path.append(Textures);
+texture_path.append(Sky);
+for (int i = 0; i FGEnvironmentMgr::MAX_CLOUD_LAYERS; i++) {
+SGCloudLayer * layer = new SGCloudLayer(texture_path.str());
+thesky-add_cloud_layer(layer);
+}
+
// Initialize MagVar model
SGMagVar *magvar = new SGMagVar();
globals-set_mag( magvar );
It only happens for me on OS X, I have never seen this problem on
Linux. It happened on my iBook and MacBook running Tiger, and now on
my MacBook running Leopard.
On Nov 25, 2007 1:37 AM, Durk Talsma [EMAIL PROTECTED] wrote:
On Saturday 24 November 2007 22:06, Hans Fugal wrote:
On OSX, for some unknown reason the sun is displayed as a square (or
diamond, if you like) instead of as a circle. Unknown to me, anyway; I
think the MacFlightGear folks have a patch. Here's a screenshot:
http://hans.fugal.net/tmp/fg/square-sun.png
In your earlier mail, you mentioned that this problem showed up relatively
recently. It seems like a particular type of texture blending isn't working
anymore (The sun basically consists of two textures with radially increasing
alpha values that blend into to the sky, thus creating an inner and an outer
halo). If you have an idea around what time this problem occurred, could you
try to revert to an older revision, and try to pin point the date when this
problem occurred? Also, could it be related to a video driver?
I'm not seeing this problem here, so I'm a afraid I'm not much use in trying
to help debugging this problem.
Cheers,
Durk
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Hans Fugal
Fugal Computing
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
