Ranger

I am having the same issue. I think that the reason we are not seeing the orbits is that, well, they are probably under the surface. Also, just to point out, with the values the way they are, you can not place the sat in the orbit and have it register as complete. I tried to have a look and see if I could figure out where those number were to change them, but did not have any success. Looks like the contract is generated with an equation based on the targets diameter, and I could no find anywhere in the save file where it could be tweaked, although I could have missed it. I am putting my current moon constellation plans on hold until there is a fix.

I would just like to point out that this is a FREE program, worked on by VOLUNTEERS. Yes, it has it's bugs. Just about no program out there more advanced then "Hello World" is bug free. But it does generally work, and it does so on all three major OS's. As a Mac user, even having to use Mono, that is an amazing feat, particularly for freeware. If you want to have the problems that you are experiencing fixed, then provide the information that they need to fix them. Exactly what mods is it happening with? Is it always the same ones, or does it change every time? Does it work after you re-start CKAN? Exactly what errors (as in exactly what wording) is getting thrown up? Things like that. You can post here, or, even better, on the Github error reporting page. And please do so politely. Because it is posts like yours, with that attitude, that may convince the people that provide us with this tool that so many of us have come to depend on to stop working on the program at all. And then not only would the bugs not get fixed, but eventually it would become unusable to EVERYONE, and we would all be back to updating out mods manually.

That is interesting. That is the exact copy and paste of what I put in, except that I have a different folder name for the version. Is CKAN in your KSP_osx folder? Again, assuming that you have not changed the name of the folder. Also, it just occurred to me, are you using the Steam version? If so, you may need to change the path. I download direct from Squad and then move the unzipped KSP folder to my Applications folder, so my path may be different if you use Steam.

No Problem. Have fun!

You do not even need to do that. Put CKAN in the same folder as your KSP.app. For example, assuming that you did not change the name of the folder after unzipping it but you did move it to the Applications folder, if you go into "/Applications/KSP_osx/" Then you type in : mono /Applications/KSP_osx/ckan.exe You do not need to cd to it. CKAN will check to see if there is a KSP.app in the folder that it is in first, and if there is you will not have to manually find it.

It works fine for me. I have CKAN in the same folder as KSP, and have never had to select the program like that.

