Hi,
Let us know what you come up with on the broadcast stuff.
Regards,
Curt.
Was the broadcast fix included in the 0.9.8 pre-release?
Recapping:
plib expects the string to be broadcast in netsocket.cpp line#80;
Simgear rejects either an explicit broadcast address xxx.xxx.xxx.255
John Wojnaroski wrote:
Hi,
Let us know what you come up with on the broadcast stuff.
Regards,
Curt.
Was the broadcast fix included in the 0.9.8 pre-release?
Recapping:
plib expects the string to be broadcast in netsocket.cpp line#80;
Simgear rejects either an explicit broadcast address
Curtis wrote:
are special characters to the unix (and probably dos) shells. The shell
will try to pass input from a file called broadcast as stdin to fgfs
and send the output to whatever is after the . Try enclosing the
entire option in double quotes to hide these characters from the shell
- Original Message -
From: John Wojnaroski [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Sunday, December 12, 2004 5:43 PM
Subject: Re: [Flightgear-devel] Broadcast Address
Curtis Olson wrote:
Let us know what you come up with on the broadcast
Curtis Olson wrote:
Let us know what you come up with on the broadcast stuff.
Regards,
Curt.
Okay, here's the answer...
In plib line #80
if (host[0] == '' strcmp(host, broadcast) == 0)
sin_addr = INADDR_BROADCAST;
expects the string argument as noted above. There does not appear
- Original Message -
From: Steven Beeckman [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Friday, December 10, 2004 2:08 PM
Subject: Re: [Flightgear-devel] Broadcast Address
Citeren John Wojnaroski [EMAIL PROTECTED]:
I've been thinking of moving over
Let us know what you come up with on the broadcast stuff.
Regards,
Curt.
I will do that...
Your short discussion on timing brought to mind an interesting question.
Since there is some unpredictability to the scheduling algorithms and device
drivers and system calls, can the 60Hz rate
John Wojnaroski wrote:
I will do that...
Your short discussion on timing brought to mind an interesting question.
Since there is some unpredictability to the scheduling algorithms and device
drivers and system calls, can the 60Hz rate really be locked.
You are right, without taking additional
Citeren John Wojnaroski [EMAIL PROTECTED]:
I've been thinking of moving over to RTLinux (there is an open-source
GPL'd
version) in 2005. It fits nicely with the structure of the opengc
display
code.
I'd like to mention RTAI (http://www.rtai.org), a Linux kernel patch
to get the kernel
, December 09, 2004, at 03:38PM, John Wojnaroski [EMAIL PROTECTED]
wrote:
- Original Message -
From: Jonathan Polley [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Thursday, December 09, 2004 1:00 PM
Subject: Re: [Flightgear-devel] Broadcast Address
You
John Wojnaroski wrote:
Hi,
Trying --native-fdm=socket,out,30,192.168.2.255,7000,udp to broadcast
the data onto a LAN for multiple machines returned the following error:
***
Error: connect() failed in make_client_socket()
SG_IO_OUT socket creation failed
Error opening channel
John,
I seem to recall having this working once. There is an extra flag you
have to enable on the socket to make it actually broadcast.
Yes, that jogs the ole' brain cells. (See Unix Network Programming,
H.R.Stevens, page 318)
I don't recall if this had to be enabled at the
plib level
John Wojnaroski wrote:
Thanks, that helps -- guess I'll dig around in the plib and Simgear code
Part of the question also relates to any penalty imposed on the FG frame
rate by adding multiple socket options for each IP address and unique port.
Any SWAG on the percentage for each additional
13 matches
Mail list logo
