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

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

Wormholes

 
  • Topic is locked indefinitely.
 

HS's bugged or random is random?
Author
Previous Topic Next Topic
joes Bazooka
Doomheim
#1 - 2012-07-11 11:32:34 UTC
Look this isn't an issue i would complain about... but i have had this happen before where an old BM of a Wh exit has been the new exit the next day and now for the last six days straight our HS exit has been at the exact same BM and beginning of a natural cycle every time? And always a new HS location.

Anyone else getting this? or should we be happy with it for as long as it lasts.
Vassal Zeren
University of Caille
Gallente Federation
#2 - 2012-07-11 12:13:17 UTC
joes Bazooka wrote:
Look this isn't an issue i would complain about... but i have had this happen before where an old BM of a Wh exit has been the new exit the next day and now for the last six days straight our HS exit has been at the exact same BM and beginning of a natural cycle every time? And always a new HS location.

Anyone else getting this? or should we be happy with it for as long as it lasts.



Yes, I was actually going to make my own post about just this. It's happened to me twice now. Weird huh?

Theory: Whs spawn in a bunch of set locations and sometimes it spawns in the same one twice. either that or the algorithm is simple enough to allow the occational location to be the same.

A bad analogy is like a leaky screwdriver.
Rroff
Antagonistic Tendencies
#3 - 2012-07-11 12:23:12 UTC  |  Edited by: Rroff
I've found that if:

Your previous static wormhole has expired (since the last person left the system).
Your the first person to login/load within your system after downtime
You warp immediatly to the previous static wormhole bookmark soon after logging in

Theres a high chance that the new static will spawn at that bookmark - not sure why but I've been able to reproduce it where 4 days in a row it spawned like that at the same place but the 5th day it spawned elsewhere but I think on that day I wasn't the first person to load the system.
Kalel Nimrott
Caldari Provisions
#4 - 2012-07-11 12:24:38 UTC
Sometimes i get that bug were you get the static by duplicate. Weird.

Bob Artis, you will be missed.

O7
joes Bazooka
Doomheim
#5 - 2012-07-11 12:25:48 UTC
Rroff wrote:
I've found that if:

Your previous static wormhole has expired
Your the first person to login/load within your system after downtime
You warp immediatly to the previous static wormhole bookmark soon after logging in

Theres a high chance that the new static will spawn at that bookmark - not sure why but I've been able to reproduce it where 4 days in a row it spawned like that at the same place but the 5th day it spawned elsewhere but I think on that day I wasn't the first person to load the system.


Your set of variables have been the same in my situation so perhaps its just one set way it loads? dunno but i'm going to try for 7 straight.
Rroff
Antagonistic Tendencies
#6 - 2012-07-11 12:27:24 UTC  |  Edited by: Rroff
I updated my post slightly - I'm not 100% but I think the previous wormhole has to expire after the last person has left the system and then no one else come in again until after downtime. That next person that comes into the system after the previous one expires HAS to both load the system AFTER downtime and warp to the previous bookmark within a few minutes of loading the system or it doesn't produce this effect.
Tarunik Raqalth'Qui
Native Freshfood
Minmatar Republic
#7 - 2012-07-11 16:34:35 UTC
Kalel Nimrott wrote:
Sometimes i get that bug were you get the static by duplicate. Weird.

If you mean two wormholes in C2 space, both with the type of your W-space static, that's not a bug. That 'extra' hole is basically the C2-space equivalent of a wandering wormhole (some suspect them to be constellation-level statics, even).
Messoroz
AQUILA INC
Verge of Collapse
#8 - 2012-07-12 01:26:46 UTC
https://bugs.eveonline.com

You can even mark it as a exploit because if you can actually reproduce it, you can selectively force your static to be what you want after finding a desired connection.
Kaivaja
State War Academy
Caldari State
#9 - 2012-07-14 02:17:08 UTC
joes Bazooka wrote:
Look this isn't an issue i would complain about... but i have had this happen before where an old BM of a Wh exit has been the new exit the next day and now for the last six days straight our HS exit has been at the exact same BM and beginning of a natural cycle every time? And always a new HS location.

