EVE General Discussion

I went into some detail in my second post in the thread, on page 1.

The short answer is that there are some smaller problems they can tackle that will shift 40-50% of the the work to another core before they stare at the daunting project of trying to multithread the physics engine itself--which might only even be possible if they make some changes to EVE's physics, I don't know.

The EVE engine has two steps: 1) calculate everything; 2) update everyone involved with the results of the calculations. The hope is that 1 and 2 can run on different cores, with 1 calling 2 asynchronously, because step 2 can take a surprisingly long time.

You f*cling ignorant ret*rd bastard, come up with a system that can effectively handle 4000 people fighting by yourself, or go home and stop whining.

I posted this in another thread, but it seems relevant:

What I think should be done, personally, (and again, I don't know how feasible this is), is for TiDi to be a region-wide "resource redistribution". Basically if system x of region y has 4000 people in it, all the other systems in the region dilate (in an inverse relationship to how many people are in the system, so a system with 0-5 players in it will dilate to a greater extent than a neighboring system with 100 people in it) in order for the server to allocate additional computing power to system x. System x might still dilate, but instead of dilating to 10%, maybe it would only dilate to say 50%, where the game is at least still reasonably playable and enjoyable. This also has various "meta-benefits", in that it allows one side to still reap the benefits of "surprise" (instead, under the current TiDi system, those advantages are lost because while only 1 minute might pass by in a dilated system, 30 minutes would go by in the neighboring systems giving the side that was taken by surprise ample time to bring in a fleet of reinforcements and neuter the effects of being caught with your pants down) because not only will the dilation not be quite as severe (hopefully) but the entire region will be, in effect, "locked down" making travel and thus reinforcement difficult, if not impossible. This shouldn't be an issue to two fleets in a pitched battle where both sides know whats coming, since the systems in which the two sides form up in shouldn't be hit by the dilation quite as hard and making the 1-2 jumps to the battlezone wouldn't be as severe as traveling from the other end of a region or even a neighboring region. This also means that the side thats better prepared and organized for the fight (taking the effects of the dilation into account) is at a better advantage which introduces a new element of skill or whatever that will need to be taken into account during war time, rather than which side can out-dps or out-tank the opposition. Basically, it creates a more tangible "high ground" in space, the side that outmaneuvers the other and engages on its own terms at the location of its choosing will be at a greater advantage if it can leverage the distance the other side would have to travel to reinforce its fleet against itself.

And if you think about it, generally half the galaxy is sitting more or less empty, I don't know what the server infrastructure is like, but if half the systems in say... Geminate are empty (or something close to it), is it really worth allocating a full load of processing power to making sure that system is functioning smoothly? If you distributed TiDi galaxy wide, the entire galaxy might dilate to 90% (which most people probably wouldn't notice) but perhaps System X would be running at 90% instead of 10%. I heard they allocated the Jita super-node or whatever to the fight the other day to try to speed things up (which really just slowed down Jita) so I suppose this is theoretically possible, though I think given the amount of people in Jita at any given time they should probably never do that one again lol. Maybe the answer is having a spare super-node or two just for when these sorts of fights pop up that aren't really used otherwise?

My .02 ISK anyway.

That doesn't have any part of what I've been saying. So whereas you might be clear in your communications to the OP, I am not him.

Therefore I cannot answer your questions for him, because well, I don't share that view.

Sounds pretty clear to me.

To clarify my statements, TiDi is a good solution for disconnects of heavily overloaded servers, but not a solution for lag (as lag still happens, by design!) and that I do not think TiDi as a final solution is ideal.

I also am confident enough to warrant that even CCP knows the inherent problems of TiDi affecting others not involved with the fight (due to being node wide not system wide) because I too have read the dev blogs from 2 years ago.

As it is a before and after, it honestly wouldn't matter if CCP doesn't do anything about their cap limits and general performance because Eve is growing and CCP needs to accomodate that growth.

Whether you are blackscreened for 20minutes, or take 20minutes to see a module activate, it's still taking 20minutes for a 1second command and it only becomes a matter of choosing a lesser evil.

If I were to be in a WH or another system not related to "your" fight and be affected by TiDi.. I would rather have you disconnect and lag out then me get affected by TiDi. If you don't like the way I answer choices, don't give me choices.

When you base an analogy off of a bad concept, you end up with a bad analogy. Allow me to demonstrate.

If a wealthy person spreads his wealth equally amongst the family, instead of focusing on his wife alone, this is a net win; as opposed to him addressing the root of the issue and not being wealthy? Did I get that about right?

Feel free to continue with the bad justifications to a shameless self promotion.

That's correct. Statistically, TiDi will decrease the time it takes for your gun to cycle. Excess server load is what causes the delay.

You're confusing the thermometer with the fever

I think you are just trying to think of "lag" as some taboo thing.

It's just an adjective for "delay".

When you want to use the word "lag" use "delay" instead and see how that applies.

No. He asked the OP's question and wanted to hear your answer to it.

You know, you could do with trying read what people write more carefully and stop putting words in their mouths…

Not in the context of networking and online gaming, no.

And I already spoke to saying I do not share that viewpoint. It was after it was already answered you kicked in.

And you should take your own advice. It isn't your discussion. It isn't your question, and it sure as hell isn't your answer.