610yesnolovely

In case anyone would need such a thing, ModuleManager patch to change ASET MFDs such that ascent page uses ExtCam1 (but has ExtCam2 as alternative), and more importantly has landing page with ExtCam2 first (then ExtCam1). Why? Set ExtCam1 to point up/forward for ascent, ExtCam2 to point down/reverse for landing when building.

Apologies for resurrecting this thread, but this as I'm collecting IVAs for another mod, this is such high quality I hope @stephm releases it or puts whatever he's done on GitHub.

Resurrected since I'm currently running both RPM and MAS, and am about to try to get kOS and kOSPropMonitor working. Looks like @vulkans YouTube video shows MAS MFDs working with kOSPropMonitor. The currently released AvionicsSystem from CKAN, does not (yet) have the ASET to MAS prop upgrades (ie. "AsetToMasUpgrade.nocfg" has not been renamed yet), I think the GitHub version does however. So in the future, if it doesn't work look for that file in AvionicsSystem and rename it (or disable just the MFD40x20 upgrade, or add a user local final patch to undo it). So for now the MFD40x20 props (which RPM will run and provide support for kOSPropMonitor) are not run by MAS versions (MAS_ALCOR_MFD40x20), so kOSPropMonitor seems (from testing) to work: Install RPM Install MAS Install kOS Install latest kOSPropMonitor (from SpaceDock, the CKAN version is older - @dsonbilldidn't update CKAN I guess?) Advert: If you like IVAs, I recently started developing this mod which lets you switch IVA in the editor and *in-flight* (supports RPM and/or MAS). It includes Stock and Missing History support for switching Stock, RPM, ASET (via DE/HonkHogans IVA), the Alexustas ASET, Ultimate Shuttle IVA, and has variants of the ASET props where a couple of MFD's are swapped out for the super new swanky MAS versions. Also for that OPT JHT cockpit, @vulkans kOS scripts are available via dropbox, see his YouTube videos. The link is the second Dropbox link he posted in answer to a comment there.

Very exciting. More IVA the better. Having the IVA switching in another mod is great also - totally expect to see people do that. It'll help once I get CKAN working, then Reviva could be a recommend or option in ERS via CKAN. And yes, making IVA of any kind seems time consuming. The way I cheated is to hand edit a couple of MAS MFDs using ModuleManager in Reviva itself as variants, as I use RPM and MAS together. The MAS MFD have much better navigation, and MechJeb support. Interesting... I've found some IVA, especially fighter style cockpits or planes, don't let you look around too much. I use TrackIR in IVA (KSP Flight Sim 2005), so I may add something like this. Did I imagine it, or did somebody have an IVA where they used external camera display parts as mirrors in a fighter cockpit? I may have seen this in another game and got confused, but it's a neat idea also.

Pull requests welcome! Does the rover have other IVA configurations? Intrigued as to what you're thinking of doing. Cool stuff I'm sure. What I've done is added a MAS upgrade variant where I replace a couple of MFD with the improved MAS variant, and I'm going to do that with the ALCOR lander - it'll have just two configs: ALCOR and ALCOR+MAS. Even then, if there's IVA / mods with just one IVA, my intention is to simply add links to the README and eventually add CKAN support for recommends/optionals such that it's easy to install all the IVA you could ever need. My next tasks are to work on a CKAN and test it locally, and set up automation for publishing on CKAN, Curse, and Spacedock - I've seen a few modders provide python automation for this. I'm currently play testing also, finally reached crewed in UKS tech tree and so thatprompted me to do the KV-1 (and missing history).

0.7.1 Pre-Release (28th Feb 2022) - Support Missing History KV-1, KV-2, KV-3, MK2 command pod and M.E.M. lander. - Configurations for Stock, ASET IVA for Making History Pods, and MAS alternatives for Mk2 and M.E.M (the KV pods are meant to be low to medium tech only).

Gosh, yes, I remember reading about how it might be done in the WPF thread - I'll add that when I start adding in support for Making History, soonish, once I get to that in my play thru, I'm stuck on building probes - since I use Unkerballed Start :-). By the way, the Warbird Cockpits are excellent.

