Eleusis La Arwall

  • Content count

  • Joined

  • Last visited

Community Reputation

243 Excellent

About Eleusis La Arwall

  • Rank
    Rocketry Enthusiast
  1. Yes, my suspicion seems correct. Removing the rotation of the model in the config file fixed the problem. Forgot to mention that, sry. MODEL { // rotation = 0,90,0 model = WarpPlugin/Parts/Command/iHall/modelCDTcore }
  2. I can reproduce the problem. Root part or not doesn't matter, all iHal parts have the navball rotated by 90° upon revert to launch. I'll re-export the part and remove the rotation node in the config for the next release.
  3. @Maelstrom Vortex I have the suspicion that this is caused by the 90° rotation of the model in the config file MODEL { rotation = 0,90,0 model = WarpPlugin/Parts/Command/iHall/modelCDTcore } It is exactly the rotation you experienced and I've seen similar problems with the rescaleFactor node on root-parts Is iHal the root part? I'll run some test to see if I can reproduce it.
  4. Interstellar liquids and how to get them to be gases.

    Most storage tanks have an integrated resource converter for liquid <-> gas that can be adjusted with a slider. Tritium must breed in (fission) reactors like the Molten Salt Reactor. Tritium also underlies radioactive decay. Deuterium is located in Jools atmosphere. Otherwise Heavy Water can be electrolyzed to Deuterium and Oxygen.
  5. LiterVolume is a temporary resource that should not be visible. LiterVolume on each tank gives its storage volume in Liter. A MM-patch converts it to the IFS fuel switches. Think I found the problem, will be fixed
  6. Alternate Parts Creation

    Sure you can use it! It's just an example, feel free to do whatever you like with it
  7. Alternate Parts Creation

    Yes, that should be possible with MM. Here's a patch that should create a duplicate of the stock Mk1 Pod before patched by VensStockRevamp (untested) +PART[mk1pod]:BEFORE[VensStockRevamp]:FOR[000start]{ @name = mk1podStock @title = Stock Mk1 Pod // or whatever you want } +PART[mk1pod] makes a copy of the part named mk1pod. :BEFORE[VensStockRevamp] tells MM to apply this patch before VensStockRevamp. :FOR[000start] is just for safety (if loaded in alphabetical order this patch will be loaded first); propably not required. Important is that the name for the duplicated part is changed with @name = <something>. Title, Manufacturer, etc can also be changed that way. Since the duplicate has a different name, other mods may not recognize this part.
  8. I'm currently running Unity 5.4.1f1 with TextMeshPro and the latest PartTools on Debian 8 (yes it's a bit old I know). For a couple of month everything was working fine, just as I was used to from Windows. A few days ago Unity seems to have broken down for no apparent reason. From one day to the other the Inspector looks like this (debug right; normal left): The Materials settings have entrys I've never seen before. Any attempts to fix this have been in vain. I've found a similar problem on the unity forums and reported my problem over there too. I was told that it seems like a bug, unless I have some strange editor plugin that is taking over somehow. So, before writing a bug-report I want to make sure PartTools is not the problem. Has anyone here encountered a problem like this or may even have a solution? The strange thing is, beside everything looking messed up, it actually still works. I went through all the Element X entrys and the fifth revealed the name "_MainTex". So I've set the texture here, exported the model and KSP loads and shows it in the VAB. Most likely I have to reinstall Unity, but I couldn't find Unity 5.4.0p4 in the linux releases. So I'd like to ask other Linux users: What unity version are you running?
  9. [1.3.1] Interstellar Fuel Switch (IFS) 2.10.0 (updated 7-10-2017)

    That is perfectly fine. All IFS tanks have an integrated (radial) decoupler. They were available for staging before, but inline-attached tanks also had a non-functional decoupler in the staging. If you don't want the integrated decouplers, you can disable them with PatchManager (Wrapper tanks still have integrated decouplers).
  10. I'm getting myself familiar with the localization support but I have a problem with the language switcher. When I set language = de and provide a dictionary file for de and en-us, KSP shows me the en-us keys ingame. When I delete the en-us dictionary file, the de keys appear. KSP title screen shows de in both cases. I've looked into severel other mods but I don't know what I'm doing wrong.
  11. [1.3.1] Interstellar Fuel Switch (IFS) 2.10.0 (updated 7-10-2017)

    The integrated decouplers no longer clutter the staging menu. It was a bit annoying to have decouplers from inline-attached tanks (that were not usable at all) in the staging. The decouplers are not gone entirely, they can be triggered from the right click menu or put into action groups. If you don't want to have integrated decouplers at all, it is also possible to deactivate them with PatchManager (integrated) by @linuxgurugamer. This handy tool can toggle MM configs on/off and makes life easier for modders and users. With PatchManager you can also disable the FuelSwitch patches for the stock parts or choose how much setups the CDT have. Currently there are 3 options for the CDT: Basic config is 4 Fuel+Oxidizer setups. The 7 setups config additionally allows you to have the Fuels without Oxidizer and the 12 setups config makes Noble gases available too. More options can and will be added in the future. Suggestions are very welcome but they need to follow some structure/concept. Please don't suggest personalized setups like "HydroLOx, Hydrogen, Xenon, HTP and Nitrogen-15" for example.
  12. [1.3] PatchManager

    As mentioned above, FreeThinker and I currently encounter a problem. It's a bit weird because this setups was working at a certain point. Whenever I deactivate a patch in the GUI and apply it, nothing happens but this shows up in KSP.log: [EXC 16:20:20.560] FileNotFoundException: /home/myuser/games/KSP_linux/KSP_Data/../GameData/InterstellarFuelSwitch/PatchManager/ActiveMMPatches/InterstellarFuelSwitch_IntegratedDecoupler.cfg does not exist System.IO.File.Move (System.String sourceFileName, System.String destFileName) PatchManager.PatchManagerClass.ApplyAllChanges () PatchManager.PatchManagerClass.drawPatchWindow (Int32 windowid) UnityEngine.GUILayout+LayoutedWindow.DoWindow (Int32 windowID) UnityEngine.GUI.CallWindowDelegate (UnityEngine.WindowFunction func, Int32 id, UnityEngine.GUISkin _skin, Int32 forceRect, Single width, Single height, UnityEngine.GUIStyle style) The file in question is not called InterstellarFuelSwitch_IntegratedDecoupler.cfg but IntegratedDecoupler.cfg. My first guess was to rename all files and srcpath to InterstellarFuelSwitch_IntegratedDecoupler.cfg but then I get a similar error stating that InterstellarFuelSwitch_InterstellarFuelSwitch_IntegratedDecoupler.cfg does not exisit. So now I guess PatchManager is looking for the wrong file. Config files are available in the latest release of IFS or on GitHub.
  13. [1.3] PatchManager

    Yes, it works! The filename of the MM-config, the filename of the PM-config and the patchName-node must match exactly. At first I renamed just the PM configs but that alone didn't do the trick. Here is my working config: Again, thank you very much for the support!
  14. [1.3] PatchManager

    Is there an example for the "exclusions" node? I've searched through all examples mentioned in the OP but could not find any and I couldn't get this to work by myself. Currently I have 3 different patches "CDT4SetupPatch.cfg", "CDT7SetupPatch.cfg" and "CDT12SetupPatch.cfg" but only one should be applied at a time. Here are the 3 Patches: In the GUI I can activate all 3 patches at the same time. I've also tried to include the modname like ... exclusions = InterstellarFuelSwitchCDT4Setups,InterstellarFuelSwitchCDT7Setups ... or ... exclusions = InterstellarFuelSwitch_CDT4Setups,InterstellarFuelSwitch_CDT7Setups ... but always the same result.
  15. [1.3] PatchManager

    Yes, that fixed it. Everything is working now. Thank you for the support!