Jump to content

Speeding Mullet

Members
  • Posts

    1,095
  • Joined

  • Last visited

Reputation

1,164 Excellent

2 Followers

Profile Information

  • About me
    Shuttle Program Director
  • Location
    Re-entering on an asteroid

Recent Profile Visitors

9,499 profile views
  1. Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 Home 64-bit (Build 22621) | CPU: Intel Core i5 12600KF | GPU: NVIDIA GeForce RTX3080 | RAM: 32GB 3200 C16 DDR4 Issue - Clicking the 'x' on any tank in in the left pane will just duplicate it as many times as you click it. SM
  2. Reported Version: v0.2.0 (latest) | Mods: none | Can replicate without mods? Yes OS: Windows 11 Home 64-bit (Build 22621) | CPU: Intel Core i5 12600KF | GPU: NVIDIA GeForce RTX3080 | RAM: 32GB 3200 C16 DDR4 Issue - Icon scaling prevents targeting body (i.e. minmus) while in map view. SM
  3. Duna - The boss gave me this laundry list of things to do and I'm going to cram it all into one day before the big meeting mission report Swooping in with a 5 month necro to post this . With the latest patch out, I've spent some of my free time over the last 2 weeks getting stuck into this challenge. I decided to go big or go home, throw caution to the wind, and try and run as far as normal what is a typical mission for me. That is to say - over complicate everything, use too many parts, and be way too detail orientated for my own good. I also elected to have multiple packages on a rocket, with other rockets relying on multiple undocking and undocking procedures, with complex staging requirements to boot. I decided to go for the primary stretch Val Watney level, and also decided that in order to keep it simple I would also boost a space station to Duna orbit as a long-term orbital outpost. Why not right? I had fun. A lot of fun. I really enjoyed basically every single part of the mission. But would the mission be even completable given the complexity? Would I succumb to the kraken? You can view the full mission report here, and then below a few summary photos from the mission: So what do I say in summary? This is by far the biggest mission I've run in KSP2. It took 24 hours of real time in designing, flying and recording the mission. In the final couple of hours it took all my might to work around the disintegrating save to get that one brave Kerbal home but make it home Hendros did. This was the most enjoyable couple of weeks playing the game since the release, and I hope you enjoyed the mission report! SM
  4. I'm still playing, please don't presume to speak for the whole community. For what it's worth I'm currently running a multi-ship return mission to Duna and Ike and (with some stubbornness) having a rather fun time. I would assume that over time new features will be added, and bugs will be squashed, and the stubbornness/fun ratio will further improve. I'll still have had fun and enjoyed myself. SM
  5. Perfectly in the context of OPs use of the word would carry nuance to the effect of - OP is emphasising that the game is playable and enjoyable, but some people may disagree. It's a "perfectly" legitimate use of the word My experience as a well-seasoned player of both games - Having played the latest patch yesterday and today I agree with OP that the latest patch is a huge step forward. I threw together a reasonably complex 8 stage Duna rocket with 4 step EDL aeroshell deployment this evening and every single part of the mission from design to landing went perfectly and was bug free, with the exception of the trajectory line bug occurring (this was solved by quitting and reloading). In prior patches I had to work hard to avoid bugs, with this one I had to work to try and create them and mostly failed. In prior patches I observed that you really have to be quite an experienced KSP player with good knowledge of how to mitigate existing bugs and a modicum of patience in order to enjoy the game, but I genuinely don't think that is the case anymore. Even without all the features that obviously have to be added to draw players over or in I still found my session to be a pretty compelling experience. There's a really good base to progress from here now, and I'd encourage anyone to give it a go. SM
  6. I did an Apollo recreation mission as part of the weekly challenges in May. 500t, 251 parts and with a total height of nearly 56 meters. I even went the whole hog on staging, sepatrons, LES, RCS, fairings and docking ports etc. to try and push as many issues as possible out of the mission. I wrote at the time that it was a very enjoyable mission and I stand by that. The main issues I faced though were as follows: Massive gimballing causing wobbly uncontrollable rocket - Turned off gimballing for all but centre engine and rocket stopped wobbling into a total flip. Wobbly rocket - Strutted every stage with eight-symmetry. sometimes twice. Wobble reduced to the point of being able to fly an efficient trajectory. General lack of control - Underestimated the SAS required to control issues caused by 1 and 2. Added additional SAS wheel. Craft still wobbled around its prograde marker. RCS useless and always firing - Turned off pitch, roll yaw on the RCS system, letting SAS deal with these functions. This made RCS highly effective and would encourage anyone to do the same if they are facing issues. Docking ports cause total mission loss - Reduced explosive force and reduced docking acquisition angle. Seemed to mitigate docking issues. Always saved before docking or undocking. Faced multiple bugs. Orbit lines invisible when lifting off from the surface with a stage separation action - Took off with the bug to get the screenshot, then reloaded and jumped the lower stage off the surface, separated the second stage then continued with mission. Some of the issues above may have been resolved since I last played and there are clearly more as others are experiencing, but it's helpful information to anyone that wants to try a similar mission which was eminently possible even 2 months ago without the need to suffer. Yes, quick saving and loading very regularly was essential, but I've just always done that out of habit for playing KSP1 for so many years. The core of the matter for me is that while I say eminently possible to do the mission and have a good time doing it, for it to be so I had to be an (I'd say very) experienced KSP player, have really good knowledge of the existing bugs and how to mitigate them, and have a modicum of patience. This isn't a good position to be in when you are trying to attract a new audience including younger players. The graphic and title is obviously click-bait as Matt Lowne is a better KSP player than me, but it does in its way point to the core of the issue - A lot of less experienced players are suffering, and the only way to stop that is to report bugs if you play, help people who ask for it, and wait for bugs to be resolved. We all knew that anyway though. SM edit - whoa, what happened to the formatting, only noticed it was borked when I switched themes.
  7. I've been away for a number of weeks so I've clearly got a lot of catching up to do with these challenges. Everything is becoming easier to work around as the patches and fixes come into play, but I still had a few issues to work through with struts and docking which I'm confident will be patched/improved soon. Very enjoyable mission and performance seems to have really increased in the latest patch for me also. Here's the full mission report with detailed description, and here's a couple of summary images of the mission: 500t and 251 parts with a total height of nearly 56 meters. This is not a small launch vehicle. Couple of things that really helped with this Apollo style mission: 1) Turned off a lot of the gimballing apart from the centre engines on each stage. This reduced engine induced wobble 2) Reduced explosive force on decouplers/separators, and reduced the docking acquisition angle 3) Turned off pitch, roll yaw on the RCS system, letting SAS deal with this. This made RCS highly effective and would encourage anyone to do the same if they are facing issues with ineffective RCS Minimal wobble on this rocket! Had to play around with struts a little to make it happen. Understand wobbly rockets probably isn't going away, but it would be nice to see it nerfed a little imho. Beautiful view over the mare as the crew enters orbit around Mun Flag planting ceremony completed There's still a bug that makes orbit lines invisible when lifting off from the surface with a stage separation action, so I took this photo, the reloaded and jumped the landing stage a couple of feet before separation so I could see what I was doing on orbit. Burning for Kerbin. I do love the engine plumes in KSP2 Back safe and sound. And bored? Tired? Come on crew! Overall, a very rewarding foray back into KSP2 after a few weeks' absence. Really pleased with the progress the team is making on the game. It's improving a lot! On to the next weekly challenge which is Duna. SM
  8. Ah right my bad. Seeing as CommNet isn't fully implemented in KSP2 and there's no published wiki for KSP2 parts, I thought we might be able to use our artistic license a little but them's the rules it seems. I've got little appetite to repeat the mission with 1 replaced part, so I'll go do something else for a while. SM
  9. Ah yes, the classic year and a half on orbit before departure to Duna! Very nice craft design, the Klass-1 is a well-proportioned launch vehicle. I'm looking forward to more complex mission reports coming out of the woodwork post patch 1, so I'll be following this one. Keep it up! SM
  10. This was a popular thread in KSP1 discussion long ago, created just after the great forum crash. It ran to over 100 pages and spanned 4 years before suddenly it stopped being posted to in 2017. I can only imagine you all just stopped building rockets that failed, so I doubt this thread will pick up any steam. Oh, who am I kidding. I'll kick things off then: I call this "Back so soon?" SM
  11. KSP Version - 0.1.1.0 Operating System and version - Windows 11 CPU and GPU models - Intel core i5 12600KF / NVIDIA GeFroce RTX 3080 Description of the bug. Expected Behaviour - crafts remain in orbit around Duna, and individual craft can be switched between without issue. Observed Behaviour - when switching between "active" craft in mission, mission parts spontaneously leave Duna orbit at 15km/s Steps to Replicate - Rocket upper stage with 4 decoupled relay stats. Decouple 1 craft, switch between vessels focuses on empty space and rest of vessel leaves Duna at 15km/s Fixes / Workarounds (if known..) reload and try again A list of ALL mods - None Other Notes: Please see screenshots in spoiler. Possibly related to physicless engine fairing ejecting backwards through the craft on decouple? SM
  12. Replicated in v0.1.1.0, however, was not quick enough to get a screenshot. Report as follows: KSP Version - 0.1.1.0 Operating System and version - Windows 11 CPU and GPU models - Intel core i5 12600KF / NVIDIA GeFroce RTX 3080 Description of the bug. Expected Behaviour - fairings decouple and drift apart Observed Behaviour - fairings eject forward through payload, then rapidly descend straight down to Kerbin Steps to Replicate - Rockket with fairing, eject fairing. Fixes / Workarounds (if known..) unknown A list of ALL mods - None Other Notes: None SM
  13. 3. Transmitting Live From Duna (Version 0.1.1.0) I knew the patch was coming and it would improve things so waited a couple of days to press on with the missions. Glad I waited as apart from 1 episode of my ship suddenly leaving Duna at 14,841m/s (solved by reload), it was basically a smooth (framerate and bug free) experience. Here's the full missions report. Dinkelstein Kerman did listen to the controller's feedback about the solar panel size, but refused to compromise more than one size, citing "big raspberries" and muttering something scientific under his breath. Thanks to Mullet Dyne we now have the right network support and mapping capability at Duna to pick a site for the next mission, where the team will attempt to land a probe on the surface of the dusty world. Here's a postcard from the mission, if anyone knows how to hide the last bit of graphics (F2 used to clear the whole UI out) let me know: Dinkelstein Kerman's rocket was a massive success and set the scene for larger and larger solar panels. No wait, no, we told you already, cut it out Dinkelstein! SM
  14. I never had any doubts even with the major bugs on release but it's night and day, it really is. What a wonderful effort over the last 3 weeks by the team. Your continued love and confidence in the title you have developed is something you should be very proud of, and it justifies my excitement in the future of KSP2 which I've displayed pretty openly over the last few weeks. Long weekend well-earned I'd say! SM
  15. Having attempted an Elcano Minmus yesterday (also tested rover on Kerbin), I definitely think wheels need some attention. I remember doing a Minmus Elcano in KSP1 (similar design powered by 20 ruggedized rover wheels) and not finding it as "floaty". I tested the KSP2 rover of a very similar design on Kerbin with the ruggedized rover wheels and it wouldn't even move. Even with the larger ones it barely got up some pretty modest hills on Kerbin, so torque could definitely be tweaked. You still have to design around the limitations of low gravity with downforce engines etc so in my opinion the compromise to realism in the interest of playability would be wholly justified. Edit - Top speed is also way too low. Let me decide how fast to impact terrain! SM
×
×
  • Create New...