610yesnolovely

Hoo boy indeed! This is a tour-de-force of an update, congratulations on the results of the tons of hard work. My oh my, KSP will be looking glorious.

I'll add a GitHub issue to look into Tantares support using whatever Missing History or other IVA might work, it is popular. Perhaps @JonnyOThan will notice, since it's Reviva is now a co-operative mod. https://github.com/FirstPersonKSP/reviva/issues/33 For tutorials, quick advice: Assuming you have Missing History DLC Use CKAN to make another copy of KSP just for developing. Install only the minimal dependencies so KSP loads quickly: ModuleManager, Reviva, B9PartSwitch and RasterPropMonitor. Add Tantares mod(s) Clone the GitHub repro (if you know Git) or download the source zip. Try editting https://github.com/FirstPersonKSP/reviva/blob/main/GameData/Reviva/0_Setup/Stock.cfg in your dev version Start with adding this near other similar lines, total guess would be tantares_crew_s1_1 Got this info from reading: https://github.com/Tantares/Tantares/blob/master/GameData/Tantares/parts/core_soyuz/_tantares_crew_s1_1.cfg look for the name = xxx line (xxx is the part name) and then the block that says INTERNAL { name = yyy } (yyy is the name of the IVA / internal module that is used). This just sets the default "Stock" for that Tantares part. Adding an alternative is a little trickier (from memory), possibly copy GameData/Reviva/1_Patches/Apex.cfg to another file called Tantares.cfg (anywhere under GameData) replace Apex with Tantares (name of mod) replace mk3Cockpit_Shuttle with tantares_crew_s1_1 (name of part) replace MK3_ApexInternals with KV1_IVA (name of internal) This may not be accurate, and if it works, it's not the official way to do things properly: but it gives you an idea of how things work: each part has an INTERNAL which specifies what the IVA is, and that's a unique name for each IVA. Each part needs two modules: ModuleIVASwitch which has an internalName field that is watched by Reviva code that actually switches the IVA on the part ModuleB9PartSwitch which targets that module that the B9PartSwitch mod implements. This needs one or more SUBTYPE nodes, each describe the value to of ModuleIVASwitch's internalName field as you select which IVA you want in the UI (PAW). Reviva code watches for that changed field and the Reviva code switches out the IVA. This means Reviva is actually just focused on the IVA switching logic code, and B9PartSwitch is the magic that defines the UI (PAW) and sub-type definitions, and does 90% of the support work, so you should read up on how that works if you (or anyone else) is interested. Might want to also read the GitHub README. Most of the work in adding mod support is writing ModuleManager .cfg files that end up building such edits, so definitely you'd need to read ModuleManager's tutorial/wiki/KSPCF posts to understand the easier parts (there's a lot of depth, but the basics are fairly easy).

I've not personally used Tantares (shocking, must remedy) - the real question here is do the command modules have any IVA at all? Or multiple? Because if there's only just one and it's default, there's not much use for Reviva - it's best for CM which have multiple IVA where you need to switch. This is mostly true for stock or where there's mods which have similar command pods (eg. stock Mk3 is kinda like BDB's Apollo CM) here a lot of IVA have been made and can be shared. Historically there's not been any IVA for Tantares, though recently there's somebody on the thread trying to make some, I guess in theory one might jam in some Making History IVA (DE_IVA?) but it'd be janky (eg. not match up well to view ports). If you know of any IVA sets, then let us know in this thread. Unfortunately I've moved half way across the world and my dev machine is in a container only a quarter of the way round the world (ie. two to three months away). Have laptop, but it's not great for development, so unlikely I can attempt it myself, but you might motivate somebody with ModuleManager skillset to help.

Good to hear! Unfortunately for KSP modding (and me playing, sheesh, so many cool KSP things released recently), I've moved half way round the world and my gamedev PC is in a shipping container that won't arrive till mid-September, and currently I'm using a mobile phone for broadband and have a laptop, not really up to gamedev specs or playing KSP tho :-( Fortunately for me, where I've moved to, western highlands of Scotland, is very beautiful, quiet/remote, but not too disconnected. The sort of place one can really concentrate and get stuff done once I'm settled. Also I won't be doing paid work until Spring 2025 at the earliest ... so I'll have some time on my hands hopefully soonish. Co-operation/patches/pull-requests welcome!

I'd try Completely Non-Agressive Rocketry and/or Taerobee - both have good starter sounding rockets. For bonus points Wacapella (which needs both, which I wrote) which is a config that provides WAC Corporal parts. I do think however that using BDB makes this contract pack work even better, but yes, that's not "smallest stock alike" ;-) - I use KSRSS Reborn, Skyhawk Science System, BDB with this mod, a great combo.

