Leszek

No, they had verneir engines. SnowWhite has said she would make some at some point. Many of us have been using the way keeper engines from Tantares mod in the meantime.

Absolutely. This is going to be a relatively quick fixer patch. No new features, only tweaks and bug fixes. Still plenty enough to hype train over. I would also expect this update wont break mods. (Err most likely.) Not that I know at all, that is just what is implied by the version numbers they chose.

In my view it doesn't. It definitely deserves the release candidate badge. If it had been released as 1.0 RC or .99, that would have been much better. This update is great. The features added are great. The polish is great. It is a GREAT update. But it is still a release candidate. That isn't a step you can skip. They tried to skip it, and named it the release. They raised the expectations of a release level product. They said things like it will be ready when it is done. But the release has problems. And these problems would not nearly be perceived so negatively if it had been a 1.0 RC instead of just 1.0. After all, they are <s>mostly</s> all trivial issues. This release should have been a triumph. It is said what is in a name? That which we call a rose, by any other name would smell a sweet. That is true as far as it goes, and it doesn't go to expectations. 1.0 full release has expectations that 1.0 RC doesn't. That is my view on the matter, right or wrong.

To be suborbital you need... 1)To be captured in the SOI. 2)Have an Ap above the atmosphere if it has one, above 0 if it doesn't. 2)Have a Pe below the top of the atmosphere if it has one, below 0 if it doesn't. I don't know about the most efficient way to do at the mun it but the way I would do it would be close... 1) On entering SOI, burn retrograde to capture. (I might wait a bit from the SOI, but not to far.) 2) If necessary burn radial-in to get the required Pe. 3) Contract should be completed here. 4) Burn radial-out to avoid hitting Mun. 5) Plan prograde burn at or near Pe to get back to Kerban as required.

They needed to install sensible pumps. A very good mod, it makes such mistakes recoverable if you have enough fuel margin.

I was thinking this advice is wrong because soupmoshpere is gone but actually more I think about it, It makes sense. I think that it is also a bit off, you should have a starting TWR of 1.2 - 1.5 or so. This TWR makes it easier to complete your turn before you are blasted out of the atmosphere and also prevents you from going too fast in the lower part of it. I normally start with 1.25 and I will thrust limit engines to makes sure I get it.

You need to put the fins on the bottom. Your fins are in the middle front. That would take real effort to get that to fly. Think of an arrow, the heavy bit is in the front and the feathers are in the back. You have the feathers in the front and the heavy bit in the back. Actually if you fly right you don't need fins at all. You just have to stay inside the circle that is the prograde vector. Like so, just ignore the commentary at the end.

Unfortunately this doesn't work in 1.0. There is no way to attach anything to the bottom of the craft.

The easiest way to see it, is like a boat. Imagine a small rowboat. You are standing on the back. You jump out to dive. The boat will move forward. This is because you have pushed off the boat in your dive. Now imagine if you were in a spacesuit and there was no atmosphere and you jumped off the back of the boat. The boat will still move forward. The atmosphere has nothing to do with it and it should be plain as day. In a rocket the exhaust is pushing off the engine, not the atmosphere.

Does a little dance!

I run bit defender. Sometimes, other times I run nothing. A virus killer is enough, actually it is overkill. It is not that I don't ever get a virus, it is just that it happens so far and few between that it isn't an issue. I had a really hard time understanding how people got a virus so easy in the past, it wasn't until I started fixing other peoples computes that I understood. Me: You already have a virus, I fixed your computer yesterday! Them: Yea it was wonky an hour after you left! Me: Let me look....why did you get this smiley cursor again, and you have this dancing girl that shows up if you aren't active for a while. I already told you this stuff is trouble. Them: Yea but she is cute, and it is free! Me: This is the third....gah...from now on, it will cost $150 if you want me to fix your computer. Them: But where friends! Me: Not for computers we aren't.

No it is not. I have already pointed out there is a bias in human thinking against coincidences, we don't like them. Someone above already pointed out why that is. The hard part is not knowing there is a bias, it is having confidence that that is what is getting you. I am a computer person, I went to school for programming, and I am a system building hobbyist. It is hard to wreck a system in the way you described. You can't do it accidentally. Think of all the amateur programmers out there. NONE of them have every fried their BIOS. It just doesn't happen. It is something you have to do deliberately. So if KSP did do it, it wasn't accidental because that would be hundreds of times harder to believe than the coincidence. Even deliberately is hard. Even if you are targeting just one kind of BIOS, say American Megatrends, that BIOS is still custom to the motherboard and manufacturer. They have protections on them. If I wanted to wreck a system, I would just write a bunch of 0's on the hard drive. Done, easy, simple, reliable. But what if it wasn't your BIOS, what if it was something else and you were just too specific in your first post? That is hard to believe as well... You see malware is a business. Malware isn't out to annoy you. The best malware is malware that is silent. It doesn't slow your computer down more than it has to. It doesn't annoy you. It doesn't want you to take it to an IT to get rid of it. It wants to use your computer to send spam for profit, or some other method of making money. Now we all know malware fails in this, it does slow your system down for example. But it isn't out to wreck your stuff for no point. Frying your system would be just that. Pointless and unprofitable. Lets not forget you are the only victim. In summery, it is nigh on unthinkable that KSP caused your issue accidentally. It makes no sense that it was done on purpose. The possibility that it was a coincidence is just about 99.999999999999% of the total causality space. Let me finish with a parable. You might remember Star Force, it was a copy protection scheme that had some serious issues. Many people blamed it for wrecking their computer, or their disk drive. These accusations are false. It had real verifiable issues but hardware failure wasn't one of them. I once pointed out to someone that my drive failed within 1 week of getting Star Force installed. (It came with Silent Hunter III) They wondered how I could possibly rail against those that argue against Star Force when I myself had been a victim. I then revealed that my drive failed a week before I got the game and not after. Had it been the other way around, even knowing what I know about software, it would have been difficult even for me to dismiss the coincidence. Knowing the bias doesn't make it easy to ignore the bias, but it is still bias.

