Mk2-R Radial Mount Parachute

[LordFerret]

KSP Version: 1.0, Windows 8.1, 64-bit, playing a Science game.

What Happened: I built a rocket (Progress-1) which had an Mk1 Command Pod with one Service Bay beneath; The Mk1 had two Mk2-R Radial Mount Parachutes attached, as well as a Mk16 Parachute on the nose. After launch and one orbit, on reentry, both Mk2-R chutes refused to deploy, even after trying with the right-click menu option. The message given was: "Cannot deploy while stowed!" (see image #1 below).

After attaining more parts and science experiments, a second (updated) version of the rocket was built with an Mk1 Command Pod with two Service Bays stacked beneath; Again, the Mk1 had two Mk2-R Radial Mount Parachutes attached with a Mk16 Parachute on the nose. Twice (because of unrelated catastrophic failures, reverting back to Launch) when attempting to deploy chutes, one of the Mk2-R's refused to deploy (and again) even after trying with the right-click menu option. The same message given was: "Cannot deploy while stowed!" (see image #2 below).

After these two events, I began to prepare to submit this (potential?) bug report, but then remembered it had been suggested I try opening the Service Bay and then trying to deploy the chute(s) again ... because perhaps the game thought the chutes were stowed in the bay. {This suggestion resulted from a previous post I made the other day on the subject: which is here.} So, I went back into the game to repeat the event for a third time to test this. However, when I did, all chutes deployed without a problem ... as if exiting the game and then reentering magically solved whatever the problem was.

I figure I will submit this none-the-less; Maybe it is a bug, maybe not, perhaps someone can take a look at it. In the mean time, I will continue to use this rocket and will report back here if it begins doing it again.

My persistent file and craft file are linked below, saved and uploaded for this report before I tried to repeat and test the Service Bay open test. The output_log.txt file is also linked below, but, unfortunately, I didn't grab it until after the third test (sorry).

Persistent

Craft

Output_log

System Specs: ASUS laptop with Intel i7-4500U cpu, 8gb mem, Intel embedded graphics and Nvidia GForce GT 745M graphics.

Thanks.

Edited April 30, 2015 by LordFerret

[Supernovy]

This is possibly caused by the chute being too close to the service bay.

Can you reproduce this reliably? Is there a certain set of conditions that will always prevent the chute from deploying? Will a quicksave/quickload combo fix it? Can you reproduce it with a very simple craft on the launch pad?

If you can get it to happen again, a .sfs (e.g. a quicksave) would be helpful.

A quick skim of the craft file shows it isn't using any fairings or other cargo bays, is this true?

Did you use the Offset or Rotate tools at all?

[xxserilviaxx]

I can confirm that this happens.

All you have to do to repeat this bug is to place radial mounted chutes in symmetry mode and only 1 of them will work until you open the service bay beneath it even if you place them as high up on the command pod as you can.

They should be 100% aligned but one is counted as being inside the bay still for some reason.

When making the craft I didnt use anything else than the symmetry tool.

I haven't tried to see if placing them individually will do anything different.

Edited April 30, 2015 by xxserilviaxx

[Speijker]

Too bad I didn't read this post earlier, or I'd have made quicksave.

Anyway; I ran into the same issue (no rotating or offset, just slapped 'm on there). If I attach the chutes to the service-bay themselves I've got no problems.

Opening the bay solved it.

And: the craft file

[LordFerret]

This is possibly caused by the chute being too close to the service bay.

Can you reproduce this reliably? Is there a certain set of conditions that will always prevent the chute from deploying? Will a quicksave/quickload combo fix it? Can you reproduce it with a very simple craft on the launch pad?

If you can get it to happen again, a .sfs (e.g. a quicksave) would be helpful.

A quick skim of the craft file shows it isn't using any fairings or other cargo bays, is this true?

Did you use the Offset or Rotate tools at all?

After reading the results of xxserilviaxx and Speijker above, I'd say it definitely involves the Service Bay.

I can reproduce it, already have twice now (as stated in OP), but I can't for sure say 'reliably'. While I did not do a quicksave/quickload test, as I said - exiting the game and then reentering did seem to fix it... but I've not really tested that out thoroughly. So far, with another flight I did late last night, the chutes all successfully deployed. As for an .sfs file, I posted a link to the persistent.sfs which was saved right after the problem occurred; It was after saving it that I reentered the game to find it mysteriously 'fixed'.

Correct, no fairings are used other than the auto-fairing of the new heat shield, and no other cargo bays / Service Bays other than what's seen. The rest of the rocket was the lifter stage.

No, I did not use the Offset or Rotate tools while assembling in the VAB. Both radial chutes were placed manually, but the Angle Snap was active.

[LordFerret]

It appears the community has come up with what will likely be the only answer to this ... see the results here.