Phineas Freak

@Sir_Fanch as far as i know there is no other way around but to a) disable TF temporarily or b) have a secondary save for testing (with TF disabled). Ideally, there should be a TF API where KCT can hook up and disable TF when a simulation is underway.

@Murdabenne a modder that has created a mod is not required to include compatibility for another mod. If a modder wishes to include such functionality then OK, if not then it is up to user (like you did with the example) to create and submit said patches.

@LordDilip because theoretically it is outdated. To "fix" this either delete the "toolbar.version" file or open it and change the "PATCH" values from 2 to 3.

@Aleksey Pschenichnikov please read first the guidelines for submitting support information:

Having an offset CoM is essential for reentering with RSS but RO manages this with it's own CoM module and not directly via the part config. The most weird thing is that VSR itself never sets a CoM in the first place...

@ferram4 yep, that's completely understandable and we are dealing with a really old mod that has not been updated. @WildLynx if you still get the error then i would strongly suggest to remove the part so that it won't be included by any future craft and use a Module Manager patch to add it to the command/probe modules.

The Protractor module by itself is fine but the actual part has a MeshCollider that is not supported by Unity 5 (and in turn by KSP) anymore. This is causing a ton of log spam, both by KSP and FAR (since FAR uses the colliders for voxelization and it fails to do so).

In that case, could you test the vehicle that includes it with and without the Protactor part? The problem should be there even if you just get it out to the launch pad/runway/

@WildLynx do you have a Protractor part included in your ship(s)?

@LordOfMinecraft99 since you said that only the fairing sides are present and you cannot change the color (texture?) of them then you have probably installed Procedural Fairings For Everything, an addon for Procedural Fairings.

This actually is about an order of magnitude higher than the (currently) best non - experimental ion thruster, the NEXT used on the Dawn spacecraft. The KSP ion engine is modeled after that engine (even the name gives it out), it's just that the thrust has been increased by a factor of ~8000.

@MarlboroMan yes, the "LifeSupport.cfg" is the only file that RO modifies (replaces) to set the required resource consumption rates.

The "scale" and "rescaleFactor" parameters require a single float value and are not comma - separated: scale = 1.0 rescaleFactor = 1.0 You probably meant the MODEL{} node scale method: MODEL { model = Path/To/Model/File scale = 1.0, 1.0, 1.0 } that can be used to scale each axis (X, Y, Z) independently.

@Ciaran the attachment nodes that are currently broken.

@Ciaran if you mean the nodes then yes, with the following Module Manager patches: @PART[SerCom1m] { @node_stack_top = 0.0, 0.187, 0.0, 0.0, 1.0, 0.0, 1 @node_stack_bottom = 0.0, -0.187, 0.0, 0.0, -1.0, 0.0, 1 } @PART[SerCom2] { @node_stack_top = 0.0, 0.187, 0.0, 0.0, 1.0, 0.0, 2 @node_stack_bottom = 0.0, -0.187, 0.0, 0.0, -1.0, 0.0, 2 }

What version of RO and VSR have you installed? RO 11.3.0 requires VSR 1.9.5 since some engine models have been changed.

@Komander Faul place it as a check parameter at the module itself: MODULE:NEEDS[TweakScale] { name = TweakScale type = free }

@NathanKell frack, i wrote pressure instead of pump...but now that you mentioned it, the AJ10 is another excellent example! Shame on me that i forgot that legendary engine.

@Ramh5 these are harmless and they do not impact the operation of RVE.

@ClLaw i do not think that @Sir_Fanch was referring to you personally but to our previous conversation. Our posts were used as a way to indicate that @Friedrich Nietzsche's question has recently been answered.

@Geschosskopf Kopernicus now has a hard dependency on MFI. Also, Distant Object throws a ton of exceptions (seems like it is not loading correctly).

@Carraux no problem, i also thought that i missed something! These discussions are the best way to learn new things. @gemini4 i also found some research papers but nothing solid. Probably that is the reason why nobody has written an alternate fuel cell config. You could try and create one though. @Nightside it is not the ignition count per se. Usually it is limited by the ignitor used (some are self - consuming meaning that you can carry/have only so much), the construction of the engine (materials and cooling limiting the overall burn time) and the propellant pressurization. On that end, TestFlight can be a much better balance point than just specifying an arbitary ignition count. The XLR-81 engine used on the Agena upper stage is a nice example of a pressure - fed pump - fed hypergolic engine that started with a single ignition and reached the capability of "infinite" restarts due to the advancements of Rocket ScienceTM.

This would actually be a nice idea but the change must be implemented via RF since it provides the launch clamp fuel pumping capability. Source for that? AFAIK Saturn V only used propellants from GSE to start the gas generator for the turbopump. Is it possible to push the required amount of propellants via the GSE?

Love the engines and especially the Aerojet MR series! Almost no part mods provide orbital insertion engines or RCS thrusters tailored for upper stages but these are perfect. Are you planning to do more engines? Cooperating with @Zarbizaure might help you both on that front.

@Kram45 RT has changed the way that it saves it's data (separate for each save) so you have to load your save, open the RT UI and reload all the available ground station configs.