CCP stop thinking up awesome technical work arounds and fix the #$% game.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

Meh...

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

There is a fix but you all wouldnt be happy with it....

...enforced limit of fleet sizes/encounters/battles.

Your lag would then be fixed.

You shut your mouth.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

From what I've seen it isn't much of a solution, it'd be more cost effective in the long run to give all EVE subscribers free fibre optic connections with the amount of subscription money frankly.

Nullsec whining

and how would that help if you suddenly had 10 fleets?

artifical limits are easily avoided. hard limits = first there win.

OOOOOOOOOOOOH

They can fix it but it would mean there would be a 800 players in local limit with traffic control being enabled to lock the gates.

There's only so much they can do in a given time to optimize the game even more, 1200 players is really alot for it to handle on one grid, all spamming actions, all doing something else, etc.

This is not true. For starters they could STOP USING PYTHON and switch to multithreaded code..

This is not true. For starters they could STOP USING PYTHON and switch to multithreaded code..

Not a programmer so forgive me if I sound stupid but...


Wouldn't they have to rewrite the entire code from scratch if they changed languages? Which would take years?

From what I've seen it isn't much of a solution, it'd be more cost effective in the long run to give all EVE subscribers free fibre optic connections with the amount of subscription money frankly.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

Correct me if i'm wrong but time dilation wasn't created to fix lag..... Time dilation was introduced to make fights fairer under extreme lag conditions. Previously the server would just randomly accept some peoples commands while completely ignoring other peoples. This meant some people were able to fight as if there was nothing wrong whilst other people were completely locked out.

Time dilation was simply a method of slowing everything down so that the server has a fair chance and processing everyone's commands.

and CCP policy about documentation is: "documentation is optional and you do it in your spare time".)

Ooh...bad move. That's like performing surgery and telling the surgeon, stitching is optional...just do it when you get around to it.

Im an proponent of over-documenting code. Makes life much easier.

So you find black loading screens very amusing I take it?
Funny how two seemingly different things can be so unequivocally one and the same. The alternative is that you won't be allowed to be in the fight at all, would you prefer that?

i don't even write code :-D even EASIER

The problem isn't the connection to the servers ... it is the workload the servers are doing that is the bottleneck. CCP would need to invest in Deep Blue style machines to fix lag. They don't have that sort of money.

The problem isn't the connection to the servers ... it is the workload the servers are doing that is the bottleneck. CCP would need to invest in Deep Blue style machines to fix lag. They don't have that sort of money.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

so... did you ask for node reinforcement?

no???

then it's your own fault. Quit whining.

TiDi is working rather well actually.

However, what worries is the amount of TiDi, i.e., how easily the server gets overloaded. 150 jump anywhere in or out... bam, TiDi. If 1400 makes TiDi run at 10-15%, it means the server would only support about 140-210 pilots fighting at full speed (right, it doesn't scale linearly, so it's a bit more). I thought the server(code) was in better shape by now.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

You can't "fix" physics.

CCP should be happy that they can support 300 vs 300 (or whatever a non-reinforced node will support) and put gate locks in place to keep it below that. Spawn bypass gates (or reroute in place gates) to jump people past the fight - allowing reinforcing fleets to engage in nearby systems.

CCP won the epeen award for largest true PvP many-on-many a long time ago at much lower numbers. Enough already. CCP encouraging ever larger massive battles is simply wasting resources that could be used to fix addressable bugs and realistic, usable content.

The only people who say this are those who wernt there or are bitter they try to play on a poor mans PC from 2002. The last two fights have been epic and worked oh so good.

Nope, just tired of hearing about tears of "I was in 500 man fleet and couldn't do ****!" for the past two years.

BTW - don't talk about something you don't have a clue about. Client side has NOTHING to do with your 500vs500 fight lag. It's all server side.

Because its CCP that makes your pooter crash in a big fight. Theres a reason why people say turn down the graphics and turn off brakets in these fights

Nope, just tired of hearing about tears of "I was in 500 man fleet and couldn't do ****!" for the past two years.

BTW - don't talk about something you don't have a clue about. Client side has NOTHING to do with your 500vs500 fight lag. It's all server side.

Because of TiDi being rolled out - I just now experienced TiDi in a 0.0 system with ***17*** people in local. Not a fight to be seen.... yet another broken mechanic brought on by efforts to babysit the monster alliances.

TiDi is node wide. So it might that there was a fight going on some other system on the node?
And fleets (200+) cause tidi to spike to 10% when they jump systems.

TiDi is node wide. So it might that there was a fight going on some other system on the node?
And fleets (200+) cause tidi to spike to 10% when they jump systems.

*snip*

If the server side is drawing brackets CCP implementation is plain stupid. Turning off brackets and turning down graphics does help low-end systems. Still has nothing to do with server lag/freeze/fail.

