The Net/Multiplayer support will mainly be designed to work in a local 10Mbit/s LAN, and not on modem lines.
At present, it takes up 10kBytes/sec bandwith for 3 objects in a mission.
The current implementation uses UDP to communicate, every server-frame
the server sends his complete status as ascii to the client.
This will lead to further optimization.
If you click 'FleetNet', you will be taken to the connect screen.
The forms/input fields you see don't work correctly yet - leave them
alone.
Click on 'Start Server' to start the server in background on localhost.
Click on 'Connect' to connect yourself to the running server.
Now you have to choose the mission you want to play.
Then click on 'Flightgroups' and after 3 seconds the action should
start.
You can start the server without using the GUI by calling TuxFleet as ./tf-server
This has only been tested from localhost to localhost. Please tell me, if you have run it in a LAN.
See file ./tuxfleet.conf to change server/client options:
see also: Startup Gui