Phineas Freak

@kugutsuTweakScale is known to cause all kind of problems, especially with FAR. It would be better to use procedural wings for custom aerodynamic surfaces.

TestFlight will zero out the ignition count if the engine in hand suffers a major malfunction. This is a normal behaviour even for engines with unlimited ignitions.

Exactly! That is why ROMini was created, to give the players a way to play with RSS (or similarly scaled systems) but without the requirement(s) of RO.

@KOCTROTTAJIthis should not happen as compatibility for these was not, by any means, removed. Please make sure that you have installed RO correctly and all of it's dependencies.

@hypervelocityRSS Expanded is required to have correct ID numbers for the bodies and not modify for any reason the original RSS IDs. Just use numbers higher than 25 (the number ID of Charon in RSS) and everything will be good. Of course any other mod that would like to add/patch more bodies will have to conform to the already used indexes but that is another story.

@NecroBonesyou mean like the Delta II/IV FUT and the Atlas V MLP? That...would be something so excellent that cannot be described!

@Warp11yes, if you have it then it works perfectly fine.

@duckmeister12please remove the RP-0 folder that you have inside your GameData folder, download the latest RP-0 package, unzip it's contents and reinstall it.

@ImkSushinice to see a re - release of this mod! Two points of interest: It would be a nice idea to add indexes for the new bodies for the bodies to have a consistent ID (crafts around a body won't be teleported to another random one if on a Kopernicus update). You can fix Dactyl by fixing the biome map name definition.

Someone would have to volunteer and add support for those (USI might be easier that KSPI since the later one does enough additions/changes to the base game to be considered as a "complete conversion" mod, like RO).

That is definitely not normal. Also KSPI is not supported by RO and in fact this might be your source of the issues. Try removing it as a first step and if that fails then post your player.log or output.log so that we can take a look.

@GillyTheGhilliethen something is wrong with your RO installation. The Vesta should be a "AJ10 Upper Stage Engine (Advanced)" engine and the Swivel should be an "S1.5400/RD-58 Series" engine.

@GillyTheGhillieno, KWR and VSR are absolutely supported by RO.

Version 0.48 of RP-0 is aimed for KSP 1.1. You cannot expect for it to work with KSP 1.0.5 without any problems and Nathan acknowledges this in the GitHub release.

I don't see a reason why it shouldn't work. I have not tried it myself nor anyone else has asked about it before though.

@Dermeisterso, to get it right, you want to use RSS and RF but without RO, correct? It that case you have to install RFStockalike to get the RF patches for the engines and ROMini to adjust the dry mass of the parts.

If you have never done it before then it is recommended to get CKAN and allow it to install all the required/recommended mods.

@StoryMusgravethe problem with RO and the prebuilt crafts is the part scaling: most part mods are created for the stock game but for RO you have to scale them to something sensible. Resources were never an issue since they are patched automatically.

@Gordon Dryplease delete your entire installation, reinstall KSP from your Steam account and the install the required mods (at first) via CKAN. I am seeing a lot of errors caused by corrupted files, you are missing at least one critical dependency (ModularFlightIntegrator) and you have some incompatible mods installed (CrossFeedEnabler, SimpleBoiloff, InterstellarFuelSwitch, OSFairings, KSPI). It would also be a good idea to move your KSP installation outside of the Steam folder so when KSP is updated it won't be overwritten.

You can still download it from the newer BobCat thread: But you have to "fix" the Mediafire URL to do so.

What do you mean by "one Hydrolox mix"? The mix between Hydrogen and Oxygen varies between different engines (and even for the same engine in reality), it is never absolute.

Both are correct. The O/F ratio is what matters (in this case it is 0.3104 vs 0.3725).

@TrooperCooper@Temeterthe avionics restrictions are a part of RP-0, not RO.

@MainSailorjust a heads up, the white version and the Gamma version of the Soyuz fairings have the same part module name (MainSailorFairing001) assigned to them (the white version will not load because it gets overwritten by the Gamma version).

@Colonel of FerocityThese parts are not provided by Universal Storage but from DMOS.