What is the difference if I implement a structure given in net_fdm_mini.cxx
source code and send this struct as a UDP packet for interfacing with
Flightgear?????or is it necessary to use complete structure given in
net_fdm.cxx????? I have taken a look at native_fdm.cxx file also and found
that we have to do htonl
or htonf before sending the packets......is it necessary????I am a newbie in
this area.......I also would
like to know about what are the padding differences and network byte order
mean?????
On 11/23/06, Jorge Van Hemelryck <[EMAIL PROTECTED]> wrote:
On Wed, 22 Nov 2006 15:20:08 +0530
umesh pandey wrote:
> I checked using Flightgear 0.9.8 but could not run it successfully.Thefew
> lines of log data are as follows:
<snip>
> > >I am also using correct command to start FGFS with external fdm:
> > >D:\FlightGear 0.9.3\bin\Win32\FGFS.EXE--native-fdm=socket
,in,30,,5500,udp
> > --fdm=external
Can you confirm that FLightGear is running, but waiting UDP packets,
probably in the middle of the ocean (lat=0, lon=0) ?
I can't remember if version 0.9.3 already had several log levels. Maybe
not. Anyway, it should reach a point where it announces that it is
opening a socket to listen on.
Then, it would be nice to check several things concerning the fdm_data.
First of all, your version of the protocol and of the struct definition
seems wrong. You should have FGNetVersion = 13, and some variables are
missing.
If you don't have the source code for FlightGear and are just
running a binary, get the source code for the exact version you use,
and look at src/Network/net_fdm.hxx. Note that it is C++ code, and it is
the only file to look at if you use 0.9.3. You will have a net_fdm.h,
in C, if you get a more recent version of FlightGear, and using this C
file should be even easier.
If it still doesn't work, check that your definition is correctly
adapted from the source code (net_fdm.h[xx]). Check the size of the
struct you send. I had that problem using UDP packets I sent from an
IRIX machine to 0.9.3 running on a Windows or Linux PC, the struct was
too big because of the enum I had left in the middle of the declaration.
Hope some of all this turns out to be helpful...
--
Jorge Van Hemelryck
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
