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 13:27
Aan: [EMAIL PROTECTED]
Onderwerp: Flightgear-devel digest, Vol 1 #585 - 8 msgs


Send Flightgear-devel mailing list submissions to
        [EMAIL PROTECTED]

To subscribe or unsubscribe via the World Wide Web, visit
        http://mail.flightgear.org/mailman/listinfo/flightgear-devel
or, via email, send a message with subject or body 'help' to
        [EMAIL PROTECTED]

You can reach the person managing the list at
        [EMAIL PROTECTED]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Flightgear-devel digest..."


Today's Topics:

   1. Version 0.7.10 (Erik Hofman)
   2. Re: A little help with sockets. (Erik Hofman)
   3. 0.7.10 (Alex Perry)
   4. Re: perplexing make error (Alex Perry)
   5. JSBSim and FlightGear 0.7.10 (Jonathan Polley)
   6. Model lighting (Jim Wilson)
   7. Strange opengl compiler error ? (Marcel Wittebrood)
   8. Problem with final linking (Michael Basler)

--__--__--

Message: 1
Date: Sun, 21 Apr 2002 14:26:20 +0200
From: Erik Hofman <[EMAIL PROTECTED]>
Organization: Eric's Conspiracy Secret Service
To: [EMAIL PROTECTED]
Subject: [Flightgear-devel] Version 0.7.10
Reply-To: [EMAIL PROTECTED]


Hi,

I think 0.7.10 is not yet ready for relase:

$ /opt/bin/fgfs --aircraft=harrier-yasim
NewAirportInit KSFO
idx = 11133
Current greenwich mean time = Sun Apr 21 12:21:22 2002

Current local time          = Sun Apr 21 14:21:22 2002

Fatal error: Failed to load 3D model
  (received from )


Same for a4-yasim.


And it seems like the default airport is shifted about 10 meters to the 
north in the scenery. There are white areas around it ??!?

Erik



--__--__--

Message: 2
Date: Sun, 21 Apr 2002 19:12:24 +0200
From: Erik Hofman <[EMAIL PROTECTED]>
Organization: Eric's Conspiracy Secret Service
To: [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] A little help with sockets.
Reply-To: [EMAIL PROTECTED]

Sergio Roth wrote:
> I'm testing a code to work as server for FGFS.  When I run FGFS  with 
> --native=socket,out,30,linux,ftp  without starting server I get the
expected 
> message of no possible conection but when I start server before FGFS
it runs 
> ok. Thus I wonder server is connecting fine but  I don't get anything
shown 
> on screen. Would someone help me on that?
> 
> Thanks.
> 
> Sergio Roth 
> 
> 
>
------------------------------------------------------------------------
> 
> /* Program: Comunication test using socket
>  (Adapted from GNU C Library Reference manual)
> */
> 
> #include <stdio.h>
> #include <errno.h>
> #include <stdlib.h>
> #include <unistd.h>
> #include <sys/types.h>
> #include <sys/socket.h>
> #include <netdb.h>
> #include <netinet/in.h>
> 
> 
> #define PORT 5500
> #define MAXMSG 5092


Since you are using ftp as a last option for --native I guess you would 
have to use #define PORT 21 here.

You would better try using:

--native=socket,out,30,linux,5500,tcp






--__--__--

Message: 3
To: [EMAIL PROTECTED]
Date: Sun, 21 Apr 2002 17:54:13 -0700 (PDT)
From: Alex Perry <[EMAIL PROTECTED]>
Subject: [Flightgear-devel] 0.7.10
Reply-To: [EMAIL PROTECTED]

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

It occurs to me that we could have easily have an automatic thing that
accepts small anonymous FTP uploads with a filename of the email address
and the content being the output of "cvs status" or the equivalent.
Curt could trivially parse the directory of files to see how many people
are successfully using a given CVS snapshot at any given time and use
this to determine when a minor release should be tarballed and uploaded.


--__--__--

Message: 4
Subject: Re: [Flightgear-devel] perplexing make error
To: [EMAIL PROTECTED]
Date: Sun, 21 Apr 2002 17:58:52 -0700 (PDT)
From: Alex Perry <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]

> I managed to sort out the problems and get things to compile.  I was
> forced to remove my altered versions of fg_init.cxx and options.cxx.
It
> refused to merge them, or replace them, or compile them, or whatever.
But
> by removing my files, it recvsed the cvs versions and it compiled.
> 
> I am still dreadfully disappointed in the framerate.  It runs about 1
or 2
> fps, whereas if I run the latest binary download I get 7 or 8 fps.

If you're running a Matrox video card, or any other brand that has
distinct 2D and 3D modes, allowing the streaming log messages to be
visible in another window forces the video card to spend most of its
time changing mode instead of drawing on the screen.



--__--__--

Message: 5
Date: Sun, 21 Apr 2002 20:24:35 -0500
From: Jonathan Polley <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Flightgear-devel] JSBSim and FlightGear 0.7.10
Reply-To: [EMAIL PROTECTED]

Due to some problems that MSVC has with how FlightGear uses overloading,
I 
still have private copies of a hand full of JSBSim files.  Will that be 
fixed in 0.7.10?

As a refresher, MSVC has a problem with functions like the following, 
overloaded,  definitions when they are used in a call to, the
overloaded, 
Tie() function.


   FGColumnVector3& GetMoments(void) { return vMoments; }
   double GetMoments(int idx) const { return vMoments(idx); }

I have added a _V to the end of the vector versions to make MSVC happy, 
but that was not the consensus when the problem appeared.

Thanks,

Jonathan Polley



--__--__--

