Issues, Workarounds & Localization

It won't fix anything unless you alter the default sync interval from 7 days to something sane.

time.windows.com is a complete pile of junk - you're lucky if you get a response from it at all, and when you do you'll often see that you're receiving "invalid" time information, so in that respect changing it may be better.

Frankly the timeservers Windows uses are pretty useless unless you live in the continental USA. Latency is too high and too unstable to be of much use.

Much better to take a look at (for example) Stratum 2 Time Servers and pick one which is geographically closer to you. In the UK at least your best bet for that will be universities - Manchester, Strathclyde and Imperial College London all have open access timeservers, so you ought to be able to get latency down to well under 50ms unless you're on a 3G connection.

Please don't do that.

Stratum 1 machines are not intended for public access, they are only intended for stratum 2 servers to sync to. Unless you are running a stratum 2 machine and providing time sync to 200-300 machines MINIMUM then you shouldn't be going anywhere near a stratum 1 machine.

Stratum 1 machines are not cheap to run as they're usually connected to a machine physically next to it running from an "atomic clock" and do NOTHING other than provide time synchronisation.

The difference in accuracy between stratum 1 and 2 is probably in the range of about 50 millionths of a second, so please use stratum 2 timeservers.

Good man - you've made a BOFH somewhere happier

It may not work for you impli but it does for me - this (clock drift) is a recurring problem in Eve, first time I think it was identified was 2005.

You might want to look at the system log files, you should find two entries something like this when you boot the machine and if they're not there then the ntp registry changes you made haven't started the service :

Source : Time-Service

The time provider NtpClient is currently receiving valid time data from ntp.cis.strath.ac.uk,0x9 (ntp.m|0x9|0.0.0.0:123->130.159.196.118:123).

then immediately after :

Source : Time-Service

The time service is now synchronizing the system time with the time source ntp.cis.strath.ac.uk,0x9 (ntp.m|0x9|0.0.0.0:123->130.159.196.118:123).

In addition if your time has changed you should also see something like :

Source : Kernal-General

The system time has changed to ‎2012‎-‎01‎-‎16T21:53:11.594000000Z from ‎2012‎-‎01‎-‎16T21:53:11.976407100Z.

Only reason I mention this is when I first did this then the ntp client was still waiting out the remaining old "SpecialPollInterval" time before starting. Edit - that means that if it had 6 days to go before contacting the ntp server then it still has the same time to go after your changes so may not start for 6 days. Solution is to set service to autostart and not wait out timer.

Good that the sisi fix works though.

Hi CCP,

I just lost my fully faction fit loki due to my overview not loading when I jumped using a border gate.

Screen shots: http://i291.photobucket.com/albums/ll291/Elitepwnz/loki-1.jpg

Killmail: egk.eve-kill.net/?a=kill_detail&kll_id=12181572

I will be petitioning this.

Details:

I was chasing a tornado with GCC, I had lost him. I warp to the Egmar stargate, there's a arazu and a loki waiting, I jump in.

OH GOODY WHAT DO YOU KNOW, THE OVERVIEW ISN'T LOADING. I check de-scan and there's this: drake, drake, drake, hurricane & stabber fleet issue, they're probably on the gate waiting for me to decloak, so meanwhile im saying **** **** **** ****, what are chances of me cloaking up with GCC, doubtful at best, suddenly the cloaking device activates and I'm like "WOOO HOOO" but the overview still doesn't load *120 seconds gone by* I restart my eve client and upon logging and I'm getting epicly pwnd by the targets and some loki's, as you can see from the screenshot.

*I submitted the petition about this issue a couple of days ago*

Response:

"Hi,

This is a known issue and we're working on resolving this issue.

Thank you for your patience in this matter and please accept our apologies for the inconvenience.

Best regards,
Senior GM Xamother
EVE Online Customer Support"

"You were recently pulled forcefully from your Loki which resulted in you losing 37255 skill points from the skill Minmatar Electronic Systems." Awesome.

Hi CCP,

I just lost another ship plus my implants due to this bug. That makes it a second ship lost on its maiden voyage in 2 weeks.

No, I can not "relog before a dangerous jump" because I move about in fleets and the fleets can not wait for one player. Nor can I afford to be left behind while roaming in hostile systems. That is a guaranteed loss.

Two days ago I was flying in an incursion fleet that was 26 jumps from my home system. Guess how long it took me to fly back home after the fleet disbanded? 1 hour 45 minutes. FOR 26 JUMPS! I relogged 3 times during that voyage.

Enjoyable? Not much.

This bug has utterly and completely destroyed my enjoyment of the game up to the point that I have cancelled my Eve Online subscription approx. 20 minutes ago and I will not be back until this bug has been fixed in production.

I'm not paying you guys for the pleasure of having my ships and pods destroyed without the slightest chance of defending myself and then getting "our logs show nothing, f*ck off" replies to my reimbursement petitions (yes, I know you don't put it so harshly but you know just as well as I do that that is the message).

Thank you and farewell (at least until this issue is fixed).

Seething with holy nerdrage,

-Dynamiittiukko

It is planned for Tuesday, the 24th January, as announced in this news message and this DevBlog.

Seriously dudes, use the work around I posted.

Ok, so after 24 hours of testing, I think I can confirm that time sync interval edit in registry does work for me. I have no lag whatsoever, even modules tick starts in the beginning, no lag after jumping, no lag after undocking.


And because I'm no-lifer for sure! I stayed ingame for about 6 hours now, did lot of missions, traveling, selling, buying and even alt-tabing to start some internet-eating stuff and everything was shiny and happy and no-laggy.


So, what I did was what has been said here by these great fellow capsuleers;


* I googled "How to change time sync" then found this PDF http://www.m0ukd.com/temp/Time_Sync_Interval_Change_Vista_XP.pdf and did everything what is there - and set the interval to 10 minutes.


* Then I found stratum 2 servers list here http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers and found the one, which is closest to me and also most alive in "Last Modified".


* Then I copied that adress in "Change date and time settings" in Windows 7 and pressed the update button.


Then I play the game. Note that even after PC restart everything is still fine, it is probably still better to press the update button again if you turn-off / turn on your computer.


I will continue to monitoring the situation and swiftly inform you if anything changes.

Or better, use one of the "pool.ntp.org" alias names for your region.

http://www.pool.ntp.org/en/

For Europe, use: 0.europe.pool.ntp.org
For North America: 0.north-america.pool.ntp.org
Oceania: 0.oceania.pool.ntp.org
Asia: 0.asia.pool.ntp.org
Africa: 1.africa.pool.ntp.org
South America: 0.south-america.pool.ntp.org

The advantages to using the pool names is that they are round-robin'd, which means that the server behind a particular name is constantly changing, spreading out the load. Which keeps any particular server from being crushed. As servers drop from the pool, they get removed from the list of IPs handed out for those pool names, so you don't have to worry about trying to get time from a dead server.