You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have on numerous occasions achieved warp at a 45+ deg angle. This is most prevalent on massive ships such as an Orca, Rorqual, Charon. This happens most often after warping to a location and not decelerating properly (see #38 , #80)
In my latest case, when the Rorqual approached my Hulk and her jetcan, on the Hulk's screen, the Rorqual got bumped by the can, and started spinning in place, as where on the Rorqual's screen, I came to a complete stop. It's likely that the server and client disagreed as to my orientation when clicked warp to the station, and so it appears on the client that I'm warping sideways. This probably only noticeable on huge ships because smaller ships don't take half a minute to align...
The text was updated successfully, but these errors were encountered:
there was a dev blog years ago that mentioned this.
ships dont have a "front", as they are just a sphere, and the dev was discussing times when he was writing/testing where the ship would begin movement sideways or backwards.
i will look into it more as i begin work on large ships again.
no current eta.
I have on numerous occasions achieved warp at a 45+ deg angle. This is most prevalent on massive ships such as an Orca, Rorqual, Charon. This happens most often after warping to a location and not decelerating properly (see #38 , #80)
In my latest case, when the Rorqual approached my Hulk and her jetcan, on the Hulk's screen, the Rorqual got bumped by the can, and started spinning in place, as where on the Rorqual's screen, I came to a complete stop. It's likely that the server and client disagreed as to my orientation when clicked warp to the station, and so it appears on the client that I'm warping sideways. This probably only noticeable on huge ships because smaller ships don't take half a minute to align...
The text was updated successfully, but these errors were encountered: