Jump to content

phoenix2004uk

Members
  • Posts

    7
  • Joined

  • Last visited

Reputation

7 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I just returned to the game having not played since 1.5 and noticed the same exception spam According to some info from the Contract Configurator git hub issues (https://github.com/jrossignol/ContractConfigurator/issues/672) it is caused by some AGENT definitions not having a title attribute which was introduced in KSP 1.2 for localization. I fixed the exception spamming in my game with these 2 steps: 1) Manually editing and fixing the persistant.sfs save file for all current and completed contracts 2) Adding a small ModuleManager config to fix the AGENT definitions that cause the exceptions The Details 1) Find all instance in the save file with a null agent string. Using an editor like Notepad++ I searched for "agent = [\r\n]" as a regular expression, this will find all instances of the null agent within all the CONTRACT nodes. You should find there is an agentName attribute that is set correctly, so I copied the agentName value as the agent value. Basically changing this: seed = 1927166245 state = Offered viewed = Seen agent = agentName = Field Research Team deadlineType = None Into this: seed = 1927166245 state = Offered viewed = Seen agent = Field Research Team agentName = Field Research Team deadlineType = None For every found instance. Might be a good idea to backup your save file before doing this, just to be safe. If you are far into a career game, you might have lots of entries to fix. 2) Save the following ModuleManager config in your GameData folder somewhere, and it will fix all the AGENT definitions that are missing the title attribute @AGENT:HAS[~title[]]:FINAL { title = #$name$ } Short and simple, find all AGENT nodes that have no title, add a title and set it's value the same as the AGENT name. Reload your newly edited save file, and the exception spam should be gone. At least, it was in my case.
  2. I've been putting together my own contract pack, and i'm not sure if i've found a bug in CC or in KSP itself relating to progress nodes. It would seem that the progress nodes are not picking up whether a particular 'achievement' has been earned by manned or unmanned vessel. For example, I created some test contracts on clean installs of KSP 1.4.4/1.4.3/1.4.2 (but i stopped there) to confirm if this was being caused by another other mods - so these installs have only Contract Configurator, Module Manager, and my test contracts installed. A contract should be able to have a requirement of type=FlyBy and checkType = MANNED, but upon completeing a manned (or unmanned) flyby of the targetBody, this requirement is still false. If you remove the checkType from the Requirement, then the requirement is then met. The following image shows the contracts in mission control, the only 2 available contracts are those without the checkType option on the FlyBy requirement, all the other contracts (which were just different variations on the same test contract) are not available due to the MANNED or UNMANNED type requirement not being met: https://imgur.com/7rcaq1y Here is an example test contract: https://pastebin.com/YjnNTmux Here is the save game file from the clean install (KSP 1.4.2): https://pastebin.com/0uB0GHng If you look in the save file, you can even see that the progress is being recorded by KSP, by looking in the ProgressTracking SCENARIO section So is this an bug in CC? (From what I could work out from looking through the source, this didn't look like the case - but i can't say for sure), or is it a bug in KSP where the progress data is not being correctly provided by the KSP API. There are no errors or exceptions in the KSP.log file either (besides the usual warnings from stock squad stuff): https://pastebin.com/7jefxjj4 *edit: this also seems to be the case in a KSP 1.3.0 install
  3. It's a common courtesy, for the huge amount of free time and devotion the modders give to this community, shouldn't need to be a rule For an update on any mod-related release schedule, please read this wiki page to know when to expect an update: https://developer.valvesoftware.com/wiki/Valve_Time
  4. Hi there, i'm getting some issues with 2 of my installed ContractPacks: BaseConstruction (I have posted the errors related to it in it's own thread), and UnmannedContracts. There seems to be a few errors with your contracts as follows, all relating to minmus Below is the snippet from my KSP.log showing the errors with UnmannedContracts. Also, pressing ALT+F10 shows CONTRACT_GROUP[spaceTuxGroup] in red, meaning disabled, i'm assuming due to these errors. (Though I do currently have 3 of the grand tour contracts available for inner planets, outer planets, outer planets and moons [i have also seen the 2.5 TRILLION cash reward for the later, which is a tad extreme in relation to the reputation/science rewards - but that is off-topic from this post] , which is odd if the enture SpaceTuxGroup node shows as disabled? maybe I just misunderstand quite what that means. I digress. [ERR 01:39:41.248] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'FirstUnmannedMinmusFlyby', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.251] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'FirstMinmusImpact', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.254] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'TargetedMinmusImpact', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.257] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'FirstMinmusOrbitalSat', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.259] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'PolarMinmusOrbitalSat', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.262] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'EquatorialMinmusOrbitalSat', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.264] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'KolniyaMinmusOrbitalSat', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.267] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'FirstUnmannedMinmusLanding', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. [ERR 01:39:41.270] ContractConfigurator.PartUnlockedRequirement: CONTRACT_TYPE 'TargetedUnmannedMinmusLanding', REQUIREMENT 'PartUnlocked' of type 'PartUnlocked': Required value 'part' is empty. These errors all apear next to their nodes on the ALT+F10 screen, and highlighted in RED/disabled. I'm assuming though, that I could fix these contracts temporarily by removing the PartUnlocked requirement, until you can release an update to this contract pack with the intended parts.
  5. Hi there, I am also finding that none of the missions from this pack are being offered, there appear to be a few errors in the contract configurations which is causing exceptions to be thrown by contract configurator. I have only 266 of 275 contracts loading from the packs I have installed, there appear to be issues with both the BaseConstruction and UnmannedContracts packs. Here is a snippet from my KSP.log showing the errors being thrown regarding BaseConstruction, however I do not fully understand what I need to do myself to fix these contracts, so i'm hoping you can roll these into your next update. (I just did a search across my whole Contract Packs folder using Notepad++ to find which files these errors seem to be coming from) This doesn't directly impact my current playthough, i'd like to have these contracts available, but it's not the end of the world if it takes a while P.S. I'd have to stitch together many many screenshots to show you the ALT+F10 output. But if it's more helpful to you then i'll do that if you wish. It's mostly green, with some yellow entries all relating to the errors that appear in ksp.log, but since the errors are from the BaseScan section, I assume that is why I get no base creation type contracts, as scanning is surely the first step [ERR 01:39:40.507] ContractConfigurator.ReachStateFactory: CONTRACT_TYPE 'BaseScan', PARAMETER '' of type 'ReachState': targetBody for ContractConfigurator.ReachStateFactory must be specified. [WRN 01:39:40.508] ContractConfigurator.ReachStateFactory: Ignoring failed parameter with child requirements. [ERR 01:39:40.509] ContractConfigurator.ReachStateFactory: CONTRACT_TYPE 'BaseScan', PARAMETER '' of type 'ReachState': targetBody for ContractConfigurator.ReachStateFactory must be specified. [WRN 01:39:40.510] ContractConfigurator.ReachStateFactory: Ignoring failed parameter with child requirements. [ERR 01:39:40.511] ContractConfigurator.ReachStateFactory: CONTRACT_TYPE 'BaseScan', PARAMETER '' of type 'ReachState': targetBody for ContractConfigurator.ReachStateFactory must be specified. [WRN 01:39:40.512] ContractConfigurator.ReachStateFactory: Ignoring failed parameter with child requirements. [ERR 01:39:40.513] ContractConfigurator.ReachStateFactory: CONTRACT_TYPE 'BaseScan', PARAMETER '' of type 'ReachState': targetBody for ContractConfigurator.ReachStateFactory must be specified. [WRN 01:39:40.514] ContractConfigurator.ReachStateFactory: Ignoring failed parameter with child requirements. [ERR 01:39:40.516] ContractConfigurator.ReachStateFactory: CONTRACT_TYPE 'BaseScan', PARAMETER '' of type 'ReachState': targetBody for ContractConfigurator.ReachStateFactory must be specified. [WRN 01:39:40.516] ContractConfigurator.ReachStateFactory: Ignoring failed parameter with child requirements. [ERR 01:39:40.518] ContractConfigurator.ReachStateFactory: CONTRACT_TYPE 'BaseScan', PARAMETER '' of type 'ReachState': targetBody for ContractConfigurator.ReachStateFactory must be specified. [WRN 01:39:40.518] ContractConfigurator.ReachStateFactory: Ignoring failed parameter with child requirements. [WRN 01:39:40.521] ContractConfigurator.Behaviour.ExperimentalPartFactory: The 'add' attribute of ExperimentalPartFactory is deprecated. Use 'unlockCriteria' instead. [WRN 01:39:40.521] ContractConfigurator.Behaviour.ExperimentalPartFactory: The 'remove' attribute of ExperimentalPartFactory is deprecated. Use 'lockCriteria' instead. [ERR 01:39:40.558] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: CONTRACT_TYPE 'BaseCommsLost', BEHAVIOUR 'ChangeVesselOwnership' of type 'ChangeVesselOwnership: Error parsing onState [EXC 01:39:40.568] ArgumentException: The requested value 'ContractAccepted' was not found. System.Enum.Parse (System.Type enumType, System.String value, Boolean ignoreCase) System.Enum.Parse (System.Type enumType, System.String value) ContractConfigurator.ExpressionParser.EnumExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseIdentifier (ContractConfigurator.ExpressionParser.Token token) ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseVarOrIdentifier (ContractConfigurator.ExpressionParser.Token token) ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseSimpleStatement[State] () Rethrow as Exception: Error parsing statement. Error occurred near '*': ContractAccepted ................* <-- HERE ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseExpression (System.String key, System.String expression, ContractConfigurator.ExpressionParser.DataNode dataNode) ContractConfigurator.ConfigNodeUtil.ParseSingleValue[State] (System.String key, System.String stringValue, Boolean allowExpression) ContractConfigurator.ConfigNodeUtil.ParseValue[State] (.ConfigNode configNode, System.String key, Boolean allowExpression) ContractConfigurator.ConfigNodeUtil.ParseValue[State] (.ConfigNode configNode, System.String key, System.Action`1 setter, IContractConfiguratorFactory obj, State defaultValue, System.Func`2 validation) UnityEngine.Debug:LogException(Exception) ContractConfigurator.LoggingUtil:LogException(Exception) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, State, Func`2) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, State) ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory:Load(ConfigNode) ContractConfigurator.BehaviourFactory:GenerateBehaviourFactory(ConfigNode, ContractType, BehaviourFactory&) ContractConfigurator.ContractType:Load(ConfigNode) ContractConfigurator.<LoadContractConfig>d__1e:MoveNext() ContractConfigurator.ContractConfigurator:Update() [WRN 01:39:40.573] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: Warning, values for onState have changed - attempting to load using obsolete values. [ERR 01:39:40.580] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: CONTRACT_TYPE 'BaseCommsLost', BEHAVIOUR 'ChangeVesselOwnership2' of type 'ChangeVesselOwnership: Error parsing onState [EXC 01:39:40.581] ArgumentException: The requested value 'ContractCompletedSuccess' was not found. System.Enum.Parse (System.Type enumType, System.String value, Boolean ignoreCase) System.Enum.Parse (System.Type enumType, System.String value) ContractConfigurator.ExpressionParser.EnumExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseIdentifier (ContractConfigurator.ExpressionParser.Token token) ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseVarOrIdentifier (ContractConfigurator.ExpressionParser.Token token) ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseSimpleStatement[State] () Rethrow as Exception: Error parsing statement. Error occurred near '*': ContractCompletedSuccess ........................* <-- HERE ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseExpression (System.String key, System.String expression, ContractConfigurator.ExpressionParser.DataNode dataNode) ContractConfigurator.ConfigNodeUtil.ParseSingleValue[State] (System.String key, System.String stringValue, Boolean allowExpression) ContractConfigurator.ConfigNodeUtil.ParseValue[State] (.ConfigNode configNode, System.String key, Boolean allowExpression) ContractConfigurator.ConfigNodeUtil.ParseValue[State] (.ConfigNode configNode, System.String key, System.Action`1 setter, IContractConfiguratorFactory obj, State defaultValue, System.Func`2 validation) UnityEngine.Debug:LogException(Exception) ContractConfigurator.LoggingUtil:LogException(Exception) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, State, Func`2) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, State) ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory:Load(ConfigNode) ContractConfigurator.BehaviourFactory:GenerateBehaviourFactory(ConfigNode, ContractType, BehaviourFactory&) ContractConfigurator.ContractType:Load(ConfigNode) ContractConfigurator.<LoadContractConfig>d__1e:MoveNext() ContractConfigurator.ContractConfigurator:Update() [WRN 01:39:40.586] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: Warning, values for onState have changed - attempting to load using obsolete values. [WRN 01:39:40.587] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: CONTRACT_TYPE 'BaseCommsLost', BEHAVIOUR 'ChangeVesselOwnership2' of type 'ChangeVesselOwnership': unexpected attribute 'parameter' found, ignored. [ERR 01:39:40.588] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: CONTRACT_TYPE 'BaseCommsLost', BEHAVIOUR 'ChangeVesselOwnership3' of type 'ChangeVesselOwnership: Error parsing onState [EXC 01:39:40.589] ArgumentException: The requested value 'ContractCompletedFailure' was not found. System.Enum.Parse (System.Type enumType, System.String value, Boolean ignoreCase) System.Enum.Parse (System.Type enumType, System.String value) ContractConfigurator.ExpressionParser.EnumExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseIdentifier (ContractConfigurator.ExpressionParser.Token token) ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseVarOrIdentifier (ContractConfigurator.ExpressionParser.Token token) ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseSimpleStatement[State] () Rethrow as Exception: Error parsing statement. Error occurred near '*': ContractCompletedFailure ........................* <-- HERE ContractConfigurator.ExpressionParser.ExpressionParser`1[ContractConfigurator.Behaviour.TriggeredBehaviour+State].ParseExpression (System.String key, System.String expression, ContractConfigurator.ExpressionParser.DataNode dataNode) ContractConfigurator.ConfigNodeUtil.ParseSingleValue[State] (System.String key, System.String stringValue, Boolean allowExpression) ContractConfigurator.ConfigNodeUtil.ParseValue[State] (.ConfigNode configNode, System.String key, Boolean allowExpression) ContractConfigurator.ConfigNodeUtil.ParseValue[State] (.ConfigNode configNode, System.String key, System.Action`1 setter, IContractConfiguratorFactory obj, State defaultValue, System.Func`2 validation) UnityEngine.Debug:LogException(Exception) ContractConfigurator.LoggingUtil:LogException(Exception) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, State, Func`2) ContractConfigurator.ConfigNodeUtil:ParseValue(ConfigNode, String, Action`1, IContractConfiguratorFactory, State) ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory:Load(ConfigNode) ContractConfigurator.BehaviourFactory:GenerateBehaviourFactory(ConfigNode, ContractType, BehaviourFactory&) ContractConfigurator.ContractType:Load(ConfigNode) ContractConfigurator.<LoadContractConfig>d__1e:MoveNext() ContractConfigurator.ContractConfigurator:Update() [WRN 01:39:40.594] ContractConfigurator.Behaviour.ChangeVesselOwnershipFactory: Warning, values for onState have changed - attempting to load using obsolete values.
  6. Regarding my previous post, after spending a few hours more scouring over google for solutions, I have proven Einstein's definition of madness wrong (trying the same thing over and over and expecting different results). I have no idea, what has happened, but the IR button is now available in the toolbar. I have just deleted and redownloaded both the toolbar mod, and IR. This did not fix the issue, button not available, same exception spam. I deleted the toolbar-settings.dat file. This did not fix the issue. I removed all mods except IR and toolbar. This did not fix the issue. I created a new save. This did not fix the issue. *smashing head on keyboard* I removed the toolbar DLL to go and do some messing around in sandbox mode using rockets and rotatatrons to try slingshotting kerbals across the ocean - don't ask why I decided I would just play without blizzy's toolbar and deal with the ever increasing stock toolbar until I got any feedback about this bug, but first, I must add the toolbar back again, to enable the option to set certain mods back to use stock toolbar. and then, the OMFGWTF moment happened.... the IR button is available to add to the toolbar!??? but, how!? I haven't changed anything since I re-installed the mods (and it wasn't working), i had simply moved the toolbar DLL out of my game folder, and had now moved the file back again, to let me change settings. I'm stumped as to what has actually happened, and why, on the moment of giving up, it is now working. I did not imagine the problem. The exception spam was happening, the IR button was not available. Now it is. Go figure! Gremlins! Touching wood here as I reboot KSP and hope the button remains on blizzy's toolbar. Incase anyone finds this small bit of info useful. The entry in toolbar-settings.dat for IR, is "sirkut.IREditorButton", as I was wondering if manually adding this to the toolbar-settings file, would make the button magically appear. So...... incase anyone else who has been having this problem stumbles back to this post - try that. If not. Then try adding and removing both mods. Creating new save games. Smashing your head into your keyboard. Praying to the lords of the internet. Eventually it might magic itself into existance. Final words, once again, thankyou for your amazing work on this mod, even though i'm completely baffled as to what cause and, eventually, what fixed, this tedious problem
  7. I'm having the same problem i've found others to be having where the IR button does not show up (and debug log is spammed with exceptions from IR), but there seems to be no solution except to remove blizzy's toolbar mod. Is there any way to force infernal robotics to use the standard AppLauncher icon instead of blizzy's toolbar? Adding some option to the IR config.xml file? Currently, when adding any IR part to a vessel, my KSP log gets spammed with the following exception inside the VAB (we're talking as many exceptions as my CPU can spew per second): [EXC 16:41:30.815] NullReferenceException: Object reference not set to an instance of an object InfernalRobotics.Gui.ControlsGUI.OnGUI () Launching the vessel (it's a command pod with a rotatatron on top), there is still no IR button and no way to control the parts. Reverting to the VAB, and once again the exception spam continues. There is no option to add the IR button to blizzy's toolbar (it's simply not in the list), the stock AppLauncher icon is also not visible. It appears as though IR cannot find the toolbar object instance to add it's button to, as made apparent by the following exception that appears on the main KSP start screen, and anytime I change scene (from what i can tell): [LOG 16:35:42.539] IR: [GUI] awake [EXC 16:35:42.555] TargetException: Non-static method requires a target. System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) InfernalRobotics.Gui.ToolbarManager.add (System.String ns, System.String id) InfernalRobotics.Gui.ControlsGUI.Awake () UnityEngine.GameObject:AddComponent(Type) AddonLoader:StartAddon(LoadedAssembly, Type, KSPAddon, Startup) AddonLoader:StartAddons(Startup) :MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) :MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) GameDatabase:StartLoad() :MoveNext() UnityEngine.MonoBehaviour:StartCoroutine(IEnumerator) LoadingScreen:Start() From my understanding looking at the IR source, the add() function is being called on a null object ( ToolbarManager == null ) , not clear on how this is happening. These exceptions are thrown every time Awake() or OnDestroy() is being called (because the button / toolbar / GUI hasn't been created?) and although it may not be directly related (we all know how crashy KSP can get with mods) whenever my game crashes, this is always the only recent exception in the game log. If possible, please either add an exception handler to the toolbar handling code and fallback to the standard AppLauncher toolbar if the ToolbarManager instance is null? Failing that, can anyone provide a copy of their GameData\toolbar-settings.dat file to see if manually adding the IR button into the config will fix the exception? I have performed both a fresh install of IR, and a fresh install of KSP to no avail. Removing blizzy's toolbar mod, fixes the problem, but IR is supposed to be compatible with blizzy's toolbar and I don't really want to lose it, but may just have to bite the bullet. I've searched on these forums, on reddit, and across the mighty google, and either the problem goes unresolved, or the user mysteriously fixes the issue without any insight (in the cases where it's the same problem, i suspect they no longer have the toolbar mod installed, as that's the only way i've found to fix this issue) Any help would be greatly appreciated, I love your mod and appreciate the hard work that has gone into it's development and is a shame to be plagued by what would seem to be such a simple issue. I have uploaded a copy of my KSP.log file (I truncated a lot of the repeated exceptions as the log file was over 50MB) http://www.megafileupload.com/9h5i/KSP.txt These are the mods I currently have installed ouput from AVC: KSP: 1.0.4 (Win32) - Unity: 4.6.4f1 - OS: Windows 7 Service Pack 1 (6.1.7601) 64bit Chatterer - 0.9.6.86 ChuteSafetyIndicator - 1.0.2 Contract Pack: Base Construction - 0.2.1 Contract Pack: Field Research - 1.1 Contract Pack: Kerbal Space Station - 2.2.1 Contract Pack: RemoteTech - 2.0 Contract Pack: Grand Tour Contracts - 0.1.7 Contract Pack: Unmanned Contracts - 0.3.10 Contract Pack: Tourism Plus - 1.2 Contract Pack: Anomaly Surveyor - 1.4 CC-CP-SCANSat - 0.5.2.1 Contracts Window Plus - 1.0.5.3 Docking Port Alignment Indicator - 6.2 Infernal Robots - 0.21.3 Kerbal Attachment System - 0.5.4 Kerbal Alarm Clock - 3.4 Alternate Resource Panel - 2.7.3 Kerbal Engineer Redux - 1.0.18 Kerbal Inventory System - 1.2.2 KSP-AVC Plugin - 1.1.5 SCANsat - 1.1.4.2 Waypoint Manager - 2.4.2 TAC Fuel Balancer - 2.5.1.7 QuickGoTo - 1.2 QuickScroll - 1.3.1 QuickSearch - 1.1.3 RCS Build Aid - 0.7.2 RemoteTech - 1.6.7 TweakScale - 2.2.1 [x] Science! - 4.8 MKS - 0.31.6 Freight Transport Tech - 0.4.1 EVAHandrailsPackContinued - 0.2 KW-Rocketry-Community-Fixes - 0.2 Firespitter - 7.1.4 UbioWeldingLtd - 2.1.2 TAC Life Support - 0.11.1.20 Olympic1's Icon Packs - 0.6 Near Future Electrical - 0.5.2 KSP Interstellar Extended - 1.4.9 SpaceY Lifters - 1.0.3 USI Tools - 0.4.2 Filter Extensions - 2.4.1 DMagic Orbital Science - 1.0.8 Universal Storage - 1.1.0.7 Interstellar Fuel Switch - 1.15 SpaceTux: Shared Assets - 0.3.6 Community Resource Pack - 0.4.4 Contract Configurator - 1.7.2 StageRecovery - 1.5.7
×
×
  • Create New...