NathanKell

RP-1 turns off stock delta V (since it's very, very wrong for RP-1). You can turn it back on in your settings.cfg file.
Find (and set back to true):
DELTAV_APP_ENABLED
DELTAV_CALCULATIONS_ENABLED

@Grant Exploit As I said, please post on the thread. I don't use CKAN myself (or KSP through steam) and can't answer your question further, sorry.

No, FAR works just fine with parachutes. Please don't spread misinformation.
 
@Kerbalito this sounds like you have a version mismatch between FAR and MFI. Please ensure you have the current FAR release and the current MFI release.

Community Resource Pack. RealFuels requires it.
@the_pazter
 
And sure enough, looking at the modlist above, it's not there. CKAN will autoinstall it with RF, and RF comes with it in the zip, so...not sure how you're lacking it. But you are...

@allmhuran as I suspected it's engine exhaust heating, nothing to do with the thermo system per se. However, the engine exhaust heating shouldn't be skipping the part.
Here's why this is happening. As it stands now, the engine exhaust damage, after it raycasts and detects a hit, finds the root transform of whatever transform it hits. And physicssig=1 parts are parented to the part that has full physics. So that 'root' check gives the parent part, not the hit part. If you watch closely in those gifs, you'll see that the convective flux of the decoupler is negative. That means it is being cooled by its environment, not heated. By contrast, the convective flux of the full-physics parent part is very high--that's where the exhaust heat is going.

Please follow the instructions in the sticky in this forum.

useVelCurveIsp = True
velCurveIsp
{
key = mach0 multiplier0 intangent0 outtangent0
key = mach1 multiplier1 intangent1 outtangent1
....
}
 
There's also an atmCurveIsp if you want an Isp multiplier based on density. You should set a fixed single-value atmosphereCurve and then use atmCurveIsp (and useAtmCurveIsp = true) to vary Isp with density, since prop performance varies with density not pressure.

Don't worry about it, it's an expected message in 1.0.5.