Jump to content

mostlydave

Members
  • Posts

    255
  • Joined

  • Last visited

Everything posted by mostlydave

  1. This is ridiculous, they know when I purchased and what Steam code they gave me, I found it by logging into their website. Why couldn't this be automated so everyone isn't trying to email support at once?
  2. I purchased KSP in 2012 but didn't transfer to steam until after April 2013. I tried what you recommended and it's not working for me.
  3. What if you bought the game before April 30th and transferred to steam later?
  4. I can't believe that they waited until launch to tell us we will need to email support, I guess I will not be playing the DLC for another week...
  5. I think this is the normal, barely competent Squad cluster.
  6. With the stock texture switching in 1.4.1 will we be able to pick textures for parts?
  7. Yeah, I'm sure there is no communication between Squad and Take Two, and Squad is just as in the dark as we are
  8. How about an update on the EULA or the lack of an opt out of KSP sending information in 1.4?
  9. Yeah, the fix wasn't in the version Squad pushed out, and they could have noted that in the release page, or by adding known bugs to the release notes, but I guess it's better to just pretend everything is OK.
  10. Squad new it didn't work before they released 1.4, but didn't bother to mention it on the release page, or by adding a "known bugs" do the release notes, so don't feel to bad about asking.
  11. The missing IVA is ridiculous, especially since the release announcement hyped the new part. Someone over at Squad should be embarrassed this build shipped. They also didn't update that release notice to indicate the IVA is missing, even though they new it was before the update was released. It's also not mentioned in the change log.
  12. I couldn't agree more, with over a year in development the amount of bugs in this release is crazy. I cannot believe they shipped this update a few days ahead of the making history update in it's current state. The only reason I can think of to do it is to try to have the community find all of the bugs before the first DLC releases. I thought other releases were tested by the community, but that doesn't seem to be the case now.
  13. It would have been great if the RCS on the new pod worked in all directions, eliminating the need to add more RCS units to a command pod
  14. Really wish the Mk1-3 RCS worked in every direction so you don't need to add more RCS to the service module
  15. Already talked this to death on the 1.4 release thread. I understand there will be bugs, but it just seems ridiculous that the new command pod is one of the major features of the update and it's missing it's interior! Where is the testing for these releases? Didn't squad used to do test release to some modders and testers?
  16. I'm not really worried about the cost, I bought KSP early enough that the making history stuff is free. I put a ton of time into the game and got my monies worth. I just find it troubling that it's OK in the game industry to ship something that's not done right, and everyone should just be ok with that. OK, I give up. It's just really disappointing to get all excited for an update when they are so infrequent, and one of the few new parts isn't right. Finding out that it was a known issue, but the update shipped anyways is the real disappointment.
  17. Why would you not just wait until next week and release a fully functional 1.4 with the fix along with the DLC? I understand you need to make money, but when I buy a game that is in development, I don't consider everything that is added unit the game is complete "free" It's the stuff I'm paying for with my purchase When I do something I do it right, I don't understand the logic of releasing a half way done update with a known bug instead of waiting until next week and releasing it fixed, and done right.
  18. We understand that, but Squad shipped and extremely underwhelming update for the amount of development time, and on top of that it's got a huge bug that someone was apparently aware of before release if it happened "late in the game". Why wouldn't you just hold off on releasing this update until it was right? I'm not trying to put you down, I love your stuff, but this update just feels like it was rushed to release to build hype for the paid DLC next week.
  19. I'd love to hear the logic behind shipping an update that took over a year to make with the IVA for the only new capsule part missing. I'm sure a lot of hard work went into this update, but to your average player it seems like Squad just gave up on quantity and quality. On top of that the answer is to just wait a week for a fix!?!?!? Really? Why in the world wouldn't you just wait a week to release fixed version? I'm kind of excited for the Making History stuff, but there is no way I'd pay for it after seeing the quality of this release. Squad should have focused on finishing and polishing the game before going for a money grab DLC.
  20. How is it possible this update took a year to make, and they couldn't even manage to get the IVA one of the few new parts right? Now it's going to take a week to fix? I'd love to know the thought process that led to shipping this update with such a glaring bug. Did you guys just give up over at squad?
  21. Anyone know what we need to block with pi-hole to prevent this tracking?
  22. I hope the update the EULA, and you are able to release this, I've been checking in on this thread, and waiting for this for over a year! Please let me know if you're looking for someone to test while you wait for the license update!
  23. Just off the top of my head, the heat shield is in structural parts, the docking port and decoupler is not in the docoupler category, neither is the service module ring.
×
×
  • Create New...