Issues, Workarounds & Localization

Update:

We have a potential fix being tested for the client freeze issue and hope to deploy this fix to Tranquility next week if our testing goes well.

The fix is currently on the Singularity test server and we encourage anyone experiencing the client freeze to play for a while on Singularity and let us know via this forum thread if you experience any client freezes on Singularity.

Instruction on how to get on the test server can be found here

I would like to thank everyone who contributed in helping us fix this issue and apologize for the inconvenience this caused during your gaming sessions.

Operating System: Win 7 64boit
Graphics Card: GTX 680
Driver Version: 9.18.13.1407
Number of Clients: 1
How long before the freeze/crash occurs? In fleet doing incursion. About 1 min once i jump on grid
What are you doing when the freeze occurs?: Just joining a incursion fleet and getting on grid. Also running 3 Monitors in surround mode.

hallelujah.... i will try this evening....

I took 7 clients on 2 computers to Singularity. I had no crashes for the three hours I was on, whereas I was going for max 25 minutes on Tranquility. Looks good!

Prior to the last big patch, I could comfortably run 10 clients on my machine. Since the patch, I can barely run half that number. Why? Something in your patch has turned your client into a complete resource hog.

Memory usage, per client, has gone up between 40 and 100MB. So where pre-patch usage was between 590 to 640 MB, now it's 660 to 720mb per client. CPU usage has gone through the roof, essentially doubled. At 5 clients, CPU usage is at 99 to 100% constantly. I have a Core 2 Intel Quad 2.2 GHZ CPU, and with 10 clients, I never broke 90% CPU usage. I play with the camera zoomed out to the max, so it's not like there is a lot of problem with rendering a lot of close in detail work. In station, CPU usage drops to 70%, but out in space, it's pinned and stays that way with only 5 clients.

People have lock up and white out issues because of the CPU usage being maxxed out. I was having the same effects and problems, because my CPU was pinned at 100% as well. There just was no more CPU time to process the amount of information needed for multiple clients, and on older machines, even a single client can completely use up all the resources. Nothign has changed on my machine since your patch, this problem is 100% with the way you patched Eve. this isn't a new thing. the exact same problem occurred when you patched in that useless P.O.S. virus you call the unified inventory.

I have friends that all have the same problem whther they're running Vista 64 like me, or Vista 32 bit, or Win 7. Right now, 2 qaccounts are unsubbed because the subscriptions have run out and I have no reason to sub them when I can't use them. I have three others I play with who also let anywhere from 1 to 3 accounts drop for the same reason. I have 2 more accounts coming up that will be unsubbed too. I'm not paying for something you've screwed up. This latest "patch" is already costing you money. If more people do this, maybe you'll actually pay attention to how and what you code, but then, this is just a repeat of fall last year.

At the same time, fix drag and drop, because that doesn't work at all for multiple items. Docking and jumping also doesn't work any more oftne than half the time, if I'm lucky, but that is also a problem that has existed since the useless inventory patch.

Take your time fixing it though. Lots of games to play that actually work ;)

It's not fixed mate. There's been no new patch except for the one a couple of days ago which actually made it worse.

What I'm actually struggling to understand is why is the "patch" that solves this deployed in the test server while people on the live server are getting crashes after crashes every single hour.

CCP has no problem in putting out untested releases but takes it's good ol' time to "test" the fixes for the previous untested and broken release! If I actually worked like this I'd probably be shitcanned when the contract renewal came up.

Sure, everyone fucks up and with so much legacy code and so many people working on the client, it's bound to happen. What's not normal is the sweeping under the rug that happened with this thread (basically, removing the one from GD) and having a couple of devs look at it part time. When a possible fix is good to go, they deploy it to the test server! Can't wrap my head around the double standards in deployments for the client.

EDIT: In case I didn't make my case clear, just put the patch in production (TQ) and let us test it where it's supposed to be used! It can't get any ******* worse than what it is right now!

Yes, I'm aware of that. But if for you that is an acceptable timeline, for me it simply isn't. I'm also a developer. I also work on a client / server application and if the client is this ****** up, we're not "waiting a week" nor are we deploying it on a test server first when the client in production is basically "randomly" freezing!

It's simply stupid to have the fix ready and deployed to the test servers just ... waiting ... for next week ... while all your customers are actually playing with the client that's broken ... while you test the fixed one ... but didn't test the broken one ... :|

Seriously ******* pissed right now as this has been broken for a week or so and it seems there's only a couple of guys working on it ... and don't even have the power to do a TQ client release.

It isn't fixed, in fact, it's worse. I just came off singularity and the "patch" over there is even worse than on tranqulity. The cpu usage is still at 100%, and the singularity client is even more of a memory hog than the one on tranquility. On tranqulity, max ram usage per client is about 720mb. On singularity, client usage is 780 to 800mb, almost 200mb per client more than before the last useless patch! You're going backwards, making things worse.

In standard fashion though, you'll push out this new garbage, and make things worse, anyway.

Go back to the drawing board.

Edit: One thing that is a cpu hog is teh new targetting ui and that rotating crosshair around it. That feature is anywhere from 3 to 5% cpu load, right there. Poor design, and even worse implementation.

Mate, this thread is about the client freezes and not about the resource hog the client is/isn't! I have plenty of resources, the CPU never goes over 10%, each client barely scratches the available ram and the client still freezes so lack of resources is not the issue.

You are indeed talking about something different. You may think the freezes are being caused by the increase in resouce usage but, like I said, it's not the case! I'm not saying it's good or bad for the client to use more resources. I'm just saying that those two issues are NOT related.

If that were the case, my CPU would be burning up too and all of my memory (16gb) would be used. Instead I have 10% cpu usage with 3 clients and less than 3gb of ram used for those 3 clients. Resources, regardless of the new patch requiring more of them, are not the cause for the freezes.

I'm trying to put some emphasize that as I would prefer CCP solve the freezing problems, which is what is being discussed in this thread! My sugestion is that you make a new thread regarding the increase in resources needed for the client, but that's a lost cause, as you'll need more resources for the game to evolve anyway.