Frank Einstein

I'm currently playing on KSP v1.7.1, pretty much all of my mods seem to be working fine right now but I just tried installing a ground station with a few experiments but it didn't want to connect to KSC even if there's a relay just beside my experiments... (The relay is connecting to KSC but the ground station stays unconnected.) I read on this forum this might be caused by Remote Tech. I also read that even if the ground station was connecting, it is so buggy on KSP 1.7.1, it's just better not using ground stations / experiments. (Apparently because of a huge spam of error messages?) If I update KSP to 1.7.3, are the ground stations going to work properly? I'm also wondering if it would be easy to create a mod to fix the error spam issue? Thank you for you support. PS. I didn't update KSP yet because I already had many problems to make everything work properly with version 1.7.1, I'm a bit tired of debugging and reading logs right now... lol PPS. I'm using Remote Tech 1.9.3

I couldn't find it at: https://github.com/linuxgurugamer/FMRS but a quick google research took me there: https://github.com/linuxgurugamer/RecoveryController I just finished compiling the modification, I just need to test it now.

I'd like to modify the source code for being able to load/save the mod to use by default inside a txt file but I can't find the sources of RecoveryController anywhere on GitHub... Any help? Edit: Nevermind, I just found it. Apparently, It's not in the FMRS folder.

Thank you!

Is it possible to disable or change the Hotkey of this mod? (Alt-0) I am using the mod "Action Groups Extended" and EVE's hotkey is bad for this. If there is no easy way to disable the Hotkey, can you tell me what file in the source code do I need to edit? Please not that I'm not complaining here, I really like the mod! Thank you for your support!

Hi! When I'm docking two vessels together, the actions from both vessels are getting merged together, which I guess is normal in this situation, but when I undock my vessels, my action groups are not reverting back like it was before docking. Some actions are also overwritten by the actions of the other ship (when two actions are on the same key). Every time I'm docking / undocking, I have to configure everything again (and again). Is there something we can do about this? If we could Import / export actions groups to different files for each ship, I think it could fix most of this problem. It could be also very useful in many situations! This is still one of my favorite KSP mod!

When you say "it looks like something is breaking when it tries to read the config settings" do you mean ".\GameData\kOS\Plugins\PluginData\kOS\config.xml" ? And can you please tell me which line(s) in my log file told you about this "config settings" problem? I started playing KSP very recently on version 1.2.2 so my game save is not migrated from an older KSP version. I always try to use the last release of addons compiled for KSP 1.2.2 but some of the best addons aren't updated yet for 1.2.2 so in few cases I'm using the latest old version (if it's still working on 1.2.2) or I'm using an unofficial recompiled release. I guess it could be the cause of this kind of bug. (Example: I'm using "Infernal Robotics" for KSP 1.1.2 recompiled for KSP 1.2) I'll try to temporary uninstall some suspected addons to find which one is the culprit of this incompatibility, assuming it's caused by an other addon... (The problem here is that KSP is taking a long time to load so it's going to take hours to do this for all my 80 addons...) I'm just an amateur programmer (batch, bash, python, javascript, c++ and I'm new to C#) but I'll do my best to find this annoying bug because I really like your addon. I never made a KSP addon from scratch but sometimes I like to modify and compile some KSP addon's source codes. I'm using "SharpDevelop" for editing and compiling my KSP addons. Also, I'd like to know if there is some addons that are known for causing problems with kOS. Again, thank you for you help.

Thank you for your reply. I think it is important to say that I am using the last version of kOS (1.0.3) with the last version of KSP (1.2.2). I am using around 80 addons with KSP, so I guess that my kOS bug is much probably coming from a compatibility problem with an other addon. I tried to look in the log for other errors but there is so many it's not an easy task. I have to mention every of my addons are all working fine despite of many errors in the log file. kOS is also working fine, I can run scripts, copy them, delete them, etc... The only problem is the toolbar button that is not working in any of the scenes. (Space Center, VAB, Ship, etc...) I found that the bug that doesn't allow me to paste in the kOS terminal comes from the MechJeb2 addon (MuMech), which is the last release. If it can help you to find the bug about my non-working toolbar button, I uploaded my full log file on Mediafire. During this log, all I did is open my last saved game, clicked the kOS toolbar button a few times, then I went into a ship with a kOS module and I tried to paste some text into a kOS terminal, then I closed the game. KSP_2017-04-09_00h48.log

I really like this addon but I have 2 problems with the last version of kOS... 1 - When I click on the kOS icon, nothing happens. It's not working either with the stock toolbar and the blizzy78's addon. 2 - I can't paste any text in the kOS terminal. Can I do something to fix one or both of these bugs? Here is the errors I get in KSP.log When I press the Toolbar button: [EXC 00:43:44.895] NullReferenceException: Object reference not set to an instance of an object kOS.Screen.KOSToolbarWindow.Open () kOS.Screen.KOSToolbarWindow.CallbackOnClickBlizzy () kOS.Screen.KOSToolbarWindow.<AddBlizzyButton>b__39_0 (kOS.Screen.ClickEvent e) kOS.Screen.Button.clicked (System.Object realEvent) Toolbar.Command.click () UnityEngine.Debug:LogException(Exception) Toolbar.Log:log(LogLevel, Exception, String, Object[]) Toolbar.Log:error(Exception, String, Object[]) Toolbar.Command:click() Toolbar.Button:click() Toolbar.Button:drawInToolbar(Rect, Boolean) Toolbar.Toolbar:drawButtons() Toolbar.Toolbar:draw() Toolbar.ToolbarManager:OnGUI() [ERR 00:43:45.424] [Toolbar] [ERROR] error while handling click event: kOS.kOSButton When I try to paste some text inside of a kOS terminal: [EXC 01:19:26.981] Exception: Can't access internal member 'GUIUtility.systemCopyBuffer' it may have been removed / renamed MuMech.MuUtils.GetSystemCopyBufferProperty () MuMech.MuUtils.get_SystemClipboard () MuMech.MechJebCore.Update () Thanks in advance.

The compiled addon for the last version "1.6.0 Alpha 4" is not in the releases. Is it possible to upload it? Thank you!

KSP is now giving me a KSP.log of more than 2gb after playing less than 1 hour... I tried to use the -nolog parameter but it's not working, obviously... I didn't understood why it wasn't working until I read this thread... I was thinking that -nolog was meaning "no log"... Before, this file was growing to maybe something like a 100mb for each game session but today after I installed 5 or 6 addons at the same time, this KSP.log started to go crazy. I guess there is probably one of these addons that is spamming errors in the log file. I don't know if it's errors or warnings because I didn't really wanted to open this 2.5gb file with notepad! Now I'll have to do some tests to find which addon is causing this excrements... It sucks because the game and all the new and old addons are still working fine even with so many errors in the log file! Thank you anyway for clarify this, I just lost about an hour trying to figure out why this -nolog parameter wasn't working for me...

I just installed this addon, I really like it and everything seems to work correctly excepting this... Is it normal that my Kerbals are needing oxygen tanks when they are on Kerbin? (I read on the Wiki of "TAC Life Support" that when you are on Kerbin, you can use the oxygen from the atmosphere. No need to have oxygen tanks? ) I have a mobile processing lab with a big air intake and it's having a lot of electricity but the two Kerbals inside still don't have oxygen to breath! The lab is right beside the runway at KSC... What am I doing wrong?!