Jump to content


  • Posts

  • Joined

  • Last visited


3,015 Excellent

Profile Information

  • About me
    Mad Scientist
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Reporting my experience, as a long-time devotee of Haystack Continued, to my switch to Targetron... I rated Haystack in the top 3 mods for indispensability. Like anything really good and/or indispensable, the few minor things wrong get magnified subjectively; they are still only minor things. In the case of Haystack, I found the UI clumsy (too many clicks to do one thing); the sort-by-distance did not seem to work accurately; moving the camera angle (while Haystack is active) was painfully slow. In addition, I always wondered whether Most Recently Used, Bookmarked, Body categories et alia might be worthwhile. In any case, here's my initial 'gap analysis' of Targetron (which I have found instantly appealing). I have converted to Targetron whole-heartedly. It's very satisfying. I have kept Haystack installed due mainly to issue #1 cited. When/if some of these issues are resolved, I will uninstall Haystack. (Note that Haystack has the ability to Destroy vessels in the same manner that the Tracking Station view has. It's more convenient for cleaning up large numbers of debris items. But I wouldn't miss it and I make no suggestion it be added.) At the moment, I'm preparing to be able to build Targetron (for Linux) with the hope to be able to contribute some code changes to submit for LGG's appraisal. I thought it was worthwhile/right to make this public so anyone can comment. I am particularly interested in other people's views, especially those of the longer-term users of Targetron, and of the maintainer.
  2. I had in mind to post a review of Targetron from the perspective of a HaystackContinued user, for the benefit of those who might like to consider switching. In addition, that review would list some of the few shortfalls in Targetron with the idea that plugging those ought to make Targetron a proper superset of Haystack. This as a prelude to perhaps offering some help in the execution of any of those changes that seem palatable to the maintainer (LGG). And before doing that, an attempt to build Targetron to see if I can manage it. Alas, I am on a Linux machine (e.g. no texttransform.exe) and the build fails. I would guess it might simply be a matter of making a Linux build configuration within monodevelop, stripped down... Any advice before I proceed?
  3. "What?? You want to see my 'EVA Repair Kit'...? Fine. Here it is... [jerk!]" Time management and accurate goal setting at its finest.
  4. OK, I see I have never had runways for NyeIsland, Polar_Alpha, HazardShallows, Harvester or SandyIsland. tl;dr Thanks for the help! EDIT: I wonder if this is because there is of some kind of renaming of KK_1700m_runway to KK_1700m_C_runway, or vice versa? Yes, renaming the 'pointername' from 'KK_1700m_runway' to 'KK_1700m_C_runway' fixes it. I may have gotten unlucky in the far past with the timing of the KSR download...? Problem Solved.
  5. Hopefully, I have the right topic for this... Is it my imagination or is the runway missing from this airport? (If anyone has a suggestion for which kind of runway was here originally, I can add it back myself.)
  6. This hits either a chord or a nerve with me. ("Easy, boy, easy!") (You are completely right (and a gentleman besides).) "If you can see their headlights pointed at you -- no matter what the distance -- they can see your headlights[1]. I am now quite clearly referring only to the 97% of cases in which the road between you is straight and you are head-on. So, now the question becomes: at what distance do your headlights become uncomfortable for the other driver? And the answer is, "you can never know what only s/he can know". (Road laws generally stipulate a distance, but how well can you judge that distance, and at night, and given the distinct possibility that the regulations are out-of-date with advanced lighting technology?) I would further argue, you do not need your high beams on at this point, since your low beams will show you enough about the surface of the oncoming road and the lights of the opposing car will show you where the general direction of the road is. Therefore: it's highly preferable to dip one's headlights, immediately another car is directly oncoming -- at any distance. Obviously, personal prudence may override any general rule of thumb and specific terrain/surface/driving conditions impose their own dictates in less usual circumstances.. Drive safely. [1] i.e. your headlights are now in their eyes!
  7. Snippets from the Mad Scientist Journal Back in January (2022), I posted Batwing Mk2, an aerial Mars Duna exploration vehicle, to KerbalX. Very pleased to be able to announce that the first (long-forgotten) Batwing Mk2 has finally arrived at Mars Duna and is preparing for LDO circularization to occur in 15m. That's a Mule nuclear transfer tug preparing for the retro burn. And, yes, now that you're wondering why it's taken 8 months to get here: I do play in "real time" (a regulatory limit: "no warp longer than 30m; find something better to do"). And, yes, I do play KSP something like 6h per day. Mad scientist that I am... Those who have been following the highly-sporadic Mad Scientist Journal will recall that I've started an independent space initiative based on a very southerly island nation (about the size of Tasmania), necessitating 60-degree inclined orbits. I made some remarks recently about synchronization of launches to assemble a space station; so here's one more observation, for those also inclined to attempt such a thing: make your first launch during full daylight note the UT (Universal Time), e.g. 04:00:00 your launch site (on Kerbin's surface in rotational motion) will be positioned again, under the established orbit, every 6h, at 04:00:00 every day. Easy. KSC High Command has announced Rule Changes for ASR operations. The current rules: any vessel/debris de-orbiting over Kerbin must be followed to the surface and/or destruction. Marked with approximate coordinates in the craft name: e.g. 'SOS 157E PFA-366 Hunter' for recovery (unless within the precincts of the KSC 'green'), a manned ASR operation must be despatched to the crash site and landed within target-switch ('[', ']') range for sunken debris, a submarine ASR operation must be despatched and likewise positioned within target-switch range once all sunken debris has fallen to the ocean (lake) floor. have been amended to additionally require (since the adoption of Targetron, which gives a 1Hz proximity update), target selection of the stricken vehicle is not permitted. ASR pilots must find and locate the target strictly by homing on the target-distance read-out. Here's another (real) example: 'SOS 87/49 SE X-97'. It gives the map grid indices which gets you in the direction to within 10 or so km. Then the homing commences... (Ah yeah: now you're asking "whyyyyy??!") It's actually a fun little game!
  8. The Terkestani Space Force out on display: Just a pair of harmless KISS-II Asterisk space station starter kits (102 tons) loaded on my new Slingshot mobile launchers. OK, here's another one:
  9. Good point. I'm an old-timer playing 1.11.2 (who may never convert to 1.12, since there is no more reason now to "keep up with versions"). So I mentioned it only because it's the vanilla mechanism. And, also, the free choice of your exact launch location. I do enjoy -60.5/39.2 because it's an island nation. Reminds me of Tasmania.
  10. Two items: 1. a new airport under development: Wadi Haifa; still indulging a "minimalist' style... this one has a little more evolution to do. (I hadn't been able to figure out how to get the Krita color picker to report the desert tundra color, but was moderately pleased to mix it by hand/eye/slider coordination and get it that close.) 2. Two, new, Terkestani launches from Olympia, 60S, both shown moments before circularization into orbits aligned with the new KISS-II space station being assembled (in a 60-degree incline):: I mention this subject again because I've gleaned a new perspective from this experience, so far: while I had thought that timing the launch window for synchronizing with a 60-degree orbit would be quite difficult (or beyond my own knack, anyway), it's become apparent that any 60-degree orbit spends more time quite close to 60S (and 60N), meaning the launch window on the ground (which is moving along a 60S track is quite long in proximity to the desired orbit. What seems to be important is -- not to insist on a 90E heading upon launch but -- to use approximately the course the target would be using IF it were overhead. And to make that simpler, and capitalizing on the flexible launch window, one may simply wait until the target HAS passed overhead and is now tracking down-range, but still in a very visible position on the navball. While it is also true that the target moves very quickly through the most southerly part of its orbit, conversely, the launchpad (on a different trajectory) moves through it quite slowly. Here's a take-away, then, for anyone feeling bored with KSP 1 (and desperate waiting for KSP2!)! Do a play-through, however you like, but restrict your launches to one launchpad, choosing from, say, Dessert Strip (6.5S), Baikerbanur, (20.6N) or Woomerang 45.3N. (I'm using TSA15 in KerbinsideRemastered.) I recommend becoming proficient with Alt-F12: Cheats: Set Position to move your vehicles from the KSC VAB to your launchpad. If you're playing for funds, and attempting vehicle recovery, target the KSC as usual; it's just gonna be harder! You are also going to have to solve the conundrum of how to get into the ecliptic, which is actually pretty easy: And remember the Golden Rule: have fun!
  11. My thanks also. Just installed and instantly warming to it. Haystack has always been in my top-3 "goto" mods but its interface has screamed skyward for improvement and, when on screen, it can really bog down camera manipulation. So, thank you!
  12. KISS-II transplants itself to a new orbit under its own power, thus fulfilling the stipulations of its Acceptance Tests.
  13. It can't be a Club without Membership, but membership is open to everybody (which is also Forum rules!). To become a member you just have to agree to abide by the rules, principally 'don't talk about Kayak Club' (which is a rule I am right now flagrantly violating -- it's kind of more of a joke on 'Fight Club', I suppose: secret clubs are just more attractive to join, don't you think?) And, technically, make one trip, either Exploration (discover new place) or Visit (find a location posted by someone else). And the 5 visitors is just a scoring limit. It doesn't stop anyone going there and posting a trip report. At that point, the location is no longer even secret and its coordinates can be published to help others. The scoring is totally not-the-point of Kayak Club, of course; just the fun[1] -- and promotion of our beautiful planet! (Did I mention you get a badge?)
  • Create New...