Jump to content

basic.syntax

Members
 View Profile  See their activity

  • Posts

    1,366

  • Joined

  • Last visited

 Content Type 

Everything posted by basic.syntax

  1. basic.syntax
    I took a closer look and noticed the model has gotten a touch-up, the black bands around it are thinner, and of course the collision model has been corrected. (Offset into other parts should be a deliberate player choice.) The "round8" crisis was a due to the proposed switch to Xenon; tons of small LF+O designs with the round8 would have broken. I don't think players can get as worked up over just a name change.
  2. basic.syntax
    Great idea; paint gets burned in a launch, and especially a re-entry. But it would require quite an overhaul to add a new layer to the textures. Some games also fade-in a dirt and grime layer over time.
  3. basic.syntax
    This is a fair counter-argument. Squad can indeed mix up the parts between the base game and expansions in any way they like. And my first poll question didn't quite capture this opinion. You wouldn't feel quite right to choose #1 'yes' but #2 'false' fits pretty well. It was Squad's own choice to include some new parts (even if it is their choice, they opened the door to the possibility of parts developed during MH making their way into the base game, and they have responded to player feedback in the past. Although this is a really extreme example, and no one should get this worked up over a part they don't have: Squad didn't have to "save the Round-8"
  4. basic.syntax
    I think scratches are OK as an idea, (its KSP not SpaceX) but as-implemented on some older parts, they are too bold and somewhat randomly placed. Scratches should be in locations that realistically get scratched - by handling equipment, weathering, etc.
  5. basic.syntax
    +1
  6. basic.syntax
    I think the new structural panels planned for MH expansion should be made available to all players. I would not be picking up the expansion just for objects as simple as these, the expansion is about its historically-inspired engines and capsules. Not to mention the mission builder! These shapes are fundamental building blocks that I think every player should have, they work with any kind of design, historical or futuristic.
  7. basic.syntax
    Forum readers used to know a release was close, when it hit the public-sourced "Experiemental" test phase. Though the community is full of good intentions, those bug reports were always a messy process for Squad to sort through. Squad appears to have some new help, thanks to T2.
  8. basic.syntax
    The 'no permission' link is to a post that is probably being hidden while it is being edited and updated. It could pop back into view at any time
  9. basic.syntax
    Rockomax Jumbo-64: I miss the piping down the sides, its now a featureless cylinder. It works better in continuity that way, I suppose, since the 8, 16 and 32 size parts would need similar bits of visual fluff added to them in a redesign. I wish Squad would leave all the older parts accessible, they could be hid or exposed with a filtering button over the parts picker, and not leave this up to modders. Old parts would work well in career mode, where you could start a game using parts found at the side of the road, and after some VAB & tech tree upgrades your space program has 'modernized' and the newer parts are available.
  10. basic.syntax
    After each update I check the really high 20m/s impact tolerance of the Twin Boar and Mammoth engines, and wonder why they get away with it. Why so high? Doesn't seem right. I can practically use them as landing legs on larger craft
  11. basic.syntax
    lol. I just went through this as well. Not the top, or the bottom - the links inside numbered sections of the guidelines are to forum posts, and inaccessible until you agree. It feels like a shrink-wrap software license agreement in the pre-internet days, where all the fine print was inside the box, but you had to break the seal to find out what it said. Not being able to access those informational links makes a poor user experience, but, like you say - nothing at those links has changed. Still, I think the linked posts should get copied outside of the forums, to static pages on the main KSP website. I also lol'd at the words "2014temp-version" in this older link in section 5.1 - but it is automatically redirected to this current link, clearly not "temp," anymore. Updating that "temp-version" link to its redirect, would add some polish to the guidelines.
  12. basic.syntax
    You've got mail! it was not sending when I wrote the question above. Tried 2-3 times, to two different moderators. Started to think it might be a browser issue, but, it "sent" when I tried it just now.
  13. basic.syntax
    Are mods not accepting PM's at this time? Fallout from hosting move? (I haven't tried in ~6 months.) I got "____ cannot receive messages."
  14. basic.syntax
    Steam sales are up to Squad, they don't have to offer a steep discount during Steam event sales, if they don't want to. I'm not expecting a 50% off sale for this expansion any time in the next 6 months, considering the fan-following that KSP has. I could believe a small discount during the Winter sale, but that's a long time to wait. And... I can't wait that long, to thank Squad for the post-sales support and updates I've received, for years now.
  15. basic.syntax
    I thought I poured over every Weekly, but you found some screenshots I don't remember seeing. Nice overview!
  16. basic.syntax
    Great news, reasonable price, looking forward to it!
  17. basic.syntax
    So many things that could go wrong, did not. An epic launch, followed by 2 out of 3 epic landings... just wow.
  18. basic.syntax
    Lee Hutchinson gently bumps the shuttle into the external fuel tank, and Scott Kelly helpfully points out: "That nose cap, there on the space shuttle? You just crushed it." Those little bumps we get away with on a daily basis, are a Big Deal in real life. Space: not a "contact" sport
  19. basic.syntax
    I've been trying to improve monitor refresh rate, but the oven bake time needed for clay of this thickness is making anything over one frame per day - really, really difficult. I need a better workflow, or some code optimizations...
  20. basic.syntax
    New players go through this in every update cycle: worries about broken mods, how to keep playing old version until X is updated. I have been around for a few cycles, so I know to make a backup of the installation. Steam is a bit at fault: All they let me do is choose between auto update, or defer an update until it's started thru Steam launcher. Steam could really use a per-game option to "notify me when an update is available / don't update until I approve."
  21. basic.syntax
    Congrats to the team for passing another great milestone in development! This code overhaul and optimization for localization should greatly enhance the accessibility of KSP for many more players. And bug fixes never go out of fashion - thanks, and keep them coming!
  22. basic.syntax
    Although "missions" appear to be a separate game mode not contributing anything to a Career Mode game, I hope / would like to see the new parts available for use in career mode. Which means they would have to be assigned values for the tech tree. Really good question here; scoring will differ wildly depending on mods used. The included "historical missions" will be subject to a "top scores" thread somewhere in the forums, I am sure.
  23. basic.syntax
    From the Store faq: Some of the historical background: http://www.eurogamer.net/articles/2013-04-11-kerbal-space-program-dev-pledges-free-expansions-after-fan-outcry
  24. basic.syntax
    While thinking about repurposed oil drums and mis-aligned bolts, I remembered this glossy article about the nuts, bolts, and imperfections of the Apollo-era F-1 engine.
  25. basic.syntax
    The expansion is wonderfully optional. I think parents with kids might enjoy setting something up with the proposed mission builder. Even without it, every current player continues to benefit from ongoing updates to the base game.
×
×
  • Create New...