TranceaddicT

Top notch detective work there, Holmes.

Call up the scipart kerbalism window, there will be a "force start" or "force run" (don't remember the exact words). That will cause the experiment to run regardless of whether data has been accumulated or not.

No, you identify the module to be patched with @MODULE[]. Using 'name = ' would be to change the module name ... you DO NOT want to do that. REMOVE: name = ModuleEnginesFX Expected result: ModuleEnginesFX will not use AtmCurve and replace any existing velCurve with the KeyValue pairs you've provided. Note: If the velCurve doesn't exist nothing will be replaced. Change "@velCurve" to %velCurve" to create a velCurve if it doesn't already exist. @MODULE[ModuleEnginesFX] { @useAtmCurve = False !velCurve @velCurve { %key = 0.0000, 1.0000, 0.0000, -0.0039 %key = 0.0500, 0.9998, -0.0039, -0.0058 %key = 0.1000, 0.9995, -0.0058, -0.0086 %key = 0.1500, 0.9991, -0.0080, -0.0127 %key = 0.2000, 0.9984, -0.0127, -0.0187 %key = 0.2500, 0.9975, -0.0187, -0.0277 %key = 0.3000, 0.9961, -0.0277, -0.0409 %key = 0.3500, 0.9941, -0.0409, -0.0604 %key = 0.4000, 0.9911, -0.0604, -0.0891 %key = 0.4500, 0.9866, -0.0891, -0.1317 %key = 0.5000, 0.9800, -0.1317, -0.1945 %key = 0.5500, 0.9703, -0.1945, -0.2872 %key = 0.6000, 0.9559, -0.2872, -0.4242 %key = 0.6500, 0.9347, -0.4242, -0.6265 %key = 0.7000, 0.9034, -0.6265, -0.9253 %key = 0.7500, 0.8571, -0.9253, -1.3666 %key = 0.8000, 0.7888, -1.3666, -2.0184 %key = 0.8500, 0.6879, -2.0184, -2.9810 %key = 0.9000, 0.5389, -2.9810, -4.4028 %key = 0.9500, 0.3187, -4.4028, -6.3743 %key = 1.0000, 0.0000, -6.3743, -0.0000 } Also: it would probably be better to bang the velCurve before adding it back. This would ensure the velocity curve is the one you've provided should any velCurve exist that extends beyond key, 20. (Not that I think there are any that go beyond key, 6.) You also forgot your commas between values.

Alpha, have you ever seen LGG's ModuleSequentialAnimateGeneric?

Concur. About the only thing that could come to making it more clear is changing the file names to read: Kopernicus-1.9.1-3 (DO NOT INSTALL THIS IN KSP1.10.1).zip

Even tho I know I should probably avoid playing with it since I'm just starting with JNSQ buuuuuuut ... What's Principia like play-wise in JNSQ?

This is for KSP v1.9.1 (Mine doesn't look up-to-date because I have BE28 installed)

Hurrah!!! This is exactly what i was looking for. SR motors looked just a tad ridiculous in that big honker. Had to light off three at a time to make it seem someone okay-ish. (And, yes, image resize is my new catnip.)

Good thing I have been playing this install sloooooooowly (more life-like doing: plan, plan, plan, cut, hammer (band, ow!), buzz, crap-crap-crap, measure, plan, measure, plan ...) and haven't gotten to a point where DR would really have an impact. (Though, now that I think about it, those sounding rockets didn't always exist as long as I had expected...)

Uhhhh, so we probably shouldn't have DR installed?

noice

As long as you're not shoving a log into a post or GitHub issue, any file sharing service is fine.

Contract Configurator has supported KSP 1.9.x since CCv1.29.0 So, if that is your limiting requirement, I guess there should be no problem.

Take care of yourself first, then worry about your hobby-projects.

When you do, it is best to upload your KSP.log to a file service like GoogleDrive or DropBox or GitHub Gist and link it It is acceptable to post a problem to the appropriate mod you believe is causing the crash. Your previous would have been a better topic for general support as it was not (even tho it seemed to be) mod specific.

Balls! That's fantastic. There needs to be a thread of tips-n-tricks like this.

You better make a lot of noise with your release because ... I WANT THIS Do you have a GitHub repository we can follow?

@Beale how did you down scale the quote pic?

If there is backward compatibility with 1.9.1, I'm game.

It's been handled. Let it go.

@Pappystein @Alsos @GoldForest Y'all are saints handling that petulance. I'd've gotten dinged had I logged on 4h ago.

Also, it is always best to provide your latest KSP.log available to us on a file service like GoogleDrive or DropBox. (Psst, my sig has a clue.) This is better than just telling us about things and a dozen or so shotgunning you with possible solutions off the top of our head.

Can confirm this is the case. Start with a clean install and add KOP & JNSQ, then go from there. Only issues are comets and Jool shaders. However, if you are just starting a new career those shouldn't be issues to be worried about. Redonkulous.

Assuming you are referring to the service arms penetrating the vessel, you should be able to right click on them and dial them back appropriately.

??? This is the current thread for it. Don't let the date it started fool you.