Jump to content

Farix

Members
 View Profile  See their activity

  • Posts

    93

  • Joined

  • Last visited

 Content Type 

Everything posted by Farix

  1. Farix
    FYI, NMM is getting a huge overhaul as the developer of Mod Organizer has now take over and is building a new mod manager from the ground up.
  2. Farix
    That is because the version file uses KSP_VERSION instead of KSP_VERSION_MIN and KSP_VERSION_MAX. A lot of other mods are also throwing warnings for the same reason.
  3. Farix
    I'm not sure what you mean, unless it's because the overhauled parts are less powerful than their stock counterparts. Or that the Mk1 Command Pod needs the ModuleDataTransmitter code added to it. Or is it the Valiant and Pug engines? Valiant is just too underpowered to be of much use and while the Pug is a good orbital engine do to it's light weight, its low thrust doesn't leave much room for error. However, that is besides the point. If someone is using these parts with the UBM tech tree, a command pod will be available in the very first node defeating the entire purpose of the tech tree. PorkJet's overhauls didn't touch the stock parts. They are entirely new parts.
  4. Farix
    Field a bug report to Infernal Robotics: https://github.com/MagicSmokeIndustries/InfernalRobotics/issues/128
  5. Farix
    If you happen to be using PorkJet's Parts Overhaul in this tech tree, then you are going to end up with a command pod in the very first node and engines and tanks not matching their stock counterparts.
  6. Farix
    So what exactly is broken other than not having entries on the new biomes?
  7. Farix
    Any known issues with running the current v0.3.1 with KSP 1.2.0 + Kopernicus v1.2.0-3?
  8. Farix
    I would actually prefer to download just the SVE texture and config files while downloading the other mods separately. It makes it much easier to upgrade the individual components and adapt for future version of KSP.
  9. Farix
    I was able EVA from the default part, but I also noticed that the textures are completely different form the ones that are available. Could this have been a old version of the part that wasn't completely removed?
  10. Farix
    Is the latest release v7.4.1? Because that was the version I was using when I encountered the problem. Anyways, I had already failed the mission so I wouldn't be able to test the part in that situation again.
  11. Farix
    Apparently, Contract Configurator breaks ScanSat (prevents scanners from activating). When I reported the problem on GitHub, @nightingale blames it on @blizzy78's Toolbar, even though the toolbar wasn't installed. https://github.com/jrossignol/ContractConfigurator/issues/590
  12. Farix
    It's always a good idea to have multiple ways to download a mod, least we have another KerbalStuff. I also know that some of us prefer not to use or support SpaceDock. Since there is a GitHub repository for the source code and they have more robust servers to begin with, why not add releases there as well?
  13. Farix
    I don't think RealPlume, RealPlumeStock, or SmokeScreen even touches the command pods in any way. But delete \RealPlume-Stock\PartOverhauls to see if the problems continues.
  14. Farix
    Is it possible to allow EVA from this part? Or at least prevent it from being used in rescue missions?
  15. Farix
    Is there an alternative download, like Curse or GitHub? SpaceDock is proving to be completely unreliable.
  16. Farix
    Hmm. Isn't Real Plum suppose to produce a smoke trail in atmo or is that part currently broken in SmokeScreen?
  17. Farix
    Beyond the addition of a life support category, other categories that I would find useful would be parachutes/airbreaks, lights, and crew cabins. Probably separate categories for solar panels and batteries outside the rest of the electrical parts for things like Near Future. I would also like to see probe cores separated form command pods.
  18. Farix
    RealPlume is just a set of config files for SmokeScreen. Unless SmokeScreen itself changes, the config files will still work with no additional modifications.
  19. Farix
    Are PorkJet's Parts already covered or do they still need their own configs?
  20. Farix
    Mainly the shuttle engine, jet engines, radial mounted engines, and one dual nozzle engine had yaw control. The rest do not.
  21. Farix
    You forgot that most of the engines have no yaw control.
  22. Farix
    This is precisely why I have not uploaded my TAC Life Support Declutter script to SpaceDock. I have absolutely no confidence that the SpaceDock will respect the wishes of the mod creators if the mod creator decides to pull their mods from the site or a third party uploads the mod to the SpaceDock. This lack of confidence stems form one of the SpaceDock developers saying that a mod creators are s*** out of luck in such a situation if the mod has an open source license. The irony is, Curse, dispute its reputation of "being evil", is actually more respectful towards mod creators by removing third party uploads or allowing mod creators to close out the mod.
  23. Farix
    If squad is going to take a mod and add it to KSP, I would rather it be a fundamentally useful mod like Kerbal Engineer or Kerbal Alarm Clock instead of more part mods.
  24. Farix
    I've rechecked in a fresh 1.1 install with just Ven's and Module Manager v2.6.21 running in 64-bit. After testing the 1.25m engines, there was no yaw control on the LV-909 "Terrier", LV-T45 "Swivel", and LV-900 "Beagle". The S3 KS-25 "Vector" and KS-25 "Badger" worked.
  25. Farix
    Have you checked the engines with gimbels. When I tested the parts in 1.1 the gimbels were very much broken.
×
×
  • Create New...