Re: [Flightgear-devel] PLIB version for building from CVS
--- Buchanan, Stuart [EMAIL PROTECTED] wrote: Hi All, Which version of PLib is required to build the current FG CVS? v1.8.4 is the latest stable release. Unfortunately, I can't add any other useful info regarding the compile error. Mike I'm getting a build error (output below), which I assume is due to an incorrect PLIB version. I'm using v1.8.4 Thanks -Stuart g++ -g -O2 -D_REENTRANT -L/usr/local/lib -o js_demo.exe js_demo.o -lplibjs - lwinmm -lplibul /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../libplibjs.a(jsWindows.o): In func tion `_ZN10jsJoystick4openEv': /home/Stuart/plib-1.8.4/src/js/jsWindows.cxx:107: undefined reference to `_joyGe [EMAIL PROTECTED]' /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../libplibjs.a(jsWindows.o): In func tion `_ZN10jsJoystick7rawReadEPiPf': /home/Stuart/plib-1.8.4/src/js/jsWindows.cxx:191: undefined reference to `_joyGe [EMAIL PROTECTED]' collect2: ld returned 1 exit status make[2]: *** [js_demo.exe] Error 1 make[2]: Leaving directory `/home/Stuart/FlightGear-0.9/source/src/Input' ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] How does the weather work in FlightGear?
--- Adam Dershowitz [EMAIL PROTECTED] wrote: On Oct 10, 2005, at 10:26 AM, Ampere K. Hardraade wrote: On October 10, 2005 03:37 am, Erik Hofman wrote: Buchanan, Stuart wrote: In my opinion, it would be better if data from multiple nearby METAR stations is used instead of fetching data from only one station. I often fly with real-weather-fetch enabled, and the plane gets a huge jolt whenever the weather is updated. The change in the visual aspects is also too sudden. Using data from multiple METAR stations could avoid the above problems and allow us to have a smooth transistion in weather. Ampere This is not as obvious as it would first seem. Some weather phenomena have very sharp transitions and some are gradual. So I don't think that interpolating weather is a trivial thing to do. For example a cold front is often a very well defined line with rain right along the front. In that case the weather right nearby is the best indicator and a METAR from 5 miles away could give a completely different story. Airmass thunderstorms are another example where very local weather is what matters. To make maters worse the METAR will just have temperature and wind, so you would have to look at a few different locations and times to figure out that a front has passed. And the local geography (mountains, lake effects, shore lines) can also be a significant issue. I am not saying that it could not be done, just that it would take some real thought and real understanding of weather phenomena for it to apply in the general case rather than just in a few specific case and make things worse other times. --Adam Maybe the best solution would be to make the transition of cloud height, air temperature, and wind from one METAR to the next occur over some length of time (minute or so), rather than abruptly. If this is possible. Mike __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] MSVC problems with 0.9.8 tarball
--- PJ Quirk [EMAIL PROTECTED] wrote: snip you can see from the screenshot: http://www.cs.unc.edu/~quirk/blankscreen.bmp Though the hud/panel can be displayed, and any airplane flies fine according to the instruments, there's just no scenery. snip Patrick, v0.9.8 comes with scenery for the 10x10 degree block with corner 130W, 30N. Did you start the sim at KSFO? If you started it in a region outside of central California no scenery will show. Mike __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear startup time
40 seconds for CVS vesion on Dell (laptop) running Linux Fedora Core 2, 1.6 GHz processor, 2 GB RAM. I can live with that. Mike --- Frederic Bouvier [EMAIL PROTECTED] wrote: It takes 23 seconds to start my build on an amd64 3400, 1Gb ram. -Fred Drew a écrit : I'm compiling a Release build. It takes me a bit under a minute to bring it up, which isn't as bad as the 5 minutes Vivian reported, but it's still longer than I'd like (and longer than I believe is necessary). I'll see what I can do about disabling navaids...that seems like it be a lot of help. I haven't found a property in preferences.xml or a command-line option for this, yet. Drew On 5/24/05, Frederic Bouvier [EMAIL PROTECTED] wrote: Drew a écrit : FlightGear takes nearly a minute to start up from my Windows build, and I'm just wondering if there's an easy way to shorten this if I'm not using all of flightgear's features. Is there one particular task that takes particularly long? Do you use the Debug or the Release build ? MSVC 7.x adds a lot of debug code in memory management (assertion check, corrupted heap) that makes the Debug build **very** slow. The Release build, as in the official win32 releases, is way faster. Maybe 5x to 10x. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d __ Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
