JPLRepo

v0.12.7 has been released. It only works on KSP 1.2.2. If you also use DeepFreeze you need v0.23.2 of that mod as well. Fixes a whole bunch of stuff. See the changelog in the OP. I also fully expect that this will break CKAN installs in a bad way. I have raised a request to get that fixed. Expect it to take a day or two to get fixed.

V 0.23.2.0 released for KSP 1.2.2. Changes the way it integrates with TAC LS. You must have TAC LS 0.12.7 if you also use that mod. @cicatrix - should also fix your EC issue. See Changelog for other changes.

I just made an update to above instructions. It's important you define and initialize your GameEvent EARLY so that ModB will find it. So it's a good idea to define it and then init it New say in Start of a KSPAddon MonoBehaviour at MainMenu for example.

Unless you backed up your previous install manually you cannot. Its a good habit to have. that said pretty much all mods that worked in 1.2.1 should work in 1.2.2 with no changes. If they are using AVC then yes they will complain about not being compatible but it should be fine to just accept these msgs.

What USI are you referring to? If you are talking about USI LS - then that makes no sense at all. There can be only one! Life support. If you are referring to other USI mods then I believe some? MKS/OKS? have config files and support TAC LS. But I personally don't use any USI mods. So maybe someone who does can help answer that a bit better. I'm about to fix all of that...

The 1.2.2 Version of the Docs has now been updated.

Yeah sorry about that. the official doc has now been updated.

No it was never meant for 1.1.2

No it did not change from 1.2 and 1.2.1. Localization is not part of 1.2.2

1. Yes it has that name. 2. No you cannot. It was a bug in the vessel detection for the KSC launchpad (when you try to launch it checks if the launchpad has a vessel on it already). The bug was the two were using a name internally that was the same. So when you tried to launch at the KSC and you had a vessel sitting on the launchpad at Baikerbanur it detected it by mistake.

Now that KSP 1.2.2 is out guys and I have holidays from my day job starting this Friday I will be able to finish this planned additions and update it next week for 1.2.2. So hang in there.

In KSP 1.2.2 there is an extension for GameEvents that allows mods to register their own GameEvents and for any Mod to find and register a callback for said GameEvents. How to use (example): Define your GameEvent as a static in Mod A: public static EventData<Part, ProtoCrewMember> onKerbalFrozen; and Initialize it somewhere early before ModB tries to find and register it. onKerbalFrozen = new EventData<Part, ProtoCrewMember>("onKerbalFrozen"); Find the GameEvent and register a callback in ModB: private EventData<Part, ProtoCrewMember> onKerbalFrozenEvent; ... //in say Awake or Start: onKerbalFrozenEvent = GameEvents.FindEvent<EventData<Part, ProtoCrewMember>>("onKerbalFrozen"); if (onKerbalFrozenEvent != null) onKerbalFrozenEvent.Add(onKerbalFrozen); //don't forget to remove them in OnDestroy: if (onKerbalFrozenEvent != null) onKerbalFrozenEvent.Remove(onKerbalFrozen); Fire your event at the appropriate time from Mod A: DFGameEvents.onKerbalFrozen.Fire(this.part, CrewMember); ModB callback will be called.

In what version? with what version? no reported bugs.. so can't investigate until someone gives me hard concrete details.

See the post I just did on your thread. Easy work around link added there

Is it Mac Sierra? Just finished posting in that other thread. so there is an known issues with Sierra and a number of threads with how to deal with it. here is one such thread

He said from the website so I'd assume that @tosha meant the KSP store. Could be wrong. Anyway that does warrant its own thread although I'd recommend providing a bit more info first. eg: what OS are you running? And a log file. Your problem sounds similar to the Mac Sierra problem, but if you are not on a Mac it may be any number of things.

Yes it appears USI LS has been changed significantly. As I don't use it I hadn't kept up with it, and after all, I wrote my mods for my own personal use.. So adding other mod compatibility is just when I have time. That said I've raised a ticket so one day I will get around to fixing it. https://github.com/JPLRepo/AmpYear/issues/55 Well I can't explain that one. According to the ScanSAT settings for that part the EC usage is 1 unit. Given physics steps the 0.02 is correct. I have no idea why it's drawing more than that. Will take some time to investigate. https://github.com/JPLRepo/AmpYear/issues/57 ...and one more bug that has been brought to my attention. RemoteTech integration is currently broken as well. https://github.com/JPLRepo/AmpYear/issues/54 I'll see how many of these I can fix once 1.2.2 is released.

Landing gear works in 1.1.3. I have not released a 1.2+ version yet as I need people with more time than me to help re-balance the lander and ranger in atmospheric flight.

Glad you like It, posts like this are much appreciated. Just to clarify there is very little of the original mod code (in fact I don't think there is any, as I have rewritten and expanded this mod over the years) and one part model that I inherited from the original author.

My youngest son had a go.

Sorry to hear you are having problems. As you have a new Mac I'm assuming it's running OSX Sierra. You say you are having problems with the installer??? but then talk about building assets definitions (which would show when you are running KSP rather than installing) The installer on mac presents you with a screen that essentially you drag the KSP folder to your Applications folder which then just copies the files. If that copy is failing the things that come to mind for you to check are: 1) Bad download? - Try to download again? 2) Are you doing this using an Admin account under OSX? (Check your settings - Users & Groups that your login is an Admin account). - Or setup admin password in security settings and it should prompt you. 3) You have enough disk space? would assume so as it's a new PC. Failing that, when it is copying/installing and fails. Does it give you any codes with a failure message? and/or have you checked the log for any errors? Or are you actually having problems Starting/Running KSP after you have installed it? If in fact your issue is with Running KSP there are known issues with OSX Sierra. Here are some workarounds for that:

All versions of KSP (and it's not just KSP) have this problem with OSX Sierra. The problem is with OSX Sierra GateKeeper security changes. OSX Sierra GateKeeper will quarantine any downloaded app. It randomly moves the files to a temp folder when you run it. This causes problems for KSP and Unity apps. By copying the folder permissions are changed and the quarantine removed. and then moving them back again. You can then execute the app. Same goes for downloaded mods. It's being looked at.

Hi folks. Yes there was an upgrade attempted on the forum software that failed. It seems as a result of this some profile pics and attachments have been lost for some users. Most likely affected pictures would be only those in the past week or two. Those affected will have to re-import their avatar picture as there is no way to recover them. The failed upgrade is being investigated and won't be attempted again until the cause is found, identified and fixed. Sorry for the inconvience caused.

Sorry? KSP 1.2+ is completely playable on OSX Sierra. Follow the workaround in the link I posted above.