the bug report was 'This report has been attached to a defect'.

Thats all it says. Would be nice to hear from CCP about this issue though.

Well... that didn't take long.

The issue is still there. I haven't encountered any significant lag after jumping yet, but the game certainly stalls for a few seconds when jumping into new systems and I feel that as I continue playing it will just increase in duration

The patch today seemed to alleviate this issue for me somewhat, I played for a little under an hour and had a couple of jumps in which it took some time for the new zone to load up but nothing like that it had been.

Has anyone else noticed anything after today's patch?

I got the same issues, started last friday, it had no issues before.... nothing changed on my desktop, as EVE is the only thing I run on it :P

It's a strange behaviour, as it does not happen every jump, sometimes it is the first jump, another time it takes 3 jumps before it lagges you out on the next jump.
Also the lag is different, sometimes is get stuck and loads for 30 seconds, while in some cases it can take up to 5 minutes.
Everything else keeps working, market, chats, maps, etc.. etc..

When you jump, it actually loads the new system (names etc.. are changed) but the overview stays empty "nothing found" and also your current speed stays active on xx M/S (this various). than a baclscreen pops up and the new system is loaded (after 30 sec to 5 minutes).

i got fed up with it so i borrowed my friends 8800 GT vid card and it fixed the load lagg instantly ...
so the game has something against ATI cards i guess

This certainly does not appear to be hardware related as there is a range of people experiencing this issue with very different hardware setups, whilst others (with NVidia, ATI and other graphics cards) have no issues at all. Unless CCP would like to indicate that the 8800GT is now a pre-requisite to running EVE properly, I am hesitant to spend money on hardware.

I'm glad to hear that you are no longer experiencing the problem though.

I would encourage everyone to post bug-reports and if you are aware of anyone else having this issue to guide them to his topic + also get them to put in bug reports.

Hopefully at some point this year we may get a response/resolution from CCP.

Hi! We are looking into this problem and it seems like we identified the cause: it seems like we are handling the case of a drifting client clock very badly at jumping (much worse than before Crucible). We are working on a fix for this.

Btw: The drifting client clock is very probably caused by your hardware and it might also cause other problems, for example incorrect shield and capacitor display or a wrong display of timers. It might be a good idea to check your hardware or try to disable over-clocking of CPU or GPU.

I suggest to relog your client before risky jumps as workaround till we manage to deploy a fix for this issue. I know that this is annoying and not always possible, but it will reset the clock and so avoid the delay at jumping (but the delay will start accumulating again).

Hi! We are looking into this problem and it seems like we identified the cause: it seems like we are handling the case of a drifting client clock very badly at jumping (much worse than before Crucible). We are working on a fix for this.

Btw: The drifting client clock is very probably caused by your hardware and it might also cause other problems, for example incorrect shield and capacitor display or a wrong display of timers. It might be a good idea to check your hardware or try to disable over-clocking of CPU or GPU.

I suggest to relog your client before risky jumps as workaround till we manage to deploy a fix for this issue. I know that this is annoying and not always possible, but it will reset the clock and so avoid the delay at jumping (but the delay will start accumulating again).

Hi! We are looking into this problem and it seems like we identified the cause: it seems like we are handling the case of a drifting client clock very badly at jumping (much worse than before Crucible). We are working on a fix for this.

Btw: The drifting client clock is very probably caused by your hardware and it might also cause other problems, for example incorrect shield and capacitor display or a wrong display of timers. It might be a good idea to check your hardware or try to disable over-clocking of CPU or GPU.

I suggest to relog your client before risky jumps as workaround till we manage to deploy a fix for this issue. I know that this is annoying and not always possible, but it will reset the clock and so avoid the delay at jumping (but the delay will start accumulating again).

Hi! We are looking into this problem and it seems like we identified the cause: it seems like we are handling the case of a drifting client clock very badly at jumping (much worse than before Crucible). We are working on a fix for this.

Hi! We are looking into this problem and it seems like we identified the cause: it seems like we are handling the case of a drifting client clock very badly at jumping (much worse than before Crucible). We are working on a fix for this.

Btw: The drifting client clock is very probably caused by your hardware and it might also cause other problems, for example incorrect shield and capacitor display or a wrong display of timers. It might be a good idea to check your hardware or try to disable over-clocking of CPU or GPU.

I suggest to relog your client before risky jumps as workaround till we manage to deploy a fix for this issue. I know that this is annoying and not always possible, but it will reset the clock and so avoid the delay at jumping (but the delay will start accumulating again).

Btw: The drifting client clock is very probably caused by your hardware and it might also cause other problems, for example incorrect shield and capacitor display or a wrong display of timers.

Any idea if this has been fixed in today's minipatch?

Might also be the cause of ship speed indicator becoming stuck at a random value

\o/ Thank you CCP Habakuk for taking the time to post on a Sunday.

This is very interesting. I knew the RTC clock on this PC is very shoddy and is drifting if left unchecked. So I have a daily sync with a time server scheduled, this is enough accuracy for all my daily work. Never have had problems with Eve on the machine too. Nothing i over-clocked, this is actually the most reliable PC I ever had. Anyway, it's great to not be stuck in limbo anymore.

