No staging commands, unable to do anything

[Cdodders]

Some craft, when placed onto the pad/runway, or even ones already launched, dont have any staging commands come up on the screen, and I am unable to do anything ie launch

the craft which have this problem are completely random, using stock parts only, stock mod craft, modified mod craf, newly built craft etc. Not one type has only this problem, it seems random. The only trend I can think of is that craft with no manned capacity arent affected

I have it on Steam

I have a fresh install (attempt to remove the problem, cache has been verified)

mods installed

BahaSP (adjustable Landing Gear)

BD Armoury

FASA

Firespitter

JSI (RPM)

Klockheed_Martian_Gimbal

KOSMOS (partial-solar arrays)

Mechjeb2

Retrofuture

RN Soviet probes

RN Soviet rockets

Soviet Pack (engines)

SpannersBoomsticks

Edit:

I have noticed that the problem only occurs with craft that have crew compartments that are not command compartments e.g. Hitchhiker crew compartments, passeger compartments, space stations etc

Edited February 8, 2015 by Cdodders

[basic.syntax]

Do the no-stages / no control - craft, have a probe core? If not, try adding any probe core, to see if probe core enables control of stages.

(I put probe cores on just about everything, even with kerbal crew, as a backup control.)

[raidernick]

This is an error that happens due to a null reference exception. Seeing as how it only happens on ships with an IVA view I'm guessing JSI is the cause. Try removing that and see if it persists. If not then you have your answer.

[Cdodders]

Not sure it is JSI, crafts with the Apollo capsule and LM (from FASA) use it and loads fine

[Cdodders]

Tested it, its NOT jsi

[Padishar]

On a new run of KSP, go to launch a single craft that show the problem and then upload the output_log.txt file and post a link to it here. There is almost certainly some error in there that will make it very obvious what the problem is...

[Cdodders]

Turns out it was Firespitter

- - - Updated - - -

Ill check in a moment

[Cdodders]

More testing, Both Firespitter and JSI caused it

[kaue4arp10]

I have the same bug here, and for what i've seen in other threads, this is a Firespitter glitch!