Is there a hook when switching vessels? I need to close my network sockets... somehow.

[jarpy]

Hi,

I have a working prototype for a part that sends and receives over UDP sockets: https://github.com/jarpy/OpenSpaceKontrol

My current challenge is that it only works for the first vessel/flight of a game session. After that, I'm still holding the UDP sockets, so the next vessel can't bind to them.

'Would love to hear any suggestions for closing the sockets when the vehicle is destroyed or switched away. Is there a simple "OnNotFocussed" kind of method I'm missing? Or do I need to pull back and make my sockets part of a broader (non-part, non-vessel) context.

Thanks very much for any help you can offer.

[Crzyrndm]

GameEvents.onVesselChange is the event that fires when switching between vessels.

[jarpy]

Thanks Crzyrndm.

Looking at your code, I'm starting to get the feeling that mine would be better implemented as a MonoBehaviour rather than a PartModule. So double-thanks for that.

[Diazo]

Note that .onVesselChange also fires on undocking, losing parts to an accident (overheating/collision/etc) so you'd have to check for that in your code.

However, looking at your code, I'd consider moving the actual UDP port binding and associated code to a KSPAddon.Flight class. Having it on a partModule like you do means that even just having two OskModule partModules on the same vessel could get interesting.

A KSPAddon.Flight class only runs once per flight scene load so you don't have to worry about binding/unbinding sockets and such regardless of what happens during the scene.

You would still need the OskModule partmodule class to control the vessel, but I think writing the logic for a single KSPAddon.Flight to recognize a vessel switch would be simpler then having multiple partModules trying to decide it between themselves.

D.

[jarpy]

Sounds like great advice. I like your split approach, with separation of concerns between "game things" (commands, telemetry) and "computer things", (UDP sockets).

Thanks for taking the time to look at my code; this is a nice place.