Message: 6
Date: Mon, 22 Apr 2002 02:32:26 -0000
To: <[EMAIL PROTECTED]>
From: "Jim Wilson" <[EMAIL PROTECTED]>
Subject: [Flightgear-devel] Model lighting
Reply-To: [EMAIL PROTECTED]

One idea I had to model a blinking light on an aircraft is to use spin
animation 
on a poly that has emmisive properties.  I'm thinking that this could be
tied
somehow to the be tied to /sim/time/elapsed-time, but I'm not sure how. 
David, can this be done with the current code?

Also, I noticed that in ac3d you can define a point of light
(omnidirectional
source) which could be somewhat useful in providing light emiting from
the
aircraft onto the runway (not extremely realistic, but better than
nothing). 
When trying this however, it appears that plib doesn't do anything with
the
ac3d    light objects.  Is this a plib problem and/or should we be doing
this
some other way anyway?

Best,

Jim


--__--__--

Message: 7
Date: Mon, 22 Apr 2002 09:07:18 +0200
From: "Marcel Wittebrood" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [Flightgear-devel] Strange opengl compiler error ?
Reply-To: [EMAIL PROTECTED]

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 behaviour on our systems.

kind regards


--__--__--

Message: 8
From: "Michael Basler" <[EMAIL PROTECTED]>
To: "Flightgear-Devel" <[EMAIL PROTECTED]>
Date: Mon, 22 Apr 2002 12:20:18 +0200
Subject: [Flightgear-devel] Problem with final linking
Reply-To: [EMAIL PROTECTED]

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

------------------------------------------
make[2]: Entering directory `/usr/local/source/flightgear/src/Main'
c++ -DPKGLIBDIR=\"/usr/local/FlightGear/lib/FlightGear\" -g -O2
-L/usr/local
/lib
 -o fgfs  main.o fg_commands.o fg_init.o fg_io.o fg_props.o fgfs.o
globals.o
log
ger.o options.o splash.o viewer.o viewmgr.o location.o
../../src/Aircraft/libAir
craft.a         ../../src/ATC/libATC.a
../../src/Autopilot/libAutopilot.a
../..
/src/Cockpit/libCockpit.a       ../../src/Cockpit/built_in/libBuilt_in.a
../../s
rc/Controls/libControls.a       ../../src/FDM/libFlight.a
../../src/FDM/Ba
lloon/libBalloon.a      ../../src/FDM/JSBSim/libJSBSim.a
../../src/FDM/YA
Sim/libYASim.a  ../../src/FDM/JSBSim/filtersjb/libfiltersjb.a
../../src/FDM/La
RCsim/libLaRCsim.a      ../../src/FDM/UIUCModel/libUIUCModel.a
../../src/GUI/li
bGUI.a  ../../src/Model/libModel.a      ../../src/Navaids/libNavaids.a
../../sr
c/Scenery/libScenery.a  ../../src/Sound/libSound.a
../../src/Airports/libAi
rports.a         ../../src/Network/libNetwork.a
../../src/NetworkOLK/lib
NetworkOLK.a    ../../src/Objects/libObjects.a  ../../src/Time/libTime.a
../../s
rc/WeatherCM/libWeatherCM.a
    ../../src/Input/libInput.a      -lsgroute -lsgsk
y -lsgephem -lsgtiming -lsgio -lsgscreen        -lsgmath -lsgbucket
-lsgdebu
g -l
sgmagvar -lsgmisc -lsgxml       -lsgserial              -lplibpu
-lplibfnt -
lpli
bnet -lplibssg -lplibsg         -lmk4 -lz       -lpthread -lm  -lglut32
-lgl
u32
-lopengl32 -luser32 -lgdi32     -lplibsl -lplibsm -lwinmm -lplibul -lm
Warning: resolving _glBlendFunc by linking to _glBlendFunc@8
Use --enable-stdcall-fixup to disable these warnings
Use --disable-stdcall-fixup to disable these fixups
Warning: resolving _glPopAttrib by linking to _glPopAttrib@0
Warning: resolving _glPushAttrib by linking to _glPushAttrib@4
Warning: resolving _glDisable by linking to _glDisable@4
Warning: resolving _glPopMatrix by linking to _glPopMatrix@0
Warning: resolving _glOrtho by linking to _glOrtho@48
Warning: resolving _glPushMatrix by linking to _glPushMatrix@0
Warning: resolving _glPixelStorei by linking to _glPixelStorei@8
Warning: resolving _glMatrixMode by linking to _glMatrixMode@4
Warning: resolving _glViewport by linking to _glViewport@16
Warning: resolving _glGetIntegerv by linking to _glGetIntegerv@8
Warning: resolving _glLoadIdentity by linking to _glLoadIdentity@0
/usr/local/lib/libsgscreen.a(screen-dump.o): In function
`sg_glDumpWindow(char c
onst *, int, int)':
/usr/local/source/simgear/simgear/screen/screen-dump.cxx:84: undefined
reference
 to `glFinish'
/usr/local/source/simgear/simgear/screen/screen-dump.cxx:86: undefined
reference
 to `glReadPixels'
/usr/local/lib/libsgscreen.a(tr.o): In function `trEndTile(_TRctx *)':
/usr/local/source/simgear/simgear/screen/tr.cxx:404: undefined reference
to
`glF
lush'
/usr/local/source/simgear/simgear/screen/tr.cxx:418: undefined reference
to
`glR
eadPixels'
/usr/local/source/simgear/simgear/screen/tr.cxx:437: undefined reference
to
`glR
eadPixels'
/usr/local/lib/libsgscreen.a(tr.o): In function `trRasterPos3f(_TRctx *,
float,

--
        Michael Basler, Jena, Germany
                [EMAIL PROTECTED]
      http://www.geocities.com/pmb.geo/




--__--__--

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel


End of Flightgear-devel Digest

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to