• Content Count

  • Joined

  • Last visited

Community Reputation

63 Excellent


About Raphaello

  • Rank
    Spacecraft Engineer

Profile Information

  • Location Moho

Recent Profile Visitors

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

  1. I'd love to finally see announcement on what next DLC is going to be
  2. Raphaello

    Give this kid a like on youtube !

    He seems to live in Poland and he speaks polish but his english is better than his polish
  3. Raphaello

    How Much Time Have You Spent Playing KSP?

    almost 500 on steam and 300, I guess outside.
  4. Raphaello

    Give this kid a like on youtube !

    Good idea! I liked the video
  5. @SQUADcongrats on the release and thanks for releasing before xmas!!!! Great job!
  6. Raphaello

    [1.7.0-1 + Backports] Kopernicus & KittopiaTech

    I'd recommend installing all recommended () mods too (you can skip RT and TACLS if you want) and FASA+Taerobee from suggested mods list. Make sure that you configure KCT to use RP-0 config.
  7. Thanks a lot, really appreciate your support!!! Maybe ckan expert @HebaruSan knows a magic solution to the problem?
  8. I guess this trick is not possible for HangarExtender or RCSBuildAid as they do not "provide" anything. Thanks anyway!
  9. Hi, mods sometimes depend on mods which had been taken over by another maintainer and the newer versions are published as a separate mod (continued, expanded, reloaded, etc). A good example are FerramAerospaceResearch and FerramAerospaceResearchContinued. I'd like to make my mod dependent on FAR in a way that would first check whether original one is available to be used in my KSP version - if it is then FAR is installed by CKAN and if not then FARContinued is installed. With such a setup, original FAR would be installed on 1.3.1 but FARContinued on 1.5.1. Is this possible?
  10. This is what we do already now. The solution I'm looking for is something that would enable anyone to choose to install RP-1 from CKAN and an updated version of KRASH would be installed automatically (or not if the user chooses so as this is a recommended mod, not a dependency) from CKAN. I thought that it would be possible for you to release "new" version of KRASH ( or for example) which would only be valid for 1.3.1. I'm not sure if this is possible though.
  11. Hi@linuxgurugamer , RP-1 is now officially released by @pap1723!!!!!! Turned out it had been just 6 days since I commented above. Have you had some time to look into bringing new version of Krash to 1.3.1? It would be great to have an official release of KRASH too.
  12. Hard to say. Dev branch was merged to master today. There are still discussions on updates though. Might be few days or few weeks
  13. Hi @linuxgurugamer, there's RP-1 release coming up soon now and these changes are quite important for both KCT (mandatory dependence) and for TestFlight. However, there's no official release with these changes for KSP 1.3.1 therefore there's unofficial build for those of us who are willing to use dev build of RP-1. With RP-1 coming to CKAN, the unofficial patch for KRASH is not a good solution - we need KRASH 1.3.1 release published on CKAN with the changes above. I've done a fork from your master earlier today to recompile it against 1.3.1 but the issue is that ClickThroughBlocker and ToolbarController have not been compatible with 1.3.1 since a long time. For my own needs, I simply restored the original code (which you've replaced with your mods) and removed dependency for these two mods. This is simple for personal use but making my version public is not so easy anymore There are two solutions I can see now: - ask you to create a version for RP-1. This might or might now work - ask you for a permission to publish my version as a separate mod i.e. "RP-1 KRASH" valid for 1.3.1 only with RP-1 as mandatory dependency. Would you be ok with one of these? Maybe there are other solutions?
  14. check out these screenshots @SQUAD thanks for providing the updates! I appreciate new content and improvements you provide to the game with each update. I am not going to update my main game yet but I also don't have any urge to immediately use all the new, shiny(!) features you've just delivered. I either finish my current modded game or I upgrade when all nevessary mods are updated. I am afraid that if you stop developing the game, it will just slowly die. I think you should reconsider public beta program again (as it was already suggested a couple of times on this very thread) - it's very easy to control for both steam and store users, would provide you with a lot of voluntary QA and give more time for modders for updates
  15. Valentina is also excited yet a bit disappointed she cannot check her new outfit in a mirror: The new burn time indicator is sooooo great!!!! It can also be easily used to check available dV in stock!!!!