Re: [Flightgear-devel] ssgLoadAC error on KEMT + patch
David Luff [EMAIL PROTECTED] said: Glad someone's using it :-) However, that callsign raises an issue. Firstly, the reg on c172-dpm is N301DP, so I guess it ought to be Trainer-one-delta-papa! Secondly, what happens when we get more than one airport in the base package with AI support (hopefully within a few months), and possibly more than one AI plane per busy GA airport (probably a bit longer - algorithms to stop them taxiing on the same bit of tarmac are non-trivial!!!). They can't all use the same callsign! It should be easy to assign different pseudo-random callsigns in the AI code, but what about the visual model? Is it feasable to have a range of letters and numerals to stick on for the reg as per the runways, or should I forget about this right now? You could do something similar to the navigation ids on the 747 glass cockpit display (using texture animation). Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ssgLoadAC error on KEMT + patch
On 9/18/03 at 11:25 PM Thomas Arendsen Hein wrote: When updating from CVS I got a conflict in AILocalTraffic.cxx, because I removed two obsolete lines in my patch which still are in CVS. The problem is, I forgot to attach my patch! So here is another one which removes these two lines. Thomas Thanks Thomas, this is now in CVS. Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ssgLoadAC error on KEMT + patch
On Wed, Sep 17, 2003 at 11:45:14AM +0200, Erik Hofman wrote: Thomas Arendsen Hein wrote: When trying to start fgfs --airport=KEMT I get: WARNING: ssgLoadAC: Failed to open '/fg_root/Aircraft/c172/Models/c172-dpm.ac/Aircraft/c172/Models/c172-dpm.ac' for reading with current SimGear/FlightGear CVS. The attached patch fixes the problem, since sgLoad3DModel expects fg_root as the first parameter, not the full path to the model. Thanks for the catch. I've put a fix in CVS. When updating from CVS I got a conflict in AILocalTraffic.cxx, because I removed two obsolete lines in my patch which still are in CVS. The problem is, I forgot to attach my patch! So here is another one which removes these two lines. Thomas -- Email: [EMAIL PROTECTED] (at work: [EMAIL PROTECTED]) http://jtah.de/ Index: src/ATC/AILocalTraffic.cxx === RCS file: /var/cvs/FlightGear-0.9/source/src/ATC/AILocalTraffic.cxx,v retrieving revision 1.21 diff -u -r1.21 AILocalTraffic.cxx --- src/ATC/AILocalTraffic.cxx 17 Sep 2003 09:44:37 - 1.21 +++ src/ATC/AILocalTraffic.cxx 18 Sep 2003 21:20:49 - @@ -154,8 +154,6 @@ //cout FGAILocalTraffic.Init(...) called endl; // Hack alert - Hardwired path!! string planepath = Aircraft/c172/Models/c172-dpm.ac; - SGPath path = globals-get_fg_root(); - path.append(planepath); ssgBranch *model = sgLoad3DModel( globals-get_fg_root(), planepath.c_str(), globals-get_props(), ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ssgLoadAC error on KEMT + patch
Thomas Arendsen Hein wrote: Hallo! When trying to start fgfs --airport=KEMT I get: WARNING: ssgLoadAC: Failed to open '/fg_root/Aircraft/c172/Models/c172-dpm.ac/Aircraft/c172/Models/c172-dpm.ac' for reading with current SimGear/FlightGear CVS. The attached patch fixes the problem, since sgLoad3DModel expects fg_root as the first parameter, not the full path to the model. Now I can enjoy hunting Trainer-two-five-charlie again :) Thanks for the catch. I've put a fix in CVS. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ssgLoadAC error on KEMT + patch
On 9/16/03 at 9:47 PM Thomas Arendsen Hein wrote: Hallo! When trying to start fgfs --airport=KEMT I get: WARNING: ssgLoadAC: Failed to open '/fg_root/Aircraft/c172/Models/c172-dpm.ac/Aircraft/c172/Models/c172-dpm.ac ' for reading with current SimGear/FlightGear CVS. The attached patch fixes the problem, since sgLoad3DModel expects fg_root as the first parameter, not the full path to the model. Hi Thomas, Thanks very much for the patch. That fixes the pink plane problem I've been seeing with the AI plane recently. Now I can enjoy hunting Trainer-two-five-charlie again :) Glad someone's using it :-) However, that callsign raises an issue. Firstly, the reg on c172-dpm is N301DP, so I guess it ought to be Trainer-one-delta-papa! Secondly, what happens when we get more than one airport in the base package with AI support (hopefully within a few months), and possibly more than one AI plane per busy GA airport (probably a bit longer - algorithms to stop them taxiing on the same bit of tarmac are non-trivial!!!). They can't all use the same callsign! It should be easy to assign different pseudo-random callsigns in the AI code, but what about the visual model? Is it feasable to have a range of letters and numerals to stick on for the reg as per the runways, or should I forget about this right now? Cheers - Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] ssgLoadAC error on KEMT + patch
On Wed, 17 Sep 2003 13:28:56 +0100, David Luff [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]: On 9/16/03 at 9:47 PM Thomas Arendsen Hein wrote: Thanks very much for the patch. That fixes the pink plane problem I've been seeing with the AI plane recently. Now I can enjoy hunting Trainer-two-five-charlie again :) Glad someone's using it :-) However, that callsign raises an issue. Firstly, the reg on c172-dpm is N301DP, so I guess it ought to be Trainer-one-delta-papa! Secondly, what happens when we get more than one airport in the base package with AI support (hopefully within a few months), and possibly more than one AI plane per busy GA airport (probably a bit longer - algorithms to stop them taxiing on the same bit of tarmac are non-trivial!!!). They can't all use the same callsign! It should be easy to assign different pseudo-random callsigns in the AI code, but what about the visual model? Is it feasable to have a range of letters and numerals to stick on for the reg as per the runways, or should I forget about this right now? ..2 parts: Adding serial/reg/etc number textures to the 3d graphics? ..and _assigning_ these numbers from FG to all, here is all kindsa schemes possible, for one-off like the Spirit of St.Louis and the EAA replica of the same, this is trivial, they have 1 N-number each. ..for the future lot of several 54 plane combat box formations of B-17's, we might wanna generate serial numbers off ip's or somesuch. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] ssgLoadAC error on KEMT + patch
Hallo! When trying to start fgfs --airport=KEMT I get: WARNING: ssgLoadAC: Failed to open '/fg_root/Aircraft/c172/Models/c172-dpm.ac/Aircraft/c172/Models/c172-dpm.ac' for reading with current SimGear/FlightGear CVS. The attached patch fixes the problem, since sgLoad3DModel expects fg_root as the first parameter, not the full path to the model. Now I can enjoy hunting Trainer-two-five-charlie again :) Thomas -- Email: [EMAIL PROTECTED] (at work: [EMAIL PROTECTED]) http://jtah.de/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
