search

TehGimp / KerbalMultiPlayer

A multiplayer plugin for KMP
http://sesau.ca/ksp/KMP.html
GNU General Public License v3.0
140 stars 53 forks source link

Warping into range of another vessel can cause the vessel to explode and sync debris back to server #650

Closed JohannesMP closed 10 years ago

JohannesMP commented 10 years ago

Discussed in this forum topic, and demonstrated at this point in the video.

Unlike #645, which is entirely client-side, the explosion caused in this case synchronizes the resulting debris back to the server.

This is probably related to similar cases, such as my previous rover tests where the other rover would explode into multiple pieces.

godarklight commented 10 years ago

Just saw something strange in my log, when I decoupled my launch stage (just about out of atmo), I saw this in the server log:

http://pastebin.com/vbnEg1S3 http://pastebin.com/edPRJt10

I can guarantee that 65km orbit's don't have 0.3 atmospheres of pressure.

godarklight commented 10 years ago

Ok this bug is obviously nothing to do with atmo, here's the steps I discovered to make this happen:

1: Rendezvous with a player as normal, but remember not to warp after you are in range. (You need to run 2 KSP's). 2: Get very close and cancel all relative velocity Everything at the moment is fine, docking mode seems to work. 3: Warp on one client but make sure you stay in range - A quick warp will do. Docking mode still seems to be working, other player is labelled in the past.

  1. Sync on the second client. You should probably be hitting bug #436 - I have a video describing the effect. It will be barely noticeable.
  2. Warp again All hell breaks loose, your ship explodes instantly and completely, and the other ship explodes into however many pieces it had.

I'll try to catch a video of this using these steps.