Jump to content

Phineas Freak

Members
  • Posts

    1,315
  • Joined

Everything posted by Phineas Freak

  1. It may be deprecated (since the KSP 1.3+ localization updates can transparently take care of the strings displayed) but it is going to be a maintenance hell (at least for me): "Earth" will now be identified as "Kerbin" and i would have to make sure that the "Kerbin" patches for EVE and Scatterer do not stomp/get stomped by other mods (like RealExoplanets or even "stock" Scatterer). It would not be possible anymore to cleanly separate patches meant for stock and RSS. As far as i can see from preliminary testing the only thing that this naming change affects is the Main Menu (EVE and Scatterer will correctly apply their effects). But, to create a maintenance hell so that the user will see the pretty effects in a scene that lasts less than 30 seconds is not worth it, at least not for me. Hmm... (last update @ 2018-12-28, 47 days at the time that this post was written)
  2. Color me interested, what configs are exactly "out of date"? Edit: and if they are so "broken" as you say then why you don't open a new issue/pull request in the RSSVE GitHub repository?
  3. You have at least an incorrect version of AJE (probably using CKAN?) so i'd start from there: https://github.com/KSP-RO/AJE/releases
  4. RealPlume expects different names for the thrust transforms in order to be able to assign different plume types. If the names match then any secondary plume definition (type, size, placement) will always be overridden by the first one, no matter what. In the above engine example, assigning "Kerolox-Lower" to the core engine automatically (and incorrectly) makes the verniers also use that plume, although the verniers should use "Kerolox-Vernier". RealPlume example with a plume setup for a similar engine (note the checks for the different thrust transform names)
  5. Does that mean that only the part config will be removed or the entirety of the engine (models/textures)? Because it is a nice model that RO uses it for some of the stock/cloned engines. On another note: the names of the main and vernier engines of the "Size2MedEngine" (RD-108 alike) are exactly the same ("thrustTransform"). Meaning that it breaks any chance of using different thrust values for the main/verniers or creating correct RealPlume configs (different styles for each nozzle exhaust). Would it be possible to change the names of the vernier thrust transforms?
  6. Can you test in a completely stock KSP installation? Or follow the standard debug practice: remove half of the installed mods, launch game, test. If it passes then install the other half, launch game test. Repeat until you have found the problematic mod combination.
  7. You have installed a version of KSCSwitcher for KSP 1.4.3: Do you use CKAN? That specific version is incorrectly tagged as compatible with KSP 1.3.1. The latest version of KSCSwitcher for KSP 1.3.1 is 0.8.
  8. The current assets have white smoke (an all-around solution for both low and high altitude smoke + a kind of condensation). Contrails cannot really be modeled, as they depend on more parameters than just atmospheric pressure. In any case, the "LREs do not produce smoke" issue has been beaten to death in the past.
  9. LREs do not produce as much smoke as the SRMs so the result that you are seeing is correct.
  10. There is. It is part of the LEM itself. Please take the time and check the RO parts in-game. Also, this discussion is off-topic and should be in the RO thread instead.
  11. @Punch All these parts have been intentionally removed. Do not try to load the stock craft files, they are never going to work as-is. You have to build them yourself (number 1 rule when playing with RO).
  12. @nauspav RSSVE depends upon RSS in order to fix that kind of stuff. But, since neither RSS nor RSSVE have been updated for KSP 1.5.1 you the results that you are seeing. I also have a nice way to report that kind of stuff since this is a thread for Scatterer and not RSSVE, assuming that you have read the RSSVE installation instructions though.
  13. @GrimT I think that the EVE incompatibility issue has been debunked by the same user as being bogus: (no Unity engine updates happened between the KSP 1.5 and KSP 1.6 branches so shaders remain the same)
  14. Because the Tantares parts have been remade and the parts do not match the RO configs anymore. If anyone wants to use Tantares then he/she will have to create brand new RO configs for them.
  15. @DKShang The game clock is outputing the time in UTC.
  16. Wouldn't that be also true for every other mod that adds Gemini, including Making History? I mean, historically, i do not expect just the Gemini command module to support a free-flying mission of more than two orbits (that is the reason why it carries the service module) and definitely not 7+ days (although the required food resources for the 15 day missions were carried of course inside it, everything else belongs to the SM). Yes you do. But these are not part of a standard Gemini spacecraft so you (the user) will need to improvise on how to achieve that (there was never a lunar Gemini mission IRL). As @RoboRay mentions, the FASA Gemini RO configs are really solid on that front. You could probably copy & paste most of the configuration files "as-is". Don't try to impovise things. If you know how to configure RO parts/write C# code/playtest things and leave useful feedback then jump in the KSP-RO GitHub page/KSP-RO Discord and i am sure that you can find a ton of things (mostly RP-1 related) that you can help.
  17. Don't tell me that you are comparing a 80+ modded KSP installation with a stock one... Anyway, RSS/RO/RP for KSP 1.4+ is a reality but, as always, you have to be patient! Also, if you want, you can help since this is a community project.
  18. Kopernicus bug, also happens in "stock" RSS. Can you open a GitHub issue and post a log file there? I am aware that some things have changed in the newer MM versions but i never tested the pack using them. Or it may be just a stupid typo... Edit: and most probably it was a stupid typo (well, multiple). Grab the latest Principia config file from the repo and try again.
  19. You are going to have a really bad time using the old pack, considering that some of the bodies are now part of RSS itself and they will conflict and most probably crash KSP on load. Link: https://github.com/PhineasFreak/RSSExpansion (although more or less in maintenance - only mode).
×
×
  • Create New...