Bornholio

Not yet that i know of, but RP0 is evolving into RP1 and there is no going back :) There is a RP1 section on the RO Discord. There is pretty extensive early game balancing after the most recent RiS game shows how easy it was to abuse SR contracts. NathanKell has been hot on tuning the timings to get first orbit closer to '58 than we have now (mid '51) Use the higher of the nodes to get a decoupler, otherwise put a decoupler on lower node and separate using that. Interstage fairing are not intended to separate, using fairings in their place will allow you to eject them out.

@species I Imagine that i have this wonderful person on my team https://en.wikipedia.org/wiki/Katherine_Johnson. and all the interns have their calc checked by her, so those time delays were calculated months ahead of time

Wanted to point out one of the best resources for information about space, rockets and science around. https://ntrs.nasa.gov/search.jsp

yes but do you do several hundred sounding rocket missions x-plane flights and other early stuff to fill in the delay for tech? :P that said, i'll start again this weekend a CKAN loaded 1.3.1 and put my 1.4.5 one on back burner (and thus likely to die) for mod/part testing. Just wish i had spare time to do the RiS

Right now they things on the list would not, mostly, be game breaking. There are some more inovative issues open that could though regardless of upgrading change the game enough. I find that the hard thing is having the mods all be available in both. I'm playing in 1.4.5 right now, not sure i want to restart a career for the 12th time

Release 1.00 for KSP 1.3.1 Thanks @pap1723 Get out your Bumpers Probably needs a 1.01, CKAN puts in the wrong proc wings, also we need to get a non-beta release of kerbal renamer 1.3.1

If you want take current master and replace the dlls with these here https://github.com/KSP-RO/RealismOverhaul/pull/1832

For anyone who not watching RP-0 on github is coming perilously close to a release of 1.3.1 RP-1, probably jumping to 1.5.1 after that. All the developmental is rolled to master. Also if you are using a release version of RO there are 160+ commits to master. hopefully a new release soon there too. Test flight is last hook for RP0 and its https://github.com/KSP-RO/TestFlight/releases/tag/1.9.0.0 got a new release

Any part that both RF and Tweakscale modifies may get a negative mass. if you get that then weird things happen. Its likely ony tweakscaled tanks tha cause tha

Actually it goes into the spreadsheet but, it can also go in as a patch (.cfg) if you want to test it immediately. Pap takes the patches out and rolls them into the spreadsheet. Unfortunately the link i made to the pdf instructions for the spreadsheet is broken. i'm going to try and move it all to the wiki this weekend. We really need a lot of work on '80s and later tech. :P

Thanks for listing that copy. The spreadsheets are mainly to get focus on requirements to run or at least features desired to run. part pack generally don't require updating even if a version of KSP changes. @donoya I'll try and get a comprehensive list on the weekend into each sheet. Also looking into getting a Orphans tech node in Developmental to make testing those unsupported parts easier.

Removing RT from the install is not critical but will remove the communication constellation missions as they rely on connectivity via RT.

[ERR 00:16:29.524] Failed to load assembly C:\Kerbal Space Program\GameData\Principia\x64\libglog.dll: ; [ERR 00:16:32.107] AssemblyLoader: Exception loading 'CC_RemoteTech': System.Reflection.ReflectionTypeLoadException: The classes in the module cannot be loaded. ; ModuleManager.3.0.6.dll Its easier, not easy though, to troubleshoot installs using output_log.txt (from you /KSP_x64_Data/ folder) All that said I'd suggest either installing few mods at a time or using CKAN and doing clusters, only RP-0 will not come up as available for required mods. (RP-0 master is not 1.3.1 compatible, but Developmental branch is. ) You have a lot of function mods that most rp-0 people don't use. but we all use different setups.

nope just use developmental branch as is for 1.3.1 (needs dll replacement for 1.4.5 or 1.5.1 though)

Make PR's and they happen, then it has something to test. Effort is always appreciated.

make a patch that does @PART["partname"]:FOR[zzzRP-0] { %category = -1 %techRequired = <pick a node> %RSSROConfig = True RP0conf = true Also add an entry cost and viola done.

They are Taniwha's addition to RP-0, think they have been in developmental for 9 months or so.

Guess i made the gif of the launch too large here is my Jotun I launcher out of vandenburg in '56 https://i.imgur.com/nvOL0eT.gifv Three Stage (pair of LR89's, LR-91 gets it to orbit in up to 240x240, has 800dV for orbital operations from a triple Cavea-B thruster. PEG gets it to orbit just fine, though it doesn't have a solution until the second stage clears. After upgrade cycles, extending the operational limit to 20 days using an improved support module. Got everything tuned so there is no space junk. even the apogee kick motor retro's out of orbit.

Will you be making a video?

There are compiles for 1.4.x of everything needed, and most of 1.5.1

Build rates are multiplied by a VAB Factor (1.0,1.25,1.5), also it allows for a second or third build channel (still have to spend points albeit at a double rate) So until 114 VAB Build points its more efficient to invest in build rate (Build Rate of 5.3) BuildRateFormula = (1+([L]*0.25))*((([I]+1)*((0.00125*((min([N],15)^2)+min([N],15)))+(max(0,([N]-15))*0.05))) + max(0.05-[I], 0))*sign([L]-[I]) Variables: N=num upgrades, I=rate index (0 based), L=VAB/SPH upgrade level, R=R&D level, S=Number of unlocked tech nodes, All "Crew Variables" Note: This uses some tricks to achieve various goals. First, the max() section sets the first build rate to start at 0.05 and all the others to start at 0. Second, the *sign() section limits the number of rates you can have based on the VAB upgrade level . It works because a negative rate is considered "disabled" See https://github.com/magico13/KCT/wiki/Presets:-Internals for what this means

Current release version of kopernicus that is up to date to 1.3.x should fix it. https://github.com/Kopernicus/Kopernicus/releases/tag/release-1.3.1-7

A lot of the things in that are in RSS now and RSS currently supports Kopernicus on demand loading. It would be more work than it seems at first. Still worth the effort if one has the time. Anyone looking at doing planets/bodies remember .dds DXT 1 for color map textures .dds DXT 5 for normal map textures .dds L8 (preferred) or .png grayscale (fallback) for height map textures .png RGBA for biome map textures

how about roverdudes https://github.com/BobPalmer/SoundingRockets or maybe just tweakscale do 'bees count :)

Likely one of the active modders will at least post a PR with the dll's updated soon. Alternatively all the source code is available and require zero non-free software. oh wait look a PR ... https://github.com/ferram4/Ferram-Aerospace-Research/pull/227