HI,i am intersted in knowing how we can read the data from the flight gear simulation like we do from microsoft flight simulator using FSUIPC,i was also intersted in knowing giving inputs to the flight gear simulation through some interface like FSUIPC.Thx & regards,SHIV K.

>HI,>i am intersted in knowing how we can read the data from the>flight gear simulation like we do from microsoft flight>simulator using FSUIPC,i was also intersted in knowing giving>inputs to the flight gear simulation through some interface>like FSUIPC.>>Thx & regards,>SHIV K.Basically, FlightGear doesn't require anything like FSUIPC in order to achieve what you require, since it exports most of its internal data by default to something that's commonly referred to as the "Property Tree", if you are familiar with the Win32 "registry" then you'll find it easy to deal with the "Property Tree", essentially it's a file-system like representation of internal FlightGear variables, these variables can be put into groups ("folders") and be referred to by their paths.This representation of internal state variables can be accessed by various means, in order to give it a quick try you'll simply want to run:./fgfs --telnet=5500(while 5500 is the desired port number)or alternatively/also:./fgfs --httpd=5501which would start an integrated http daemon (server) that exports all properties via a simple sort of web interface.you can then access Flightgear by either running:telnet i.e.:telnet localhost 5500or by pointing your browser to the correct address, i.e.:http://127.0.0.1:5501Make sure to:a) Download FlightGear (incl. Base Package):( Download FlightGear Source Codethen1) read the documentation under $FG_ROOT/docs2) read the documentation under $FG_SRC/minidocsAfterwards search the (devel) mailing list archives at baron.flightgear.org for potentially interesting topics.Also, you may find it helpful to sign up with the FlightGear Developer's mailing list (check FlightGear.org)Please note however, that depending on what exactly you want to implement, it MAY become necessary to modify (recompile !) FlightGear slightly to make it export certain variables that aren't yet exported, this is actually a rather trivial thing to do, though.PS: All the aforementioned documents are also easily obtainable checking them out from FlightGear's CVS, either by using a cvs client directly or by using the viewcvs web frontend that's located at FlightGear.org

Make sure to have at least read the following files before digging further:http://cvs.flightgear.org/cgi-bin/viewcvs/....viewcvs-markuphttp://cvs.flightgear.org/cgi-bin/viewcvs/....viewcvs-markuphttp://cvs.flightgear.org/cgi-bin/viewcvs/....viewcvs-markuphttp://cvs.flightgear.org/cgi-bin/viewcvs/....viewcvs-markup(Note that all of these files should be also present in your local installation)