In addition to the methods mentioned in the 'Common Problems/Fixes' thread, here
you will find a fine collection of information and possible fixes about lag issues with
NF. This thread has been merged with some other threads to concentrate the
information. Currently, this thread contains the following sections:

Part I. "NF Lag Solutions" by Yuno (TeamNF mk1)
Part II. "Lag - The Occassionally Unresolveable Issue" by eze1 (TeamNF)
Part III. "Lag-Related: How to transmit Traceroute Results" by Obst

============================================================

Part I. "NF Lag Solutions" by Yuno (TeamNF mk1)

Dear Fans of NF,

We have been receiving many reports of players complaining about lag while playing
NF. We have been adamantly searching for all possible solutions. In the process we
found some interesting details of things that may be causing lag in the game. Please
read the following possible solutions carefully.

A. Lag caused by some NICs (Network Interface Cards).
1. Right mouse click on My Computer and go to "System Properties".



2. Click "Hardware" and click on "Device Manager"



3. Click on "Network adapters" and double click on whichever network adapter you
have. Mine is Realtek as you see in the picture.



4. Go to "Advanced" tab and you see a number of items in the Property section.
Here are the important details, so please read carefully.

a. Click "Offload Checksum" item and make it "Disable" under "Value".
b. Click "Offload TCP_LargeSend" and make it "Disable" under "Value".
c. For some other cards, they have a "TASK_OFFLOAD" menu; make it "Disable"
for "Value".
d. If you do not see these things, please upgrade the Network adapter driver to the
latest one.


Changing these setting will reduce lags in any other online games as well.

B. Some codecs (i.e. audio video) generate lags in NF

We have received a report from a few players that some codecs cause heavy lag
with NF. Unfortunately we do not know which specific codecs are causing these
problems at the moment. Please go to the "Add/Remove Software" menu and
delete "codecs" installed on your PC. If you provide us with a report of a specific
codec which conflicts with NF then we will give you 500,000 credits for each codec
you reported. You must test it and send the codec file along with your report. Please
submit your report to [email protected]

C. Turn off NF options.
If above two suggestions are not working for you, please turn off Navy Field effect
options. Press the "F10" key during battle and you will see the bottom window.



Turn off the options in red square.

D. Play other games.
If all 3 suggestions are not working out for you then delete Navy Field and play
other games like World of Aircraft, Never Quest, or Lameage. Just let us know before
you go, so we can call you back when we have new solutions. However, I really
would like you to try out Harbor Assault before you go. It's good and coming very
soon.



Thank you all for supporting Navy Field.


Yuno a.k.a Lag Hunter
-------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------

Part II. "Lag - The Occassionally Unresolveable Issue" by eze1 (TeamNF)

Lag - The Occassionally Unresolveable Issue

Lag is one of the most difficult issues to address from a Tech Support aspect when
any online game/activity is concerned. There are SO many factors involved, that
giving a definitive answer is nearly impossible. Lag can be caused by something as
simple as a fragmented hard drive or a bad cable/wire connection to something
nearly impossible to correct like an Internet Provider issue.

To compound the issue, a problem with lag can be experienced by one person in a
city while another individual in the same city has absolutely NO lag. A simple wire not
transmitting data properly, an intermittent Network Interface Card(NiC)/driver
problem, certain pc software(anti-virus/pc monitoring software updating), and even
a faulty signal splitter with the improper DB loss can cause lag/packet loss and other
connection issues.

If it was a massive issue from ALL players, it may be a server issue. But case-by-
case issues are tricky at best to resolve. So please consider this when
the "lagmonster" strikes you. Please don't assume that the NavyField servers are
the cause of the issue. There are far too many other factors involved to make such
an assumption. NavyField is only as "perfect" as the humans that make up
the "internet". And the people that build the computers etc. Some things are beyond
our control....lag is sometimes one of those issues. Please understand this...it's not
that we don't want everyone in the world to be able to play NavyField lag-free(I'm
sure we'd all love that actually), it's just that we don't have control over every
aspect of every connection to every computer of every player.

Thank you for your patience when the "lagmonster" strikes you

eze1 - TeamNF


============================================================

In an effort to reduce the amount of stickies in Tech Support, I have asked obst's
permission and combined his Tracert sticky with this one. Thanks Obst, again :)
------------------------------------------------------------------------------------------------------------

Part III. "Lag-Related: How to transmit Traceroute Results" by Obst

Lag-Related: How to transmit Traceroute Results

Hi there!

Sometimes people experience enormous amounts of lag, and sometimes that lag
cannot be fixed by following any of the hints provided in this forum.

For these people, it is suggested to do a "traceroute" to the NF Servers and supply
the results of that to TNF, this way they can find out where the problem lies.

Please, before going on to spam TNF with traceroutes (Don't spam them, lol!),
please check out this thread first and try the hints given there to fix the lag:

http://www.navyfield.com/board/view.asp?Num=3723&Sort=E09


Now, on to the actual traceroute. Please follow these instructions step-by-step!

1) You need to enter the Command-Prompt.

To do this, either press WindowsKey+R



Or access it via the Start-Menu. Go START->RUN



2) An input-window will pop up. Type "CMD" (without "") and press OK.



3) Congratulations, you are in the Command-Prompt!

The size of the prompt may vary! I resized mine to fit this Guide!




4) Now you need to know the IP-Adresses of the Servers.


Nebraska 211.43.149.199

Kaiser 211.43.149.200

5) The command to traceroute is "tracert X", where X is the IP.

For example, let's say I want to traceroute New York Server. Then I will type "tracert
211.43.149.201" and press enter.



It will then do a series of automated processes, just sit back.



6) After a while, the traceroute will come to an end. Either it normally finishes or it
times out at a certain point, but that does not matter for now (that's TNF's business
^.^).

It may take some time, and it will try 30 times even when it times out several times.

When this happens, you may just proceed to step 7 and work with what you already
have.

If it finishes normally (by either going through 30 tries oer reaching the target IP)
you can now get that info to TNF


7) Now you have to mark the whole traceroute and copy it.

To do this, left-click into the lower-right corner of the prompt, keep the button
pressed and move the cursor towards the upper left. This will select anything in
between.

Now, to copy this info just press the ENTER-key!

Please watch this animated picture for better visualization:



***IF YOU CANNOT MARK THE TEXT DO THIE FOLLOWING***

[A] Open a Command Prompt as in 1), or work with one that is already open.

[B] Press the icon in the upper-left corner of the title bar and press "Properties",
--> Or Right-Click into the Command Prompt's Titlebar.

[C] Select the "Options" Tab.

[D] Check the "QuickEdit Mode" and "Insert Mode" boxes.

[E] Press OK.

[F] Check the "Save Properties for future Windows with same Title" box and press
OK.

***THEN IT SHOULD WORK***

The marked text is now copied to your clipboard and you may either paste it into a
new textfile or directly put it into an email.

This email should be sent to [email protected] , as subject enter something like
for example "Traceroute Results, Lag in Europe".

In the mail, give your account name, server and your location as well as the
traceroute results as well as any additional info you may have.

Please NOTE: You may not get a response, but any information you supply like this
WILL HELP!

Example mail:



===========================================================

*edited by eze1 10-17-06*
*Server IP corrected by rolleso 06/30/07*
*NY Server IP added by eze1 11-25-07*
*Server IP updated by rolleso 01/14/09*
*Server IP updated by rolleso 09/17/09*
*Server IP updated by rolleso 02/19/10*