Actually, you don't know what killed your BIOS. The two events happened not that far apart and you guessed they were connected. People don't like coincidence and it is hard to explain it to them. Really hard. It almost certainly wasn't KSP for the simple reason that many people updated today and didn't have issues. Back when I did tech support I used to see this sort of thing all the time. They got a new printer, and their monitor died. Our printers fault. Sometimes it is so very obvious that the two aren't connected, a guy's 20 year old TV dies suddenly 2 months after they get <A US TV Provider>. Guess what, yep, it is the providers cable box that broke it. It took 45 minutes and two floor managers to explain it to him. Shockingly enough, the fact that the TV was 20 years old is the reason why the guy needed a reason for it to fail. After all after 20 years, why now? It almost certainly wasn't malware either, the bios just went. Malware has a purpose now a days, it is big business. They want to make your computer part of a botnet, or they want to highjack your browser for advertisement reasons. The days of frying computers for fun were over 20 years ago.

And what gives you the right to declare that? You are not the mod maker, you do not get a vote bigger than the rest of us. This mod is not dead. Many will still use it. If you don't, fine, but what was the point to this post?

My posts today that have to do with 1.0 have been all negative. However this isn't because I think 1.0 sucks. I like it, a lot! But there is just that one thing that is bugging me most, heat shields flipping my craft. So that is what I have been reading and talking about most. The issue may differ but this is going to be the same for most people. It is just like tech support, no one ever calls to say my printer is working just fine, so you get a skewed perception of the product you support. These forums aren't as bad as tech support as people will come and say AWESOME, but the idea still applies.

Now that 1.0 has come out I can confirm that the X-37's purpose is to test the new stock aero. Pretty obvious in hindsight, I don't know how any of you didn't figure it out.

We have parking orbit. 208 x 177 km's

New T0 is 7:03 from now. That is in just over 20 minutes. This is based on weather forecast. They had a 90 minute window to start. Not sure how much time is left but it has to be more than half I think. And I was Ninja'd this time!

Current new T0 is 6:53 EDT or about 20 minutes from now.

My guess from reading the new aero description is that the part does have drag. It is calculated before hand. The shield is then placed below the capsule which for reentry purposes is putting the drag ahead of the CoM since the capsules drag is occluded but it's mass isn't. This is the same as putting fins on the front part of the rocket.

Heat shield first. You are going to have to post a screenshot for a better answer.

Then I am afraid I don't know. The possibilities that are left don't seem that likely. They include, an engine is thottle limited differently. A Rapier is in a different mode (Or is that an aerospike, I don't use either that much). An Engine isn't lined up properly. The fuel tanks you are draining first aren't opposite each other. .... Do any of those engines have gimbal? If not you might not have enough control. You can put fins and more SAS on but you really shouldn't have to.

Another possibility is that your asparagus isn't right and you are draining the tanks non symmetrically.

Just like Radam says you are going to far from prograde. You do not need more fins or reaction wheels, at least nor normally. You have to stay inside the circle of your prograde vector until you get up to at least about 30 km high. Where the torque comes from is the more you point away from the way you are going, the more the side of the rocket is hitting the airflow. If you go to far, the force on the side of the rocket is more than you can counter and you flip out. Old stock style of go to 10 km and then turn 45 is horribly horribly wrong and dangerous. With new stock aero/FAR/NEAR you have to get used to kicking 5 degrees when low and slow and then following your prograde over as you go. My commentary is a bit off at the end but here is how it is done.

I always jettison my science before reentry. It didn't help. I turned off SAS and off I went. Turned SAS on and the capsule (Just the standard SAS, not hold retro or anything.) did its dance and drained battery. It was just 3 parts, the capsule, the heat shield, the parachute. Some people seem to get some stability so I am not sure why I am not. It seems to me that this needs tweaking. It is a clean install right from the steam folder. Later on when the mods are ready I will copy-pasta to my normal game folder and run from there leaving my steam folder pristine.