Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by Kobymaru

  1. New release is up! Version 2.4.1 for KSP 1.8 to 1.12.x Download from GitHub or Spacedock Changelog: ## v2.4.1 for KSP 1.8 to 1.12.x - 2021-06-27 ### Changes since the last release - Support for KSP 1.12.x - Max decelerating G-force readout now correctly displays the predicted value - Targeting vessels that are splashed down is now possible
  2. Turns out that this is enough to reproduce it, and turns out it's unrelated to KSP 1.12 and has been in the mod for a long time. I have trouble figuring out the reason though, so for now please just disable Trajectories when you fly an EVA Kerbal. For 1.12 I should do more testing, but hopefully I can get a release out soon.
  3. Because it's compatible with versions up to 1.11. ps.: Next guy who says it doesn't work with 1.12 or asks for an update gets reported. It will be ready when it's ready.
  4. Here: https://github.com/dkavolis/Ferram-Aerospace-Research/releases/tag/v0.16.0.1_Mader And also on CKAN if you click the "Versions" Tab, you can select the previous version.
  5. It's FAR v0.16.0.2, it always returns 0 Force. Fortunately, this has been fixed already. So either revert to v0.16.0.1, build the current master or wait for the next FAR release.
  6. Hi! I can not reproduce this, I installed Trajectories and nothing else, but I did not get those errors in my Log file. Trajectory was displayed correctly. Is it possible that some settings file was left over from when you had the toolbar installed and enabled?
  7. This means that the prediction is wrong. There could be a few reasons for this: Predictions in the upper atmosphere are difficult, so if you spend a lot of time there, deceleration will be underestimated. Physics time warp actually changes your trajectory! The higher the time warp, the less drag you experience. Is "Use Cache" enabled in the settings? That increases performance but decreases accuracy.
  8. Guys chill out, I occasionally come in here and change the thread title as well as the AVC metadata.
  9. Hi @CBase, I stalked you on GitHub and those cache changes look very interesting. Why do you think a pull request is not a good idea? It would be really cool if we could have your stuff as pull requests (preferrably separate ones) that we can look at and review, and maybe get them fixed up so that they can be included in a release.
  10. Would one of you guys mind creating a GitHub Issue here with the logs: https://github.com/neuoy/KSPTrajectories/issues Edit: Nevermind, PiezPiedPy amazingly quick-fixed it.
  11. I don't think we have one, but good idea! Could you make a GitHub issue for it? The only problem i can see is that "hotkey space" is getting pretty crowded with many mods. Any suggestion for a good (not overused) key?
  12. Just FYI, I'm neither dead nor missing, but rather busy at the moment. This is unfortunate, but that doesn't mean Trajectories is "abandoned", especially since PiezPiedPi is still working on it. Great thanks to @PiezPiedPy for keeping our mod up and running!
  13. Hi @linuxgurugamer! I have an issue in the VAB, namely I get very small stutters that are most noticable when the camera is moving around. Uninstalling KCT fixes the issue. They are not GC Runs (I checked with MemGraph), but I do get a lot of these messages in the KSP.log: [LOG 18:36:14.981] [KCT] Attempting to take control of launch button [LOG 18:36:15.025] [KCT] HandleEditorButton.controller is null [LOG 18:36:15.503] [KCT] Attempting to take control of launch button [LOG 18:36:15.546] [KCT] HandleEditorButton.controller is null [LOG 18:36:16.027] [KCT] Attempting to take control of launch button I'm using KCT version with KSP 1.6.1, but also affected. Disabling "Override Launch Button" in the settings does *not* work around the issue, stutters are still there. Please note that the Realism Overhaul fork of KCT (here: https://github.com/KSP-RO/KCT) does not have these stutters! So there is likely something that broke between when it was forked and now.
  14. Where were all of these performance reports when I implemented this ages ago and asked for feedback? If that's common for everybody, we'll disable it by default again. But this time I'd like to know some details first: how many parts does your craft have, how long is the trajectory?
  15. The cache makes long trajectories (when you spend a lot of time in the first 10 km of the atmosphere) quite imprecise. I did some performance testing and it looked like disabling the Cache would not be too bad in terms of performance. I didn't expect people to notice the difference too much, TBH. If using the Cache still gives you satisfactory precision, leave it on.
  16. Oops, sorry. Fixed now. Yes, I disabled the Cache by default. This means higher precision but worse performance. You can turn the cache back on in the settings.
  17. Do you mean that this is not possible or that you don't have time for that? There is another mod by Raidernick who has an LK as well: https://github.com/KSP-RO/SovietSpacecraft/ He recreated the engine assembly pretty accurately, with the RD-858, RD-859 and the vernier thrusters as separate parts: Maybe you could take a look at these and see if you can replicate that? I'd love to use your version of the Lander, it's truly beautiful.
  18. New release is up! Version 2.2.3 for all versions of KSP from v1.3.1 to v1.7.x Download from GitHub or Spacedock This is simply a recompile, so no new features in this one. About the Kopernicus issue: We now have a mechanism for Bootstrapping the right version of Trajectories. However, I am not certain that this mechanism is needed or if we can maybe just use the same DLL for all versions. I'll discuss this with @PiezPiedPy , and we will push another featureless recompile if we decide to remove it.
  19. I'm busy with real life, and looks like PiezPiedPy is too. We could probably push out a point release for 1.7 compatibility, but it would basically be a recompile and wouldn't have new stuff in it.
  20. The force calculation takes into account the temperature/density of the atmosphere, velocity, drag and lift on every part of the ship, every 2 seconds. The value for the drag depends on which other parts are attached, and the value for all of these depends on the position of the ship. The position of the ship depends on the values in the previous steps, and the values depends on the position in the previous steps, ... There is no single value you can paste.
  21. I think we might have made a mistake with the "backport" releases: we prepended the KSP version to the Trajectories version, and the CKAN robots might have gotten confused. I'll try to sort it out in the next release.
  22. Hi there! Hey there! I am using KSP 1.3.1 with RealismOverhaul, Realist Progression 0, RSS and a bunch of other mods with Principia 2018120707-Erdős-0-g3e2334a95bcfc6869b5464ecda5ae48b5412dba0 . Unfortunately, my Scene load times seem extremely long. Without principia, a scene change takes 10 - 15 seconds. With 2018081110-Desargues, every scene load took at least 1:30 minutes. With 2018120707-Erdős, this became even worse. Now every scene change takes 3 minutes!! During that time, the Memory usage drops quickly by 2-3 Gb and then slowly builds up these 2-3 Gb until the scene change completes. My savegame has about 36 vessels, and the save file has a size of 10 mb. Is this to be expected with principia? I know 1-3 minutes doesn't seem like much, but it seriously disrupts the gameplay. Is this a bug? Is there a workaround for this? (I have reported this on GitHub as issue #2038)
  • Create New...