Airlock placement problem

[nli2work]

So working a command pod part... everything's working, except Airlock and ladder. I read the wiki entry couple of dozen times now and I've tried to place the hatch and ladder triggers like the copula pod. I'm using Unity Box collider for ladder up the middle, and airlock on either side. but wherever I place the Airlock pivots, inside or outside the physics collider, I get the hatch obstruction error. The closes I get to a working airlock is the Kerbal spawns at the COM of the pod, and gets ejected outside.

The Pod requires compound colliders, but I made sure the airlock triggers are only intersecting top convex collider.

where should the airlock pivot be placed? how big should the airlock trigger be? It looks like the Kerbal is spawned where the trigger's pivot is, but that doesn't seem to work when the pivot is outside of the pod's collider.

[Orionkermin]

I hope this helps, as you see the box collider is the area that the kerbal will spawn in and the blue pointer is the direction he will face. Also make sure your Airlock and Ladder are tagged as such. In your case you'll want to make the ladder a tall collider box so they can climb up.

[nli2work]

Ooooh kay. I see what it was... the Airlock's X and Y must be 0. Z can be any position.

Kinda strange way to do it... why require X and Y be 0??? but that's how it works. I'll have to move my crew hatch, but good to know for the future.

Thanks!

[Orionkermin]

I don't think x and y require zero. That's just how my example ended up. It's more about the position of the transform and the box mesh. Think of the box as needing to be big enough to contain the kerbal and the transform has to be in the middle of the box.

[nli2work]

hm... after testing a bunch of different set ups, the only way I've been able to get it to work is with the transform Y at 0. The X doesn't seem to matter, the game forces it to 0 once on the launchpad. The actual trigger box can be off center and flat. Kerbal spawns at 0,0, transform.z. Z position also must be negative, behind the CoM. really strange how it works.

Edited June 17, 2014 by nli2work