Networking

Hosting Network games

You need to understand basic networking and NAT to get the most out of this section.

If you have issues hosting, consider putting the Host PC outside the Firewall using a true IP address! This works 100% of the time (only required by the HOST of the game). If you do so, make sure you disable M$ Networking and File and Printer sharing, also helps to have a good software Firewall on your PC. People have hosted using modem dial-up or broadband, so if you’re stuck hosting, this is a sure fire way for it to work.

More light reading…
http://www.simhq.com/simhq3/sims/combat_helo/longbow2/faq.shtml#firewalls

AV8R’s MP guide

“Been successful thus far with 5 player (didn’t have more LB2 pilots around at the time from our F4 squadron). Been able to get laggless, jitterless, smooth flights running single missions and campaigns. Even running 3+ missions in a row without having to exit.

Tips:

1. SPEED playability and matching

   Get systems to be roughly matched in speed. For Solo or MP you need to do this to get the sim to run the right speed and to reduce MP warping and jitter. Around 750Mhz works fine. Using the TURBO.EXE program to slow down fast systems such as:

   2.0Ghz, 35-40%
   2.4Ghz, 30-35%
   3.2Ghz, 10-15%

   Turbo Deceleration Approximation
   (CPU Speed, GHz) x (Percent of Full) = 0.750 GHz

   For example;

   2.4Ghz x Percent = .75 GHz
   Percent = (0.75)/(2.4) = 0.31 or 31 Percent

   Download TURBO.EXE here

2. Bandwidth and Ports

   I’ve been successful in hosting with either Dialup or Cable (broadband) connectivity. In fact, LB2 likes the stability and speed of 56k modems, as that what it was optimized for. Yet it works for broadband too. Just make sure the Host and Clients have the correct ports available. NAT problems can sometimes be overcome by going out to the DMZ of your router's firewall.

   Router/Firewall ports
   47624 TCP
   2300-2400 TCP/UDP
   26210 TCP

3. In game setup SOP

   Ping meter means nothing, ignore it

   Once inside the mission map/arming/tasking/briefing/waypoint scheduler, only one person should make a change at a time or else it can get out of sync. Once changes are made, do a SYSTEM/Data Transfer, and then tell the next player to make their changes.

   Its best to do pilot positions first, then move waypoints, then arming, all red text must be gone and all human pilots must be placed before proceeding to fly.

   Optionally, everyone run the REHERSE function after first getting into the mission scheduler. Sometimes this helps with getting all players synched up before making mission edits.

   Once in the cockpit, each player call "in pit" before spooling up and taking off. Give all players a chance to get "in sim".

4. Chat Box management

   Use ALT-CAPs twice to eliminate the chat box. CTL-CAPs to move its position from bottom to middle to top.

   Note that you can manually edit the built in chat taunts (like CTL-F1 when the chat box is up)

5. A/C related

   You can put two players into same ship. Even the HOST can be the CPG for another human piloted ship.

   This player has been able to get into LBs and BlackHawks. Any attempt to get into a Kiowa has resulted in a game lockup or MS error popup before entering the cockpit phase. If someone has solved this problem, please share how it was done.

6. Graphics card related

   I’ve been successful with Nvida GF4 Ti4600, ATI 9800 Pro, ATI X300 video cards on 3.2, 2.4 and 3.0 GHz systems, respectively. The GF cards do well with the Glide wrapper and the ATI with the D3D for the cases where I want to run x4 A.A. and Anisotropic filtering. These reduce the jaggies and improve the quality of the graphics. There are some anomalies I’ve seen with the D3D such as: spike glare graphics when firing Hellfires at night and mirrored reflective cockpit glass (which is clear on the 3DFX).

Enjoy

AV8R“

(c) 2001 Speichts.com