Multiplayer Connections in F4 v. 1.07
by Glenn "Sleepdoc" Kletzky, MD
This article, written by the head of the i-Beta team, will help you make effective connections in the latest release of Falcon 4.0. "Sleepdoc" welcomes your input and response. You can mail him at the link above.

Before you can connect in multiplayer Falcon 4.0, you must learn the definition of a few simple terms:

Connection-Host:

(Also called the C-Host). The connection host is the person who allows other players on the Internet to connect to his machine.

In order to be a connection-host, you tell others that you are hosting a game. Then you give your friends your IP. When you go into the comms window you simply select the appropriate comms speed for your modem (33.6 is a great choice no matter what modem you have) and then you select "internet". You will notice that when you select "Internet", a placeholder for an IP address comes up in the comms window.

DO NOT enter anything. Simply press connect. This makes you the C-host. We like to say that C-Host "connects to himself. In LAN play, you don't use IP addresses, so this concept doesn't exist. All players simply select LAN and presses connect.

Connection-Guest:

(Also called the C-Guest). The connection guests are the guys and gals who connect to the connection host. They do so by selecting 33.6 in the comms window (or whatever, I recommend 33.6 for now till you learn more sophisticated techniques) and then pick "internet". Now enter your C-host's IP address and press "connect" and you will be connected to the C-Host in the chat lobby. You can see the chat lobby by simply pressing the "comms" selection again.

OK. I think i need more of a play by play to host a MP session.

Basically, here is how it unfolds.

1. I set up a static IP for my gaming rig.
Reference: http://portforward.com/networking/static-win7.htm
Done.
2. I forward port ranges for Falcon 2934-2935 and also enter each into single port forwarding.
Reference: http://portforward.com/english/routers/port_forwarding/Linksys/WRT160Nv2/Falcon_4.htm
Done.
3. I add firewall rules to allow access for incoming connections. Two rules added - both for TCP and UDP
Reference: http://www.youtube.com/watch?v=SF2biULCay8

OK... ports should be open. I check port checker and it shows closed... OK - no big deal. DCS shows closed until the game is actually launched for port 10308. Maybe this is the same.

So i catch my buddy on TS3 and we try to connect.

1. I launch Falcon BMS. Goto COMMS on top tab and click it.
2. I give the server a name "OUTLAWS" and DO NOT enter any IP information in the bar as I am the C-HOST and M-HOST. I disable IVC and click connect. I DO NOT enter anything in for CONNECTION BANDWIDTH
3. I am back at Menue page and the COMMS tab is lightly flashing. I click on it and it shows "d0o0m" in the lobby.
4. I invite my friend to join and offer him my IP address as defined by a "whats my IP?" query in Google.
5. He types it in and cannot connect.

Questions:

1. At what stage do I invite my clients to join? I do notice there are further options after I select a TE. In particular there is a Rules of Engagement window which pops up after I Committ ONLINE. Should my client be trying to join after this is settled?

2. Am I correct in assuming the ports should be visible once the server is up (as is the case with DCS A10)

3. Does KOTAR acutally ALWAYS have static targets on the ground for A2G FCR to pick up? I overflew yesterday and there was nothing there but ground texture.

I cannot achieve a screenshot of the Falcon in game windows... it keeps taking a shot of my USB mimo monitor instead so I can't show you what I am seeing - hopefully my description suffices.

Any help is greatly appreciated and perhaps this thread can help other noobs suffering the same difficulties.

Thank you!

is it a problem if PFChecker says my port is open but that it is unable to ping my router?
Also ... do i NEED to use IVC? I have been told to ignore it until i get used to the simulator..