Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Rear Commander
|
Posted - 2009.12.03 17:16:00 -
[1]
Edited by: Rear Commander on 03/12/2009 17:18:02
I undocked into hostiles. I didn't move and watched my session time, when it hit zero I spammed approach on the station. Range is reported at 1360 meters. I start spamming dock (which at this range approaches station)
I pulse the MWD, still spamming dock, and easily make it to 0m. I'm still spamming dock. I hit the station, still spamming dock.
"Docking operation already in progress. Estimated time 30 seconds".
I bounce off the station, range is still 0m though, still spamming dock, still can't dock and die and am podded.
I received no gang invites or other player generated session change timers. I didn't lock or shoot anything. I did nothing except approach the station, pulse the mwd and spam dock, inside fock range, after the session undock timer was up. What just happened? Why am I dead?
|
Ancy Denaries
Forever Unbound
|
Posted - 2009.12.03 17:23:00 -
[2]
Sounds like something that should be petitionable.
Also Originally by: Rear Commander inside fock range
was epic. ---- The Demigodess with a Conscience - An EVE IC Blog Personal Killboard |
Lindsay Logan
|
Posted - 2009.12.03 17:26:00 -
[3]
Asking here will not give you answers, petition it.
|
James Tritanius
|
Posted - 2009.12.03 17:28:00 -
[4]
"Docking operation already in progress. Estimated time 30 seconds".
That usually happens when it lags... real bad. Happened to me quite a few times in the past but it usually docks up in 5-10 seconds after that message.
|
Rear Commander
|
Posted - 2009.12.03 17:29:00 -
[5]
I'm asking here because I'm waiting to hear if other people have had this happen or if there is some new hidden timer post-dominion etc.
Basically I'm trying to gather some info, because atm it sounds like total BS to me.
|
Lindsay Logan
|
Posted - 2009.12.03 17:45:00 -
[6]
Originally by: Rear Commander I'm asking here because I'm waiting to hear if other people have had this happen or if there is some new hidden timer post-dominion etc.
Basically I'm trying to gather some info, because atm it sounds like total BS to me.
Thus, we tell you to petition it
|
Lazarann
Mercury Nation House of Mercury
|
Posted - 2009.12.03 17:59:00 -
[7]
This happened to me as well only it was on a stargate. It's been a while, but if remember correctly, your problem is spamming the dock button (I was spamming the jump button). When you see that message "docking in progress etc etc" and continue to spam dock, I believe it keep resetting or something. Either way, that's your problem. Next time just click once or twice and let it happen. I was able to petition my loss and get it back though so you should be able to as well. ---------------- A million faces, each a million lies |
Impolite Andevil
The Shadow Knights
|
Posted - 2009.12.03 20:32:00 -
[8]
Originally by: Rear Commander I'm asking here because I'm waiting to hear if other people have had this happen or if there is some new hidden timer post-dominion etc.
Basically I'm trying to gather some info, because atm it sounds like total BS to me.
That exact scenario has happened to me pre-dominion. It's lag, and it is petitionable.
|
Jovialmadness
|
Posted - 2009.12.03 21:09:00 -
[9]
Lag is not petitionable. Oh can you petition it? Absolutely! Will you get your stuff back? Probably not. "our logs did not show any issues". Being that it's near patch time you might luck out so try it. |
Gavin DeVries
|
Posted - 2009.12.03 21:41:00 -
[10]
I've seen it many many times, just not in combat situations. Quite often when I warp to a station to dock, the warp will drop me 2000 meters or so out. As a general rule it won't dock until I get to less than ~ 400 meters, so I kick on my AB or MWD. It won't dock automatically if I get to <400 meters though; I think it just calculates a time required at max speed before docking, so I click dock again when I get close.
Anytime I click dock, docking starts but doesn't happen, and I click again, I get that message. At a gate the message is "Session change already in progress". At a station it's the one you saw. ______________________________________________________ Isn't it enough to know that I ruined a pony making a gift for you? |
|
Rear Commander
|
Posted - 2009.12.11 14:47:00 -
[11]
Originally by: Gavin DeVries I've seen it many many times, just not in combat situations. Quite often when I warp to a station to dock, the warp will drop me 2000 meters or so out. As a general rule it won't dock until I get to less than ~ 400 meters, so I kick on my AB or MWD. It won't dock automatically if I get to <400 meters though; I think it just calculates a time required at max speed before docking, so I click dock again when I get close.
No. As I clearly state in the OP, drop out AFTER 30 seconds of waiting for session timer was 1360m. And I then reapproached to zero before spamming dock.
Petition response (after a week) was the log shows me trying to redock immediately. What do I tell them GM? Of course the log shows this, THE LOG DOESN'T START until you DO something. Undocking, waiting 30 seconds, and then redocking shows as an insta-dock in the log. And I didn't DO anything for 30 seconds after undock, so it shows me trying to redock less than 4 seconds after the first log entry...
To make sure of that I checked previous combat logs where I burn back to gates and jump out. Under 15 seconds from the first entry in the log, meaning the log doesn't sart until you break your cloak or break your station undock invuln.
But what do I tell a GM who doesn't understand their own logging system and insists that the logs show nothing?
|
Lady Spank
Amarr Sekret Kool Klubb HYDRA RELOADED
|
Posted - 2009.12.11 14:57:00 -
[12]
I've recently been playing on a connection via stolen wifi with horrendous lag and would get that docking issue frequently
Worth a petition.
Originally by: Tirus Sinobi Your response has set your intelligence barrier so low that anything you post from here on that breaches it, will have to be considered posted by somebody else.
|
Siigari Kitawa
Gallente The Aduro Protocol
|
Posted - 2009.12.11 15:02:00 -
[13]
Originally by: Rear Commander
Originally by: Gavin DeVries I've seen it many many times, just not in combat situations. Quite often when I warp to a station to dock, the warp will drop me 2000 meters or so out. As a general rule it won't dock until I get to less than ~ 400 meters, so I kick on my AB or MWD. It won't dock automatically if I get to <400 meters though; I think it just calculates a time required at max speed before docking, so I click dock again when I get close.
No. As I clearly state in the OP, drop out AFTER 30 seconds of waiting for session timer was 1360m. And I then reapproached to zero before spamming dock.
Petition response (after a week) was the log shows me trying to redock immediately. What do I tell them GM? Of course the log shows this, THE LOG DOESN'T START until you DO something. Undocking, waiting 30 seconds, and then redocking shows as an insta-dock in the log. And I didn't DO anything for 30 seconds after undock, so it shows me trying to redock less than 4 seconds after the first log entry...
To make sure of that I checked previous combat logs where I burn back to gates and jump out. Under 15 seconds from the first entry in the log, meaning the log doesn't sart until you break your cloak or break your station undock invuln.
But what do I tell a GM who doesn't understand their own logging system and insists that the logs show nothing?
------------------------------------------------------------ Gamelog Listener: Siigari Kitawa Session started: 2009.12.11 13:38:42 ------------------------------------------------------------ [ 2009.12.11 13:38:49 ] (notify) Ship stopping
No, the gamelog creates itself as soon as the session change timer begins.
When you undocked, a session change timer started. In this above example, I waited 7 seconds after undocking to stop my ship. That means I could not redock for 23 seconds after stopping.
If you attempt to dock before your session change timer is up, that breaks your invulnerability.
|
Rear Commander
|
Posted - 2009.12.11 15:04:00 -
[14]
Edited by: Rear Commander on 11/12/2009 15:04:02
Quote:
No, the gamelog creates itself as soon as the session change timer begins.
When you undocked, a session change timer started. In this above example, I waited 7 seconds after undocking to stop my ship. That means I could not redock for 23 seconds after stopping.
If you attempt to dock before your session change timer is up, that breaks your invulnerability.
No, I'm at work now, but can post examples when I get home.
|
Brent riper
Caldari Night Wolves Deprived of Existence by Mercenaries of the Night
|
Posted - 2009.12.11 15:34:00 -
[15]
Originally by: Rear Commander Edited by: Rear Commander on 11/12/2009 14:48:44
I undocked into hostiles. I didn't move and watched my session time, when it hit zero I spammed approach on the station. Range is reported at 1360 meters. I start spamming dock (which at this range approaches station)
I pulse the MWD, still spamming dock, and easily make it to 0m. I'm still spamming dock. I hit the station, still spamming dock.
"Docking operation already in progress. Estimated time 30 seconds".
I bounce off the station, range is still 0m though, still spamming dock, still can't dock and die and am podded.
I received no gang invites or other player generated session change timers. I didn't lock or shoot anything. I did nothing except approach the station, pulse the mwd and spam dock, inside dock range, after the session undock timer was up. What just happened? Why am I dead?
**UPDATE** Gm quotes that the logs show me trying to redock 4-6 second after undock. However, logs don't start recording entries until you start doing something. So if you wait the full 30 seconds after undocking before trying to redock, your logs show you requesting redock at 1 second. And redocking fine at 1 second I might add...
But what do I tell the GM?
i had the same thing happen to me once well similar i was within perfect docking range repping my alt while killing wt. then it got to hot so degressed waited the timer was still in half armour doing fine tried docing wouldn't dock kept giving me the same answer above. eventually lost that ship and insta docked my main .. odd eh so i sent it as a petition on both chars as reference and got my ship back as it was a game mechanic fail. send simple petition and you should get your stuff back.
AND further more, Carthage must be destroyed!! |
Omara Otawan
|
Posted - 2009.12.11 17:30:00 -
[16]
When I get that message while docking it usually means the connection dropped but client didnt realize it yet.
Did you disconnect a short while later by any chance? |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |