open All Channels
seplocked EVE General Discussion
blankseplocked 30 second delay while gating ?
 
This thread is older than 90 days and has been locked due to inactivity.


 
Author Topic

Steno
The Department of Justice
Posted - 2005.01.13 19:05:00 - [1]
 

Occasionally while flying across the great expanse of eve you will try to jump at a stargate, however instead of jumping you get a message:

"your ship sensors are still tuning in on subspace frequencies. Estimated time left:30 seconds."

I was told this was lag, however, it is not lag and i can reproduce it every time. When you come out of warp near a gate (using an instajump) you slow down and stop but if your readout still says "warping" when you try to jump you get that message and a 30 second delay penalty.

I dont see a reason for it. To me this would follow the same reasoning as activating a missile launcher before I have lock and geting a 60 second delay after I finally lock before I can fire the weapon.


So what is the use of this penalty? Yes, i've adapted, having gotten much more cautious of when i push jump button. But why is this penalty/feature here?

Elve Sorrow
Amarr
Celestial Apocalypse
Posted - 2005.01.13 19:09:00 - [2]
 

Otherwise you get stuck, and you have to petition to get back ingame. So basicly, a crap fix to faulty coding.

Steno
The Department of Justice
Posted - 2005.01.13 19:14:00 - [3]
 

very bad "fix". i can currently use an instajump and if i actually watch the readout for the .5 seconds i can jump but if i accidentally jump too early i am penalized 30 seconds. very stupid "fix" in my humble and non programmer opinion

Piscis
Gallente
0utbreak
Outbreak.
Posted - 2005.01.13 19:39:00 - [4]
 

Edited by: Piscis on 13/01/2005 19:39:01
Originally by: Elve Sorrow
Otherwise you get stuck, and you have to petition to get back ingame. So basicly, a crap fix to faulty coding.


*snip* - until you are a profesional programmer that has worked on a project with such complexities that the eve universe shows. It's not a case of crap programming, it's a case of complicated programming. Yes, they could probably program it so that it didn't do that - but that takes time, both man hours, and cpu cycles. To have everything synced perfectly in a game of this size and complexity is really a mammoth task. It would take a fair few hours to properly sync the jump cycle. Why do that, when there are much more pressing bugs?

It's not like instas are direct game mechanic. CCP never intended them to be used like this. Anyway, just use the autopilot when you've started warping to the insta. It activates the jump as soon as it is safe to do so. Rant over.

Edited, be friendly - Wrangler

agrizla
Posted - 2005.01.13 19:45:00 - [5]
 

Originally by: Steno
i can currently use an instajump and if i actually watch the readout for the .5 seconds i can jump but if i accidentally jump too early i am penalized 30 seconds


Just turn the autopilot on as you're coming out of warp then you won't get stuck - turn it off as soon as it says "jumping to...." and you're all set to go again in the next system.

Apologies to the people who have read this 15 million times Razz - if the forums weren't such a pile of archaic junk and had a search function I'm sure we wouldn't see all this coming up again and again and again .......

Maya Rkell
Third Grade Ergonomics
Posted - 2005.01.13 19:59:00 - [6]
 

Rather have em fix jumps than ANYTHING else.

Dirtball
PinK Tac0 ReasearcH
Posted - 2005.01.13 20:46:00 - [7]
 

Edited by: Dirtball on 13/01/2005 20:47:18
I'm not sure of the complexities involved but in other mmo's you can change your weapons and some even armor while fighting, but in EVE you have to wait 20 seconds or however long while you're docked in the station not engaged in any type of fighting to simply switch ships.

w0rmy
Destructive Influence
Posted - 2005.01.13 22:35:00 - [8]
 

Originally by: Piscis
until you are a profesional programmer that has worked on a project with such complexities that the eve universe shows. It's not a case of crap programming, it's a case of complicated programming. Yes, they could probably program it so that it didn't do that - but that takes time, both man hours, and cpu cycles. To have everything synced perfectly in a game of this size and complexity is really a mammoth task. It would take a fair few hours to properly sync the jump cycle. Why do that, when there are much more pressing bugs?


Blah blah blah blah blah blah blah....

Its not like you have any more of an idea as to the code in EVE than he does.


Steno
The Department of Justice
Posted - 2005.01.14 01:58:00 - [9]
 

Originally by: Piscis
Edited by: Piscis on 13/01/2005 19:39:01
Originally by: Elve Sorrow
Otherwise you get stuck, and you have to petition to get back ingame. So basicly, a crap fix to faulty coding.


*snip* - until you are a profesional programmer that has worked on a project with such complexities that the eve universe shows. It's not a case of crap programming, it's a case of complicated programming. Yes, they could probably program it so that it didn't do that - but that takes time, both man hours, and cpu cycles. To have everything synced perfectly in a game of this size and complexity is really a mammoth task. It would take a fair few hours to properly sync the jump cycle. Why do that, when there are much more pressing bugs?

It's not like instas are direct game mechanic. CCP never intended them to be used like this. Anyway, just use the autopilot when you've started warping to the insta. It activates the jump as soon as it is safe to do so. Rant over.

Edited, be friendly - Wrangler


more pressing bugs... yes there are many bugs... but i'd say that being killed in the game because of extremely poor mechanics is in extreme poor thought. leaving me sitting at a gate for 30 seconds of penalty for something someone though was an easy codeing solution instead of an actual fix. i'm being punished for in essence for something that is more than a bug, but instead a lazy mans fix to a serious problem

theRaptor
Caldari
Tactical Operations
Posted - 2005.01.14 03:38:00 - [10]
 

Originally by: Dirtball
Edited by: Dirtball on 13/01/2005 20:47:18
I'm not sure of the complexities involved but in other mmo's you can change your weapons and some even armor while fighting, but in EVE you have to wait 20 seconds or however long while you're docked in the station not engaged in any type of fighting to simply switch ships.


"Quick Throgrim distract the Ogre of +2 hurtiness while I get out of this chain and into some plate"Laughing

Albus
Reikoku
Band of Brothers
Posted - 2005.01.14 09:45:00 - [11]
 

I would have thought the most sensible option would be not to have the "Jump" command available until you have completely left warp, in much the same way that the "Scoop to drone bay" command is not available until all your drones are in range and the "Warp to " commands are not available if you're already in warp. That way there is no chance that you can try to jump too early.

Alternatively, change the code so the 30 second session change timer isn't activated unless you successfully jump, whereas at the moment it seems to be activated whenever you try to jump, even if the game won't actually let you do so at that point.

SwitchBl4d3
Heretic Army
Posted - 2005.01.14 09:49:00 - [12]
 

you wait till the speedometer starts dropping then click jump.

Lucre
STK Scientific
Black-Out
Posted - 2005.01.14 12:58:00 - [13]
 

Originally by: Dirtball
I'm not sure of the complexities involved but in other mmo's you can change your weapons and some even armor while fighting, but in EVE you have to wait 20 seconds or however long while you're docked in the station not engaged in any type of fighting to simply switch ships.

I must confess this bugs and puzzles me.

Okay, I can see that putting a session change timer on jumping might fix the problem of people getting stuck on jump. I've got stuck and had to petition often enough to appreciate that, even if the fix has its flaws too.

But why do we have similar timers on switching ships after docking? Or on interracting with a gang? Or on ejecting from your ship? I can't recall any of these ever making me 'stuck', so what purpose do these other timers serve?

I'd like to believe there was a reason for these - but I really wish someone at CCP would tell us what it was!


 

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only