Excellent, the more IVA choices, the better. There's two ways you could do this: both would need to depend on Reviva - either change the IVA package itself and add a MM script to add an additional "SUBTYPE" node to the Mk1 Lander IVA supplied by reviva, or send me a pull request on GitHub to add it. The file in question is https://github.com/harveyt/reviva/blob/main/GameData/Reviva/Stock/mk1lander.cfg - ModuleB9PartSwitch with moduleID = IVASwitch and follow the same pattern. If the IVA needs data in the RasterPropMonitorComputer - check the DE_IVAExtension SUBTYPE, you put it into the subtype - the Reviva DLL can handle both RPM and/or MAS settings: it essentially removes those modules and reloads them (a reboot) when you switch. If the IVA does anything more than that (changing other module via MM) those changes are probably not going to work, at least for in-flight switching and probably doesn't make sense anyway - for example the Ultimate Shuttle IVA changed the crew capacity which would be interesting in-flight (when you switch back, do the extra 3 kerbals go on forced EVA, or do you store them in carbonite...). Such edits, even in editor, may or may not work - I've not fully investigated that: if it's changing a property marked KSPField for example, in-editor, does that get saved for the vessel, and/or OnLoad/OnSave do it, or are the parts and modules always loaded from the part database. As to Probe Control Room - I'm going to look at that soonish, after Missing History support, since I do use it myself. I'm guessing it's weird but from what you say, sounds like it'll be possible.

Whoa... that's a whole heap, my brain will explode if you write more. Thanks! I'll have to re-read that when I'm more awake. I knew some of those things, the more general development (I think most modders are software developers by day), but the particular tips about KSP, this forum, markdown, pandoc, shields.io - that's super useful. The forum editor really sucks, and after some forum searching I concluded that the best approach is to look at people's GitHub and try to guess how they did it. For build automation @Nerteahas some here: https://github.com/post-kerbin-mining-corporation/build-deploy, and https://github.com/ihsoft/KSPDev_ReleaseBuilder by @IgorZ- plenty of good stuff out there. I'm a Linux, Emacs, make, python, automate-all-the-things old school (but not as old some ).

I know, all 22 of us who fly in IVAs will be happy (a joke from the MAS topic). I was just flying using the Mk1 Cockpit, the ASET variant is great, but it doesn't have access to NavUtils, so while in flight I switched to the DE IVA which does. However I might add an alternative that patches in an RPM MFD to replace the green screen CRT in that IVA. That's the beauty of the system, you can use ModuleManager magic to do minor edits like this without even touching the other mod. I supply additional DE IVA alternates for all of stock which replace one or two ASET MFD with the brilliant MAS MFD, so you can select either DE or DE+MAS. The latter is probably my favourite setting. I also took time to add the Warbirds Metric and Imperial variants for the Mk1 Inline both normal and retro all in one part - I think @theonegalen will appreciate that, as they're such fantastic cockpits. For modders it could be used to provide an empty IVA (for performance), and one or more alternative IVAs, and due to using B9PartSwitch, adding part upgrades is totally possible: you could have an analog command module with a couple of tech upgrades. I may add options for that for stock one day (it's on the task list). The secondary point of the mod is to collect all the known working IVA mods with links and instructions (or CKAN config) in one place, so people can install them easily. Reviva will provide patches via MM to make sure they work (as much as possible).

Love this mod. Makes flying/landing so much easier. Just installing 1.12.3 again (using CKAN), and this is a must have mod. Couple of minor bug fixes for @linuxgurugamer which may cause NavUtils to not load or warn, if you're not paying close attention (downside of CKAN): netkan / CKAN is missing depends: Click Through Blocker ToolbarController SpaceTuxLibrary The NavInstruments.version file might need a KSP_VERSION_MAX with 1.12.99

