Rockets stuck in place over launch pad.

[Jeb is my copilot]

It only happens with Apollo style rockets with the lander between the capsule and the booster and only with the MKI lander can and alcor, and only when engines are attached to the lander. The MKII works fine and i can launch the MK1 and alcor when they are on there own with no engine. Its like the can gets pinned in place but will then lift off if i go to the next stage up. Also the nav ball shows the pro and retrograde indicators bobbing around about 90 degrees from one another while this is happening.

Here are some pics if that helps. the second pic shows the nav ball issue.

All my other rockets work even if they are resting on the bells so its not the old sticky pad issue.

[KeyserSoze]

It only happens with Apollo style rockets with the lander between the capsule and the booster and only with the MKI lander can and alcor, and only when engines are attached to the lander. The MKII works fine and i can launch the MK1 and alcor when they are on there own with no engine. Its like the can gets pinned in place but will then lift off if i go to the next stage up. Also the nav ball shows the pro and retrograde indicators bobbing around about 90 degrees from one another while this is happening.

Here are some pics if that helps. the second pic shows the nav ball issue.

All my other rockets work even if they are resting on the bells so its not the old sticky pad issue.

I'm having that same problem, although it seems to happen when I attach boosters to a 1.25m launch - it's a probe launcher, so no kerbals on it... if I take off the boosters, the problem doesn't exist. I've also tried different boosters and different decouplers to confirm it wasn't part related... I'll do some more testing; will update if I find anything else.

[steve_v]

Are you both running KJR?

If so, get the latest from github.

[Jeb is my copilot]

Ok, well it definitely has something to do with Joint Reinforcement. I had the latest version when it was happening but i reinstalled it any ways, same problem. Then I deleted the mod all together and the problem went away, so its something to do with the latest version.

[steve_v]

It's supposedly fixed in the dev version on github (not yet released), or roll back to 2.4.5.