AbhChallenger

Now that Twitter has confirmed that KSP is coming to WiiU. I would like to express my opinion. Which is sadness over such an obviously flawed decision to port KSP to the WiiU. I know that Unity 5 makes it possible to put games on many platforms at once. However, That does not mean it is a good idea. KSP is not Mario. It makes use of CPU heavy physics to present a semi-realistic experience. And the WiiU's CPU is anything but powerful. Not to mention that with only 2 gigs of memory. It simply is not good for an ever growing game. The worst part is. There is no way you can say that the weakness of the WiiU will not be a factor on the decisions regarding parts or features. So the game will have gimped potential simply to make some extra sales... How sad. It is a dark day for KSP and it's fans.

Two things to keep in mind tho. NASA would order decrew long before supplies run out. In case there needs to be an emergency recrew to save the station. Progress will help. But in the grand scheme of things it is better at delivering fuel and re boosts over cargo. And HTV is a one off thing. Giving the station a few extra months of supplies. ISS remaining crewed is going to require zero failures all the way until a good part of next year. Assuming SpaceX needs that long for Dragon to fly again.

Progress alone was never enough to keep the station supplied. Progress will merely delay decrewing if they can't rapidly fix dragon. It is interesting tho. Because of the dire situation of supplies onboard the station. I can theoretically see NASA approving an emergency launch of an already flown dragon. Congress would approve it over leaving the multi billion dollar station unmanned.

The absolute worst this can delay "Humanity" is one or two decades. (And that is assuming SpaceX and commercial involvement in NASA collapses completely) However in the grand scheme of things. We are still going to be able to get off this rock. Just a tiny bit longer than we had hoped. Technology moves forward. Eventually the good ole rocket will be hopelessly outdated.

sarbian, Flood gates open for a week of RC testing on Steam? Sounds a bit dramatic to me. And frankly is borderline elitism. - - - Updated - - - That were tested by QA and Experimental teams before we got to use them. Which to your credit worked well. What I am worried about is what the switch to Unity 5 has in store.

Personally I do not sign NDAs so I would never be allowed to join the experimental team.

That was ages ago. And unless I am mistaken. It was not using the steam beta. Steam beta you have to deliberately enable the thing that says beta. The thing that says "Testing only" or "UNSTABLE!!!" We do not need the QA builds or very early Experimental. Just toss a week on the planned date and let people poke around with an RC version. It does not have to be the higher quality of testing at that stage. It needs quantity.

The Carbon Space Launch System. Because it is a carbon copy of every overpriced, job creating waste of taxpayer money meant to take NASA back to the moon for decades.

This shows in my opinion that a steam beta as a "third stage" of testing would be beneficial. Let folks not under NDA test for a week or so before it comes out. They may find nothing. They may find the showstopper that slipped past the two other teams.

We don't know IF the two teams spotted the issue before 1.0 was out. Because of Squad's (Rather silly in my opinion) NDA. Personally I feel a good middle ground for 1.1 is simply allow steam beta say a week or so before planned launch. Anyone complaining about changes that happen between steam beta and steam public will be branded a fool because the beta will clearly say that it is for testing ONLY. Yes that does mean absolutely crap bug reports (Oh noes my rocket flipz!! HALp!!!1) But it will allow a little heads up if an issue somehow made it past the two teams that are under NDA. IF 1.1 is indeed the great move to Unity 5. I feel that all the testing that is possible should be allowed.

Targets? The team got a few negative comments on the forum. I highly doubt people are sending you PMs saying "OMFg ... w3re you testing!!11 You suxOrs!" Sad that NDA prevents you from talking about testing after the fact. Squad should modify it.

This. Unity 5 is the best chance Squad will have for a long time to actually implement a quality 64 bit client. One that becomes the standard instead of the exception. It must not be rushed for any reason.

Perhaps I went a little far in saying what I did about the testing team. However, It IS time for a change. Squad needs to allow either FAR FAR more people onto the testing team or they need to start doing Steam Betas. Some of these issues were frankly obvious and not being spotted may indicate that the team involved with testing is simply too small.

Another reason why 1.1 needs much much more testing.

We don't want to back to the days where modders disable X64 support because it makes support that much harder for them. KSP with Unity 5 needs to be tested, tested, tested, bugfixed, balanced tested, tested, and then more testing before it is public.

The very fact that it required a laundry list of changes in a single hotfix says otherwise. Along with bugs discovered only once streamers got their hands on it.

To me 1.0 has been one of the worst launches of a KSP version in it's history. And then a hotfix changes the aerodynamics less than a week from the game coming out of beta? Version 1 was not ready. Either the experimental team failed to notice obvious bugs or you rushed 1.0 out the door. Either one shows that there needs to be a big change in how these versions are handled. Squadcast seemed to hint that 1.1 will feature the long awaited KSP in Unity 5. If this is the case then PLEASE PLEASE do not rush it! If a Unity 5 bug itself is preventing a bugfix. Wait it out! Do multiplayer work or something to pass the time instead of pushing 1.1 out and blaming Unity for everything. Test. Fix Test more and then Test more when you think you have tested enough.

It should have been caught in experimentals. Along with many other very obvious things.

No I mean actual beta. As in the one you have to deliberately activate in steam to access. Along with rules regarding requirements to post issues in a beta forum along with rules about how mods are handled. Will it lead to some chaos? Yes. Yet it beats what we have now where OBVIOUS bugs were spotted by streamers less than 24 hours before launch.

Geeez! It is quite obvious just how little 1.0 was tested before launch. These are NOT small changes and break a good deal of the effort people have gone into updating their mods/crafts after 1.0 launched. This is absolutely why public betas NEED to return. The experimental team is just not cutting it anymore. Especially if converting to Unity 5 is in store for 1.1

Valve did not take 75 percent. They took standard microtransaction percent. Bethesda took the lions share.

Requesting this awesome tool updated for KSP 1.0

By that time period probes will be so advanced and common that I HIGHLY doubt there will be support for a Taxpayer funded manned mission. Given the choice I would rather a manned mission to Pluto over Jupiter.

That's assuming that they blow off very slowly. Instead of very sudden.

Usually it is just stop playing for a week or two for mods to update. However this time I think I am going to let KSP reinstall completely from Steam. I had been thinking about just playing other games until whatever version got Unity 5. However, with those performance improvements. I likely will play 1.0 a great deal.