Jump to content

DibzNr

Bug Hunter
  • Posts

    154
  • Joined

  • Last visited

Everything posted by DibzNr

  1. @CFTeague2 It wasn't entirely clear from your report, but I believe this is the same issue, so I've merged your report
  2. @ShadowZone Merged your report with this post
  3. This seems to be strictly a visual bug caused by placing the wings with the COP visualiser already enabled, toggling the COP visualiser off and then on again causes it to correctly recenter, OP's mention of the plane wobbling left/right on the runway is most likely an issue with their landing gear placement rather than an aerodynamic issue.
  4. Your assessment seems to be correct, there is a small delay between the biome changing and the starlab actually pausing its progress (being in a lower orbit makes this more apparent), if the experiment finishes during this small delay then it will be counted for the biome the vessel is currently over instead of the biome the experiment was initiated over.
  5. @StephensanUnarchived your report @CameronLerouxMerged your report with this post
  6. @nasafan2841 Unarchived your old report and merged your new one into it
  7. @roly Merged your report with this post, as it encompasses the same general issue of science reports being missing
  8. Reported Version: v0.2.1 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 | CPU: AMD Ryzen 5 5500 | GPU: RTX 2060 | RAM: 40GB Severity: Medium Frequency: 100% Issue: For some reason, firing any decoupler on the craft causes all jet engines to start draining from every fuel tank with methane in it, completely irrespective of crossfeed setup or fuel lines, this effect even persists through quicksaves and toggling the crossfeed option on and then off again. In the attached video I ran an experiment using a test craft with a variety of engines including methalox, nuclear and ion engines as well as one of every jet engine, the large mk3 fuel tank they're all attached to is completely drained of fuel and the only available fuel on the craft is attached via a decoupler with crossfeed disabled, firing the 1st stage causes every engine to flameout as expected (with the odd exception of the ion engine which seems to ignore crossfeed by default, I'm unsure if this is intended behaviour but figured I'd note it here), but then firing a random decoupler suddenly causes the jet engines to spring to life as they can now draw fuel from the fuel tanks, even through the decoupler they are attached by still has crossfeed disabled on it. Repro steps: Build a craft with a jet engine, a decoupler and a methane/methalox fuel tank behind said decoupler with crossfeed disabled, then attach a 2nd decoupler anywhere on the craft Launch the craft, fire the jet engine, note how it does not drain from the fuel tank behind the decoupler Fire the 2nd decoupler, note how suddenly the jet engine starts drawing from the fuel tank behind the decoupler despite its crossfeed still being disabled Video:
  9. @nikofbean I'm not 100% certain but looking at your video it seems very similar to the symptoms of this bug (which is notoriously common on Laythe), so I've gone ahead and merged your report with this thread
  10. ksp2_x64.exe 2024.02.19 - 11.17.52.02.DVR - Trim.mp4 It seems that the vessel is correctly recovered, the issue is that the vessel's icon in the tracking station is not properly deleted afterwards, which results in a vessel icon that points to a non-existent vessel, leaving and then re-entering the tracking station correctly deletes the icon, the crash occurs due to the game trying to switch focus to a non-existent vessel.
×
×
  • Create New...