Jump to content

xcq

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

5 Neutral

Profile Information

  • About me
    Curious George
  1. On the contrary, I find it updating too slow. :-) Mainly because it is inconsistent: The orbital part seems to go fluent and change each value with almost each frame (I guess something between 30 and 60 ups?), while I can see the 10 updates / second in the vessel part and it seems like it is stuttering to me. Might just be personal preference. I can live with the fact that VAB/SPH values are not overly specific, because I think pre-flight Engineer is just a tool to estimate your performance. Your ideas sound good. However, just to be clear: What I'm pointing out is that there's a difference between right-clicking the turbojet engine mid-flight and the thrust displayed in the Flight Engineer, see the screenshot from my previous post. The Flight Engineer claims it delivers e.g. 220kN when in fact the engine tooltip says there is only half of that amount, e.g. 110kN.
  2. I've tried the fix with the DLLs dated to Apr 03, 14:09. Mostly no issues, but I have noticed two things so far: 1. In comparison with the original Engineer, it seems the Thrust displays have gotten a little bit jerky. I guess it's more performant that way, it just doesn't look as... fluent, I guess. 2. Turbojets seem to produce wrong Thrust information which results in wrong TWRs which results in critical mission failure. At first this happend to me with a B9 part, but I just tested the stock Turbojet, see here, the discrepancy is almost factor 2. Oddly enough the Turbojets say max thrust 225kN in the tooltip and basic jet engines do not seem to be affected.
  3. So I finally get around to register at KSP Forums to contribute to the general knowledge. First off: Great idea, especially for people who want to upgrade their system and estimate the improvements on KSP. One suggestion though: At your second post the "Cinebench and Passmark" graph is missing the individual names of the CPUs. It would be really helpful, if they were right next to the data point, and you didn't need to look the values up and make a guess which ones they could be. Also did the benchmark with my old and new system. I tried my normal save with tons of mods but that was horrendously slow. Started with a brand new KSP 21.1 install and save, nothing else there. Only thing I changed from default settings was the resolution and physics delta-time. V-Sync was apparently forced by something else and I was too lazy to fix that. I stopped each run after exactly 6:00 in-game flight time had passed. FPS data: https://docs.google.com/file/d/0B0PzQSzrNEYnNmZVU2lTTm42WDg/edit?usp=sharing PM/CB: Q9300 @ 2.5GHz: Passmark 3,588; Cinebench 2.96 Q9300 @ 3.1GHz: Passmark 4,267; Cinebench 3.62 4770K @ stock: Passmark 10,970; Cinebench 8.55
×
×
  • Create New...