On 12/11/06, Bil Galbraith <[EMAIL PROTECTED]> wrote:
I'm attempting to set up a small networked FG
simulation, with the FDM model and instrument panel
running on one machine, the other computers will be
out-the-window views.
All computers in question are running WIndows XP SP2,
and I am running the compiled FlightGear 0.9.10
distribution package downloaded recently.
FlightGear does start and act normally when started
using the FG icon or using the batch script below (The
last fgfs.exe and subsequent commands are all on one
line):
set FG_HOME="D:|FlightGear_0.9.10"
set FG_ROOT="D:\FlightGear_0.9.10\data"
set
FG_SCENERY="D:\FlightGear_0.9.10\data\Scenery;D:FlightGear_0.9.10\data\WorldScenery"
D:\FlightGear_0.9.10\bin\Win32\fgfs.exe
--fg-root=D:\FlightGear_0.9.10\data
--fg-scenery=D:\FlightGear_0.9.10\data\Scenery;D:\FlightGear_0.9.10\scenery
--airport-id=KSFO
--aircraft=c172p --control=keyboard
--disable-random-objects --disable-ai-models
--disable-clouds --enable-clouds3d
--geometry=1280x1024 --timeofday=noon
Now, I've attempted to send out the FDM data via a UDP
socket, adding the following to the above batch file,
as detailed in the GetStarted guide:
--native-fdm=socket,out,60,,5506,udp
I get the following error message back:
Error: connect() failed in make_client_socket()
SG_IO_OUT socket creation failed
Error opening channel communication layer.
I/O channel config failed.
I've searched the documentation and old emails, but
found nothing that talks on this subject. Can anyone
provide any insight and/or corrective actions? Is this
something that works on a Linux system but doesn't
work correctly under Windoze?
Also, in the native-fdm command, is the "60" the rate
that is is cranking out UDP packets?
Bill, yes the 60 is the rate (in hz) that the data is spit out (or read
in.) You should configure FG to sync to the vertical refresh rate of your
monitors (set that to be all the same for all your machines.) And then set
the hz to match this rate. I recommend setting up your displays at 60hz for
best timing results.
I don't know why FG can't create the outgoing sockets ... that shouldn't
depend on the other machine even existing I don't think. UDP is fire and
forget ... The very first thing I would check is the firewall, that could
be blocking things. I forget how to open up specific ports with the windows
firewall, but I assume that would be better than turning the whole thing
off.
Regards,
Curt.
--
Curtis Olson - University of Minnesota - FlightGear Project
http://baron.flightgear.org/~curt/ http://www.humanfirst.umn.edu/
http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------------------------
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-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-users