I recently posted my first mod announcement to the forums, the forum editor is okay for general chit-chat, but it's a PITA for mod announcement readme. I do not wish to ever waste three hours of my time wondering trying to format a large document by hand, wondering why it forgets half of my edits. Not. Fun. I noticed a lot of well formatted, image laden mod announcements - from what I've read the easiest way to do this, especially with GitHub, is write markdown and display it in a browser on GitHub, then once you're good just copy and paste that. Usage of pandoc (which I'm aware of) may be useful. Any seasoned modders advice? A good example I found was @zer0Kerbal's - the GitHub readme.md is quite marvellous.

The idea came from the B9PartSwitch thread, both @theonegalen and @Bonus Eventus had experiments that suggested it was, so thanks to them for trail blazing. The motivation was I fly mostly first person, especially aircraft in IVA with TrackIR, joystick and throttle. Flight Sim KSP! Bonus: I put in DE+MAS on most stock command pods (you'll need MAS, RPM, DE IVA and all their dependencies). This provides alternative IVA which are copies of the DE ones, but one or two of the MFD have been upgraded to MAS MFD's, which are superb.

I think I answered my own questions, and just published the mod in question - I wanted a way to have multiple IVA internals and mods all at once, and be able to switch them in the editor using B9PartSwitch, and uses SUBTYPE with MODULE switching - the module in question is part of my mod - it does the correct internal updates in editor or in flight to make IVA switching possible. Thanks @blowfish - you made me (and hopefully the other 21 people who use IVA mods) happy. See https://github.com/harveyt/reviva/blob/main/plugin/ModuleIVASwitch.cs from:

KSP 1.12.x - Reviva - The IVA Revival! KSP Reviva is the IVA Revival! For Kerbals who like to fly first person. Supports multiple IVA mods at once (IVA mods not included). Supports RPM and MAS. Allows IVA internal switch via B9PartSwitch: Allows selecting different IVA on each command module in editor/saves. Allows for on-the-fly IVA switching while in flight. Soon :: CKAN support so you can install Reviva and all the IVA mods you ever wanted. Currently only stock IVA and some popular IVA mods are covered, the intent is to extended the coverage over time. Required Mods Reviva - note that this does not include any other mods below in the download. KSP Forums GitHub Latest Release Download and extract the Reviva-x.x.x.zip file at the root of your KSP installation. SpaceDock - SpaceDock CKAN - Available Curse - Probably never B9PartSwitch ModuleManager RasterPropMonitor (RPM) Recommended Mods DEIVAExtension Optional Mods MOARdV's Avionics System (MAS) ASET Mk1 Cockpit ASET Mk1 Lander Can ASET Mk1-2 Command Pod Warbird Cockpits Ultimate Shuttle IVA ASET IVA for Making History Pods Many more, see Support Progress and Dependency Summary for the full list as more are supported. Some IVA mods require downloading from GitHub, Dropbox or even Zip files in GitHub issues and must be installed in their suggestion locations for Reviva to work correctly (directory names under GameData are very important). Changes 1.0.0 Release - Major Updates by JonnyOThan JonnyOThan is awesome! He's now a co-contributor for Reviva on GitHub, so he has full power and authority to do anything with the mod. This release is mostly due to his hard work to really make this mod shine. Giant refactoring of patches to make it easier to add support for mods and parts Fixed bugs regarding RPM variable persistence and action group memos being lost Fixed bugs that prevented ProbeControlRoom from working properly with Reviva Added Apex and Kermantech options for mk3 cockpit Fixed some configuration bugs 0.8.1 Release - Bug fixing (2nd Jan 2023) Fixes: Added support for AirplanePlus Mk1/0 Caged Inline (same as Mk1 Caged Inline). Note that the part does not fit exactly and has the wrong interior window structure, but is better than nothing. 0.8.0 Release - Bug fixing (16th Dec 2022) Fixes: Fix GitHub Issue 9: Thanks to JonnyOThan: Clone the partInfo so that changes to the internal config don't affect all instances of the same part. Extra fix from Fix GitHub Issue 9, again thanks to JonnyOThan: Fix an issue with internals that don't have crew capacity, exposed by FreeIva. 0.7.7 Release - BDB 1.11 Support (22nd Oct 2022) Adds: Slightly improved support for BDB 1.11 Release. Hermes/Mercury: Added Placeholder (empty) and BDBAlternate (super minimal, non-functional) Vinci/Gemini: Added Placeholder (empty) and BDBAlternate (old FASA, non-functional) Kane/Apollo: Added Placeholder (empty) and BDBRPM (functional RPM variant of non-functional BDB) Sina/LEM: Added Placeholder (empty) and BDB2 (new BDB non-functional IVA), the older BDB remains unchanged for compatibility. NOTES: Previous Reviva 0.7.6, 0.7.5, 0.7.4 will still work fine with BDB 1.11 - though the new non-functional LEM IVA will not be selectable. Currently no LEM variants have IVA switching: ie. no engine cover, Taxi, Lab, Shelter. You get the BDB default only. Similarly any Mercury, Gemini or Apollo variants (eg. Big Gemini or Apollo 5-Crew) do not have IVA switching, BDB default only. 0.7.6 Release - Moar IVA and BDB (24th Sep 2022) Adds: Support for: Starilex Intra-Vehicular Solutions - an excellent retro Mk1 pod. Available for Stock Mk1 and BDB Hermes / Mercury CM. Uses RPM. Max-Ksp MAS IVA Pack - excellent retro Mk1-3 and MEM pods. Available for Stock Mk1-3, Making History MEM, BDB Kane / Apollo, Sina / LEM. Uses MAS. SABS_IVA: MAS-enabled IVA - partial support (it provides a full set of Stock and Making History pods using MAS) for Mk1, Mk2, Mk1-3, MEM and BDB equivalents. Uses MAS. These are work-in-progress, I may add configs for everything else later. Snakeru's Mk2 Pod IVA - excelent retro style Mk2. Available for Stock and BDB Vinci / Gemini. Note that this is a ZIP file in a GitHub issue and is Beta, but to me is the best retro MAS style IVA for the Mk2. 0.7.5 Release - Airplane Plus (28th Apr 2022) Adds: Support for Airplane Plus: Warbirds (Bell Heli, Citation, Old Fighter Inline, X1 Supersonic, B29 Bomber) Warbird Cockpits Airplane Plus IVA Pack (Bell Heli, Bombardier Jet, Cessna, F-18 Fighter, Huey Heli) Airplane Plus IVA Pack Airplane Plus F-16 ASET/RPM for Falcon cockpit Needs to be installed in GameData/AirplanePlusFalcon. 0.7.4 Release - BDB experimental (28th Apr 2022) Adds: Added "Experimental" support for MOARdvPlus BDB Kane (Apollo) CM: MOARdV's Avionics System (MAS) Only covers the standard 3 crew Kane/Apollo CM. Original MOARdVPlus FASA variants still present and unmodified, they're hidden, don't use them as they won't work as well. Reviva MM config changed to support BDB 1.10.x naming Specialized action group switches work (eg. EVA Light) Glass variant also seems to work. Interior model does not match exterior so "Interior Overlay" will not look great. Will improve when BDB updates the interior. Also even more "Experimental", all Mk1-3 IVA interiors also available and seem to be functional, but definitely look even more silly with "Interior Overlay". Will not ever fix this. Fixes: Fix MASFlightComputer support to correctly update config data. This was required to get the MOARdVPlus special action groups to work. Probably helps make other IVA a little more accurate. Updated README.md with more IVAs, and links to completed mods. 0.7.3 Release - Bug fixes (12th Apr 2022) Fixes: Support QuickIVA when loading strait to IVA (GitHub Issue #6) Handle any configuration errors by remaining on same IVA (GitHub Issue #5) 0.7.2 Release - Bug fixes (11th Mar 2022) Fixes: Undocking two of same craft causing crash (GitHub Issue #3) Correctly switch IVA for in-flight craft where multiple similar craft present (GitHub Issue #4) 0.7.1 Release - Stock and Missing History (28th Feb 2022) Support Missing History KV-1, KV-2, KV-3, MK2 command pod and M.E.M. lander. Configurations for Stock, ASET IVA for Making History Pods, and MAS alternatives for Mk2 and M.E.M (the KV pods are meant to be low to medium tech only). 0.7.0 Pre-Release (3rd Feb 2022) Support for RasterPropMonitor (RPM) and/or Avionics System (MAS) IVA. Covers stock command pods, cockpits, landers and cuppola only. Configurations for Stock, RPM, MAS, ASET, DE_IVAExtension, Warbird Cokcpits and Ultimate Shuttle IVA variants. For Players If you like flying in first-person from the in-vehicle crewed cockpit, either in stock or using RPM and/or MAS, then this mod is for you. Features: Allow switching of IVA from stock to different alternates (if needed mods are loaded) using B9PartSwitch This can be done from the editor, and the settings are saved with the ship design. This can also be done live from flight! Use the PAW right-click menu on the command module when not in IVA (yup, not realistic, but this is KSP). This allows for the player to load this mod on existing saves and change IVAs on already flying craft, or to try out different IVA. Without Reviva, only the "last" IVA mod for each command module would be available. Links together stock and modded IVA into one place and provides limited patches to ensure they work in 1.12.x. Note that this mod doesn't include the IVAs, but provides links for recommended or optional IVA mods, plus patches to allow them to run and be switched dynamically. Very low overhead on in-game CPU/GPU performance: command modules get an extra ModuleIVASwitch, and switch detection only happens when changes are made. Note however that all the Internal modules are loaded into memory, so load times will be a little slower, and memory usage a little higher for each IVA pack you install. Don't go too crazy. The best way is to look at all the different IVA mods for a particular command pod or cockpit, try them out and pick one or two. Note that the first option is usually the non-functional stock or original mod IVA, these typically have less performance impact. The different IVA selection does not change the characteristics, mass, cost or other data on the actual command pod: it's all visual for IVA. This means you can change at any time without penalty, by design. Thanks blowfish :: For B9PartSwitch which provides all the clever part switching and UI. Electrocutor :: For ideas in WPF and KSP forum that inspired idea. sarbian :: For Module Manager which provides ways to reconfigure everything. alexustas :: For the amazing ASET IVAs and props. MOARdV, JonnyOThan :: For Raster Prop Monitor (RPM), making IVAs look all fancy. MOARdV :: For Avionics System (MAS), making IVAs look even more fancy. DemonEin :: For DE_IVAExtension which provides decent IVA for all of stock. Honk Hogan :: For IVA_ASET_MAKING_HISTORY which provides decent IVA for Missing History. theonegalen :: For Warbird Cockpits IVA, and forum posts that inspired that this is possible. G'th :: For the Ultimate Shuttle IVA. linuxgurugamer :: For the hopeful adoption of this mod if I wander off in the future. License MIT License - (C) 2022 Harvey Thompson Source Repository on GitHub For More Information See the GitHub README

Talking to you as requested (though technically this is after starting to use this feature). I'm new to KSP modding (like I started yesterday on C# modding, I've done some minor Module Manager before), so I'm getting used to how things work in KSP, and I'm using B9PartSwitch with a new mod I'm developing. The B9PartSwitch module switch works great when I use it on my own module: OnLoad() gets called with the ConfigNode changes as expected. Question: Am I right in saying for basic modules (without specific support in B9PartSwitch), that it doesn't change anything else (for example updating this.part.partConfig - specifically the module's ConfigNode), so you have to do all your update work in OnLoad()? That should either change a KSPField persisted data in your own Module, and/or implement OnSave() if that's not possible? Secondary Questions: OnLoad() will also be called when first loading the vessel - I take it that one should be careful and take that into account? Is there a good way in OnLoad() to detect "we are loading a part" vs. "we are doing a B9PartSwitch switch"?

Alternative solution from memory I've found to work: remove the decal(s) from the vessel, then edit the text, then re-apply - that will also fix a broken black decal.

Yay! Thanks @DMagic I found this mod so useful, glad you updated. You do make some super cool mods.

Love the IVA - in particular the 1980's reel-to-reel brings back memories. Yes kids, I actually have somewhere a backup tape from such a device with some C source code on it.

I kept hoping @linuxgurugamerwould come along and organize us. Very happy to hear that this may hopefully happen. I'm happy to help! Note that I've personally not tested the changes I proposed, I got lazy and just used @NicolaSixversion which from what I saw in GitHub has my suggested fix in it. I did not however check if there were other fixes/changes, but that worked great, so I got distracted again actually playing.

I've had this issue: Kerbal Engineer still reports the right values, but stock dV didn't on a rocket with a probe core as root, and a base/tower/umbilicals. I removed the base, tower, etc, and used without (which of course was fine), then later re-added and then it worked, which doesn't make sense unless I'd accidentally mis-rooted. So the stock dV code runs from the root down each parent/child chain to calculate dV and I'm guessing something about launch bases causes an exception which aborts the computation? If so then making sure these parts are after any and all engines might be enough: Root -> Stage 2 -> Stage 1 -> Stage 0 -> Base What about this configuration: Stage 2 <- Root -> Stage 1 -> Stage 0 -> Base Ie. the root part has two parent/child chains (Stage 2 is "above" the root physically), but it only assigns the dV if it can process all the stages, but it sees "Base" first because it follows that chain first from the "Root" (down physically).

Looking forward to trying out this out. I'd prefer the system where non-sample based experiments are always 100% on transmit/recovery, but sample based is only 100% on recovery, but much less (eg 50%) on transmit. Anything that requires a Kerbal to do (or reset), or is sample based should be more science points. That way if you send a probe you can do lots of biomes/situations with transmissions, but in total that'd only be about third of the total possible science somewhere (eg. Duna), so you have have a probe with return to get third more, and send a Kerbal to get the last third (roughly). That way the repetition is not tediously doing the same thing, but a different kind of mission/build.

I've been playing 1.12.2 using UKS, mostly works (esp. with the LV-T05 and LV-T10 patches from @kcs123(thanks!!). Hope one day @theonegalen(thanks! I'm also using your Warbird IVAs which are superb) can update the mod, but until then in the spirit of community... I've been using a bunch of mods in early career, including SXT Continued from here: Included below is a ModuleManager patch which attempts to balance just the engines in SXT Continued (there's waaay too much else). Initially I just ignored the engines that seemed to powerful, but just in case anyone wants to use these or improve them. I did it by comparing engines to other similar and tried to work out where they probably should appear, so I could have made it harder, but it still might have some engines too early or too late. Open to suggestions for better balance. See the comments.

I'm not an expert, but scalar is probably not want you want to fiddle with. There should be seperate Kp, Ki, and Kd values - each of these are set specific to the plane (I don't think Kramax Autopilot has auto-tuning which is where the PID controller learns quickly and settles on suitable values). They all combine and affect each other, but I believe Kp may be too large (if it overshoots too much), or more likely Kd not large enough (if it doesn't, but keeps oscillating). This dude knows more than I do, and has some advice. PID controllers are pretty much everywhere, so there's plenty of Youtube videos that describe how they work. Personally, I always use Atmosphere Autopilot, because it's magical in it's ability to make planes fly really smoothly. For "fixing" any plane under manual control you just turn it on with "P" and it magically works (after a few seconds of slight oscillations). It also does what's called "Moderation" which basically means your movements won't kill your Kerbal with high G maneauvers (you can turn that off if you need to do acrobatics or for drones). Under the hood it's more complex, because it's got PID auto-tuner swhich works for any aircraft in any situation (if it's possible to stabalize). It has similar autopilot features to Kramax: