Andy Ross wrote:
Yes, it seemed to me that opengl wasn't getting linked, so I was moving the link order around in experimentation. The stock configuration has the libraries in the correct order. I apologize for the confustion on this aspect. BTW, the stock configuration provided the same message.> *but* it is in the wrong place> i.e Win32 linkage is quite different then Unix linkage and the order > of the libraries *is* important ie sybols must be resolved *after* they > are used.
I'm involved with the autopilot.sf.net project and we are exploring flightgear integration with our simulator. The helicopter flight model was written by Aaron Kahn and has a VERY realistic hover simulation. Optionally, a flybar component can be introduced into the model for further simulating R/C class helicopters.
flight model is at:
http://cvs.sf.net/cgi-bin/viewcvs.cgi/autopilot/sim/src/heli-sim/
This is our focus as we are working on a GPS aided INS system for R/C helicopters and airplanes. The simulator allows us to work on the groundstation, kalman filter and other vehicle systems in virtual reality.
The Kalman filter is at:
http://cvs.sf.net/cgi-bin/viewcvs.cgi/autopilot/sim/src/imu-filter/
Navigation prototype is at:
http://cvs.sf.net/cgi-bin/viewcvs.cgi/autopilot/sim/src/controller/
Trammell from the autopilot.sf.net project found an old flightgear-users message that detailed the cygwin build procedure. This email was enough to get flightgear compiling on my system. It seems cygwin is pretty messy with regards to OpenGL and X11 (three sets & variations of GL headers!!).....
I don't know enough about flightgear yet to know how to integrate the flight model... Either internally or as an external driver? Although, I must admit that I have been having too much fun flying and using flightgear and not enough time looking at the code :-)
Plib networking also looks attractive. We have a TCP/IP based state server on the sim and a UDP based state server onboard the vehicle. We are working to reconcile them (into UDP due to the nature of our wireless telemetry system) and someone mentioned Plib. Between flightgear and opengc, it would be great to adhere to some sort of open source simulation network standard.
our TCP/IP networking is at:
http://cvs.sf.net/cgi-bin/viewcvs.cgi/autopilot/sim/src/state/
Our UDP network is embedded in the onboard filter and ground station at the moment and isn't very modular (... hack ...)
I have done mostly Java work for the past 3 years. This has spoiled me in regards to build systems. Switching back to C/C++ multi-platform systems has been a rude awakening...I got a little spoiled these past four years doing Java stuff at NextBus.</plug>
Thanks for the responses on this cygwin issue.
Dennis
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
