lyndonguitar

For all I know it was not planned for .20, Maybe they are doing something special for crew containers in future updates. like transfering kerbals. All crew containers would have portraits and IVA then, planning on adding more crew tanks before releasing this one

The problem is not with the bug reports, the problem is these people think they know better, like the OP. Let Squad handle all the development plans and roadmap, we just do the bug reporting. There is a reason why Squad is developing the game and we are the customers. It's like going to Mcdonalds and telling the cooks there how to cook their own food.

How many members do the QA team have?, How many different system configs do they possess? How many people bought, own and play KSP??, How many different system configs do they possess? unfortunately you are one of the players who has these so-called game-breaking bugs. fortunately I didn't experience any of it. Maybe bash me too for not extensively testing the game? The unfinished game has bugs: FACT The QA team has ironed out as many bugs as they can but still overlooked some bugs: FACT The community is so massive compared to the QA team that some bugs were found shortly after release: FACT they will fix it eventually: FACT meanwhile you can play .19, if your still unsatisfied with .20: FACT What's the point of all of this?? You guys are just impatient, Let's see you guys make your own game and do better. You paid for the game knowing that it is still unfinished, is in an alpha state, has bugs like it or not. It's a gamble. With your attitude you should have waited for the final release version, may it come 2013, 2020, 2030 or beyond.

WE are that bigger team if there's any, You fail to realize it

Which is not perfect, They iron out as many bugs as they can, However due to the nature of the game, there will be some overlooked bugs. They can't possibly test every single possible thing that can happen in the game, let alone have every single possible setup, hardware or software to test the game. there will be some overlooked bugs, like it or not How many members do the QA team have? How many people own KSP? as I said, you aren't being forced to play .20, You can still play .19(if you've backed it up) while you wait for .20 hotfixes Is this the first early access alpha release game you've played? Because I am so damn sure KSP is better than 99% of them. If you think KSP is already buggy, wait till you play other games.

Can you fix it please? I would love to use them, There's only two rotating ring mods in KSP, yours and Nautilius Also there is a bug in the G-hab, if I reload the vessel, the G-hab will return to a pre-animated state, it still acts like it was inflated, but it appears to be deflated.

Can you tell us more? how many FPS before and after? If exact value aren't available, at least give us an estimate

no legal way that I know of But if you have a backup copy of .19, temporarily switch the folders of .19 and .20 so that .19 will be placed on the steam ksp folder. and .20 on the back up, then tell steam not to auto update KSP, that way you could play KSP .19 on steam.

i was just going to start a thread like this. anyways yeah, I would like to know what the general current lag limit, For my rig, which is i7-2600 4.5ghz, 8GB RAM, Radeon HD 6870, It super lags on 500+ parts. like 10 FPS, normal FPS is around 100+, I tried playing .20 for a bit, just to test the features, Normal fps is 200+, but never tried to push it because I switched back to .19 due to mod compatibility reasons. A General question would be, Anyone here who had any heaviliy part'd vessel that previously lagged on .19 but now runs better on .20?

HELLO "The alpha phase of the release life cycle is the first phase to begin software testing (alpha is the first letter of the Greek alphabet, used as the number 1). In this phase, developers generally test the software using white box techniques." This is a public alpha. the public, which is us, tests the game. then provides feedback to help with the next incoming patches and updates, if there's a very, very critical bug that is preventing majority of the players from playing, they might release a hotfix. are you saying they should test it more before releasing it to ensure it will be bug-free when WE test it?? If you don't want to be a part of testing or bugs, Uninstall KSP and wait for version 1.0, AND THEN PLAY. If there are bugs like what you are saying, that's the time you complain Is this the first time you have played a Pre-release state of any game? The mentality of "alpha - bugs are okay" is a fact, It's called alpha for a reason, If there was little to no bugs it would be called "GOLD version" It was well posted all over the net, forums, facebook, youtube, etc etc. even before it was released, It's your fault you don't look in the news that much. Devs can only do so much when it comes to announcements. and about the compatibility thingy, If you loved your saves and mods it should have come into your mind. I just bought the game one month ago, 300 hours of gameplay already and I already knew that when then next update comes, always assume that everything could break, as the case with many of the video game updates.

You do what I'm doing, Still play .19.1 while waiting for the mods to update to .20, After all, I would rather play with my favorite mods than play the newest update. Let's look at it this way, Mods are already part of your game, KSP base have update to .20, but your mods still don't. So you could say that .20 isn't there yet. and you can stick to .19

How come I haven't seen this yet till now!

Thanks for updating it!

I found out that the update broke alot of mods, so First thing I did was to revert back to 19.1 to play, and wait until my favorite mods catch up

Nice mods! I use some of them. The G-Hab one, why is the graphics glitchy in 19.1?

Oh yeah! love this! subscribed, I hope Fustek don't mind

Any problems with the .20 version?

Thank you, It stopped my ships from exploding

There has been some of the parts that work fine, only missing their textures, I guess it has something to do on how the new update reads textures. Any have an idea on how to fix them to properly detect the texture files?

Maybe enabling transfering to seats only at launchpad or runway , if you already launched your ship you won't be able to teleport to the seat anymore

I never knew it was that hard, on all my landing and bases, I just picked it randomly, it seemed flat to me

Thanks for the quick update! I don't advise putting that option, I don't like to magically transfer kerbals outside the ship, remember most of the people that use crew manifest use it to simulate transfering Between "Connections inside the ship", Not magically teleporting anywhere. I would like to always use EVA to get to a seat, but that's just me, maybe include an toggle option later

Why do some of my planes explode suddenly after a quickload? anyone else who has this problem? I'm using 19.1

Does this have problems with .20?

working for .20?