marauder13

Thank you both for the responses. I will set up a couple of landing missions and see if that is what will happen. Since I am relatively new to the mod, this is helping me to explore it in a more constructive manner. With this reply, I guess it is time to make a move toward base building.

Darkherring, thank you for your reply. I tried what you suggested with the forced transfer, but all I get when I pulled that up on the Dashboard is "No other vessels, or no crew present." This is incorrect on both counts as the space station has a crew of four and the supply vessel a crew of three. Both vessels were once again approximately 75m apart when I got that message. Nothing has changed since my last attempt just prior to posting. Oh, I am using the 1.6.1 release of KSP, along with the 1.1.0.0 versions of the USI mods. I knew there was something I forgot to add to the original post.

G'Day everyone. I hope this is the right place for my questions. If not, please let me know the proper place and I will head off there. I am a new player of the USI mods, and I am having a little difficulty with logistics. From what I have read, a Consumer module can pull material from a Warehouse module if they are no more that 150m apart. All figures quoted are at the time the vessels are supposed to be able to transfer supplies. I have an orbital space station over Kerbin, which has an operational Tundra Pioneer and Logistics module attached with a pilot within. Also as a part of the space station is a life support tank, with 446/4500 supplies. I have launched a rocked with a 2.5m Kontainer Tank, with 4455/4500 supplies within. Both tanks are set with Local Warehouse On. According to all I have read, when these get within 150 metres, the space station should start pulling supplies over from the supply vessel. I have had the two ships at 75m +/- 5m, and no transfers have occurred. It is obvious to me that I have missed something somewhere in my reading, but I am at a loss as to what it is that I have missed. Does anyone have any ideas as to what I am doing wrong, or not doing right? Thanking everyone in advance for their time, M13

G'Day Brigadier, I know the question was sort of Ckan related, but since I noticed the limit when I looked at the details that came up, I thought it was more relevant to Roverdude than the author of Ckan. I meant no disrespect to Roverdude and his efforts, but I was simply asking if it was something that he overlooked, or it was easily changed. If it was not the case, then I would find a work around, since other people have said elsewhere that the MKS mod worked well with 1.6.x. I missed the reference to the constellation build, and I am sorry for asking the question that I did having missed that. I will do my best to be more thorough in future before posting any questions. Finally, no, I was not aware of that functionality, and since you have mentioned it, I have found it, and tinkered with it and got the result that I was after. Thank you for point that out to me. Finally, I would once again like to apologize for any mistakes, disrespect or other errors on my part with the asking of my question. I have the utmost respect for all the mod authors of all the games I play, not just KSP. I try to find answers before I ask questions, and when I do, I try to be as polite and understanding as I can because of the time and effort people like Roverdude put into their work. So, now, fully armed with new info, I shall go forth and use it for the greater good of Kerbal Space Exploration. Thanking everyone for their time, consideration and answers, M13

G'Day Roverdude, I tried to load MKS via Ckan, and it cached it. On further investigation, I saw that MKS is rated up to 1.4.9, and I am using 1.5. Is it an easy thing to change to flag it, and other of your Mods, to be compatible with KSP 1.5.x? I can install it manually, but I would prefer to use Ckan where possible. Thanking you in advance for your help, M13 P.S. Merry Christmas to you & your family. Have a good one

OK, I confess I may be a little slow concerning these kind of applications (Mod Install/Admin), as it is the first of its kind I have used. The Mod Admin application is correctly detecting that some of my mods are out of date. Yet, I can't find a way to get the application to download the latest version from the source site. I'm not aware of any manual process from what I have been able to find in my explorations, nor any automatic ones. I have probably overlooked it, but for the life of me I can't find it. Any tips, pointers, suggestions, etc will be gratefully received. Thanking you in advance for your help, marauder13

Sorry MacTee, it's me again. I have been trying to download mods via the internal browser from the KSP Forums. When I tried to download the Kethane Mod from /threads/23979, I got the following error message listed below. Once more, thanking you in advance for your time and assistance. Edit: I tried to download Kerbal Crew Manifest from /threads/60936, and received the same error message. I thought giving you this further information could prove useful tracking down the cause of the error. See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Net.WebException: The remote server returned an error: (404) Not Found. at System.Net.WebClient.DownloadFile(Uri address, String fileName) at KSPModAdmin.Utils.wwwHelper.DownloadFile(String downloadURL, String downloadPath, DownloadProgressChangedEventHandler downloadProgressHandler) at KSPModAdmin.Utils.KSPForumHelper.DownloadMod(String downloadURL, ModInfo& modInfo, DownloadProgressChangedEventHandler downloadProgressHandler) at KSPModAdmin.Views.ucModSelection.HandleModAddViaKSPForum(String kspForumURL, String modName, Boolean installAfterAdd, DownloadProgressChangedEventHandler downloadProgressHandler) at KSPModAdmin.Views.ucModBrowser.tsbDownloadMod_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- KSPModAdmin Assembly Version: 1.4.0.12 Win32 Version: 1.4.0.12 CodeBase: file:///E:/Games/KSPModAdmin/KSPModAdmin.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.34003 built by: FX45W81RTMGDR CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Deployment Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Deployment/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- Microsoft.mshtml Assembly Version: 7.0.3300.0 Win32 Version: 7.0.3300.0 CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

MacTee, I just downloaded this version, and so far so good. Thank you for the fix. Some feedback - the scan feature appears to be picking up every directory within the parameters specified, rather than just those with KSP in them. For me, this is not a big issue, but one worthy of bringing to your attention for future work. Once more, thank you for all of your work, and the swiftness of your reply and creation of a fix. M13

G'Day MacTee, I have just downloaded version 1.3.11, unzipped the application, and ran it. It successfully detected both of my 0.23.5 versions of KSP, yet didn't find the 0.24(x64) version that was in the same folder as the other two that were detected. When manually attempting to add the latest version, I got the following message from the mod manager - "This is not the KSP install path." The 0.24 version of KSP is working, as I have run it. Is there any reason the Mod Manager is failing to recognize the new version? Thanking you in advance for your time and assistance, marauder13