I constructed two teleporter locations - one at the surface of the planet, and one at the top of a space ladder. The idea was instead of riding an elevator for 5 minutes, I could just beam back and forth. Pad A is on the surface. Pad B is 400m up above the surface. But also: pad A is a docked entity, and pad B is a docked entity. So essentially they are docked ships to try to get around the whole "shields drop when teleporting" bit... I can teleport to Pad A from Pad B. Then from Pad A back to Pad B, but then I can't go back. I double-checked my destination pad, hit activate, and nothing. No beaming. I also can no longer interact with any blocks around me - I can add blocks, but can't manipulate or remove anything. I logoff and quit game. I log back in and I'm floating in space 1000 or so meters away from where I should be. But once I travel back, I can manipulate the blocks again where I was previously trying. I can beam again. But once I go back and forth one full time, Pad B ceases to function again, and I have to repeat logging off, flying back, and continuing.
Description
Details
- Task Type
- Bug
- Affected Gamemode(s)
- Multiplayer
- Reproducible
- uncertain
- Last tested (version)
- 0.19485 (Dev)
- Category
- Control Block System: Systems
- First occurrence (version)
- 0.19476
- OS-Specific
- No
- Hardware-Specific
- No
- Video Card Vendor
- uncertain
- Username/Profile on Steam
- major_payne
<replace this line with the file content>
<replace this line with the file content>
Event Timeline
Hello
on what server is this happening?
is the part in Space over the Planet to which the receiving pad is docked a direct part of the planet ?
if yes, it is 400 blocks above the planet surface (approx.) ?
it always works once in both ways after relogging ?
how long did you wait between activations ?
This is happening on an Ubuntu Linux 64-bit server. The video will show you beaming from a docked platform on the planet, to a docked platform ~400m above. Both pads are technically docked to the planet. It always works the first time going pad a, to pad b, then back to pad a, but then stops functioning. The video shows me beaming from pad a, to pad b, removing blocks (successfully), then beaming back to pad a, then I cannot remove any blocks and the pad also will not function to let me transport.
If I enter a build block, I can manipulate blocks on the planet's structure. When I exit the build block, I still cannot manipulate anything in person. If I enter a ship core, then exit the ship core, I can now manipulate blocks again and use the transporter for a back-and-forth trip before the cycle repeats itself.
ah .. ok .. now i get it ^^
as you already have a setup for that, please try one last thing
make sure you are in gravity and alignet to the planet after you come back from Pad b to Pad a and not to pad a. and check for interaction again then.
if that isnt working either i am going to test and forward it
You'll notice in the new video posted:
I spawn in space because the last logout I had just transported and I could no longer transport or affect blocks. So I clipped out my transit time back to the planet's surface.
So I checked my alignment with the planet, and transported to pad b. I checked my alignment/gravity and altered blocks, then transported back to pad a. I can no longer alter blocks. I check my alignment/gravity. Try transporting to pad b, and a ship's pad, and no-go. I then spawn a ship core, enter, and exit, check alignment, and now I can edit blocks and transport. But now you'll notice I still cannot edit blocks after only transporting one time. So I spawn another core, enter, exit, align, and now I can edit and transport again. Once I beam back to pad a, I can't edit anything, so I hop in the ship core and out again, and now I can edit/transport. So it at first appeared to be every cycle of pad a > pad b > pad a, but it appears that it can happen after only pad a > pad b, or pad b > pad a.
-Confirmed-
Teleporting between two teleporters while the server saves (spamming /force_save while activating teleporter) and probably also while under heavy load the Client and the server get out of sync in regard to the position of the astronaut that was transported.
offset position is not consistenly the same
i did spawn underground within the planet in this picture from the other players view (me being the one in yellow in front)