Thanks. Sounds good.
Maybe for version 2
Definition of attachment points (Hand, foot, back?
Ability to change cockpit view mesh?
Maybe for version 2
Definition of attachment points (Hand, foot, back?
Ability to change cockpit view mesh?
Attachment points along with some way of interacting with attached payloads (probably a set of clbkGeneric messages) is already planned - cockpit meshes are likely a v2 feature though.
I was just thinking about that while finishing off implementing vessel -> vessel transfers. The best way I can think is to have an oMMU vessel interface exposing functions to be called when events happen in the core - allowing custom behaviors on events, denying ingress when a docking port is closed etc. Something along the lines of this (excuse the pseudocode):
Code:class IMMUVessel{ public: bool OnTryTransferCrew(const oMMU &otherVessel, const oMMUCrew &crewMember,int dockingPortID = 0) = 0; bool OnTryCrewEnter(const oMMUCrew &crewMember, int airlockID = 1) = 0; }