Re: [Flightgear-devel] Re: "old" 3d clouds code
On Montag 13 Juni 2005 11:03, Melchior FRANZ wrote: > Probably a good idea. The old code is broken, unmaintained, and uses nasty > binary cloud definition files, while the new code yields much better > results (except when flying through clouds). The old code may be more > advanced in some respect (and slower :-), but it'll remain in the Attic/ > anyway, so if someone wants to pick it up again, fix it, and make it better > than the new clouds, go ahead ... Hmm, while I am a bit late now. I have not used the new code for some weeks. That is because of a crash in the OpenGL driver when called from the 'render in texture' initialization. So I cannot really tell how it looks like. Since nobody other complained I think it is a problem in this driver. So the last thing I remembered was that flying through clouds was much better with the old code. The new clouds seem to be afraid from an aircraft. They just move out of the flight path. As a result you almost never fly through clouds. Is this still the case? And if so, could the new cloud code be changed to behave like the old one in this case? If I understood right the Harris code really simulates the air. That means one could extract realistic upwinds and downwinds from that simulation. It's a pity, but since I don't have the time to look into that I cannot vote for keeping that ... Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] A380 3D model FDM reference point
On June 13, 2005 02:40 pm, Innis Cunningham wrote: > Hi Martin > > Martin Spott writes > > >Hello, just an informal note > >To my impression the A380 needs an offset vector for the FDM reference > >point in order to make it rotate around its CG. Could the author > >confirm ? > > This is correct I was going to move the whole 3D model in AC3D after > everything > was finished but that has not happened yet.If you want to provide offsets > for it > feel free > > >Cheers, > > Martin. > > Cheers > Innis If there is going to be changes to the A380-set.xml, please wait until Curt has uploaded my updates first, which should be anytime now... On the subject of finishing the A380, is there any kind soul who wouldn't mind helping me to come up with a few Nasal scripts? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] poll
Water isn't the only other material that should be modelled. There are also other materials such as grass and soil. Right now, I can take a short cut across the grass in any airport without concern, and these sort of behaviours should bring some consequences. =) Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Completely OT (but aviation related.)
On Mon, 13 Jun 2005 13:39:21 -0500, Curtis wrote in message <[EMAIL PROTECTED]>: > Arnt Karlsen wrote: > > > On Mon, 13 Jun 2005 12:14:09 -0500, Curtis wrote in message > > <[EMAIL PROTECTED]>: > > > > > http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/ > > > If you scroll down a bit there's a take off picture (with the tail > > > wheel just coming up) and then two landing pictures (notice the > > > position of the airplane relative to the shadow.) > > > > ..but there were other arrivals? ;o) > > http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/Link/IMG_2045.html > > That's one of my favorite non-flight pictures because of the sun > angle. It's taken in my driveway so there was no flying that day. ..those prop tips, ... taxiing? ;o) > One of these days it would be fun to rig up a wireless camera on > board. I could do several flights with different camera placements > and orientations, mix in some ground footage, set to music, and it > could come out looking really cool. I've got an ultra cheap wireless > video system, but it has horribly short range and horribly heavy > batteries, and a really crappy camera so it's not very good for > flying (and not much good for anything else for that matter.) :-) ..you're thinking about flying "the video"? Use those batteries in your 1/4 scale Colditz bath tub and wind up a generator spool and feed it magnetism off your magnetic prop drive flange. Tap that spool thru a diode bridge and a 7805, smooth things with a coupla capasitors each side of the 7805, and hike the 7805's 5.0VDC with a .3V zener diode to 5.3VDC. You want sound too. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] poll
On Mon, 13 Jun 2005 22:11:42 +0200, Gerard wrote in message <[EMAIL PROTECTED]>: > It was said that we do not have to make the Hollywood quality movie > and i agree. ..we have enough to get funding for the missing bits. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Backing out Andy's p51d changes
Jim Wilson wrote > P.S. Any chance someone good with nasal could write me a quick script for > changing the BOOST value to 1.0 at 20,000FT ASL and then back to 0.4 at > 19,999.99FT? I'd try and figure it out, but my time is very limited right > now. tia > If you still want this stuff - a Nasal file is attached which monitors altitude asl and changes the boost setting appropriately. I've added a 50ft dead zone to prevent hunting: seems to work OK here. Put it in P51d/models. You'll need to add this to the p51d-set.xml file: Aircraft/p51d/Models/p51d.nas Regards Vivian p51d.nas Description: Binary data ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Gerard Robin schrieb: I can give to Ralf the prize, if everybody agree. Thanks, too much honor ;-) Ralf ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] poll
> > > > > If someone wants to make a submarine simulator then they are > > > > > welcome to make a fork of FlightGear and name it SubGear but > > > > > I'm interested in aerodynamics and not aquadynamics. > > > > > > > > ...then we have the waves made by the aircraft floats. ;o) > > > > > > You are right and today we have to search for the best effect with > > > an object animated like the aircraft shadow. I have tried to do it > > > http://ghours.club.fr/Walrus-Villefranche1.jpg > > ...neat plane, but your sparkling waveless "spray" demos my point nicely, > dunk a Walrus into 5 thru 25ft seas, and you'll find that the one ton > big toothed seal can spank you mildly thru _roundly_, just like the > water the plane lands or dunks into. ;o) > > > > May be with Sparkle we could get a better aspect > > > > And I forgot: Plib include some functions in _SSG Auxiliary Libraries_ > > which are very useful. > > ...useful to model physical forces? Or just to hit the degauss button > remotely to simulate a nose punch? ;o) > > ...don't read me as "we have enough fancy eyecandy", we need more of that > too, but we also need "running water" here. ;o) > Anyway, that is mainly to illustrate the discussion, to demonstrate the limitation of our system (today). I did it only on that Walrus because it is little (the animation is only driven by the aircraft speed, agl and pitch). It was said that we do not have to make the Hollywood quality movie and i agree. However we could try to find the way which drive to get the best picture, with a combination of specific animations driven by speed, forces,... light processing, and characteristics of materials. It is a pity to see a seaplane taking off, and nothing happen on the sea level , the ground-effect is able to give parameters which could help the design. The new 3D clouds are a good exemple of programming ressource, which could be used to simulate random waves ( i will get god lightnings or rather devil fires, if i continu in that way ). -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 20:07 +0200, Ralf Gerlich a écrit :
> Hi,
>
> Gerard Robin wrote:
> > open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE) =
> > -1 ENOENT (No such file or directory)
> ^^
> Did you see those blanks at the end of the filename? Are these actually
> in the original report? Where could these come from?
>
> Ralf
>
Yes now that is good, my first correction introduced probably an other
blank.
After using Emacs no Problem (ahrrg kedit),
i continu to learn where are the traps.
I can give to Ralf the prize, if everybody agree.
And many thanks to everybody.
--
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 20:53: > I had a little break for dinner, now: > > the answer for Entertain: It's not funny any more, now that we know that you fooled us by adding two spaces to the ~/.fgfsrc config line. ;-) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] poll
On Mon, 13 Jun 2005 01:50:21 +0200, Gerard wrote in message <[EMAIL PROTECTED]>: > Le lundi 13 juin 2005 à 01:13 +0200, Gerard Robin a écrit : > > Le dimanche 12 juin 2005 à 22:07 +0200, Arnt Karlsen a écrit : > > > On Sun, 12 Jun 2005 10:43:44 +0200, Paul wrote in message > > > <[EMAIL PROTECTED]>: > > > > > > > On Sunday, 12 June 2005 09:22, Erik Hofman wrote: > > > > > Ampere K. Hardraade wrote: > > > > > > I like that idea. It would be nice to fly along the coast > > > > > > of a tropical island, look down and be able to see the white > > > > > > sand under the water... or flying above a coral reef and see > > > > > > the corals on the sea floor. =) > > > > > > > > > > > > Seperating land and water will also allow tidal effects to > > > > > > be modelled. As for underwater exploration, I for one > > > > > > wouldn't mind taking the UFO down and see some underwater > > > > > > landmarks such as the Titanic. hehe. > > > > > > > > > > I think we're all getting carried away a bit. We are aiming at > > > > > a professional *flightsimulator* to be used as a training aid, > > > > > not for Hollywood film making. > > > > > > ...the funny thing is, FG _is_ useable for film making, and > > > wasting some time on making an "Hollywood film" could easily land > > > us some serious funding to do the things we wanna do. > > > > > > > > Erik > > > > > > > > Personally I don't care much for submarines and sealife in a > > > > flight sim. What Flight Unlimited did was when you crashed in > > > > water the screen went a murky water color and your altitude > > > > starts heading for negative figures. No fish, no sharks and no > > > > coral but you get the point that you just crashed into water > > > > and that should be sufficient in my opinion. > > > > > > ...true, but landing a sea plane in any significant weather, means > > > we should model sea states, waves behave differently depending on > > > things like currents, depth, wind etc, also on lakes and rivers. > > > > > > If someone wants to make a submarine simulator then they are > > > > welcome to make a fork of FlightGear and name it SubGear but > > > > I'm interested in aerodynamics and not aquadynamics. > > > > > > ...then we have the waves made by the aircraft floats. ;o) > > > > You are right and today we have to search for the best effect with > > an object animated like the aircraft shadow. I have tried to do it > > http://ghours.club.fr/Walrus-Villefranche1.jpg ..neat plane, but your sparkling waveless "spray" demos my point nicely, dunk a Walrus into 5 thru 25ft seas, and you'll find that the one ton big toothed seal can spank you mildly thru _roundly_, just like the water the plane lands or dunks into. ;o) > > May be with Sparkle we could get a better aspect > > And I forgot: Plib include some functions in _SSG Auxiliary Libraries_ > which are very useful. ..useful to model physical forces? Or just to hit the degauss button remotely to simulate a nose punch? ;o) ..don't read me as "we have enough fancy eyecandy", we need more of that too, but we also need "running water" here. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 19:58 +0200, Melchior FRANZ a écrit :
> * Gerard Robin -- Monday 13 June 2005 19:41:
> > Not so Quick..
> >
> > Oh do you remember i told you :
>
> I do remember. But I don't believe you.
>
>
>
> > fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le-
> > boss/.fgfs/preferences.xml
>
> Entertain us and post the output of
>
> $ strace -fF -eopen fgfs --config=/home/tux-le-boss/.fgfs/preferences.xml
> 2>&1|grep tux
>
> Should be from the same machine, of course, and with the (non)file
> unchanged.
>
> m.
>
I had a little break for dinner, now:
the answer for Entertain:
$ strace -fF -eopen fgfscvs --config=/home/tux-le-
boss/.fgfs/preferences.xml 2>&1|grep tux-le
open("/home/tux-le-boss/.fgfsrc.servlinux.gours", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/home/tux-le-boss/.fgfsrc.servlinux.gours.gz", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/home/tux-le-boss/.fgfsrc", O_RDONLY) = 3
open("/home/tux-le-boss/.fgfsrc.servlinux.gours", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/home/tux-le-boss/.fgfsrc.servlinux.gours.gz", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/home/tux-le-boss/.fgfsrc", O_RDONLY) = 3
open("/home/tux-le-boss/.fgfsrc", O_RDONLY) = 5
open("/home/tux-le-boss/.fgfsrc.servlinux.gours", O_RDONLY) = -1 ENOENT
(No such file or directory)
open("/home/tux-le-boss/.fgfsrc.servlinux.gours.gz", O_RDONLY) = -1
ENOENT (No such file or directory)
open("/home/tux-le-boss/.fgfs/preferences.xml", O_RDONLY|O_LARGEFILE) =
5
>
--
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Completely OT (but aviation related.)
> From: "Curtis L. Olson" > > This is not FG related, but I figured I'd do a little show and tell. > I've been collecting a few pictures, so I thought I should share them. > I may have mentioned in the past that I do a bit of R/C airplane > modeling. Last fall I found such a good deal on a ready to fly, kit > built Citabria (with engine and radio) that it was impossible to pass it > up. It's a beautiful plane and relatively big. It has an 84" wingspan > (which is about 2.14 meters.) I flew it Thursday for the first time, > and then Saturday in my local club's scale fly-in. I have a couple > pictures here: > > http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/ > That is big. Our cat wants me to tell you he volunteers to be a test pilot. Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Completely OT (but aviation related.)
Arnt Karlsen wrote: On Mon, 13 Jun 2005 12:14:09 -0500, Curtis wrote in message <[EMAIL PROTECTED]>: http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/ If you scroll down a bit there's a take off picture (with the tail wheel just coming up) and then two landing pictures (notice the position of the airplane relative to the shadow.) ..but there were other arrivals? ;o) http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/Link/IMG_2045.html That's one of my favorite non-flight pictures because of the sun angle. It's taken in my driveway so there was no flying that day. One of these days it would be fun to rig up a wireless camera on board. I could do several flights with different camera placements and orientations, mix in some ground footage, set to music, and it could come out looking really cool. I've got an ultra cheap wireless video system, but it has horribly short range and horribly heavy batteries, and a really crappy camera so it's not very good for flying (and not much good for anything else for that matter.) :-) Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Ralf Gerlich -- Monday 13 June 2005 20:07:
> > Gerard Robin wrote:
> > > open("/home/tux-le-boss/.fgfs/preferences.xml ", [...]
> > ^^
> > Did you see those blanks at the end of the filename? Are these actually
> > in the original report? Where could these come from?
>
> Arghh. Good catch! Apparently, fgfs doesn't strip that. And Gerard
> uses a crappy editor.
Maybe this should be changed like so:
diff -u -p -U1 -r1.67 options.cxx
--- options.cxx 25 Feb 2005 21:20:17 - 1.67
+++ options.cxx 13 Jun 2005 18:39:45 -
@@ -1537,3 +1537,3 @@ fgParseOptions (const string& path) {
// catch extraneous (DOS) line ending character
-if ( line[line.length() - 1] < 32 ) {
+while ( line[line.length() - 1] <= 32 ) {
line = line.substr( 0, line.length()-1 );
or more efficient ... :-)
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Melchior FRANZ -- Monday 13 June 2005 20:24: > Add this to your ~/.vimrc and become a happier man: > > set listchars=tab:¦¯,trail:×,extends:»,precedes:« > or this: > > set listchars=tab:°`,trail:°,extends:>,precedes:< followed by set list of course, ... m. :-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Completely OT (but aviation related.)
On Mon, 13 Jun 2005 12:14:09 -0500, Curtis wrote in message <[EMAIL PROTECTED]>: > http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/ > > If you scroll down a bit there's a take off picture (with the tail > wheel just coming up) and then two landing pictures (notice the > position of the airplane relative to the shadow.) ..but there were other arrivals? ;o) http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/Link/IMG_2045.html -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 20:07 +0200, Ralf Gerlich a écrit :
> Hi,
>
> Gerard Robin wrote:
> > open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE) =
> > -1 ENOENT (No such file or directory)
> ^^
> Did you see those blanks at the end of the filename? Are these actually
> in the original report? Where could these come from?
>
> Ralf
>
Yes I did observe it, after modification ==> no change, it could have
been a good explanation.
thanks
--
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Ralf Gerlich -- Monday 13 June 2005 20:07:
> Gerard Robin wrote:
> > open("/home/tux-le-boss/.fgfs/preferences.xml ", [...]
> ^^
> Did you see those blanks at the end of the filename? Are these actually
> in the original report? Where could these come from?
Arghh. Good catch! Apparently, fgfs doesn't strip that. And Gerard
uses a crappy editor.
Add this to your ~/.vimrc and become a happier man:
set listchars=tab:¦¯,trail:×,extends:»,precedes:«
or this:
set listchars=tab:°`,trail:°,extends:>,precedes:<
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Camera/FOV/View Frustum question.
Ok, I figured out what's wrong. I'm trying to set the right properties, but those properties don't exist. I know this is a newbie question, but what's the procedure for creating and initializing a property node? I tried defining it in preferences.xml, but that just gave an error. Thanks, Drew On 6/13/05, Drew <[EMAIL PROTECTED]> wrote: > > Yes, I think I was successful in adding support for asymmetric view > > frustums. It's a bit of a hack to get there, but the way I have set it > > up I think is slightly more intuitive than just passing l, r, t, b, n, f > > parameters to the glFrustum() function. > > . > > . > > . > > --prop:/sim/current-view/frustum-left-pct=0.0 > > --prop:/sim/current-view/frustum-right-pct=0.33 > > Curt, > > I know I'm reviving a somewhat old thread here, but I'm trying to use > this code to implement something similar. It's a digital > pan/tilt/zoom camera control, and since I'm panning around a piece of > an image, it's the same situation with an offset image center. > > Anyway, I'm modifying these properties real-time, and it's not > changing anything. Is this something that will only work during > startup, or am I doing something wrong? Is there a function I can > call to force the changes to work real-time? Are they too > computationally intensive for this (I don't imagine it would be, since > you can rotate a standard view in a similar way). > > Thanks, > Drew > ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] The invisible file search
Hello, Have been reading the thread on the unreadable preferences file, and noticed a small detail that may be a clue. In the subject line of "writing rules ... in fgfsrc", I see an odd block character just before the "f" in "fgfsrc". It appears in messages from Gerard and Andy, but not those from Melchior. Is there a chance a non-ASCII or non-printing character snuck in so the paths do not actually match? Reading the mail with Thunderbird 1.0.2 on an XP system. In some messages it renders as a multiple space, possibly a tab. -- Bill Earnest [EMAIL PROTECTED] Linux Powered Allentown, PA, USA Computers, like air conditioners, work poorly with Windows open. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Hi,
Gerard Robin wrote:
open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
^^
Did you see those blanks at the end of the filename? Are these actually
in the original report? Where could these come from?
Ralf
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 19:41: > Not so Quick.. > > Oh do you remember i told you : I do remember. But I don't believe you. > fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le- > boss/.fgfs/preferences.xml Entertain us and post the output of $ strace -fF -eopen fgfs --config=/home/tux-le-boss/.fgfs/preferences.xml 2>&1|grep tux Should be from the same machine, of course, and with the (non)file unchanged. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Gerard wrote: > Melchior wrote: > > Yes, and I was right: this file just doesn't exist! This is not an > > fgfs message, but one of the operating system. > > Not so Quick.. > Oh do you remember i told you : You can't really argue with a syscall result. The file isn't there. Maybe there are some other conditions (lack of x permissions in a directory on the path?) that will produce an ENOENT instead of an EPERM, so it's not impossible that the file is present. But the bottom line is that fgfs can't read the file. We can't debug this for you; you need to figure out your system configuration first. Try, as the user running fgfs, things like: ls -l /home/tux-le-boss/.fgfs/preferences.xml cat /home/tux-le-boss/.fgfs/preferences.xml > /dev/null more /home/tux-le-boss/.fgfs/preferences.xml You will eventually discover what the problem is. Again, the syscall result is telling: you can argue on the mailing list until you collapse from exhaustion and you will never convince the OS that the file is there. :) Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 19:31 +0200, Melchior FRANZ a écrit :
> * Gerard Robin -- Monday 13 June 2005 19:19:
> > open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE) = -1
> > ENOENT (No such file or directory)
>
> Yes, and I was right: this file just doesn't exist! This is not an
> fgfs message, but one of the operating system.
>
> m.
Not so Quick..
Oh do you remember i told you :
fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le-
boss/.fgfs/preferences.xml
Working positive result
>
> Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 19:19:
> open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE) = -1
> ENOENT (No such file or directory)
Yes, and I was right: this file just doesn't exist! This is not an
fgfs message, but one of the operating system.
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Gerard:
> --config=/home/tux-le-boss/.fgfs/preferences.xml
>
> Error loading config file: Failed to open file
> at /home/tux-le-boss/.fgfs/preferences.xml
Melchior:
> Well, then this file just doesn't exist or has wrong permissions.
Gerard:
> Yes Existing, good permissions
Melchior:
> Try this:
> $ strace -fF -eopen fgfs 2>&1|grep tux
Gerard:
> open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE)
> = -1 ENOENT (No such file or directory)
Ding ding ding! We have a winner! :)
Andy
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 18:53 +0200, Melchior FRANZ a écrit :
> strace -fF -eopen fgfs 2>&1|grep tux
The answer is:
open("/home/tux-le-boss/.fgfsrc.servlinux.gours", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/home/tux-le-boss/.fgfsrc.servlinux.gours.gz", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/home/tux-le-boss/.fgfsrc", O_RDONLY) = 3
open("/home/tux-le-boss/.fgfsrc.servlinux.gours", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/home/tux-le-boss/.fgfsrc.servlinux.gours.gz", O_RDONLY) = -1 ENOENT (No
such file or directory)
open("/home/tux-le-boss/.fgfsrc", O_RDONLY) = 3
open("/home/tux-le-boss/.fgfsrc", O_RDONLY) = 5
open("/home/tux-le-boss/.fgfs/preferences.xml ", O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
at /home/tux-le-boss/.fgfs/preferences.xml
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Completely OT (but aviation related.)
This is not FG related, but I figured I'd do a little show and tell. I've been collecting a few pictures, so I thought I should share them. I may have mentioned in the past that I do a bit of R/C airplane modeling. Last fall I found such a good deal on a ready to fly, kit built Citabria (with engine and radio) that it was impossible to pass it up. It's a beautiful plane and relatively big. It has an 84" wingspan (which is about 2.14 meters.) I flew it Thursday for the first time, and then Saturday in my local club's scale fly-in. I have a couple pictures here: http://www.flightgear.org/~curt/Models/Current/MidwestCitabria/ If you scroll down a bit there's a take off picture (with the tail wheel just coming up) and then two landing pictures (notice the position of the airplane relative to the shadow.) I am also involved with the UMN Aerospace Engineering department building a UAV. I am the airframe assembler/maintainer and chief test pilot. We've done a successful maiden flight of our airframe, but haven't started plugging in any avionics. http://www.flightgear.org/~curt/Models/Construction/Rascal110/ It's not quite a "predator" or "global hawk" but it sure is a lot of fun to fly. :-) It's by far the biggest R/C airplane I've flown. Oh, and if that wasn't enough to distract me from my FG duties, I'm also building my own "low cost" UAV. I have the airframe up and flying. I have the stabalization system installed and tested. My next step is to get the flight computer up and running and begin working on the programming for that. My primary goal is to get a self stable, self navigating airplane up and flying very inexpensively. Beyond that, we'll just have to see what little toys (radio modem? wireless video? etc.?) I can sneak into the family budget and stay under the radar screen. :-) http://www.flightgear.org/~curt/Models/Current/EGN-1/ I do hope at some point to tie in FG to both of these UAV projects. Specifically we want to try out some ideas of using FG as a real time visualization tool for the UAV in flight ... either to draw a 2d live updated instrument panel on the ground station, or to draw a synthetic view of the world from the UAV's perspective or probably some of both. Because the UAV and maintain straight/level flight and can navigate itself (I guess I should say "will be able to") flying the airplane could simply be a matter of plunking down new waypoints on a virtual map. This isn't quite as exciting as those posts about people getting their full scale pilots licenses, but it's nice to get away from the computer screen once in a while and do something "real" even though my feet have to stay firmly on the ground. (Unless I crash, at which point there is a lot of subsequent jumping up and down and vocal noise.) :-) Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 18:34: > Le lundi 13 juin 2005 à 18:24 +0200, Melchior FRANZ a écrit : > > * Gerard Robin -- Monday 13 June 2005 17:56: > > > Error loading config file: Failed to open file > > > with .fgfsrc > > > > > > --config=/home/tux-le-boss/.fgfs/preferences.xml > > > > Well, then this file just doesn't exist or has wrong permissions. > Without your wrapper, does the system working ? It works with my wrapper, and it works with that --config line in my ~/.fgfsrc. Try this: $ strace -fF -eopen fgfs 2>&1|grep tux and see which error code it returns. Isn't really a topic for "devel" ... m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 18:34 +0200, Gerard Robin a écrit : > Le lundi 13 juin 2005 à 18:24 +0200, Melchior FRANZ a écrit : > > * Gerard Robin -- Monday 13 June 2005 17:56: > > > Error loading config file: Failed to open file > > > at /home/tux-le-boss/.fgfs/preferences.xml > > > > > > with .fgfsrc > > > > > > --config=/home/tux-le-boss/.fgfs/preferences.xml > > > > Well, then this file just doesn't exist or has wrong permissions. > > > > m. > > Yes > Existing, good permissions > > I did also something which is "verboten" i have tried under root > itself. Whoua the bad boy.. > > I'll give up. > > only one question: > Without your wrapper, does the system working ? > > I forgot to say, existing and good permissions, i prove it: Command fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le- boss/.fgfs/preferences.xml Working positive result So. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Camera/FOV/View Frustum question.
> Yes, I think I was successful in adding support for asymmetric view > frustums. It's a bit of a hack to get there, but the way I have set it > up I think is slightly more intuitive than just passing l, r, t, b, n, f > parameters to the glFrustum() function. > . > . > . > --prop:/sim/current-view/frustum-left-pct=0.0 > --prop:/sim/current-view/frustum-right-pct=0.33 Curt, I know I'm reviving a somewhat old thread here, but I'm trying to use this code to implement something similar. It's a digital pan/tilt/zoom camera control, and since I'm panning around a piece of an image, it's the same situation with an offset image center. Anyway, I'm modifying these properties real-time, and it's not changing anything. Is this something that will only work during startup, or am I doing something wrong? Is there a function I can call to force the changes to work real-time? Are they too computationally intensive for this (I don't imagine it would be, since you can rotate a standard view in a similar way). Thanks, Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 18:24 +0200, Melchior FRANZ a écrit : > * Gerard Robin -- Monday 13 June 2005 17:56: > > Error loading config file: Failed to open file > > at /home/tux-le-boss/.fgfs/preferences.xml > > > > with .fgfsrc > > > > --config=/home/tux-le-boss/.fgfs/preferences.xml > > Well, then this file just doesn't exist or has wrong permissions. > > m. Yes Existing, good permissions I did also something which is "verboten" i have tried under root itself. Whoua the bad boy.. I'll give up. only one question: Without your wrapper, does the system working ? -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 17:56: > Error loading config file: Failed to open file > at /home/tux-le-boss/.fgfs/preferences.xml > > with .fgfsrc > > --config=/home/tux-le-boss/.fgfs/preferences.xml Well, then this file just doesn't exist or has wrong permissions. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] RE: Flightgear-devel Digest, Vol 26, Issue 41
> This is how it was designed since it's main purpose was sending data to > the serial port or over the network. The file option (as it is now) is > very useful for generating log files, so it is not possible to do it > like that at this time. However, you might want to add carriagereturn to see if that helps. If it doesn't work either it would be possible to add a specialized line-separator that performs a fseek(0) just prior to writing the line. Erik Not worked also; maybe my mistake but i decided to play on generic code ,,, thanks for the help _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 17:35 +0200, Melchior FRANZ a écrit : > * Gerard Robin -- Monday 13 June 2005 17:21: > > 2/ with .fgfsrc > > --config=$FG_HOME/.fgfs/preferences.xml > > > i get the message: > > Error loading config file: Failed to open file > > at $FG_HOME/.fgfs/preferences.xml > > Shell variables aren't expanded in the config file (AFAIK). That's done > by the shell when you give it on the command line. Just write it out: > > --config=/home/robin_hood/.fgfs/preferences.xml > > m. > i did not use robin_hoodbecause of copyright but again the same message: Error loading config file: Failed to open file at /home/tux-le-boss/.fgfs/preferences.xml with .fgfsrc --config=/home/tux-le-boss/.fgfs/preferences.xml --nmea=socket,out,0.5,servlinux,5500,udp --airport=LFNH --geometry=1280x896 --enable-real-weather-fetch --timeofday=afternoon Oh... i did not say before , i had tried it... i know just a bit about Linux (since 1995) beuh and before that time UNIX... again beh . -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Vivian Meazza -- Monday 13 June 2005 17:37: > You need to have both - that would be reasonable since why would you set one > and not the other - a feature rather than a bug? It's at least a usability bug. The clouds code interprets cache_size=0 as "turn off rendering". So you can't have a value set with clouds off. This should, of course, be a separate variable. It's not like we can't afford two extra bytes on today's machines. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Melchior FRANZ > > * Gerard Robin -- Monday 13 June 2005 16:32: > > Le lundi 13 juin 2005 à 15:16 +0100, Vivian Meazza a écrit : > > > --prop:/sim/rendering/clouds3d-enable=1 > > > --prop:/sim/rendering/clouds3d-cache-size=4096 > > > Does not work the program overload the data. > You need to have both - that would be reasonable since why would you set one and not the other - a feature rather than a bug? V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 17:21: > 2/ with .fgfsrc > --config=$FG_HOME/.fgfs/preferences.xml > i get the message: > Error loading config file: Failed to open file > at $FG_HOME/.fgfs/preferences.xml Shell variables aren't expanded in the config file (AFAIK). That's done by the shell when you give it on the command line. Just write it out: --config=/home/robin_hood/.fgfs/preferences.xml m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 16:58 +0200, Melchior FRANZ a écrit :
> * Gerard Robin -- Monday 13 June 2005 16:32:
> > Le lundi 13 juin 2005 à 15:16 +0100, Vivian Meazza a écrit :
> > > --prop:/sim/rendering/clouds3d-enable=1
> > > --prop:/sim/rendering/clouds3d-cache-size=4096
>
> > Does not work the program overload the data.
>
> I have since a long time --config=$FG_HOME/preferences.xml in my ~/.fgfsrc[1]
> (where $FG_HOME is set to $HOME/.fgfs/), and this ~/.fgfs/preferences.xml
> file says (among many other things):
>
>
>
>
> INIT = func {
> setprop("/ai/models/ship/controls/glide-path", 0);
> setprop("/sim/sound/volume", 0.6);
> setprop("/sim/rendering/clouds3d-cache-size", 4096);
> }
> settimer(INIT, 0);
> ]]>
>
>
>
>
>
>
> [1] OK, that's a lie. I *had* that in my ~/.fgfsrc, but I dropped that file
> because fgrun overwrote it (which is fixed now), so I moved it into my
> ~/bin/fgfs wrapper as command line option. But that's just a minor detail.
> :-)
>
I would have to be please to you and say yes that's OK
Sorry i cannot.
sometime ago i tried it and again i get==> follow me==>
1/ with command line
fgfscvs --airport=LFNH --aircraft=P38-L --config=
$FG_HOME/.fgfs/preferences.xml
everything good :-)
2/ with .fgfsrc
--config=$FG_HOME/.fgfs/preferences.xml
--nmea=socket,out,0.5,servlinux,5500,udp
--airport=LFNH
--geometry=1280x896
--enable-real-weather-fetch
--timeofday=afternoon
i get the message:
Error loading config file: Failed to open file
at $FG_HOME/.fgfs/preferences.xml
very bad :-(
I am probably wrong somewhere :-?
thanks
>
--
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
> For Cygwin users, OpenAL needs to be retrieved from this site: > > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz > > I placed this file in the /usr directory and untar'ed it, though some > place it in the > /usr/local/ directory tree - which might be more appropriate. Some library > and dll files > are untar'ed into your bin/ and lib/ subdirectories. > > Once the files are untar'ed, you must cd to the include/AL/ subdirectory > and modify all > the files where "_WIN32" is present (use grep) and change it to simply > "WIN32" (that is, > remove the underscore). Also, in alc.h you must change the code at top to > look like this: > > #ifdef WIN32 --- CHANGE TO THIS > #ifdef _OPENAL32LIB > #define ALCAPI __declspec(dllexport) > #else > #define ALCAPI __declspec(dllimport) > #endif > > #ifdef WIN32 --- CHANGE TO THIS > typedef struct ALCdevice_struct ALCdevice; > typedef struct ALCcontext_struct ALCcontext; > #endif > > Once these changes are made, you should be able to compile simgear. > I'm just in the middle of finally pulling an faq update together (various exams cropped up). I'll put this in. Are there any other issues people want to go in? Giles Robertson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* Gerard Robin -- Monday 13 June 2005 16:32: > Le lundi 13 juin 2005 à 15:16 +0100, Vivian Meazza a écrit : > > --prop:/sim/rendering/clouds3d-enable=1 > > --prop:/sim/rendering/clouds3d-cache-size=4096 > Does not work the program overload the data. I have since a long time --config=$FG_HOME/preferences.xml in my ~/.fgfsrc[1] (where $FG_HOME is set to $HOME/.fgfs/), and this ~/.fgfs/preferences.xml file says (among many other things): [1] OK, that's a lie. I *had* that in my ~/.fgfsrc, but I dropped that file because fgrun overwrote it (which is fixed now), so I moved it into my ~/bin/fgfs wrapper as command line option. But that's just a minor detail. :-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 16:32 +0200, Gerard Robin a écrit : > Le lundi 13 juin 2005 à 15:16 +0100, Vivian Meazza a écrit : > > Gerard Robin asked > > > > > Something wrong ? > > > in fgfsrc in have: > > > > > > --geometry=1280x896 > > > --enable-real-weather-fetch > > > --timeofday=afternoon > > > --prop:/nasal/local/script= > > > > > > > > > nasal does give error message: Nasal parse error: parse error in /nasal > > > [0]/local[0], line 1 > > > > > > does writing --prop:/nasal. good > > > > > > > > > > Just do this: > > > > --prop:/sim/rendering/clouds3d-enable=1 > > --prop:/sim/rendering/clouds3d-cache-size=4096 > sorry > Does not work the program overload the data. > thanks > > > > V. > > I did not answer fully to your solution i only want cache-size=4096 I know if i buy both i get the good answer for the same cost :-) -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 07:37 -0700, Andy Ross a écrit : > > Andy Ross a écrit : > > > --prop:/sim/rendering/clouds3d-cache-size=4096 > > > > It should work but the program overload the data, only one way the > > nasal way > > That sounds like a bug to me. The command line should be overwriting > anything in the configuration files. Is the cloud code (over-)writing > this property at initialization time? > > Andy > I don't know, probably during loading, i did not looked into the code (it was said during new 3D clouds implementation, we should have to use nasal for that point) without nasal, after loading the aircraft, looking on the menu the buffer size still continu to be 1024. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] A380 3D model FDM reference point
Hi Martin Martin Spott writes Hello, just an informal note To my impression the A380 needs an offset vector for the FDM reference point in order to make it rotate around its CG. Could the author confirm ? This is correct I was going to move the whole 3D model in AC3D after everything was finished but that has not happened yet.If you want to provide offsets for it feel free Cheers, Martin. Cheers Innis ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt > > In the developers' list archives is the best we have. Cygwin wouldn't > work > > at all if it were not for the excellent work by Norman Vine. There's no > sign > > of OpenAL being ported to Cygwin at the moment, so this is the best we > have. > > We are in constant danger of being left behind. > > > > Have you got it to work yet??? I guess I could tarball up my version > here > > for you, when I have a bit more time. > > Yes. I now have a FlightGear executable - though I won't have time to try > it until this > evening at the earliest. > > I'd like to submit the text below to a FAQ or wherever it should be on the > FlightGear/SimGear site: > > --- start --- > > For Cygwin users, OpenAL needs to be retrieved from this site: > > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz > > I placed this file in the /usr directory and untar'ed it, though some > place it in the > /usr/local/ directory tree - which might be more appropriate. Some library > and dll files > are untar'ed into your bin/ and lib/ subdirectories. > > Once the files are untar'ed, you must cd to the include/AL/ subdirectory > and modify all > the files where "_WIN32" is present (use grep) and change it to simply > "WIN32" (that is, > remove the underscore). Also, in alc.h you must change the code at top to > look like this: > > #ifdef WIN32 --- CHANGE TO THIS > #ifdef _OPENAL32LIB > #define ALCAPI __declspec(dllexport) > #else > #define ALCAPI __declspec(dllimport) > #endif > > #ifdef WIN32 --- CHANGE TO THIS > typedef struct ALCdevice_struct ALCdevice; > typedef struct ALCcontext_struct ALCcontext; > #endif > > Once these changes are made, you should be able to compile simgear. > > --- end --- > Hmm ... I think we ought to correct the tarball first - we shouldn't ask people to correct it. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
> Andy Ross a écrit : > > --prop:/sim/rendering/clouds3d-cache-size=4096 > > It should work but the program overload the data, only one way the > nasal way That sounds like a bug to me. The command line should be overwriting anything in the configuration files. Is the cloud code (over-)writing this property at initialization time? Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 15:16 +0100, Vivian Meazza a écrit : > Gerard Robin asked > > > Something wrong ? > > in fgfsrc in have: > > > > --geometry=1280x896 > > --enable-real-weather-fetch > > --timeofday=afternoon > > --prop:/nasal/local/script= > > > > > > nasal does give error message: Nasal parse error: parse error in /nasal > > [0]/local[0], line 1 > > > > does writing --prop:/nasal. good > > > > > > Just do this: > > --prop:/sim/rendering/clouds3d-enable=1 > --prop:/sim/rendering/clouds3d-cache-size=4096 sorry Does not work the program overload the data. thanks > > V. > > > > ___ > Flightgear-devel mailing list > Flightgear-devel@flightgear.org > http://mail.flightgear.org/mailman/listinfo/flightgear-devel > 2f585eeea02e2c79d7b1d8c4963bae2d > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 à 07:13 -0700, Andy Ross a écrit : > --prop:/sim/rendering/clouds3d-cache-size=4096 It should work but the program overload the data, only one way the nasal way thanks -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Gerard Robin asked > Something wrong ? > in fgfsrc in have: > > --geometry=1280x896 > --enable-real-weather-fetch > --timeofday=afternoon > --prop:/nasal/local/script= > > > nasal does give error message: Nasal parse error: parse error in /nasal > [0]/local[0], line 1 > > does writing --prop:/nasal. good > > Just do this: --prop:/sim/rendering/clouds3d-enable=1 --prop:/sim/rendering/clouds3d-cache-size=4096 V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] YASim turbo/supercharger issues
Some time ago I wrote: > > Andy Ross: > > > > If you do mean this equation then I can certainly live with that. If > > > not, I'll need to put my thinking cap on ... I've updated the > > > graphical representation here: > > > > Remind me again which one of these is the "real" engine data, and what > > the source is? The only line on this graph that has the dropoff seems > > to be the polynomial you posted. The others (including the linear > > one) all have better agreement, qualitatively. We can play with other > > forms too, like c((x+1)^e - 1) (for some e < 1, and with a c that makes > > the > > slope through the origin ~ 1). > > > > The real data is series 1, but only up to rpm-normalised = 1. For values > above 1, it's just a continuation by eye of the data. > > (See http://www.turbotechnics.com/supercharger/expo.htm Note that max > power > is at 6500 rpm, and that the supercharger output is nearly flat at 7000 > rpm.) > > I selected > > y = -0.25x^3 + 0.15x^2 + 1.11x > > because that had the best fit between 0 and ~ 1.2, which was the region in > which I was most interested. This was based on the working assumption that > an engine develops rated power at more or less the full supercharger > output. > At the moment, the equation gives a reasonable match to the known > performance. All the other curves are possibilities; that's why they are > there :-). > > I discarded the linear option because of the lack of tail-off, and the > other > polynomial as a poor fit in the operating region. On further > consideration, > perhaps the 'ln' solution doesn't tail off quickly enough, although it's a > very good fit indeed up to ~1.1. > > So far as I can see supercharger design and matching it to an engine is as > much art as science, and there are many different options. I'm reasonably > convinced that the supercharger output should tail off quite sharply after > max power, otherwise an engine would just go on developing more and more > power at higher and higher rpm until it broke or the supercharger did!. In > practice this doesn't happen because the cross section of the inlet is > carefully chosen. > > I'm sure that you can come up with some more alternatives. Let's try them > and see if we like them. > We seem to have got stuck on this one. I haven't pursued it because the Hurricane model wasn't ready. A beta version is now ready. It, along with the Spitfire and P51D need the attached modification to YASim. The diff provides a supercharger output which varies with engine rpm. It assumes that the normalized supercharger output is ~ 1 when the engine is at the nominated peak-power rpm (normalised). A 'power' equation of the form ((A*(B^x))*(x^C) has been derived empirically from some representative supercharger data. This provides near-linear output over the normal operating range, with fall-off in the over-speed situation. It proves an excellent match to published contemporary figures for the Merlin XX in the Hurricane II, and should also do so for other Merlin variants. It allows the engine to over-speed to 2.5 times the nominated peak-power rpm, and will not break beyond this (although the engine/supercharger probably would in real life!). Unlikely, but allows an unexpected YASim configuration. It also provides an additional control - Boost Control Cutout - which overrides the Boost Control (or wastgate in Yasim). The Spitfire, Hurricane and P51D all had this for use in combat. Finally, the diff corrects a minor bug in the output to the property tree and provides a Boost Gauge input. The beta version of the Hurricane IIB is available here: ftp://abbeytheatre.dyndns.org/fgfs/Hurricane/ There is a tarball (hurricane.tgz) or you can grab all the files individually. The diff is also available there. You WILL need to apply this to run the Hurricane, but so far as I can tell, no other YASim model is adversely affected. Some pictures are here: http://myweb.tiscali.co.uk/vmeazza/FlightGear/HurricaneIIb-3.jpg http://myweb.tiscali.co.uk/vmeazza/FlightGear/HurricaneIIb-4.jpg http://myweb.tiscali.co.uk/vmeazza/FlightGear/HurricaneIIb-5.jpg http://myweb.tiscali.co.uk/vmeazza/FlightGear/HurricaneIIb-6.jpg There remains some more eye-candy to do: nav lights, beam approach marker lamps, realistic rad and oil temperature readings etc. In the meantime I would be grateful for any comments, not least that it all downloads and installs correctly! If you do decide to give it a go you'll probably need this: http://home.clara.net/wolverine/BOB/misc/Spit_Hurri_Manuals.zip Regards Vivian yasim.diff Description: Binary data ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Gerard Robin wrote: > Something wrong ? > > --prop:/nasal/local/script= > > nasal does give error message: Nasal parse error: parse error in /nasal > [0]/local[0], line 1 The --prop argument is not an XML parser. Just pass the literal script text as the value, no CDATA munging is needed or legal. Note also that the script you list above is a noop. It assigns a INIT function as a local variable but never calls it. If you want to set the /sim/rendering/clouds3d-cache-size to 4096, what is wrong with: --prop:/sim/rendering/clouds3d-cache-size=4096 Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
> In the developers' list archives is the best we have. Cygwin wouldn't work > at all if it were not for the excellent work by Norman Vine. There's no sign > of OpenAL being ported to Cygwin at the moment, so this is the best we have. > We are in constant danger of being left behind. > > Have you got it to work yet??? I guess I could tarball up my version here > for you, when I have a bit more time. Yes. I now have a FlightGear executable - though I won't have time to try it until this evening at the earliest. I'd like to submit the text below to a FAQ or wherever it should be on the FlightGear/SimGear site: --- start --- For Cygwin users, OpenAL needs to be retrieved from this site: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/openal_cyg.tgz I placed this file in the /usr directory and untar'ed it, though some place it in the /usr/local/ directory tree - which might be more appropriate. Some library and dll files are untar'ed into your bin/ and lib/ subdirectories. Once the files are untar'ed, you must cd to the include/AL/ subdirectory and modify all the files where "_WIN32" is present (use grep) and change it to simply "WIN32" (that is, remove the underscore). Also, in alc.h you must change the code at top to look like this: #ifdef WIN32 --- CHANGE TO THIS #ifdef _OPENAL32LIB #define ALCAPI __declspec(dllexport) #else #define ALCAPI __declspec(dllimport) #endif #ifdef WIN32 --- CHANGE TO THIS typedef struct ALCdevice_struct ALCdevice; typedef struct ALCcontext_struct ALCcontext; #endif Once these changes are made, you should be able to compile simgear. --- end --- Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] writing rules with --prop for nasal in fgfsrc
Something wrong ? in fgfsrc in have: --geometry=1280x896 --enable-real-weather-fetch --timeofday=afternoon --prop:/nasal/local/script= nasal does give error message: Nasal parse error: parse error in /nasal [0]/local[0], line 1 does writing --prop:/nasal. good -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
Jon Berndt > > > Hmmm ... we had to fiddle with it to make it work some months ago ... I > > forget exactly what we did > > This seems really unfortunate for FlightGear - that we have to rely on > another package > where some of us have to "fix" the code to work for CygWin users. Is this > even documented > anywhere? > In the developers' list archives is the best we have. Cygwin wouldn't work at all if it were not for the excellent work by Norman Vine. There's no sign of OpenAL being ported to Cygwin at the moment, so this is the best we have. We are in constant danger of being left behind. Have you got it to work yet??? I guess I could tarball up my version here for you, when I have a bit more time. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] OpenAL for CygWin
> Hmmm ... we had to fiddle with it to make it work some months ago ... I > forget exactly what we did This seems really unfortunate for FlightGear - that we have to rely on another package where some of us have to "fix" the code to work for CygWin users. Is this even documented anywhere? jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] xml formatting
Erik Hofman wrote: eagle monart wrote: i am trying to output a airspeed and gmt with generic protocol. i am writing it to a txt file however the file is growing. i wanted xml form to rewrite on to same line as an example line1 is gmt and line two is airspeed ..format is like that. i subtracted line seperators in xml form but still continues to write new datas. how can i set this? This is how it was designed since it's main purpose was sending data to the serial port or over the network. The file option (as it is now) is very useful for generating log files, so it is not possible to do it like that at this time. However, you might want to add carriagereturn to see if that helps. If it doesn't work either it would be possible to add a specialized line-separator that performs a fseek(0) just prior to writing the line. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Call to French community about Airport LFPO
Airport LFPO -Paris Orly gives a bad runway position. The defined take-off point is outside of the visual runway position. I dont know if the error is in the Airport data. Does anybody has tried to modify it ? Thanks > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: [PATCH] Re: animation bug
> From: Jim Wilson > > Hi Melchior, > > There was one thing I forgot to mention. In that animation.diff patch file > you also have an unrelated change that does some > clamping in the material animation. I understand the logic behind this, > but the typical behavior (the way the translationn > values are handled further down the line) is the texture wraps at > 1.0 and < > 0.0. IIRC, this behavior is essential in some > of the 747 panel stuff. > > I haven't tested this myself, but thought I'd give you a heads up in case > there's a problem lurking in that particular change. > Err umm...looks like I got the wrong idea with "trans.min"/"trans.max"...mixed up "transparency" and "translation". Throw in "transformations" and I'm really confused! Sorry about that. :-) Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: "old" 3d clouds code
Gerard Robin wrote: Oh sorry if you mean _bumped_ clouds it can be removed. Eh, no. It's yet another one... Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: "old" 3d clouds code
Le lundi 13 juin 2005 à 13:05 +0200, Erik Hofman a écrit : > Melchior FRANZ wrote: > > > Both the "old" 2D clouds (note the "TWO") and the new 3D clouds consider > > METAR. > > The old 3D clouds that Erik is talking about do AFAIK not. They are ugly and > > broken, and aren't representative for anything. It sounds as if you are > > mixing > > up 2D and 3D. > > As far as I know the "old" 3d clouds do not use metar for anything. In > fact it just shows the same cloudfield over and over again. > > Erik > OK i understand what you mean, i haver used it. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: "old" 3d clouds code
Le lundi 13 juin 2005 à 12:58 +0200, Melchior FRANZ a écrit : > * Gerard Robin -- Monday 13 June 2005 12:21: > > Le lundi 13 juin 2005 à 10:29 +0200, Erik Hofman a écrit : > > > How would you all feel about making the "old" Haris' 3d clouds code > > > obsolete by now? > > > We must keep it, with Metar it is the most Representative of the real > > weather the new 3D clouds is beautiful only. > > Both the "old" 2D clouds (note the "TWO") and the new 3D clouds consider > METAR. > The old 3D clouds that Erik is talking about do AFAIK not. They are ugly and > broken, and aren't representative for anything. It sounds as if you are mixing > up 2D and 3D. > > m. > Oh sorry if you mean _bumped_ clouds it can be removed. We must be able to choose between normal clouds and new 3D clouds, because, with Metar, when i look at the windows (you probably can do it :-) ), i worry, i see a sky which is nearly the same than that i have on my screen, and an other sky with new 3D clouds. I do not contest that new 3D Clouds takes in account Metar, up to now, it is not able to give the real picture. (that could be probably improved). You could understand that i must, now, be careful when i give my opinion, since the _JSB_crash_handling_affair_ which makes for me crash down many hours of work.( to keep it i must run with a permanent patched fg). But i get off the main subject... OK!! > -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: "old" 3d clouds code
Melchior FRANZ wrote: Both the "old" 2D clouds (note the "TWO") and the new 3D clouds consider METAR. The old 3D clouds that Erik is talking about do AFAIK not. They are ugly and broken, and aren't representative for anything. It sounds as if you are mixing up 2D and 3D. As far as I know the "old" 3d clouds do not use metar for anything. In fact it just shows the same cloudfield over and over again. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: "old" 3d clouds code
* Gerard Robin -- Monday 13 June 2005 12:21: > Le lundi 13 juin 2005 à 10:29 +0200, Erik Hofman a écrit : > > How would you all feel about making the "old" Haris' 3d clouds code > > obsolete by now? > We must keep it, with Metar it is the most Representative of the real > weather the new 3D clouds is beautiful only. Both the "old" 2D clouds (note the "TWO") and the new 3D clouds consider METAR. The old 3D clouds that Erik is talking about do AFAIK not. They are ugly and broken, and aren't representative for anything. It sounds as if you are mixing up 2D and 3D. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] "old" 3d clouds code
Le lundi 13 juin 2005 à 10:29 +0200, Erik Hofman a écrit : > > Hi, > > How would you all feel about making the "old" Haris' 3d clouds code > obsolete by now? > > Erik > We must keep it, with Metar it is the most Representative of the real weather the new 3D clouds is beautiful only. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] New JSBSim Branch
It appears as though JSBSim CVS is in a good state, with the new code, and new directory structure. Notes: 1) No attempt has yet been made to test this with FlightGear - that will take a little bit of work. Things are different: the directory structure, the code, the aircraft config files, etc. 2) I have only attempted to build this under Cygwin and Borland C++BuilderX. 3) Some aircraft, engine, script, etc. files have not been validated against the new config spec. 4) Documentation for the new spec is forthcoming. 5) More information on the converter is pending. Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] xml formatting
eagle monart wrote: i am trying to output a airspeed and gmt with generic protocol. i am writing it to a txt file however the file is growing. i wanted xml form to rewrite on to same line as an example line1 is gmt and line two is airspeed ..format is like that. i subtracted line seperators in xml form but still continues to write new datas. how can i set this? This is how it was designed since it's main purpose was sending data to the serial port or over the network. The file option (as it is now) is very useful for generating log files, so it is not possible to do it like that at this time. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] New developer
On Mon, Jun 13, 2005 at 02:11:55AM +, Ampere K. Hardraade wrote: > On June 13, 2005 12:42 am, Manuel Bessler wrote: > > The stuff is still here: > > 1. http://cockpit.varxec.de/fgfs/fgfs_717-200.tar.bz2 > > 2. http://cockpit.varxec.de/fgfs/fgfs_717-200_71.blend.gz > > They are not there. Ooops, my bad. (My old server redirects to my new server, but the files are only on the old one...) I've put them on my new server: http://cockpit.varxec.net/fgfs/fgfs_717-200.tar.bz2 http://cockpit.varxec.net/fgfs/fgfs_717-200_71.blend.gz http://cockpit.varxec.net/fgfs/fgfs-screen-001.jpg ... http://cockpit.varxec.net/fgfs/fgfs-screen-005.jpg The screens show the state of the 3d model. Regards, Manuel ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] xml formatting
i am trying to output a airspeed and gmt with generic protocol. i am writing it to a txt file however the file is growing. i wanted xml form to rewrite on to same line as an example line1 is gmt and line two is airspeed ..format is like that. i subtracted line seperators in xml form but still continues to write new datas. how can i set this? time GMT (hhmmss) string /fdm/acms/sim/time indicated speed (kt) int /fdm/acms/velocities/airspeed-kt _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: "old" 3d clouds code
* Erik Hofman -- Monday 13 June 2005 10:29: > How would you all feel about making the "old" Haris' 3d clouds code > obsolete by now? Probably a good idea. The old code is broken, unmaintained, and uses nasty binary cloud definition files, while the new code yields much better results (except when flying through clouds). The old code may be more advanced in some respect (and slower :-), but it'll remain in the Attic/ anyway, so if someone wants to pick it up again, fix it, and make it better than the new clouds, go ahead ... m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] "old" 3d clouds code
Erik Hofman wrote > Hi, > > How would you all feel about making the "old" Haris' 3d clouds code > obsolete by now? > > Erik > Supported Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] "old" 3d clouds code
Hi, How would you all feel about making the "old" Haris' 3d clouds code obsolete by now? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
