So I tried KMP yesterday, without much success. I could launch something, but I tended to lose the server connection after leaving the KSC safety bubble and entering an orbit. I just set the loglevel to debug on my own server and noticed the following: When inside the KSC bubble, the server works fine, CPU load is around 5%. When leaving the KSC bubble, the server reports a new vessel, CPU load goes up to about 50%. Now, the bad stuff happens when I seperate a stage: CPU load goes up to over 100% (dual-core machine) and "Vessel GUID is reported to be destroyed" is spammed to the server's log file. I manually checked the SQLite database, and the vessel is marked as destroyed there. The spam stops, if I disconnect my client (although that might take a while, since the server's overloaded). In the example log below, I disconnected quickly after the spam started, but if I don't disconnect, it won't stop. The server was running mono 4.0 on Debian, the client is running on Windows 7 x64. Everything on version 0.1.1.3. [09:22:18] [Info] : wuselfuzz has joined the server using client version 0.1.1.3 [09:22:19] [Activity] : wuselfuzz set to lead subspace 4 [09:22:19] [Activity] : wuselfuzz activity level is now IN_GAME [09:22:23] [Activity] : Sending all vessels in current subspace for wuselfuzz [09:22:23] [Activity] : wuselfuzz activity level is now IN_FLIGHT [09:22:38] [Activity] : wuselfuzz activity level is now IN_GAME [09:23:08] [Activity] : Sending all vessels in current subspace for wuselfuzz [09:23:08] [Activity] : wuselfuzz activity level is now IN_FLIGHT [09:25:11] [Info] : New vessel 628fd71e-cce6-4443-a292-0d626a23cdf5 from wuselfuzz added to universe [09:25:19] [Info] : New vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 from wuselfuzz added to universe [09:25:19] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:21] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:22] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:24] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:26] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:28] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:29] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:31] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:33] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:35] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:36] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:38] [Activity] : Vessel 1a0158fb-dd8c-4551-812e-b597f3c13403 reported as destroyed [09:25:49] [Activity] : wuselfuzz activity level is now INACTIVE [09:25:55] [Info] : Client #1 wuselfuzz has disconnected: Timeout [09:25:55] [Info] : Client failed to handshake successfully: InvalidOperationException