My experience with TiDi is that it is great for fleet battles but horrible for jumping through gates. Yes it is hard to lock targets, but it is harder to lock targets with a black or frozen screen. TiDi is a step in the right direction. Now, if we could only cut down on the 5 minute stargate jumps (with traffic control) ...

If TiDi is node wide - then the implementation is completely wrong.

If TiDi is node wide - then the implementation is completely wrong.

I've changed my mind about TiDi breaking low populated systems. If TiDi kicks in I know a blob fleet is on its way. Thanks for expanding local!!!

If the node is getting hammered so much that it has to slow the game down to 10% of its normal speed then why should it work any faster on other systems the node is running? It somehow magically gets more cpu time out of thin air to run the other systems on the node?

How could it not be node wide? It's the node that is having trouble handling the requestsGǪ
GǪexcept that node assignment and geography aren't necessarily linked.

Gee, I was able to lock people and the system was down to 10%. Stop whining. Everyone but you thinks time dilation is an excellent solution to reducing the EFFECTS of lag (since there's no way to remove lag completely, stop telling them to "fix the game" when players keep finding new and creative ways to break it)

it's just a matter of where you draw the magical time difference. As far as EVE the universe is concerned some part of it needs to run slower so the entire galaxy doesn't collapse. That can be at the fleet planetary system level, node level (cluster of PS's), or the entire universe (superset). The line should have be drawn at PS's level. CCP implemented it at node level because they can't handle the incoming fleets into the target battle system instead of dynamically adding PS's to the dilation zone as needed (they went with simpler coding). That's what's screwing non-fleet participants over.

Doesn't excuse other problems it is causing...

Now Zleon, with that knowledge and given parameters to work with - how is CCP supposed to just TiDi a single thread on a node which is overloaded?

PS: no, as I said earlier.. they can't pull threads from the node to mildly reinforce it yet, as the pleyers would be disconnected.

GǪsuch as?

Node size + blue/red check + no neutrals allowed in.

The point is is, you can have open-end resource-consuming batltles that may work as best as possible, but not necessarily well, or limited battles assured to work well within their allotted resources.

'Cause the problem is the one thread (or probably at most 3 threads) causing the overload, not the entire node. So dilate the one thread and there you go... there is no reason to hit an entire node with TiDi.

This issue is closely related to design simulations done in the engineering community - time scaling and microtime problems have been worked on for years in EDA. Maybe CCP needs to consult with them.

Like maybe the outbreak of server crashes since the TiDi release? Spreading outbreaks of system lagg reported from all over?

I would suggest if you don't know what you are talking about, don't talk.

Correct me if i'm wrong but time dilation wasn't created to fix lag..... Time dilation was introduced to make fights fairer under extreme lag conditions. Previously the server would just randomly accept some peoples commands while completely ignoring other peoples. This meant some people were able to fight as if there was nothing wrong whilst other people were completely locked out.

Time dilation was simply a method of slowing everything down so that the server has a fair chance and processing everyone's commands.

TiDi is implemented because there does not exist a hardware solution that will handle the computation load and also the time of flight problem across the net.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

*snip*

They are working on those things, just toooo slow. There was a time Market was running on same cpu core as the rest of the system, afaik now there are dedicated market nodes. ...

... Next step would be enabling separate grids to run on different cores and live migration between CPU cores, preferably over the network so they could migrate them between servers and not only between cpus on same machine.
Of course best case scenario would be rewritting "battle code" into something MULTITHREADED so one big battle can use more than one CPU on a Node (nodes are multi CPU, CPUs have HT) dividing load. Calculating distances, misses, damages, movements, it could all be multithreaded and done at the same time instead of doing it in sequence.

please fix lag and combat altogether.

Introduce new Area of Effect weapons, which instantly finishes blobs. If someone blobs and stands still, weapons of mass destruction can hit the centre of the blob and wipe them out.

Pilots will have to think smaller, maneuverable groups.

please fix lag and combat altogether.

Introduce new Area of Effect weapons, which instantly finishes blobs. If someone blobs and stands still, weapons of mass destruction can hit the centre of the blob and wipe them out.

Pilots will have to think smaller, maneuverable groups.

Also, they should be able to be fired through cynos.

Currently fighting in 92D. 1260 in local and dilation is so bad I cant lock anything.

Dilation is FAIL. This is NOT fun and simply not worth participating in big fleet PvP anymore.

CCP stop thinking up awesome technical work arounds and fix the #$% game.

Gee, I was able to lock people and the system was down to 10%. Stop whining. Everyone but you thinks time dilation is an excellent solution to reducing the EFFECTS of lag (since there's no way to remove lag completely, stop telling them to "fix the game" when players keep finding new and creative ways to break it)