EVE General Discussion

The logs showed something!!!!


Glad to hear it though.

Dear GM, introduce POD catapult. Leave ship behind - new incentive to eject early.

+1

however petitioning wont get you your isk back.. unless there is actually a problem. People should die if they dont know how to save there pod in low/null without bubble. however if someone has a problem that is legit then petitions and bug reports should be sent. your perfect world scenario doesnt always exist.. especially in eve.

That was just punishment because you are bad, and should feel bad.

Petitions have nothing to do with lawyering. If the logs show an error you get reimbursed. If not you don't. What Ferguson seems to fail to realize is that even people who don't "choke" often still get podded due to the internet not being instantaneous in its communications.

It may be that due to his internet provider or his location he has always gotten his pod out absent a bubble or smarty but for others that is not the case. In eve how good your internet connection is will have a large impact on how competive you will be. People can look at stats or whatever you want but a *very* significant aspect of the game has nothing to do with choking or not choking. It has to do with your internet provider.

That is why Jack dents proposal here:
https://forums.eveonline.com/default.aspx?g=posts&m=491606#post491606

That pods be given time to warp out is not a scrub suggestion. Its a suggestion from someone who understands that the internet is not "instantaneous" so making mechanics based on the assumption that they are, is stupid.

Electric signals in copper wire propagate at roughly 2/3c, depending on how crappy your cabling is.

Optic signals in fibre cable propagate at speed s with s < c since while the carrier wave itself may travel at c, it does not travel down the fibre in a straight line, but gets constantly refracted at the outer edges of the fibre ("bounces between them"). So the distance inside the fibre is actually longer than the fibre itself resulting in signal propagation speeds below the speed of the carrier wave.

You are correct that "ping" does not measure speed but round-trip time. But, in the absence of anycast setups, usually time to a relatively fixed destination. If now the routing path stays the same you have time and a rough idea of the distance to the destination (if you actually know the destination's location; also distance here is not length of the traveled path), thus speed in a distance per unit of time sense. An information transmission speed though, not physical signal propagation speed.


In practice this is largely irrelevant though, since icmp echo is, due to small packet sizes and the protocol design, less affected by differences in the deployed switching technologies along its path, has no retransmission delays, congestion control algorithms, uneven endpoint support of things like selective acks, various fragment reassemblies along the path or window scaling problems on the endpoints.

There are myriads of possibilities why your echo RTT can be good, but the time it takes your application to successfully transmit a specific amount of information down what you perceive to be the same path via TCP very bad.

Game clients are much like interactive shells tough and not bulk transfers, so a bad baseline RTT which can be established via "pings" can dramatically increase the subjective unresponsiveness of the application.

I never used to get podded, I could always escape. Since crucible I've been getting podded loads. On every occasion the UI was telling me I was actually in Warp.

I did petition all this, but I was told the records couldn't prove anything either way. I just assumed I was sucking more, but now this thread makes me think again.

Wow. You really like your name bunches.

Soooooo, much speculation and guessing as far as whether anything changed, whether something changed that could have affected the warp mechanics, etc.

Dev response?... No? It would actually help, you know.