Forums » Bugs

Unable to Jump.

Aug 17, 2004 RattMann link
I was killing bots and needed repair. Hit the "N" key for Nav Screen, selected
the sector I wanted to go to (Divinia D-6), waited for "Nearest Large Object
>3000m" (in green), clicked on "jump" and was returned to the sector I was trying to get out of. HUD showed "Ready to Jump." Nothing happened. I tried
it seven more times with the same result, that is: NOTHING. Had to use
"ESC-Exit" to recover.

Bug Report Filed.

[Edit] Just started to log back in. Noticed that I have another "death" credited to me. I did NOT die in the above mentioned process, and should not have one charged to me. What the HECK????
Aug 17, 2004 paedric link
It sounds (to me) like you where killed by the bots while using your nav screen in hostile territiory. Were you turboing away at 200m at the time you where using the nav screen or where you using your sub warp engines to cruise at 65m? This is a new one on me.
Aug 17, 2004 Eldrad link
It sounds to me like you lost your connection to the server (a bug which seems to be happening sometimes) and during that time the bots were still moving and you were sitting still since the server was receiving no information from you.
Aug 17, 2004 RattMann link
I was at full turbo speed (200m) when this occurred. I made eight attempts at a
"jump" during this event. Each time I clicked the jump button, the normal sector
view came back on-screen, and the message "ready to jump" was displayed. This
is how I knew how many tries I made. I was way out in "open" space at the time
and there were no "blips" on radar.

Lost connection to server? Makes some sense, but where do the "ready to jump'
messages come from? The client or the server?
Aug 17, 2004 roguelazer link
Ready to jump was what it displayed when jumping had a timer...
Aug 17, 2004 Eldrad link
The ready to jump is what is displayed after the timer finishes counting down (which is instantly at the moment). It's client side (though you would jump if the server didn't think you were ready).
Aug 17, 2004 a1k0n link
Right. It takes a full minute of non-responsiveness from the server for your client to abort; in the meantime, your client just kind of drifts on its own. This is almost certainly what happened -- some Internet outage between you and the server occurred; you lost control of your ship, but a bot could still see you and kill you.

Maybe a 'disconnection warning' icon on the screen after a few seconds of network inactivity would be a good idea.

We've been having some occasional short network outages at the office here. Our server is not in a colocation facility and hasn't been for a while. Once the new facility is ready, we can expect much better uptimes.
Aug 18, 2004 CIPOBO link
Actualy im unable to jump to Jallik (system 13) F-2. Same to Dantia (system 30) J-2. All systems from 1 to 12 are locked this way.
Aug 18, 2004 RattMann link
Had another occurance of this today. It is/was a loss of connection to the server.
No doubt about it...
Aug 18, 2004 a1k0n link
Being stuck in a loading screen trying to jump to a particular sector is a different problem. I haven't figured out why it's doing this yet.
Aug 19, 2004 a1k0n link
Hmm. There's yet another problem; sectors with storms seem to crash. This started right after we brought the server online in its new location.. very strange.
Aug 21, 2004 raybondo link
crashing clients and sectors should be fixed now.