Jump to content

allmhuran

Members
  • Posts

    1,440
  • Joined

  • Last visited

Everything posted by allmhuran

  1. It will be in here: Kerbal Mechwarrior Program on Google Drive , but there's basically no chance anything works anymore. I stopped working on it as of about KSP 1.06 when wheel auto-struts prevented them from being able to walk.
  2. Something like this, perhaps? https://gfycat.com/thatabsolutefritillarybutterfly
  3. Take two did what amounts to an attempt at an ethics panel, while they fill their games with microtransactions and think loot boxes aren't a form of gambling for kids, on the contrary, their CEO actually said loot boxes are protected by freedom of speech and could not be legislated against. The overwhelming response to said panel seems to indicate that they don't have the moral credibility to pull that off.
  4. I'm not able to use discrete throttle control in afbw 1.8.3.3, ksp 1.12 win 64. The four non function are throttle+, throttle-, cut throttle, and full throttle. All other bindings seem to work. Issue created here https://github.com/linuxgurugamer/ksp-advanced-flybywire/issues/34
  5. But the reason doesn't really matter. People getting excluded from the SDLC is normal. People being included is the exception. OK, so you're saying that it's how much earlier that matters. What would be an acceptable amount of time? Do we need to account for people who might be camping in the mountains without access to a computer or the internet for several days? Obviously I don't mean to imply that this is what you are saying, I just mean to demonstrate that there does not seem to be any reasonable objection in principle to the idea of "some people being able to play it earlier than me". And why does anyone care in the first place? Are people worried that they will get teased at work/school because "nyah nyah I have KSP 1.1.(experimental bugfix release) and you don't"? Isn't that a bit childish?
  6. I think the statement that "no one should be excluded from [...] development including testing/input" is a bit odd. Nobody outside of Squad was involved in writing the code, so we're definitely excluded from development. In previous releases only a small number of people outside Squad were ever included in the testing process, and only towards the end of the cycle, and again, that's pretty normal. Why do you think that as a customer you should be involved in the whole dev/test/regression lifecycle? I guess maybe I just don't really understand the content of your complaint. If your complaint is, really, just that some people are going to get a newer version of KSP before you do... well, let me try to demonstrate why that's just a bit silly. Let's say the game is released on the second of April at 7am my time. That's a Saturday for me. So I can get up nice and early and play it right away for that whooooole day! (I don't work on Saturday). But, oh no, people in Los Angeles are 19 hours behind me, so that would be midday on Friday for them. Most people will be at work or school when it gets released, and probably won't be able to play it for another several hours. And then a few hours after that it will be bed time! So I'm going to get KSP 1.1 before they do, and I'm going to be able to play it for way longer on that first day than they are. What should we do, shake our fist at the concept of time zones for being so unfair?
  7. It doesn't look like you've said anything that responds to Snark's argument. Snark said it would help everyone and why that was so. Prima facie, his argument seems reasonable. You've asserted that Snark is incorrect, but you haven't demonstrated why he is incorrect. Indeed your statement that "the game would be released at the same time regardless" actually supports Snark's argument, because it means that when the game does get released it is more likely that we get fast patches for mods (a good thing), and there is no downside because according to yourself, the game is being released at the same time anyway.
  8. I'm not assuming that, it's just a figure I threw in to make things more concrete. Feel free to substitute the variable "x" if you like. The point is that Squad has surely thought about how long it would actually take and have decided that it would delay the release for longer than they would like, so they have, on balance, decided not to do it. Right, it's designed for the most part to help test mods. In other words, it's designed as a big experimental bug chase primarily for mods. So yes, it is a big experimental bug chase. Are you a mod developer? If not, then by your own argument, you have no reason to receive the release. If you are a mod developer then you can make your own inquiries, as was suggested earlier in the thread. And no, I won't be getting it early. I bought from the store. I am eligible to transfer to steam if I wanted to, but I prefer being able to manage the content myself.
  9. But that would defeat the purpose of the release. The point is to have a wide range of people to test, submit bug feedback, and retest when the system updates. This is not simply a case of some people getting the 1.1 release before other people get it.
  10. Guys guys guys gals, let's look at this with a little calm rationality. The Steam distribution network creates the opportunity for Squad to do this wide experimental release for no additional effort on their part. That's good, because it means it doesn't cut into their 1.1 bugfix development time. Fundamentally, the complaints here seem to be this: "Other people are getting the game early. I want to get the game early too." But for squad to make it possible for you to "get the game early too" they would have to redevelop the store updater, set up the required processes for store updates, and so on. Doing this would take time. Which means, yeah, everybody would be able to get it at the same time.... but everybody would be getting it later. Let's say, right now, Steam users will get the experimental on the 43rd of Blarpril, and the full game will be released to everybody on the 57th of Blarpril. But store users complain, and Squad decides to support this experimental via the store. This takes, say, 10 days. So now Steam users AND store users get the experimental on the 53rd of Blarpril, and the game is released to everybody on the 67th. So we went from "You get the full 1.1 release on the 57th of Blapril" to "You get the experimental release on the 57th and the full game on the 67th". Is that really what you want?
  11. Hi, thanks.

    I considered that, but two problems arise

    1) The rover wheels tend not to all go in the same direction (ie, "forward" = both clockwise and anticlockwise rotation for the turret) when attached with symmetry. You could, of course, disable the motors on one side, but then it tends to slip around a lot.

    2) The throttle is needed to set the cannon range (higher thrust = more range), so the throttle input would be set to do two things at once, which can cause problems. You can set different keybinds for the rover throttle, but I actually use a throttle and stick (thrustmater warthog) so that would be annoying for me.

×
×
  • Create New...