These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Test Server Feedback

 
  • Topic is locked indefinitely.
Previous page12
 

Time Dilation 0%... System Remaps in Future ???

First post
Author
Sleekman
Sebiestor Tribe
Minmatar Republic
#21 - 2011-10-02 01:45:39 UTC
It's not going to dilate with 10 people, you have to reach the point where the server starts to lag before it even thinks about using it, and then it goes up in stages.

Assuming you could lag the system even slightly, it's only going to dilate a fraction before coming back to normal.
GeeShizzle MacCloud
#22 - 2011-10-02 03:11:58 UTC
lol some of the excuses for 'problems' on here are soo absurd! but i like reading them anyhow!

a lot of people seem to be forgetting that because a system might go into TiDi, doesnt mean every1 BUT you will go slow. you will too.
and also places like jita have been purring along at 60%ish server usage for a little while now.. and with optimisation after optimisation thats slowly diminishing. you'd have to do a lot to lag it out... and a HELL of a lot to lag it out in order to really make use of scanners to scan out targets u might not have had the time to consider.

BUUUUT even then u have to contend with the fact locking and scannings gonna take a lot longer, ten every action u want to do after that will take longer still, by that time ur targets just about warped off.


TiDi i believe was initially conceived as a way to make the combat mechanics of eve fair to all on the node, whether uve loaded grid already or not. there were many instances where fights in say 020 and similar, a massive pre-emptive force would get into system early and lag the system out whenever they got word of any possible hostiles jumping in.
Most of the time this meant the ones already on grid had a free turkey shoot, killing people desyncing and trying to load grid.

it ment that if ur taking sov.. u get there early, u lock the system down and if anything moderately expensive jumps in, its dead b4 it even knows about it.
now it seems that the general consensus is that its an abuse of the limitations of the servers. so someone suggested slowing time so that the servers can process ALL requests when theyre made, instead of what we currently have of prioritising combat over grid loading.
Lord Helghast
Center for Advanced Studies
Gallente Federation
#23 - 2011-10-02 03:14:58 UTC  |  Edited by: Lord Helghast
Phantom Slave wrote:
Kagan Storm wrote:
Is it just me or is this scenario possible Somebody test it and feal free to give me the credit :)

Super loogs in. You catch it. It loogs off agreesed.... you dialate time by ungrooping everithing and launching all drones....t ime goes slower for system X lets say 1 sec real time equals 0.5 seconds in game

=========

Now you have 30 min to get reinforsments to kill that super??????????????????

From what i understand everybody in system slows down.
Please confirm. Cool


And usual reason you dont kil la super is cause reinforsments are slow and you dont have enough DPS


Pretty sure that it'd take a few hundred people all with ungrouped mods to even affect the dilation of that node at all, probably closer to nothing, and if there's 300+ people in the system attacking a logofski super I don't think you'll need 30 minutes in the first place.


Not to mention its been pretty well pointed out that the titan/supercarrier logoffski trick is more exploit than real tactic, hence why they have said that titans etc might get an EHP nerf as its rediculous that a titan can just log off at start of battle and those 150 battleships cant kill him cause of a stupid ewarp...

also TIDI to hit 50% requires a LOT of load, and if theres that much load the titan was going down anyway...

TiDi isn't for systems with 50 guys with drones out, its for 500v500 battles and things where the server is truely crushed

Oh no now Supers aren't LogOffsky invulnerable during 1200 player battles poor babies...

What will those alpha fleets do now that only really worked due to lag making alpha the only thing that worked and 0 tactics needed.... wow tactics who would have thought
Lord Helghast
Center for Advanced Studies
Gallente Federation
#24 - 2011-10-02 03:19:32 UTC
Nova Orion wrote:

He does have a valid point though, it will start depending on ppl finding out how to overload the node, like taking drone boats, bringing a lot of warriors for instance, and just launch and abandon. At some point someone will find a way to do that, and they will have a huge advantage when it comes to reinforcements.

Also you can look at it otherwise as well, let's say you field 300v300. Normally the fight would be over before 100s more would come. But now you have maybe 10 times as much time to make it in time (with TiDi 10%) which will further increase the lag. I do believe TiDi can fix a lot of issues, I just hope CCP thinks of everything before enrolling it =)

/Nova



you do realize that 300v300 currently dont lag most nodes right?

and if a 300+v300+ fleet fight is going on and does hit TiDi say 50%... it gives both sides the same advantage of being able to call for reinforcements, unlike is now where 1 side gets advantage... TiDi is BALANCE to massive battles
Messoroz
AQUILA INC
#25 - 2011-10-02 20:43:07 UTC
How do you prevent Time diliation from activating when it shouldn't....i.e. Jita LOL
CCP Habakuk
C C P
C C P Alliance
#26 - 2011-10-02 21:23:58 UTC  |  Edited by: CCP Habakuk
Messoroz wrote:
How do you prevent Time diliation from activating when it shouldn't....i.e. Jita LOL


We can (manually) exclude nodes from Time Dilation, if necessary - for example if a bug causes a huge CPU spike.

For Jita: If Jita gets overloaded because of anybody shooting the statue or some kind of warfare action then Jita should be dilated like any other system. If Jita gets lagged out mostly because of market and inventory transactions then we might need to disable Time Dilation for this node, as these actions are not dilated anyway and the system could be running at 10% speed, while the market is still running at full speed and lagging everything out. This said: Jita is currently in pretty good shape and far from reaching 100% CPU.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing

Previous page12