At last,I tried a sample program to send external fdm data to Flightgear
0.9.10.I now could see Flightgear responding to packets.However problem came
that as soon as the packets are arrived the time of day automatically
changes to night and I need to readjust the settings.
I would also like to
Curtis Olson wrote:
Endianess is definitely handled. And even for 32 vs. 64 bit systems, they
all still use a similar convention where integers and floats are 4 bytes and
doubles are 8 bytes. As long as we confine ourselves to ints, floats, and
doubles (and use an int for boolean values,
Hi,
I am using FGFS 0.9.10.I tried sending FGNetFDM structure(given in
net_fdm.cxx)(after doing htond or htonf) from one computer to another
computer running Flightgear but couldnt get it running. I tried Packet
Analyzer to check whether packets are reaching the particular PC or
not.Ifound that
ypedef struct {...} mystruct_t;
mystruct_t anInstance;
char * sendbuffer = (char *)anInstance;
At the source computer I tried to print the char* sendbuffer by using
printf(Data=%s,sendbuffer);
But I cannot see any data packets formed.Is that i am using wrong format for
printf or is the
umesh pandey wrote:
[...] Can anyone provide me with sample UNIX
program to run Flightgear from external fdm data in the form of UDPpackets.
Another instance of FlightGear ? ;-)
To my understanding the NetFDM wasn't really designed to be driven by
anything but FlightGear on the same type of
On 12/12/06, Martin Spott wrote:
umesh pandey wrote:
[...] Can anyone provide me with sample UNIX
program to run Flightgear from external fdm data in the form of
UDPpackets.
Another instance of FlightGear ? ;-)
To my understanding the NetFDM wasn't really designed to be driven by
anything
On Tue, 12 Dec 2006, umesh pandey wrote:
ypedef struct {...} mystruct_t;
mystruct_t anInstance;
char * sendbuffer = (char *)anInstance;
At the source computer I tried to print the char* sendbuffer by using
printf(Data=%s,sendbuffer);
Hi Umesh,
That printf() is quite unlikely to produce
Hi Curt,
Curtis Olson wrote:
The NetFDM packet structure is designed to work across platforms and the
data field sizes and types are somewhat carefully chosen to avoid packing
differences between compilers.
Hmmm, isn't NetFDM the copy the struct to a network packet-interface
or did I mix
On 12/12/06, Martin Spott wrote:
Hi Curt,
Curtis Olson wrote:
The NetFDM packet structure is designed to work across platforms and the
data field sizes and types are somewhat carefully chosen to avoid
packing
differences between compilers.
Hmmm, isn't NetFDM the copy the struct to a
Curtis Olson wrote:
Yes, NetFDM is what you say, but we've made sure all our data aligns on 4
byte boundaries, we only use 4 or 8 byte data structures, and we send
everything in network byte order. With these rules, you would be hard
pressed to find a system that is incompatible. (This
On 12/12/06, Martin Spott [EMAIL PROTECTED] wrote:
errrm, and, at least some of them don't even dare to think of
using current versions of FlightGear. I was told they're afraid of
running into the hassle of reworking half of their interface with every
new version of FlightGear, because
Curtis Olson wrote:
Work was done to improve the NetFDM structure prior to v0.9.10 so if you did
your experiements earlier than that, the picture has most likely changed.
I did most of my tests way before 0.9.8. Does this mean the current
NetFDM is safe for use with 64bit- as well as
On 12/12/06, Martin Spott wrote:
I did most of my tests way before 0.9.8. Does this mean the current
NetFDM is safe for use with 64bit- as well as big-endian systems ?
I don't have the ability to personally test a lot of combinations, but yes,
this should all work well as of v0.9.10.
After converting FGNetFDM structure(given in net_fdm.cxx) by using
htonf,htond or htonl, do we need to convert the structure into char packets
and send to FGFS. I am using FGFS 0.9.3.
On 11/24/06, Anders Gidenstam [EMAIL PROTECTED] wrote:
On Fri, 24 Nov 2006, umesh pandey wrote:
What is the
On Tue, 28 Nov 2006, umesh pandey wrote:
After converting FGNetFDM structure(given in net_fdm.cxx) by using
htonf,htond or htonl, do we need to convert the structure into char packets
and send to FGFS. I am using FGFS 0.9.3.
Hi!
Well, when you have used hton*() on your struct it should
On Fri, 24 Nov 2006, umesh pandey wrote:
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
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
I checked using Flightgear 0.9.8 but could not run it successfully.The few
lines of log data are as follows:
Running Main Loop
===
Updating time
Current Unix calendar time = 1164188445 warp = 0
Current GMT = 11/22/2006 9:40:45
Current Unix calendar time = 1164188445 warp = 0
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.The few
lines of log data are as follows:
snip
I am also using correct command to start FGFS with external fdm:
D:\FlightGear
19 matches
Mail list logo
