Re: [Flightgear-devel] Bug-Report for FGFS v0.8.0
Hello, I got this from ldd command: libmk4.so.0 = /usr/lib/libmk4.so.0 (0x4003c000) libz.so.1 = /lib/libz.so.1 (0x40081000) libglut.so.3 = /usr/lib/libglut.so.3 (0x4009) libGL.so.1 = /usr/lib/libGL.so.1 (0x400c8000) libXmu.so.6 = /usr/X11R6/lib/libXmu.so.6 (0x4010f000) libXt.so.6 = /usr/X11R6/lib/libXt.so.6 (0x40125000) libSM.so.6 = /usr/X11R6/lib/libSM.so.6 (0x40172000) libICE.so.6 = /usr/X11R6/lib/libICE.so.6 (0x4017c000) libXi.so.6 = /usr/X11R6/lib/libXi.so.6 (0x40194000) libXext.so.6 = /usr/X11R6/lib/libXext.so.6 (0x4019c000) libX11.so.6 = /usr/X11R6/lib/libX11.so.6 (0x401ab000) libpthread.so.0 = /lib/libpthread.so.0 (0x4026b000) libm.so.6 = /lib/libm.so.6 (0x40281000) libstdc++-libc6.2-2.so.3 = /usr/lib/libstdc++-libc6.2-2.so.3 (0x402a4000) libc.so.6 = /lib/libc.so.6 (0x402f1000) libGLcore.so.1 = /usr/lib/libGLcore.so.1 (0x40419000) libdl.so.2 = /lib/libdl.so.2 (0x40737000) /lib/ld-linux.so.2 = /lib/ld-linux.so.2 (0x4000) Hmmm, for it seems he hasn't linked any metakit library? Ok, I'm going to check it with statically linked metakit Regards, Roland Haeder ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Bug-Report for v0.8.0 - self-fixed ;)
Hello again! Well, I fix it up with help from Andy Ross: The new metakit lib is installed to /usr/local/lib/ but there's also a metakit lib at /usr/lib/. So I simply removed the old /usr/lib/libmk4.so* and it's working now. Thanks. But what about fixing-out some compiler warnings? Roland :-) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug-Report for FGFS v0.8.0
Hmmm, for it seems he hasn't linked any metakit library? He did: libmk4.so.0 = /usr/lib/libmk4.so.0 (0x4003c000) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear compression
Jim Wilson wrote: What do the gear/compression-norm values in YASim represent? Is it a distance or travel range fraction or something else? It's a normalized value -- a fraction. A value of 0 represents full extension, 1 is full compression. The actual length numbers can be gotten from the aircraft configuration. If you like, exporting a compression-m wouldn't be hard at all. The problem is that not all gear compress linearly; think of the spring steel gear on light planes, or the weird bending gear on the Hornet. The advantage of a normalized value is that you can interpolate any bizzare animations you want and know that it won't break when someone changes the gear compression in the YASim configuration (this just happened for the 747, for example). Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug-Report for FGFS v0.8.0
Roland Häder wrote: But what about fixing-out some compiler warnings? Most of those appeared with gcc 3.2, I believe. They don't look too scary to me -- mostly C++ standardization stuff. I'm sure they'll be fixed soon. Scanning through it quickly, it looks like mostly David's code. Sloppy bum; we oughta fire that guy. :) Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] gear compression
Andy Ross [EMAIL PROTECTED] said: Jim Wilson wrote: What do the gear/compression-norm values in YASim represent? Is it a distance or travel range fraction or something else? It's a normalized value -- a fraction. A value of 0 represents full extension, 1 is full compression. The actual length numbers can be gotten from the aircraft configuration. If you like, exporting a compression-m wouldn't be hard at all. The problem is that not all gear compress linearly; think of the spring steel gear on light planes, or the weird bending gear on the Hornet. The advantage of a normalized value is that you can interpolate any bizzare animations you want and know that it won't break when someone changes the gear compression in the YASim configuration (this just happened for the 747, for example). Ah, very good. The way you have it is the way I'd prefer for animations. Like you said if I need to look at measurements the info is there. Thanks, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] 172P Progress
I've been doing a little more work on the 172p interior. When this plane gets well enough along, I'm going to suggest making it the default startup plane (in the 3D version): http://www.megginson.com/flightsim/c172p-int-01.png http://www.megginson.com/flightsim/c172p-int-02.png http://www.megginson.com/flightsim/c172p-int-03.png I know that it's too blue -- more like a 1970s Cardinal. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
