EVE Information Portal

All I am saying is enforce limits at a level that keeps it just under the node's ability.

-or-

Force blobs to split up with mechanics and spread the load. Have the number of guns shooting a target effect tracking and missile damage (with a max effective dps on the target being proportional to sig radius).

Basicly, fix the problem at the source.

I never have planned that and I continue to not plan that. Where'd you get the idea that I ever did plan to do that?

90% means 10 RL seconds = 9 in game seconds.

TiDi amount = ( In game seconds ) / ( RL seconds )

A values I call Gamma, after the term used in Relativity.

CCP Veritas: Really liked the test. On seeing the "slowed camera" I find its fine the way it is. I expected something much worse. But if you slow time below 10% I would leave the camera at the 10% level.

I see, thanks.

The "source" of the problem is Us - The players.

You cannot stop us blobbing in a system by artificially limiting numbers in the system because we will find ways to exploit this by

• Stacking those numbers in our favour by filling the system with our bigger blob before you are ready -or-
• If the attacker and defender numbers are balanced by CCP to be say 400v400, then you can forget 3 way fights, surprise hot drops, and having that hidden subcap fleet one titan bridge away.

You cannot force us to split up by using multiple simultaneous objective because you will hand a massive advantage to the defenders. Why ...

• If the attacker must complete all objectives the defender needs only to defend at one point -or-
• If the attacker must complete the majority ( say 3 out of 5), Attacker must attack 5 times, defender must defend only 3 times.

Its easy to SAY "fix the problem at source". I don't like "blobbing" any more than you do, but its a reality of Eve. I also, probably like you, really really HATE the completely FUBARed chaos that is an overloaded node.

Yes, TiDi is a compromise, but please stop whining about how you don't want it because you will only accept your own version of a "perfect" solution.

This seems like a technically-sound temporary improvement to a permanent problem. Cheers, CCP. However, disguising system/client/node lag with a spiffy 'EVE physics' excuse seems like a cup-and-ball game to me.

I hope CCP continues to work towards additional optimizations which would, ideally, replace this workaround in the future.

When you showed the slowed down panning in the video the fps seemed to be tied to the simulation speed factor. Sure, scene complexity also pushes down the client fps, but this looked heavier than what I'm used to (the largest battle of eve: I was there), but it might just be that your machine is weak

Perhaps this has been asked already, but from your simulations Veritas what can we expect with regards to overall fleet fight time? If one of the goals of time-dilation is to preserve game mechanics, will that possibly have the effect of reducing the net fleet fight time, or will it increase it regardless?

For example, will the ability to properly control weapons result in killing the enemy fleet more effectively, thus reducing lag and the time-dilation amount, with a net reduction in the fleet fight time despite the time added by time-dilation? Hope that made sense.

I just want to know if CCP pays GeeShizzle, or does his fan boi love for them goes so deep he can't see them spoon-feeding us bull**** and trying to pass it off in the name of innovation. "Oh hai, we make camera choppy and turn a circle from green to red, you're all welcome!!! Want monocle now for $10??"

i was on about the idea on the old forums ur championing, the only way you would be able to forcefully take sov, is sort of the waay its still done now. You'd need to lag a system out quickly to discourage defenders trying to defend, best way ive seen something do that is by blobing supers, so you'd pump supers into a system early before any timers come out, regardless of their HP.
Logging in and undocking is still kind of jumping into a system and trying to load grid.. so the aggressors could kill anything desyncing.

then after the defenders call it quits/decide theres no point loosing more ships due to the server lagging out, the aggressors start raping through the low HP structures with the 100's of supers they'll have in system

High HP structures werent the reason super blobs rose to being used soo often. primarily it was to discourage defenders from trying to defend by making it more than likely, any shiney ships they use to defend, will more than likely not load grid or desync and die needlessly before accounting for any form of defence.