Anyone else getting this? or should we be happy with it for as long as it lasts.

It seems that if the wh expires while the server is down (normal downtime or patch deployment or something similar), the new wh will spawn in the same location. Bug or feature? I don't know, but it seems to be repeatable.
joes Bazooka
Doomheim
#10 - 2012-07-14 02:19:59 UTC
Kaivaja wrote:
joes Bazooka wrote:
Look this isn't an issue i would complain about... but i have had this happen before where an old BM of a Wh exit has been the new exit the next day and now for the last six days straight our HS exit has been at the exact same BM and beginning of a natural cycle every time? And always a new HS location.

Anyone else getting this? or should we be happy with it for as long as it lasts.

It seems that if the wh expires while the server is down (normal downtime or patch deployment or something similar), the new wh will spawn in the same location. Bug or feature? I don't know, but it seems to be repeatable.



I don't get how that is repeatable? Every static i have had has always lasted 24 hours and 20mins, don't know why the 20mins but they do.

I know this because it can be quite a pain waiting that out.
trevormax
Deep Core Mining Inc.
Caldari State
#11 - 2012-07-15 11:06:44 UTC
joes Bazooka wrote:
Kaivaja wrote:
joes Bazooka wrote:
Look this isn't an issue i would complain about... but i have had this happen before where an old BM of a Wh exit has been the new exit the next day and now for the last six days straight our HS exit has been at the exact same BM and beginning of a natural cycle every time? And always a new HS location.

Anyone else getting this? or should we be happy with it for as long as it lasts.

It seems that if the wh expires while the server is down (normal downtime or patch deployment or something similar), the new wh will spawn in the same location. Bug or feature? I don't know, but it seems to be repeatable.



I don't get how that is repeatable? Every static i have had has always lasted 24 hours and 20mins, don't know why the 20mins but they do.

I know this because it can be quite a pain waiting that out.


I believe the extra 20 min is because of downtime.
Rroff
Antagonistic Tendencies
#12 - 2012-07-15 12:54:35 UTC
Messoroz wrote:
https://bugs.eveonline.com

You can even mark it as a exploit because if you can actually reproduce it, you can selectively force your static to be what you want after finding a desired connection.


Can't force it to connect to something specific, just make it so the static WH in your system spawns in the same location in the system as the previous one - the k162 side still works within the normal mechanics.

Its not 100% reproduceable so I'm not entirely sure what factors control it happening but it is quite often reproduceable with the same steps.
joes Bazooka
Doomheim
#13 - 2012-07-15 22:35:08 UTC
Rroff wrote:
Messoroz wrote:
https://bugs.eveonline.com

You can even mark it as a exploit because if you can actually reproduce it, you can selectively force your static to be what you want after finding a desired connection.


Can't force it to connect to something specific, just make it so the static WH in your system spawns in the same location in the system as the previous one - the k162 side still works within the normal mechanics.

Its not 100% reproduceable so I'm not entirely sure what factors control it happening but it is quite often reproduceable with the same steps.



Can confirm i didn't get it to work for the 7th day but the new variable in this was that i logged on before the static expired and all previous times i logged on after the static would have expired then warped to it and it was a new static.

So perhaps it needs the system to be clear from DT to the expiration of the static for it to appear in the same location inside the WH.
jonnykefka
Adhocracy Incorporated
Adhocracy
#14 - 2012-07-18 12:39:07 UTC
I've replicated exactly this on Sisi with a U210.
Daneel Trevize
Give my 11percent back
#15 - 2012-07-18 19:43:53 UTC
In relation to that extra 20mins on a 24h hole, apparently due to DT's duration: could this be because DT is now done via TiDiing the whole cluster to 0%? Perhaps this change to the way the whole sim is paused and resumed is causing the issue (assuming it's an issue and not just how things always were, given variance)?