With the way that KSP is set up for Mods, I do not think that you could do that easily, at least using an external program. You might have an easier time asking for Mod Manager to add that functionality, or even get Squad to build it in. For right now, your best bet may be to just have a stock KSP set up in a separate folder. When you want to play stock, you open the clean version. When you want to play with mods, you open the other. You will have to have a version of the game (each with it's own CKAN) for each "profile", but it would be quicker then what you are currently doing. That is what I currently have.

Unfortunently, the only way to start it up is through the Terminal, which is under Applications>Utilities folder, if you have never had to use it. Then type in: mono $path/ckan.exe So, since CKAN should be in your KSP folder, assuming that you have not changed the name of the folder and it is in your Applications folder, it should be: mono /Applications/KSP_osx/ckan.exe It should start up after that. The interface can be a bit wonky at times, and it looks like Windows, but it does work.

There is a filter that shows new mods. Just select "new in repository" from the filter list. However, if we can not have the "flag for watching" option that I remember being discussed a while back, an easier to implement option of an "updated" filter would be helpful for times like this, where so many are moving up from 1.0.5 to 1.1. For people like myself that are going with a clean install, and so do not have anything installed to flag as needing to be updated, having a listing of all the mods that have been updated since the last time CKAN was run would be helpful to see when that one mod that we have been waiting on has finally been updated so that it can now be installed.

No worries.

I do not think that this is what the OP was asking for. In order for that to work, they would have to install the mod first. They are asking for a way to mark a mod for possible future installation, not install it now. They are worried that they will probably forget about a mod in the future. They mentioned a manual text file as a work around to remind them to consider a mod later.

Of all the...! I just tried this, and it fixed the problem that I have been having since December with CKAN not starting up! Thing is, I thought that I had tried a totally clean install of KSP and CKAN in a new folder and it had not worked either. Oh well. At least it is working now. Not that it will do me much good with the current situation.

I just checked my own. There is nothing beyond the "share" directory. There is a folder for another game there, but no "applications"

I am just wondering if there is any update on this issue. I have not seen anything further (at least publicly) since. I am doing things manually for now, but I would much prefer to use CKAN. I am also not sure if anyone else is having this issue or if it is just me.

Thanks As I said, the CKAN window flashes open for a brief moment, usually under a second, and then it quits. I just tried using a left over version that I had in a previous KSP version, and it did pop up with an update. I refused, and then the same thing happened. So it may be an OS update issue...

Here is the video link. You have to wait for the second round at about 0:22 to really see what I am talking about Actually, it reminds me a bit of some of the kerbal rockets that I have launched in previous versions, when the solar panels drop off on launch.

OK, THAT makes a bit more sense. I will see if I can get a video posted here when I get home, assuming that no one else beats me to it...

Oh, I know that ice breaking off is normal. I just am not used to seeing them quite as big, or going on as long. I am not sure of the size of the rocket, but a lot of these pieces seem to be at least a couple of meters to a side, and they were still coming off, in the same size, several seconds after it cleared the tower...

I saw a bit about this on the news this morning. I had a look and did not find anything posted about it here. Apparently China launched a science satellite to look for Dark Matter. I am currently at work, so I can not find/post a vid, but or even look very deeply into it myself, but here is an article about it. http://www.nasaspaceflight.com/2015/12/chinese-long-march-2d-lofts-dampe-a-dark-matter-investigator/ From the vid that I did see about it on the news, however, one thing that I noticed is that there seemed to be a LOT of ice breaking off, and in really big chunks.

Having another issue. For the last few days, whenever I try to start ckan, it flashes open for a second or so, and the it quits. The following is what is left in my OS X Terminal. I can not remember if it coincides with the last update of either ckan or OS X. Anyone having the same issues? mono /Applications/KSP_osx\ 105\ unity\ ckan/ckan.exe 3971 [1] ERROR CKAN.URLHandlers (null) - There was an error while registering the URL handler for ckan:// - Could not find a part of the path "/Users/username/.local/share/applications/mimeapps.list". 3994 [1] ERROR CKAN.URLHandlers (null) - at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, FileOptions options) in <filename unknown>:line 0 at System.IO.FileStream..ctor (System.String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, System.String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) in <filename unknown>:line 0 at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare,int,System.IO.FileOptions,string,bool,bool,bool) at System.IO.StreamWriter.CreateFile (System.String path, Boolean append, Boolean checkHost) in <filename unknown>:line 0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize, Boolean checkHost) in <filename unknown>:line 0 at System.IO.StreamWriter..ctor (System.String path, Boolean append, System.Text.Encoding encoding, Int32 bufferSize) in <filename unknown>:line 0 at System.IO.StreamWriter..ctor (System.String path) in <filename unknown>:line 0 at (wrapper remoting-invoke-with-check) System.IO.StreamWriter:.ctor (string) at System.IO.File.WriteAllLines (System.String path, System.String[] contents) in <filename unknown>:line 0 at CKAN.URLHandlers.RegisterURLHandler_Linux () in <filename unknown>:line 0 at CKAN.URLHandlers.RegisterURLHandler (CKAN.Configuration config, IUser user) in <filename unknown>:line 0 Newtonsoft.Json.JsonReaderException: Unterminated string. Expected delimiter: ". Path 'available_modules.ContractConfigurator.module_version.['1.1.1'].abstract', line 46027, position 72. at Newtonsoft.Json.JsonTextReader.ReadStringIntoBuffer (Char quote) in <filename unknown>:line 0 at Newtonsoft.Json.JsonTextReader.ParseString (Char quote) in <filename unknown>:line 0 at Newtonsoft.Json.JsonTextReader.ParseValue () in <filename unknown>:line 0 at Newtonsoft.Json.JsonTextReader.ReadInternal () in <filename unknown>:line 0 at Newtonsoft.Json.JsonReader.ReadAsStringInternal () in <filename unknown>:line 0 at Newtonsoft.Json.JsonTextReader.ReadAsString () in <filename unknown>:line 0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.ReadForType (Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonContract contract, Boolean hasConverter) in <filename unknown>:line 0 at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject (System.Object newObject, Newtonsoft.Json.JsonReader reader, Newtonsoft.Json.Serialization.JsonObjectContract contract, Newtonsoft.Json.Serialization.JsonProperty member, System.String id) in <filename unknown>:line 0

I am assuming that you are on a Mac and recently updated to 10.11, since I had the same issue when I did so. See my post here to see the fix that I found: http://forum.kerbalspaceprogram.com/threads/100067-The-Comprehensive-Kerbal-Archive-Network-%28CKAN%29-Package-Manager-v1-14-3-27-Sep-2015?p=2242469#post2242469 If my assumptions are off, well, maybe it can help you to figure it out.

Yes, /usr/bin does exist. And as for reporting, the person that posted the message that caused me to try this route said that he has done so. Switching back the permissions, I can see that and even even agree with it. I just was not sure about mono working afterwards. But I switched the Admin group from "Read & Write" to "Read only" (In case I need to unlock it again for updates), and CKAN worked fine. I will report on any issues with updates when it comes up. And here is the result of the echo command: /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin$

I looked around a bit on the Mono mailing list/forums. Found the issue. Hope that you do not mind that I will explain the fix here for others. Apparently when you try to run the Mono installer, it tries to install to /usr/local/bin/. However, the "bin" directory does not exist by default in El Capitan. And the installer will not create it for some reason. So you need to manually do so before you run the installer. It is a hidden and locked directory, so you will need admin access, but since the installer also need an admin password, that should not be an issue. However, I will give detailed instructions in case someone that does not normally do things like adjusting permissions needs to fix this issue. 1) In the Finder, Select the Go menu, then Go to Folder... 2) Type or copy in /usr/local/ and hit "Go" 3*) When it opens, right- or control-click in a clear area of the window, and select "Get Info". This is also available if you have the window selected under the File Menu. (optional) If it is not already expanded, click on the little triangle beside "Sharing and Permissions" so that it is pointed down and that area of the window is expanded. 4) In the lower right corner of the Get Info window, click the lock icon and then enter the admin password. 5) Then to the lower left, select the "+" button. This will add who can make edits to the "local" directory 6) I would suggest just selecting "administrators" in the dialog box that opens up, as that will prevent users that do not have admin access from doing anything with a system directory. You can also just select your account, which will prevent anyone else from doing anything. Then click "OK. 7) When whoever you select shows up in the "Sharing and Permissions" area, change the "Privliege" drop-down to "Read & Write" You can now close the Get Info window. 8) Back in the "Local" window, either right/control-click again or go the the "File" Menu again and select "New Folder". Name this folder "bin" You can now install Mono normally. It should install in this new directory, and should run normally now. *Note that I had done the unlocking of the directory as part of my experimenting to get the installer to work. It MAY not be necessary, but I know that it will work, so that is what I am explaining. You can try skipping to step 8 at this point, but it may or may not allow you to create the directory, and if it does the installer may not be able to write to it.

Sorry for the delay, I have been AFK for a few days I kind of figured that it was a problem with the actual Mono install and not with the mod, but I figured it was worth a shot to ask if anyone else had had the same issue after the 10.11 update. I tried the "mono -h" and I did indeed get the same error.

Has any other Mac users had any issues since 10.11 dropped? I had to do a format to get it to install (long story) but I can not seem to get Mono to work since. I have tried both version 3.12.1 as noted on the plugin user guide and 4.0.4.4, which is a "preview package" which should work with 10.11, but I still get "-bash: mono: command not found" when I try to start up CKAN Anyone have any suggestions?