Hello again!

Our test-server Singularity was updated today with a (potential) fix for this issue. We had to change a bit more than expected, but we are hopeful that the new solution is more stable than before.

I had a short test of this in Singularity, but it would be awesome if you guys (who have this issue on TQ) could try it out! If you already used the test-server at some point or you always wanted to try it: Now is the time for it!
Details: The client is now re-synchronizing with the server every 10 minutes (the time interval might be changed later).
If you are trying this on Singularity, then please take special care of your UI in space after you were logged in for about 10 minutes. Try to jump and dock. It would be great if you are running logserver.exe to get logs for the case that anything breaks - more info at http://wiki.eveonline.com/en/wiki/Logserver. Please send a bugreport if you find any issues (add my name to the title of it) and please also reply in this thread - I will continue to monitor it. It might be possible that 10 minutes is still too long for you guys (if your clock is drifting too fast) and you still have some load lag: please reply in this thread if this is the case.
More information about Singularity can be found here: http://wiki.eveonline.com/en/wiki/Singularity

I have the same, it appears to be everytime a new skybox is loaded ie changing regions and certain constellations.
It probably is an ATI card thing as the only people i know who have the issue use them cards.

I was able to find a workaround for this on TQ! By default, the Windows time syncs via NTP with "time.windows.com". I switched it to sync with "time.nist.gov" instead, and that seems to have solved this issue with Eve. I have played for hours without noticing the slightest bit of jump lag.

Glorious CEO: Thank you a lot for testing it on Singularity!

DurrHurrDurr: How much is a noticeable difference for you? It might be useful, if you could save a logserver log of being ingame for at least 30 minutes while doing stuff and adding this to a bugreport (with the subject including my name).
For the release of this fix: As the fix is a bit more complicated it is not possible to "hotfix" it - it is currently scheduled to be included in the next client patch for Crucible 1.1.

Caroline Grace: These symptoms look a lot like problems with the clock sync - but it might be that your clock is sometimes a bit too fast and sometimes a bit too slow, which would explain the different issues.

After 4-8 minutes of being actively in space (ie. shooting a POS, travelling, etc) I notice a difference of about 20-25 seconds between my system clock and the game clock. This gets exaggerated the more I travel and hang around in space. However, the difference doesn't seem to really exceed ~120 seconds.

How do I set up my client to log?

This is some serious clock drift, which you are experiencing there - I'm not sure if we will ever be able to compensate this fully, but it should be at least better with this fix. The instructions for logserver can be found at http://wiki.eveonline.com/en/wiki/Logserver.

This issue didn't exist at all before the release of Crucible. Do the devs have any idea what's created the drift?

As far as I know (as lowly QA dude): Before Crucible there was a clock sync at jumping (which was broken with Crucible), but if you stayed within one system you should have drifted like it is now on TQ.

Just pointing out that I was playing fine after the initial Crucible release. Caravan events and new exploration content had me log in for hours, I def. would have noticed the bug. It was the pre-Christmas patch that broke Eve for me.

This didn't fix the problem.

making my laptop sync with a stratum 1 time server near my location

Please don't do that.

[snip]

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.

Fair points. Changed. Even found a stratum 2 server that's significantly closer to me than the stratum 1 I was using until now. With luck, I may actually have gained accuracy.

.d

CCP could you please give us an eta for Crucible 1.1? It would be much appreciated.

Seriously dudes, use the work around I posted.

Seriously dudes, use the work around I posted.

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.

I wasn't trying to take credit, we can all see earlier posts came up with solution. My post was meant to clarify the previous posts and stress the need to alter sync intervals.

Well I am still experiencing it, even after having set it to every 15 minutes.

Hopefully tomorrow's patch will make this whole discussion redundant anyway. :)

I played yesterday for a few hours without any issues at all.

I will keep an eye out however in my future roams.

I'm actually still using the sync tool found at http://www.timesynctool.com/ which may be the only point of difference.

TPG? No wonder mate... should have gone with a real provider like Telstra

I will post my server up when I get back from work. Have you got the sync set to every 15 minutes?

Simply pull out the BIOS battery of your motherboard and put it back in again, this resets all your sync settings back to default.

It has fixed my eve client and if the issue still occurs than simply replace the battery.

I hope that this helps you people that still have it.

I would also like to thank CCP for helping us greatly with this issue.

Thanks and bye.

Time-syncing has not fixed the problem for me.

Remind me to send you like 50mil. Fixed me right up. Jumping like the demigod that we are! thanks man.

Molic Blackbird, Archinquisitor and Faffywaffy: Could you please write bugreports with logs from logserver.exe, so that I can have a look and check if it is the same old problem (which should be mostly fixed) or if anything new is going on with Crucible 1.2? Please add my name to the title or description, so that I can find the reports more easily.

