TaranisElsu

Are you sure the Water Purifier gives infinite reuse? It should only run at 90% efficiency, which should act like a 10x multiplier...

Version 0.10 changed all of the consumption rates, the resource densities, and the amount of resources in each part.

That's because the amount of supplies in your existing vessels (your base) has not changed. Only the rate at which the supplies are consumed. New vessels should be more consistent since they will be created with the right ratio of supplies.

@Cyrik, one issue is that you should be linking to "https://raw.githubusercontent.com/Cyrik/MapResourceOverlay/master/GameData/MapResourceOverlay/MapResourceOverlay.version". Note the githubusercontent.com instead of github.com. That's probably not causing your problem though... I have a small problem to report in the latest version (v1.1.4.1): http://i.imgur.com/Fk4CNan.png. The window is really tall and narrow when reporting a compatibility issue. It was fine when it reported mods with newer versions available. It also completely locks up my whole computer when checking the 15 "KSP-AVC ready" mods I have installed. I cannot browse in another window during the update check. Once it finishes, everything is fine. But until then... This has been an annoyance for a while now, not just the latest version or two, but it is starting to really annoy me as I install more compatible mods. This might be the problem. Please don't just spin while waiting. Log file, in case it helps. EDIT: spinning on the isDone check does seem to be the issue. I tried out a fix, and sent you a pull request.

That was a design choice. All command pods have resources built in because it allows short missions without needing extra parts. If you are adding a Hitchhiker Pod, then you are making a bigger and/or longer mission and you can add some supply containers depending on the total number of Kerbals and your mission length. I need a log file before I can do much to help: https://github.com/taraniselsu/TacLifeSupport/wiki/Help The 64-bit Windows version has so many problems. Try the 32-bit unless you really really need 64-bits and can tollerate the crashes, errors, and bugs. And I need a log file before I can do much to help: https://github.com/taraniselsu/TacLifeSupport/wiki/Help You should have received a warning that the vessel was running out of or is out of Electric Charge before that happened. I will try to make that clearer though. Have you tried Tal's tanks? It seems to work for me in 0.24.2. I have not really tested it though because I have not had much time to play. I second the recommendations to look at MKS/OKS or Procedural Parts. Procedural Parts even allows you to make spherical tanks like in Tal's set. Sadly, no torrodial though. The large containers aren't meant to be used by a single kerbal, really. Those are intended for seriously long, multi-kerbal missions and/or colonies. Also, in just stacking supplies like that, you're consciously choosing to bypass the mechanics entirely, so that's on you. That being said, I still kind of agree with your point; has anyone suggested maybe adding a spoil rate for food, so if you pack a ton onto a vessel with a single kerbal, much of it will go bad? Just an idea. Then you could add more balance for long missions by adding cryo-storage containers of food that are heavier (on account of refrigeration). After the last rebalance, I calculated that you would need 2.4 large containers to send a 6 Kerbal crew to Duna and back, and 6.4 for a trip to Jool and back. Establishing a (semi-) permanent station or base would need a whole lot more. And really, you should not be sending a single Kerbal that far. Poor guy, he would get quite lonely . The ISS currently has 6 people on it, and it is just in LEO. Thanks for pointing that out! Fixed ! I need a log file before I can do much to help you: https://github.com/taraniselsu/TacLifeSupport/wiki/Help Are you running the 64-bit Windows version? It has so many problems that I would recommend staying away from it for now. How much memory is KSP using? Have you tried making a separate install with only my mod and ModuleManager, and see if it works then? There is no reason that TACLS would cause a crash on entering the VAB. It is most likely caused by something else. Sorry I did not keep track of before/after numbers, but your numbers sound like they are in the right ballpark. It looks like you were only looking at the "units" that are produced/consumed, which are affected by the change in density in addition to other changes. That is why food consumption looks like it is higher but water and oxygen consumption look like they were decreased. As Taki117 said, it should happen automatically using a ModuleManager script. Did it miss one? Any part with crew capacity (up to 30!) should get the part module, but only command pods get 3 days of resources added. Sorry, I was missing your greenhouses here: https://github.com/taraniselsu/TacLifeSupport/wiki/Description#greenhouses! I'm trying to make sure I have everybody's stuff listed. Do you want to adjust the current amount on your ships? Or the starting amount in each pod and supply container when you create a new ship? If you want the former, then use the numbers in the spreadsheet to calculate how much of each resource you want, then edit your persistent.sfs file with the desired values (backup your file first!).

LOL, I just updated TAC Life Support