Yup, you need a bunch of mods to make Reviva shine as it's just a tiny part of getting IVA to work really nice. I also recommend FreeIVA so you can leave your seat and explore your ship. Come join us in modded land. Use CKAN to automatically install everything. I have over 300 mods, and it's very pretty... and yes, this picture is KSP1. Mods that make this look like this: KSRSS Reborn, Cape Canaveral for KSRSS, EVE (Volumetric Cloud Patreon edition) and Atmospheric Beats for EVE VC, and of course Reviva and it's definitely required mods, plus I think either DE IVA or perhaps Warbirds IVA.

FYI: Reviva has been transferred on GitHub to https://github.com/FirstPersonKSP/reviva - so a bunch of people can collaborate better. Consider this also a confirmation of transfer of any license to that organization, and the right of that organization to change license and do whatever they think is best (I'm part of the organization of course, but more people is better). The old links will still work, so nothing should be impacted.

Find the KSP game root folder (C:\Program Files (x86)\Steam\SteamApps\common\Kerbal Space Program - if you use Steam), put text in some file with a ".cfg" extension under the "GameData" folder. My recommended is make a folder based on your name, and file based on mod, so "...\Kerbal Space Program\GameData\MarxMan28Patches\EskandareAerospace.cfg". Typically people post fixes like this for mods, so you can repeat the same pattern. I have about 30 or so files like this. There's several players out there who put their patch folders on GitHub.

Release 1.0.5 - kOS Support (19th Feb 2024) Adds: Very very small kOS processor for each Capella Nose Cone, to allow for very basic programs and/or simulate control via radio.

With 2.0.3 release I got 4 ModuleManager errors - details here https://github.com/JadeOfMaar/RationalResources/issues/61 with simple one liner fix that seems to resolve it.

This is great, exactly the sort thing I was looking for as I also use Skyhawk Science System and wanted appropriate kOS machines to appear on probes and CM in a balanced way. Thanks!

JonnyOThan is awesome! He's now a co-contributor for Reviva on GitHub (ie. has full power and authority to do anything with the mod), he's got my energy and time than I have, so expect some more cool things soon. Who knows, it may motivate me to help out too :-)

You could also try FuelVent - it's different and weird (it's actually a tiny LFO engine) so it probably still works in space. I like both for different reasons.

For anyone using this mod, works great in 1.12.5! One minor set of fixes I use ensure the Radio Biome science part works - it was slightly broken: The experimentID was incorrect. The usage requirements was incorrect: You need crew in the vessel (value 3), not the part (value 5) which would be impossible, so it can't be used on a probe, by design. // Fix Science @PART[EHI_ball]:AFTER[Eskandare_Heavy_Industries] { @MODULE[ModuleScienceExperiment] { @experimentID = ballbiomeanalysis @usageReqMaskInternal = 3 } }

I automate all my launches using anything reasonable: typically the Scripting Module in MechJeb which is easier than kOS. Probe science and launces are two clicks "Start" on MechJeb script and then "Launch" on NASA Countdown (which automates some pre-launch sequencing via staging). Sometimes I restart my career, and it's always fun to launch several rockets in a row and just watch it go and take pictures. If Kerbals are present, I switch to using some automation and Kerbals 1st person in IVA - both fun alternatives. Below is Pioneer-1 in BDB, with KSRSS Reborn, Skyhawk Science System and History of Spaceflight contract. The script has a "parallel" section where the left panel is sequencing the staging to orbit, and the right panel is doing roll, pitch and circularizing. The last four actions are using action groups to collect science. I just unlocked MechJeb's Ascent Guidance, so it gets easier to program as you get more MJ modules. Usually later though I have multiple programs (launch, orbit, transfer, return).