dr.phees

Still, what about the suspiciousness?

A basic description is here: https://en.wikipedia.org/wiki/Aircraft_flight_control_system#Secondary_controls KSP also allows trimming your craft. Using that for SAS would allow combining user/pilot input with the trim, eliminating the weird bumps when you try to correct pitch while in SAS mode.

Yes. A 60% chance. And that's worldwide. English covers about 11%, Chinese alone comes to about 16%, more than doubling the user base. All together the new languages cover roughly 30% of the world population. (This excludes foreign language speakers and the groups might overlap, but we should expect KSP to have roughly twice the userbase or more now.) And now the changes to KSP will allow easier integration of more languages, probably even for modders. I think this is quite a change. My guess for a good next Language: French. EDIT: The numbers are based on the estimated L1/L2 speakers of: Englisch: 400/400 (L1/L2) Spanish: 570/90 (L1/L2) Russian: 260 (L1) Chinese: 1200 (L1+L2) Japanese: 125 (L1+L2) (all numbers in million people)

If I didn't speak english, I would actually be much more interested in a localised version. If only to finally experience the bugs first hand! Also: THE HYPE!!1!

This makes it sound bad. Since Squad is a company, they need money. Without selling an abonement, they have to find new markets. We cannot expect them to bring out updates for free without having something to pay people with. Sure, Squad itself isn't without flaws, but morally questioning them for earning money seems a bit strange in itself.

In this case squad should be perfectly able to do this without looking at any code. It is a basic thing and already implemented in the stock SAS. It is "just" a bit of rewiring...

I hope this will be done at some point. I am currently trying to find out if there is some way to do this via an addon. The problem is, that the autopilot input would have to be re-routed to the trim. Does anyone know if that is theoretically possible at all? With kOS it should be quite easy to do, I would guess.

Yes, would be nice. "a new star system" would require either procedurally generated planets, which could be a nice DLC, or simply open/activate a jumpgate-system to moons of the various planets, allowing a kind of late-game alien-tech travel network. Nice addition and a end-game goal. Minor critique: Retrograde polar orbit doesn't make sense.

That's not really true! This particular ion drive is made for small craft. The ion drive itself scales nicely, it just isn't meant for quick dV changes. It is, due to its low TWR, meant for constant thrust scenarios. No reason to keep them small at all. It is actually handled as a possible drive for manned long range missions. You are right, though: It is not very suitable for a tug

Thanks. This behavior would really help. I hope someone at SQUAD picks this up. (By the way, I think this solution would also be nice to see in MechJeb...)

Exactly, you nailed the explanation.

I routinely fix one small wheel below my spaceplanes' tails, so I won't rip off the engines when pitching up too far.

No. I mean I want to be able to fly an SAS stabilised craft without the sudden jerks back and forth when I touch the controls. IF SAS used TRIM instead of the direct input, that would be the case. Also it would be good to keep SAS's input when turning it off, basically making SAS input the trim when disabling it. You could disable SAS and have butter smooth flight. Without having to immediately compensate for it recentering the controls. An example: The autopilot settings in FlightGear do exactly that. You let your plane for example hold a course and turn off the autopilot. The trim stays, so the plane doesn't turn a bit in that moment and you take over a perfectly balanced and stable craft from the autopilot.

Do you hate it when your craft is tugging along on SAS and you want to correct the course a bit? You touch pitch controls and it gets all wobbly. There is a simple solution to your problem: SAS should not control the control input, but work via the TRIM settings. You control input would be combined with the TRIM and you would have perfect controls even with SAS activated. Better yet: Allow the TRIM settings to be kept when leaving SAS (maybe with a modifier key or so) and move your craft from SAS to full manual control without even the slightest bump. Why we should do this? Because usually it is done like that. Your input is combined with stabilisation/trim. If it is still unclear what I mean exactly, move down three posts. User OHARA does explain it better!

I'm one of the early buyers. I currently maintain 4 game installations. One is my own, meeting the early-adopter-all-DLC-included criteria, the others were gifts to others and don't include it. From my view, early adopters are basically responsible for the outcome of the community, which is in my view pretty brilliant. Sure, I like the idea of getting the expansions for free, but I will happily pay for the DLC, at least for the ones I gave away and make it another gift. Actually, I bought the first gift as a thank you, just because KSP delivers so much and I felt fair to pay again. (The good old comparison between a cinama ticket and KSP pricing makes sense here.) So, yes, I think paying for a DLC will not hurt most users and it makes sense to pay SQUAD again at some point to keep on working anyway. So, I would vote against an unlimited "season" pass.

Finally! Have been asking them for months!! I hope the Unicorns are evil and aggressive, trying to pierce wheels where ever they get a chance!

Oh man, now I am hyped!! And I'm on a train!

They are the remnants of a space colonisation went partly wrong. Kerbin was chosen as it sported some interesting things, like the pyramids, where the initial colony was set up. Another second colony later became the KSC. The first colony made one mistake: They opened up the pyramids and set free deadly spores. An ancient intelligent species lived on Kerbin once and somehow created something deadly and accidentally set it free. When they found out what had happened, they created the pyramids as a warning for any interstellar species and decided to bomb their own planets surface clean, except for the warning pyramds, which were sitting in a dry and dead place anyway. The location was called Death Valley. Well. Now the modern colonists set free that particular curse. They were shocked and decided to find a way off the planet. Since their original space port at the pyramids is too dangerous, they set up a new space program and that's where you kick in. The airport on the island was an off-limits installation for research flights to other locations like the Death Valley installations. It was considered to be too dangerous in the end and the whole research program was closed down. Kerbins never built cities and control their own numbers very strictly since they know, that they all have to leave Kerbin at some point. Their currency is necessary, as the resources are very limited in a colony and the currency mainly shows the resource availability.

I am pretty sure the homes are the hills. Ever since the Kerbals have known that space travel is possible, they developed a certain fear of aliens. They decided to tear down all the visible structures and remove all signs of habitation. They needed homes, though, and since Kerbin itself was a pretty flat and boring planet, they decided to re-build their homes as artificial mountains. Inside those mountains, they have underground cities. Some rogues decided to go the other way, they actively search for alien contact. The undergrounders found one simple way to get rid of them and not endanger the society any more: They founded the KSP in the hope of giving those rogues a way off Kerbin and possibly, at some point, out of the Kerbol system. That is also the reason for that single actively used space center. They want to build it back when the rogues finally have left. Think about that. Whenever you scream in over the mountains just before the KSC, millions of Kerbals swear about the noise those damn rogues make.

Yes, that would be brilliant. I would like to see a few surface mountable, low profile variants as well.

I am using mini-claws with Tweakscale all the time, they work great! Tweakscale should be stock anyway. It would lower the number of similar, just differently sized parts in the partlist (and a little bit of RAM usage I guess).

I am running modded and unmodded installs and the longest I get KSP to run is a bit over 40 minutes. It's about the same for both, modded and stock. This happens while doing things. If I leave KSP unattended, it does not crash. My machine is a Linux 64bit Core2Duo E8400 with 8G RAM.

Could be a nice new mod: The cycler calculator!

It is in! You can switch the orbit line fade bahaviour! Well done, Squad!!

Yes, loading the KSC still takes its time.