Thanks Julian,
I have a ATI M-4 graphix card that is indeed not the fastest available
but does have some 3D-acceleration (An Opengl TAB is available in the
screen properties (adapter, next advanced).
I think this means that a pre-compiled flight-gear (thus a binary) will
sometimes show strange
Hi,
could any one tell me why the most recent CVS of PLIB/Simgear/FlightGear
from today does not do the final linking? I don't recall having seen this on
the list before?
This is (a recently updated) Cygwin under Win XP.
Thanks and
Regards, Michael
--
Currently, the 2D panel displayed in the 3D model is a kludge. It
works enough of the time that you can fly, but some strange things
happen from time to time:
1. The 2D panel instruments show through any 3D objects that should
obstruct them, such as the yoke.
2. The 2D panel does not move
Dear Michael,
You have exactly the same errors on screen as I reported friday in my
openGL question :-) It seems to be a cygwin related problem.
kind regards,
marcel wittebrood
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Verzonden: maandag 22 april 2002
It would be nice to get a CVS version that all the developers agree
will compile and run on their systems, then (arbitrarily) label it 0.7.10
Maybe it would be useful to label this 0.7.10 release as feature rich but
unstable (considering several pieces are broken that have been working in
This sounds like a great plan. It makes sense I think to set these up
external to the model (as xml files).
As for using the 2D panel, maybe in the model scenegraph we could use a
callback from the leaf where the panel will go to solve #1.
Another technique that I was thinking about to solve
Marcel,
You have exactly the same errors on screen as I reported friday in my
openGL question :-) It seems to be a cygwin related problem.
Thank for keeping an eye on it.
I returend from opengl 1.1.06 to 1.1.05, but this did not yet help either.
Norman, I think you have close relations to
Alex Perry wrote:
I propose that the PLIB project takes a community booth at LinuxTag
http://www.linuxtag.org June 6-9 this summer in Karlsruhe Germany.
This PLIB USERS booth would be a place for the dozen-odd projects
that conspicuously incorporate plib (and any others that join in)
to
Alex Perry wrote:
I propose that the PLIB project takes a community booth at LinuxTag
http://www.linuxtag.org June 6-9 this summer in Karlsruhe Germany.
This PLIB USERS booth would be a place for the dozen-odd projects
that conspicuously incorporate plib (and any others that join in)
to
I'm just wondering if a windows developer would mind building a 0.7.10
windows version (--without-logging) and send it to me for the ftp site
... likewise for the other platforms (or let me know when you have it
built and available on your site so I can update the links on the
flightgear download
On Monday 22 April 2002 07:39, David Megginson wrote:
Currently, the 2D panel displayed in the 3D model is a kludge. It
works enough of the time that you can fly, but some strange things
happen from time to time:
1. The 2D panel instruments show through any 3D objects that should
I have a copy of built with MSVC, but it is still reporting itself as
version 0.7.9 when it starts.
On Monday, April 22, 2002, at 01:25 PM, Curtis L. Olson wrote:
I'm just wondering if a windows developer would mind building a 0.7.10
windows version (--without-logging) and send it to me for
How do I get sound for my FDM? I have an engine model and I can get the
rotational speed. How do I use this to get the pitch of the engine
sample?
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
The 0.7.10 version of config.h-msvc6 reports itself as
#define FLIGHTGEAR_VERSION "MSVC6-WIN32-0.7.9"
Which gets printed on startup. It also exports the following version constant.
#define VERSION "0.57"
Jonathan Polley
Ugh, that's ugly. The configure script takes care of this
automatically with unix/cygwin. Could something be done with the
am2dsp.pl script?
Curt.
Jonathan Polley writes:
The 0.7.10 version of config.h-msvc6 reports itself as
#define FLIGHTGEAR_VERSION MSVC6-WIN32-0.7.9
Which gets
Alex makes some good points. So I'm wondering, why can't we have things like
throttle/mixture, yoke, flaps, trim wheels, prop pitch, etc. not be part of
the instrument panel (except in 2D panel mode)? I mean they really aren't
instruments anyway. If we accepted that seperation, then what
Many multihead capable video cards will only do 3D acceleration on the
main
head. If the instrument panel is placed on the second head, it had
better
use 2D GL calls. Therefore, the panel has to intrinsically be a 2D
database.
I had heard this before, so I was expecting disaster
Michael Basler writes:
You have exactly the same errors on screen as I reported friday in my
openGL question :-) It seems to be a cygwin related problem.
Thank for keeping an eye on it.
I returend from opengl 1.1.06 to 1.1.05, but this did not yet
help either.
Norman, I think you have
Alex Perry writes:
Depends on the card, and on the driver support. Recent cards are ok.
However, it puts another hardware purchase requirement on new users.
True, but things change very quickly
why just the other day some were saying that treating OpenGL
under unix as a non-windowing system
http://www.vso.cape.com/~files/fgfs/fgfs_0_7_10.tgz
I'm having problems to download this file:404 not found
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
20 matches
Mail list logo
