• Content Count

  • Joined

  • Last visited

Community Reputation

2,800 Excellent


About swjr-swis

  • Rank
    Self-proclaimed Groomer of the Orbits

Contact Methods

  • Website URL Array

Profile Information

  • Interests Array

Recent Profile Visitors

9,997 profile views
  1. The part that is actually not realistic is the generic drag cube calculation of the game applying full drag on a 'face' that is in reality producing THRUST (it's an engine after all). Not arguing about your rules, it's your challenge, just commenting on the 'realism' thing. Differences, as shown in the post that I got in just after you, are really negligible, and in fact look in favour of 1.10.1 as far as I can tell without doing the entire run. But again, your rules. I'm fine with it not qualifying if you intended from the start to only allow 1.10.1.
  2. Ok I had a moment to spare to run a test lap on the 1.10.1 install. Fresh reinstall off Steam (without DLC to save load time), and a direct copy of the tweaked craft copy&pasted right out of the 1.3.1 save, and directly loaded onto the runway. Screenshots at the first lap and a split second later with the game version information shown, just to prove it's really 1.10.1. The results are, as I expected, pretty much negligible. In fact if anything, the craft is performing marginally better in 1.10.1 than in 1.3.1. It would seem I am at a disadvantage doing my runs in 1.3.1. Note that I rebuilt your craft from scratch based only on your screenshots, since I can't load a 1.10.1 craft in 1.3.1 and you haven't shared it anyway. Without having the original, I can't 100% guarantee I got it all exactly the same to start with, before I made the changes I listed. Offer is still open to send you the craft file, so you can compare them for yourself and verify it performs as shown. I'm specifically not posting it here to respect your choice of not sharing your craft, but I have no issue letting you have it - it's your design anyway, with a few tweaks.
  3. Up to OP to rule on this, but something to consider: when opening and closing a cargo bay, there's a bug in which KSP will sometimes 'remember' the drag values/forces that parts in the bay were experimenting, and you end up stuck with them even when the bay is closed again. I did comparisons right after 1.10 dropped, I didn't really notice any significant differences in aero performance, but I'll reinstall 1.10 and do the run there. I looked through the rules before I entered my attempt and didn't notice version being specified, but now it is indeed there in rule #1. Edited in afterwards? I guess that invalidates my attempt. I won't have opportunity to do another long-range run again in a bit, there's work and life and stuff to deal with and even at an average of 40 min/lap with a plane that practically flies itselfonce on cruise, it's a long time to keep an eye on the game screen while needing attention on other things.
  4. Especially important if you're flying with RAPIERs like most entries in this challenge, since they don't have a generator. Good catch.
  5. Tip: include a probe core. The probe core will take over flying while your crew are unconscious.
  6. The F3 readout numbers are notoriously inaccurate, to the point of useless. On my 8 laps entry, it displayed a total of 69M km.
  7. Might I call on the Smokey Yunick rule on this one? Even if it goes marked on the leaderboard and it's the only one to be allowed, I'm rather curious to see what range one such designs might achieve. Might pose an extra challenge to see if a regular entry can achieve similar results.
  8. If this is about needing a longer run, I don't think it matters if you taxi to and use some of the flat area around the KSC too. It's being allowed explicitly for landing as well, why not for take off. But perhaps specifying what you want/need to do would make answering the question easier.
  9. Not sure what happened here... you must've edited this exactly between me opening the thread and posting my own entry, but at reloading it locked up my browser entirely, showing just your imgur album link and no pics. Gotta love this forum software. What mod provides that arrow indicator? I don't think I've seen that one before.
  10. I got curious to see what range I could get out of a low nr of RAPIERs. A single RAPIER plane, while easy to design for one fast lap, seems to have too little margin to carry a long-range fuel load. The Mk1 cabins kept overheating too, so I shelved that for now and tried with two RAPIERs instead. Presenting the swis-circ 2b. 8 laps in 05:20:24. Pure stock, twin RAPIER powered, hybrid Mk2/Mk1 fuselage to combine the high temp tolerance of the Mk2 cockpit with the low drag high fuel density of the Mk1 LF tanks. Since it starts with 832 of LF space unfueled and lands with 116 unused, this design has the potential of another 3-4 laps with some prioritizing and a bit more tweaking. Highlights below, full imgur album here. On the runway. Note that there's still quite a bit of tank space unfilled. First lap. Obligatory screenie from the other side of the world. Coming in hot for landing on the 8th lap. Results screen. 116 units LF left after 8 laps.
  11. You are not using that airframe to its full potential yet. I suspect a combination of relying too much on the autopilot mod, resulting in a less than optimal flight profile, and a not quite optimally balanced plane. I got the impression from your screenshots that more must be possible, so I did a manual rebuild (you offer no craft file, and I'm in still on 1.3.1 anyway). Parts-wise, the only things I think I changed from your build are the precooler at the front instead of the structural tube, the slightly smaller Big-S elevon 1 for the canards, and I used larger landing gear (2x LY-35 and 2x LY-99). I did offset parts somewhat different to balance it better for zero CoM shift. Clarification: this is not an entry to the challenge - it's basically @Krazy1's plane rebuilt in 1.3.1 with a few tweaks and flown a bit differently. Just showing there's room for improvement in this entry. P.S.: @Krazy1 I can PM you a link to the tweaked craft file if you want it; just let me know.
  12. A small example of the kind of clipping I think is fully warranted in KSP. I've been playing around with a small and fast long-range Mk2-body jet. I wanted to have just the cockpit, a single engine, and the minimum parts required to make it fly and perform the way I want. Long-range to me means being able to go anywhere on Kerbin and return without refueling. Fast means a maximum flight time of around 1 hour. Additionally, I want a probe core included if at all possible - I play with G-forces on, so I need a safety net for when pilots momentarily pass out at high loads. Preferably, I want this jet to look the part as well... it needs to be nice and sleek. I decided to try with the Wheesley first, since it's a champion at low fuel consumption. I can reach cruising speeds of Mach 1.7 - 2 @ between 12-14km with Mk1 body planes, which allows them to circumnavigate on as little as 200-300 LF. But I had my mind set on Mk2. Mk2 body drag increases very rapidly when off prograde, and the Wheesley is not exactly high performance which leaves very little margin, so this means I have to balance the plane very carefully to navigate the corridor that will allow it to punch into supersonic and maintain high cruise from start to end. It also means I need to keep this plane down to a single stack - the additional drag of even tiny nacelles would be too much. After some unsuccessful iterations that told me I couldn't even afford to use radially attached intakes (and that there most definitely is a 'right' size of wings), I ended up with a stack of Mk1 cockpit, long Mk2-1.25m adapter, Mk1 diverterless intake, 1.25m probe core, and Wheesley. The Mk2 adapter would've been enough fuel on its own, but as the cockpit is so much heavier than the engine there's no good way to keep this balanced through fuel usage. And I needed intake air. The DSI offers extra fuel tankage, plenty of air intake, and the possibility to offset for balance, all while still being part of the single stack. DSI is then offset as far to the fore as possible, clipping it almost entirely inside the Mk2 part of the body, with the core offset into the exact CoM and the Wheesley offset further back again to visibly 'fuse' with the 1.25m end of the Mk2 adapter. Both the DSI and the Mk2 adapter are then only filled partially, to the exact amounts that make CoM stay exactly put from full to empty. Bonus: the DSI scoop is outside the body (no 'magic' air) and integrates beautifully for a visually very plausible design. Cherry on top: since I am only using part of the tank volume of both DSI and Mk2 adapter, I can even 'justify' the clipping of the parts, for those to whom such things matter. Pics or it didn't happen: Craft file: https://kerbalx.com/swjr-swis/Mk2-Mini-2b
  13. This looks like an old problem from several KSP version ago resurfacing again, which makes sections of the surface randomly start floating away. Not sure if they ever found what the cause was, but I seem to remember it was much more likely to happen if you used the Scatterer mod.
  14. If you balance your spaceplane carefully so it can sustain SAS radial out, it should be able to bleed away enough speed to minimize reentry heat exposure time. Additionaly, you can add a single linear RCS port to the cockpit, offset so it's just in front of the nose, and it'll move the shock cone just off the cockpit skin when you have to pitch down into prograde again. Just these two tricks will make the Mk1 cockpit a lot more viable for spaceplanes.
  15. It is absolutely still a factor. Don't take anyone's word for it, regardless of their online following; just try it - takes all of 2 minutes and one revert to prove it to yourself.