Changes Finished rebalancing and added costs. Note that all the consumption rates changed, and the amounts of resources in all vessels changed. Your ships may have more or less supplies, and may have more or less delta-V because the masses of all the containers and recyclers also changed. The InstallChecker now runs on the loading screen instead of waiting until the main menu. I also added more logging, and added checks for changes since 0.9.1. Fixed issue with click-through in the Space Center and Editor scenes. Warning: I recommend a full delete and re-install when upgrading to this version. Read some important notes about upgrading from previous versions.

Can't you use ? as a substitute for the space character? Like this? //spaceX @PART[*]:HAS[#author[Lazarus?Luan],~name[FalconLowerGear]] { @category=-1 }

@JeffreyCor and @AviatorBJP, I thought I noticed the differing speeds for some axis directions, but I wasn't sure. Not sure what could be causing it though... The code is consistent. Interesting suggestion. Not sure how useful it will be though... Yeah, but that requires spending money. And I would only use it for KSP since my joystick still works for other games that I've played. Even other Unity games . You can change it to whatever key you want. I don't know how to allow modifiers yet though. I will add that as soon as I figure it out. It should be installed in the KSP/GameData/TacStickyControls, just like it is packaged within the zip.

I was frustrated trying to understand the ControlTypes enum for use with the InputLockManager, so I converted the values into binary: None 0 PITCH 1 ROLL 100 YAW 1000 THROTTLE 10000 SAS 100000 PAUSE 1000000 STAGING 10000000 CAMERAMODES 1 00000000 MISC 10 00000000 CAMERACONTROLS 100 00000000 TIMEWARP 1000 00000000 MAP 10000 00000000 LINEAR 100000 00000000 QUICKSAVE 1000000 00000000 QUICKLOAD 10000000 00000000 VESSEL_SWITCHING 1 00000000 00000000 CUSTOM_ACTION_GROUPS 10 00000000 00000000 GROUP_ABORT 100 00000000 00000000 GROUP_GEARS 1000 00000000 00000000 GROUP_LIGHTS 10000 00000000 00000000 GROUP_BRAKES 100000 00000000 00000000 GROUP_STAGE 1000000 00000000 00000000 GROUPS_ALL 1111110 00000000 00000000 ACTIONS_SHIP 10000000 00000000 00000000 ACTIONS_EXTERNAL 1 00000000 00000000 00000000 ACTIONS_ALL 1 10000000 00000000 00000000 RCS 10 00000000 00000000 00000000 WHEEL_STEER 100 00000000 00000000 00000000 WHEEL_THROTTLE 1000 00000000 00000000 00000000 EVA_INPUT 10000 00000000 00000000 00000000 EDITOR_ICON_HOVER 100000 00000000 00000000 00000000 EDITOR_ICON_PICK 1000000 00000000 00000000 00000000 EDITOR_TAB_SWITCH 10000000 00000000 00000000 00000000 EDITOR_SAVE 1 00000000 00000000 00000000 00000000 EDITOR_LOAD 10 00000000 00000000 00000000 00000000 EDITOR_EXIT 100 00000000 00000000 00000000 00000000 EDITOR_NEW 1000 00000000 00000000 00000000 00000000 EDITOR_LAUNCH 10000 00000000 00000000 00000000 00000000 EDITOR_UI_TOPRIGHT 11111 00000000 00000000 00000000 00000000 EDITOR_PAD_PICK_PLACE 100000 00000000 00000000 00000000 00000000 EDITOR_PAD_PICK_COPY 1000000 00000000 00000000 00000000 00000000 EDITOR_EDIT_STAGES 10000000 00000000 00000000 00000000 00000000 EDITOR_EDIT_NAME_FIELDS 1 00000000 00000000 00000000 00000000 00000000 EDITOR_ROTATE_PARTS 10 00000000 00000000 00000000 00000000 00000000 EDITOR_UNDO_REDO 100 00000000 00000000 00000000 00000000 00000000 EDITOR_SYM_SNAP 1000 00000000 00000000 00000000 00000000 00000000 EDITOR_OVERLAYS 10000 00000000 00000000 00000000 00000000 00000000 EDITOR_MODE_SWITCH 100000 00000000 00000000 00000000 00000000 00000000 EDITOR_UI_TOPBAR 100001 00011111 00000000 00000000 00000000 00000000 EDITOR_UI 101101 10011111 00000000 00000000 00000000 00000000 EDITOR_SOFT_LOCK 111110 01100000 11100000 00000000 00000000 00000000 EDITOR_LOCK 111110 01100000 11100000 00000000 00000100 00000000 TRACKINGSTATION_UI 1000000 00000000 00000000 00000000 00000000 00000000 TRACKINGSTATION_ALL 1000000 00000000 00000000 00000000 00001100 00000000 KSC_FACILITIES 10000000 00000000 00000000 00000000 00000000 00000000 KSC_UI 1 00000000 00000000 00000000 00000000 00000000 00000000 KSC_ALL 1 10000000 00000000 00000000 00000000 00001100 00000000 APPLAUNCHER_BUTTONS 10 00000000 00000000 00000000 00000000 00000000 00000000 ALL_SHIP_CONTROLS 11111111 11111111 11111111 11111111 11111111 11111110 00100010 10111111 All 11111111 11111111 11111111 11111111 11111111 11111111 11111111 11111111 Now it is easier to see which flags are set with which values. Here is the simple (and ugly) Python script that I threw together: def insert_spaces(string): return ' '.join(string[i:i+8] for i in range(0, len(string), 8)) with open('flags.txt') as file: for line in file: tokens = line.split() flagName = tokens[0] flagValue = int(tokens[1]) flagString = "{:64b}".format(flagValue) flagString = insert_spaces(flagString) print("{0:23} {1} {0}".format(flagName, flagString)) Note that I already scrubbed the ControlTypes file so that instead of: using System; [Flags] public enum ControlTypes { None = 0, PITCH = 1, ROLL = 4, YAW = 8, ...etc... it looked like: None 0 PITCH 1 ROLL 4 YAW 8 ...etc...

I recommend using my TacGenericConverter as a replacement for the stock generator module. Or use the modified version of my class created by RoverDude for Karbonite, MKS/OKS, etc. You should really talk to him since it sounds like your effort is overlapping with what he is doing. And I will be folding his changes into my class eventually (he hasn't shared them with me yet).

Changes Added support for the KSP Add-on Version Checker (KSP-AVC) and the KSP-AVC plug-in. Moved the OX-STAT earlier on the tech tree, to tier 4. Justification: stock allows sending manned craft to the moons or other planets almost right away. Life Support severely limits that, mainly electricity requirements because supply containers are available in the Survivability node (tier 3). Added some logging to the InstallChecker. Should help when trying to debug people's installs. Rescue Kerbals now start with resources. The first time a Rescue-mission Kerbal is encountered, it is given 10-90% of the normal resource amounts. That gives anywhere from 36 minutes to 5:24 hours to complete the rendezvous and get the Kerbal aboard. You will need to be careful that you do not get too close before you are ready. Notice Now includes the KSP Add-on Version Checker's MiniAVC. It does a GET request to http://ksp-avc.cybutek.net/ to find the latest release number. It is opt-in and no information is sent to the server. I recommend downloading the full KSP-AVC Plugin to get the most out of it. And encourage other mod authors to support it.

Please read https://github.com/taraniselsu/TacLifeSupport/wiki/Help and follow the instructions.

Thunder Aerospace Corporation presents our latest innovation: Sticky Controls Someone -- Bill? -- got a little too excited during his last flight and spilled his drink on the control panel. Now the control stick won't return to neutral when released! The weird thing is that some pilots started saying the plane was easier to fly, so we hired an intern to spill drinks on every control panel. Through many trials and careful experiments, we have found the ideal amount to spill. Also includes some cleaner for when it is no longer desirable, like after reaching space. The latest release is version 0.3.1 which works with KSP 1.0.2. Download below. Having problems with this mod (or any others)? Read the [Official] How To Get Support. I cannot do much to help without log files. Just something that I threw together because I was frustrated trying to fly planes using the keyboard. I have many hours on MS Flight Simulator, and this makes the controls behave similarly to that. In my opinion, it makes planes much easier to fly in the atmosphere. I probably would never have created this if I could just get my stupid joystick to work with KSP, but it is really old . Features NOT ALL FEATURES ARE IMPLEMENTED YET. Each attitude control input (the WASD keys) moves the controls by a small amount and the controls do not return to neutral when released. Works kind of like trim, but more adjustable and easier to work with. May be familiar to players of the Microsoft Flight Simulator series. Fully adjustable: easy to change the amount the controls move per key press. Immediately center the controls by pressing ` (The tilde key in the top-left of US keyboards, next to the 1). Set to the current control positions by pressing Y. Useful for setting the controls to what SAS was using before turning off SAS. The idea was shamelessly stolen from Extended Trim. Toggle on/off whenever desired by pressing Alt+`. Displays a small window showing the current control positions, along with the configurable settings. Not implemented yet: The window can be shown or hidden by clicking the button, which can be displayed on its own, in Blizzy's toolbar, or in the stock toolbar. Not tested with RemoteTech2 nor MechJeb. I suggest that you turn this off if using MechJeb controls, if you have no connection for RT2, or if signal delay is significant. Configurable settings: - Speed: how fast the controls move while pressing the key - Step: the minimum amount the controls are moved per key press. It also snaps the controls to multiples of this value, so larger values cause it to change in large discreet steps. - PrecisionControlsModifier: scales both Speed and Step by this amount when "precision controls" is turned on (the Caps Lock key in KSP's default key bindings). - Minimum Time: the time in seconds a key has to be held down in order for the controls to move more than a single step. - Exponent: larger values make the controls move much faster when holding a key down longer. When set to 1, the controls move the same amount per unit of time regardless of how long the key has been held down. - Position Dead Zone (new): controls the dead zone around zero where the controls have no effect. - Position Exponent (new): larger values make it so controls have less effect when near zero and a much larger effect when farther from zero. - ZeroControlsKey: the key bound to zeroing the controls. The default is 'z'. Note that toggling on/off is always Alt plus this key (need to change to support Mac/Linux) - SetControlsKey: the key bound to using the current control positions. The default is 'y'. License Apache License Version 2.0 Download the latest version. Download from Curse (coming soon) (Alternate Download) Source code available on Github. Change log Release v0.3.1 - Updated for KSP 1.0.2 - Changed to use OnPreAutopilotUpdate so that SAS and other autopilots can override the input. - Keeps the current trim when setting control positions. - Added position scaling and a deadzone. - Resets the control movement speed when crossing the neutral point. - Fixed rover compatibility. I did not realize wheel steering and wheel throttle were handled separately. - Changed the default settings to my preferred settings. - Updated MiniAVC to v1.0.3.0 - Updated to latest TacLib: sets the min/max KSP version, hoping that future KSP updates won't break too much. Release v0.2 - Updated for KSP 0.25 - Changed the default key to toggle on/off or zero controls to ` (The tilde key in the top-left of US keyboards, next to the 1). - Locks out normal inputs when enabled. - Refactored the way control input works: it moves the controls slowly at first, speeding up as you hold the key down longer. - Added a key for capturing the current control positions. Defaults to y. Useful for setting the controls to what SAS was using before turning off SAS. The idea was shamelessly stolen from Extended Trim. Release v0.1 - Initial version Notice This mod includes version checking using MiniAVC. If you opt-in, it will use the internet to check whether there is a new version available. Data is only read from the internet and no personal information is sent. For a more comprehensive version checking experience, please download the KSP-AVC Plugin.

That's pretty easy to do. So easy in fact, that if you REALLY wanted it, you can do it youself by copying the KAS Module "GRAB" from any part.cfg (of a part which can be grabbed with KAS, of course) to the lights. I recommend using the RCS Block's version, they are relativly similar in size and attachment. You can find it in the KAS/addModule.cfg. I'm pretty sure someone has done this before and posted it in this thread, let me search real quick: [flies away] Someone else did post that in this thread before, which is where I got it from. I should have made a note about who . Anyway, not mine, but here it is: @PART[light*]:HAS[@MODULE[ModuleNavLight]]:NEEDS[KAS] { MODULE { name = KASModuleGrab evaPartPos = (0.0, 0.0, -0.15) evaPartDir = (0.0, 0.0, -1.0) storable = true storedSize = 5 attachOnPart = True attachOnEva = False attachOnStatic = False attachSendMsgOnly = False } } Caution: I have not used KAS nor this mod in a while so no guarantees that it'll work. I've been spending what little KSP time that I have working on my own mods. Hopefully I'll have time soon to put together a play install. This will definitely be one of the mods that I'll use then.

What units are your "days" in? 6 hours or 24 hours? I assumed 24-hour days but Shimmy is doing a fly-by of the Mun, and his total trip is estimated at just over a single 24-hour day... His MET time was ~13.5 hours at periapsis over the Mun.

Please read https://github.com/taraniselsu/taraniselsu.github.io/wiki/Help and follow the instructions. A log file really really helps.

I just want to throw it out there that for a keostationary orbit, your "Surface" velocity will be 0 m/s. And for a keosynchronous orbit, the east/west part of your surface velocity will be 0. That is how I know that I have achieved the desired orbit.

Changes Updated for KSP 0.24.2. Bug fix: was letting the user edit fuel levels on other planets/moons besides Kerbin. Bug fix: the popup window should now close when the user clicks anywhere outside the popup window. Added an Install Checker. Displays the mod's version number in the Settings window. Added support for the KSP Add-on Version Checker (KSP-AVC) and the KSP-AVC plug-in Download from Curse (after the upload is approved).

Those errors are not from this mod. I do not call Part.GetConnectedResources. If it happens again, please read https://github.com/taraniselsu/taraniselsu.github.io/wiki/Help and follow the instructions. I cannot help much without a complete log file. To answer your original question: while landed, click the popup button and click Edit. That will only show while prelaunch or landed on Kerbin.

Changes Updated for KSP v0.24.2. Added a Kerbal Mission Elapsed Time (MET) Added support for the KSP Add-on Version Checker (KSP-AVC) and the KSP-AVC plug-in. Displays the mod's version number in the Settings window. Download from Curse (after the upload is approved).

Thank you for the log file Where did you download it? TACLS should not be listed as a "Non-DLL" mod, so it sounds like you are missing the .dll file. [ModuleManager] compiling list of loaded mods... Mod DLLs found: Assembly-CSharp v1.0.0.0 ModuleManager.2.2.1 v2.2.1.0 Non-DLL mods added: TacLifeSupport Mods by directory (subdirs of GameData): NASAmission Squad ThunderAerospace Did you download from one of these links https://github.com/taraniselsu/TacLifeSupport/wiki/Download ?

The numbers in my spreadsheet are different from version 0.9. Due to discussions with NathanKell and others, I decided to change a couple things and rebalance. Though the numbers in the spreadsheet should be roughly 1/2 of the defaults in 0.9. Check your command pods, and make sure they have an equal duration for each resource: Food time == water time == oxygen time. You can use the Build Aid in the VAB or SPH. If not, then double check your installation and read https://github.com/taraniselsu/TacLifeSupport/wiki/Tutorial#installation-tutorial. If things still don't seem right, then please read https://github.com/taraniselsu/TacLifeSupport/wiki/Help and follow the directions. If you are experiencing any bugs or crashes, then please read https://github.com/taraniselsu/TacLifeSupport/wiki/Help and follow the directions. I cannot help much without a log file. It just gives me so much useful stuff when trying to determine what might be going wrong. Possible errors are everything from 64-bit is horribly buggy to using the wrong version (i.e. not v0.9pre4) to incorrect installation. Please help me help you.

The MiniAVC does not seem to be working as expected for me. I get the impression that it is still checking for updates even though I told it not to. Is it because I had the full version installed and removed it to test? Executing: MiniAVC - 1.0.1.0 Assembly: K:\Games\KSP_win-test\GameData\ThunderAerospace\TacLifeSupport\MiniAVC.dll [Log 19:15:01.2140679]: Starter was created. [Log 19:15:01.8741056]: FirstRunGui was created. [Log 19:15:06.0063420]: Remote checking has been disabled for: TAC Life Support [Log 19:15:06.0173426]: FirstRunGui was destroyed. [Log 19:15:06.3473615]: K:\Games\KSP_win-test\GameData\ThunderAerospace\TacLifeSupport\TacLifeSupport.version NAME: TAC Life Support URL: [url]http://ksp-avc.cybutek.net/version.php?id=9[/url] DOWNLOAD: NULL VERSION: 0.9.0.1046 KSP_VERSION: 0.24.2 KSP_VERSION_MIN: NULL KSP_VERSION_MAX: NULL CompatibleKspVersion: True CompatibleKspVersionMin: True CompatibleKspVersionMax: True [Log 19:15:06.3473615]: [url]http://ksp-avc.cybutek.net/version.php?id=9[/url] NAME: TAC Life Support URL: [url]http://ksp-avc.cybutek.net/version.php?id=9[/url] DOWNLOAD: [url]https://github.com/taraniselsu/TacLifeSupport/wiki/Download[/url] VERSION: 0.9.0.9910 KSP_VERSION: 0.24.2 KSP_VERSION_MIN: NULL KSP_VERSION_MAX: NULL CompatibleKspVersion: True CompatibleKspVersionMin: True CompatibleKspVersionMax: True [Log 19:15:06.3553619]: IssueGui was created. [Log 19:15:06.3563620]: ToolTipGui was created. [Log 19:15:08.4084794]: IssueGui was destroyed. [Log 19:15:08.4494817]: Starter was destroyed. [Log 19:15:30.1297218]: ToolTipGui was destroyed. Complete log file if you want it.

Did you read https://github.com/taraniselsu/TacLifeSupport/wiki/Help ? Please follow the instructions. And Windows 64-bit is so buggy right now. It most likely has nothing to do with my mod. Please use 32-bit unless you really need it.