Volt

Members
  • Content count

    684
  • Joined

  • Last visited

Community Reputation

27 Excellent

About Volt

  • Rank
    I believe I can fly, I think.
  1. I find the PhysX solution quite feasible. I mean, these crashes never happen randomly as such. They happen when performing a random action such as attaching a part or docking a craft. There's got to be an action or actions that are triggering this, and probably they were added in 1.1.2
  2. Bets on getting up to 1.1.5 much quicker than we got to 1.0.5.
  3. Tell me about it with the frequent updates. I installed about 40 mods yesterday, discovered I couldn't play due to excessive GC, and today they bring out another mod-breaking update with plenty of spaghetti-code bugs to come with it. Lovely! I love the naming convention of FAR though; so many important people in Air Eng really have never been credited. Even just here in the UK, there were many, many lead designers and innovators in the 30s-50s who get almost no recognition in history.
  4. They managed to break a surprisingly large amount of stuff... spaghetti code due to the pace of the final days of 1.1 dev and patching?
  5. Ahh, so some of the 'all my mods are broken again' antihype is people not being informed. Phew!
  6. Have all the mods rolled over and died again - has anything significant changed?
  7. There's something in the changelog about garbage creation for the Part.Update() function. I'll do some testing later but I may have to deal with the ever-falling-down fence in my garden first.
  8. Well, this is my Gamedata folder, unchanged since I ran GCM earlier: So yeah, with lots of mods. I mod-sniped a little bit by removing all mods and trying it with just one, but even with just B9 and dependencies installed (a fairly large mod in RAM footprint but not plugin footprint) the GC was nuts compared to no mods. I imagine it is a lot to do with unoptimised code from modders, especially after all the rushed fixes for 1.1. It's worth noting that the GC measurements were taken without any parts inserted and the major GC issues start only when entering one of the hangars for the first time, but without any parts being added to trigger the stutter. It only gets worse.
  9. So we're in for the long haul, then, is what you're saying. No overmodding for the time being - in fact, very little modding at all - for those of us who get a headache from poor FPS and stutters. krakens - I've been waiting for 1.1 for months then 1.1.1 for another couple of weeks, and now I have a super-overpowered PC here playing War Thunder and Tonks. Great. Edit: I've also just confirmed - just to make sure - GCmonitor indicates it is indeed GC that's causing my stutter. The 'garbage' is going up at a rate of about 20MB/s which is just incredibly bad. KSP is the only game I know of that has this problem, despite playing several games on the Unity platform. I wonder what their solutions are?
  10. Problem is, I do only really suffer from it with mods. It's noticeable in the FPS graph without mods, but the overhead only becomes untenable when extra RAM usage is put on. At the same time, I'd argue that this bug is preventing comfortable use of mods, which is supposed to be a feature of KSP - let's be honest, SQUAD themselves can't be expecting people to play their stock game forever and their efforts to assist modders are proof of that. So yes, we do need to demonstrate that the problem originates in stock, but I think it should be emphasised that the stutter is preventing modded, rather than stock, gameplay and thus limiting the experience of a lot of players who don't play stock (ie, those of us who have played since the early days and are understandably looking for a wider experience)
  11. Ahh, so it's possible - with our new increased spare RAM overhead - to limit GC to a longer period for 64-bit installs? I mean, every 10 minutes an extra stutter would be no worse than autosave. It's definitely a case of raising awareness.
  12. GC is a re-appearing disaster in 1.1.1. I installed many, many mods and tested it and the stutters lasted about a second every 10 seconds - so irritating it's unplayable. Removing all mods, the stutter is barely visible but it's there. So I installed ONE mod and its dependencies and the GC is back, probably half of what it was with 30+ installed. It manifests as a deep drop in FPS on the performance page then a spike upwards before Vsync takes over again. It really is awful and I won't be playing it, which is insanely disappointing because I built a new PC mostly to mod the heck out of this game and a stock engine bug (which is surely fixable) has ruined it for me. Is there anything we can do to make this less prominent or is it a permanent gamebreaker?
  13. This looks like a fantastic solution to my biggest problem with FAR flight and might even get me back into it! I was sick to death of having to feather-tap the controls to get small control deflections, which is exactly the reason mouse aim is in War Thunder also (apart from arcade scrubbiness :P) so this will just be amazing. Time to hit the tutorials to re-learn aircraft design analysis.
  14. My PC is in bits, being used as a component burn-out rig (testing old components to sell)! I have a graphics card in four bits on my desk! Y u do this! In all seriousness, well done SQUAD on the long development cycle and the rapid work you've been doing. The prerelease was still pretty messy and you had a lot on your plate for the short time between 1.1P and 1.1. Hope you all sit down for a good rest and a drink-induced stupor.
  15. I tried to takeoff from the KSC mountains after popping just the aileron of my swept-wings science puddlejumper, in a bad landing. I'm not sure if it was Atmosphere Autopilot that did it, but the combination of short field takeoff and high takeoff AoA (the runway was down a slope) caused the aileron-less wing to stall, drop and drive the aircraft down. Shame; I always love a good in flight emergency.