linuxgurugamer

I recommend you do one of the two things: Install your mods using CKAN. This will install any dependencies, and, depending on your option, not install the MiniAVC.dll files. If it does, it will also install ZeroMiniAVC, which will delete them for you automatically Install ZeroMiniAVC on your own, it will do the removal for you, and doesn't impact the game experience The short answer is yes, if you insist on doing things manually, you can (and must) remove all the MiniAVC.dll files, otherwise they will break the game

New release, 0.0.2.4 (included unreleased 0.0.2.3) 0.0.2.3 Added toolbar button, only available at space center Added GameNotes for SpaceCenter Allows entry of new gamenotes Made font settings global instead of per-part Make skin global Added font settings to Stock Settings window Refactored a bit, broke classes out into individual files Added a few more events to be autologged, default is false Added second column in stock settings to control which events get logged 0.0.2.4 Fixed bug where vessel log was not being saved to save file Updated current crew report in log to show unmanned if no crew Changed name for vessel log files from a date/timestamp to a compressed guid (need to use guid for uniquness) Added check for VesselNotesLogs module on the vessel at launch, if not there, prompts the user added code to sanitize the filename which is based on the vessel name Fixed memory leak Fixed date calculations to work with non-standard days and years (usually changed via Kopernics) Added window to display all logs, and display selected log Moved the Font Size buttons to upper left, and the S (for Skin) and X (for exit) to upper right

@SpaceTigerDoes this still work in 1.12.4?

MiniAVC .dll is not in this mod, and it doesn't have any dependencies

that's what I was wondering, that's your process although it seems you do it by hand

New release, 2.8.3.5 Fixed path for loading files (broken by new launcher)

New release, 1.7.0.1 Fixed path for loading files (broken by new launcher)

New release, 0.20.0.3 Fixed path for loading files (broken by new launcher)

New release, 1.1.6.6 Added code to save settings on every scene change 1.1.6.5 Fixed path for loading files (broken by new launcher)

New release, 2.0.4.3 Fixed small error in previous fix in path for loading files (broken by new launcher)

New release, 2.21.5.3 Fixed path for loading files (broken by new launcher)

New release, 1.8.3.4 Fixed path for loading files (broken by new launcher)

New release, 0.6.18.4 Fixed path for loading files (broken by new launcher)

New release, 0.0.1.3 Some minor code cleanup

New release, 0.3.1.3 Some minor code cleanup

New release, 1.9.10.2 Fixed path for loading files (broken by new launcher)

new release, 1.1.0.3 Fixed path for loading files (broken by new launcher)

New release, 1.1.1.2 Fixed path for loading files (broken by new launcher)

yes

Just curious, what's your process for committing, etc? I know that there is a mod somewhere which keeps multiple versions/iterations of a vessel, don't remember rhe name of it right now

New release, 2.0.4.2 Fixed path for loading configs (broken by new launcher) Fixed memory leak caused by not removing callbacks

Here is the recompile, I was never happy about it, so never bothered to do a release: https://github.com/linuxgurugamer/HopperGuidance/releases/tag/0.3.0

New release, 0.8.0.9 Fixed issue with filepaths caused by new KSP launcher

New release, 2.0.0.9 Fixed invalid file path caused by new KSP launcher

First, your welcome Second, I'm not the developer of this mod, just maintaining it. That being said, I don't think the shaders can be moved/imported to this mod without some work. Maybe if someone else gets the urge, but for me, this is in maintenance mode