For all others, who are still experiencing issues: Please also write bugreports about it with included log-files, we will keep trying to find better solutions - maybe there is something in the logs, which help us to pinpoint the remaining issues.

Btw: We could not find anything, which would explain this to be worse with Crucible 1.2 or which would explain it to be worse in fleets, except that the computer *might* be a bit slower, if it is running at full load (for example during fleet-fights). Please reply here and send bugreports, if you have any additional info.

I am having this issue as well, while you may not be able to find anything that would explain this being worse with Crucible I can confirm that I never suffered this problem prior to Crucible. Could it be something related to changing the session timers?

You can check for how much your client is drifting in comparison to our server by running logserver.exe and searching the logs. Every 10 minutes following message will be logged, which states the current difference to the server:
*** Soft Clock Sync adjusting by

Archinquisitor, Molic Blackbird: Thank you for your bugreports! Your problems are indeed caused by clock drift problems - the drift is too high for our current re-sync system. [...] Please reply here and send bugreports, if you have any additional info.

[...] Fire up timesynctool [...]

What I don't understand is if the clock is updated every ten minutes, why would the drift accelerates over time? It might start out at 20-30 seconds, but after 3-4 hours it could be 120+ seconds.

Switching from Windows XP to Windows 7 solved the problem for me.

...Your problems are indeed caused by clock drift problems - the drift is too high for our current re-sync system. ......

I am quite worried if this lag thing affects my skill training....

Will the Crucible 1.5 patch contain solutions that help alleviate this problem?

Yes, Crucible 1.5 will contain improvements to this problem. We don't know yet if they are sufficient, but we hope, that these will hide the problem as much, that you won't notice it while playing. We are still investigating possible software causes for this problem which might lead to better solutions after Crucible 1.5

[shameless plug] These improvements will be active in tomorrow's mass test on Singularity. Feel free to join the mass test, if you experience this problem on TQ and want to check it out. If you manage to gather logs and send these through a bugreport: Even better! [/shameless plug]

I have been reading the patch notes http://community.eveonline.com/updates/patchnotes.asp and am wondering where the improvements are relating to this as I can see nothing specificaly related to this issue.

This is indeed missing in the patch notes, as the real fix is still not made - but the values of the existing clock-sync are being changed, so that a basic check is done every 5 minutes (and more often if clock drift problems are detected) and we are now allowing to correct more than 2% of clock drift.

Greatly improved...thank you. When running 2 clients there is still a delay of around 10-30 secs in some jumps but at least I can now play with 2 accounts at once.

Good to hear this! I would be very interested in a log from one of these 10-30 sec delays. If you manage to get logs please attach them to a bugreport and include my name in the title of the bugreport.

Sure, does it make a difference how i run the logging app with 2 clients running?

Always happens upon a gate jump and usually when time dilation is in effect.

Will jump into a new system, both overview and grid will not load. But the eve chat channels are working fine. Logging out and back in immediately always works but by then I'm playing catch up with the fleet and risking death.

Anyone else get this BS, is there a workaround?

Spoiling my PvP. Happened 3 times in 4 ops :-(

After reading this thread it's not quite clear to me whether CCP is even trying to look for possible causes to the clock drift. All the replies seem to be assuming that it's a hardware problem and nothing can be done about it, just mitigate the symptoms by syncing with server time

I just had to bring this up because I've had some HUGE clock drift since Crucible 1.5, and it only seems to occur when running EVE. Just starting the client and staying in the login screen makes my system clock lose consistently 5 seconds every minute. I have not been able to reproduce it with any other program or game, and outside EVE the clock runs just fine. I've also noticed that the drift is proportional to frame rate. For example if I run with interval four (15fps) I only lose about 1 second per minute

Maybe it is a problem with hardware, drivers or something, but at the very least it tells me that EVE client has to be doing some really weird stuff that no other program does to reveal the problem

Gonna make a bug report too; just wanted to post here for everyone to see

Win XP Pro SP3 32bit / Intel Q9450 / 4GB / Abit IP35 / 8800 GTS 51

Hi, I'd appreciate it if those of you who have time could see if this issue has been resolved for you on the build that's currently on the Singularity Test Server. Thanks for your patience with this!

It's pretty hard to believe how six months can go by with a bug like this and still no progress is made. I just had to relog 3 times after jumping through 2 gates. I've reset my internet clock and all that crap and it hasn't fixed anything.

At least we have new skins for Minmatar ships. Oh wait, they're terrible.

Ship skins are made by graphic artists in CCP, whether they worked on it or not wouldn't affect the fixing of bugs in code. God forbid a graphic designer starts programming.

changed my settings from fixed window.. to fullscreen and :for now: i don't seem to have any lagg problems anymore.

Delaying pressing the jump button by a few seconds so that you aren't with the 1st batch of jumpers does massively diminish the chances of it happening.

Not much of a workaround if you like being fast tackle or if you are being chased but at least it seems to work.

Filed a bug report with a log server file of this happening. Jump into system with a fleet of about 80 people, everything loads except my ship in space, and the overview. No grid.

Hope the log server helps track this down.