Hodo

I see several problems with that craft. The first is everything Master Tao said. Second you weren't going that fast but you "yanked" up on the nose in around a second. You went from just about 20deg nose up, to almost 90deg nose up. That is a change in pitch of 70+ degrees in less than a second, of course your wings and your craft is going to fly apart. You were traveling at 150m/s when you did it, which doesn't sound fast till you convert that to mph, and realize you made the change in direction at over 170mph! I suggest turning on flight data in FAR so you can see what the atmospheric density is so you can plan your menuevers accordingly. It will be the number that gets larger the faster you go and will end in "pa" for units of pascal pressure. One last thing, for those tank setups, you have to add a LOT more struts for them to be able to withstand any type of lateral G forces. On something that size I would have at least 5 sets of B9 struts along the top and 5 sets along the bottom. Why B9 struts? Because they are stronger then the stock ones.

Alright now that I have a few minutes I hope I can explain roughly what I did. Mind you it was a few months ago and I haven't bothered or wanted to try and repeat it, because it took me almost 8 hours of play time to get that ONE landing right. It was a lot of quick save and reloading. But basically I did one drop where I let it plumet all the way to the ground, timing roughly when it hit each layer of the atmosphere when the chutes should be deployed and when the landing gear should be deployed. I failed to account for the thick atmosphere of Eve and the fact that the craft jettisoned its heatshield with its deorbiting thruster. That was a pain in the butt. But I adapted and overcame. I set my re-entry angle from the start on the deorbital burn, so the PE was set pretty high because it was Eve, any shallower with DRE the probe would have just skipped, any deeper and it would have burned up. But I had to tell the FC (flight computer) to perform the burn at a set delay that I manually put in 15min before the burn node, and told it to burn for the exact m/s needed to achieve the PE I wanted. I then had it jettison the engine and come in heatshield side down... well that didnt work because I screwed up on the building of the probe and had it set to high in the shield so the shield went with the engine. But it survived re-entry, I had to pre-program in the maintain nose up retrograde, until it got to the thick atmosphere, then I let it tumble through the atmosphere to disipate as much of the heat as possible. I also had to tell it to pull in the antennas and solar panels at a certain point. That was the point I could no longer send anymore updates to the probe, and even if I could it would have been to late. I had to make sure that at T-25min to node I had EVERYTHING programmed in the FC before it hit T-15min. Because at that point I would have 3 minutes left to send last minute adjustments, because at that point the probe went on the dark side of Eve and I would lose signal from Kerbin. Everything had to be perfect. It wasn't but it was mostly good, I messed up and the gear didnt come down and one chute burned off of it leaving it 2 which lead to a lopsided landing. Which resulted in it rolling down a hillside for about 100m before stopping on its side. But the solar panels extended while it was tumbling down the hill which tore them off, and the long range satelite antenna was facing the ground. But the omni directional antenna extended at T+5min and worked! So all in all success.

Q button on the flight computer box. It will open the command box. You can add an additional delay if needed in the commands, like I did in those pictures. I had a 25minute delay at one point because I didn't want it to extend its antenna while it was still travelling mach 2 through the upper atmosphere. Then all you do is hit your action keys as needed, they will show up in the delay action log, and any control changes like turns or pitch changed you should use the SASS buttons on the left of the Flight Computer. If I had more time I would explain more in depth but currently busy at work and taking a few minutes to see what I can help out with. Oh one more thing... All those commands have to be sent WHILE you have signal.

FAR does... to some degree. And is FAR better then stock. See what I did there.

First... Did you follow the instructions on install? Second... Did you follow the instructions at all?

You can do it with the on board computer if needed. I did it a while ago for landing on Eve with a 7+ min signal delay and losing the signal path 2 minutes before atmosphere interface. I programmed in EVERY command for landing it near a set spot on Eve. It was a nightmare but it can be done. As seen here...

You were probably posting your imgur album wrong. simple fix... [ imgur] xyz12 [ / imgur] -------------------^^^^^album identifier there no # at the end. And no spaces in the brackets.

Yeah pretty much, everything is up to date up there last I checked a week ago.

Ok thanks so docking washers.. may have to try that later tonight. +1 thanks

Anyone have any links to someone instructions on how to make variable geometry wings with IR? I have tried a few times and I am trying to see how others are doing it.

Honestly looks like a conflict with MechJeb, something MechJeb is looking for is causing the faults. Try removing MJ and booting.

Works fine for me.

Camlost, I was testing an aircraft about the same weight as a F-16C, with the same engine and seeing if it could perform the same accelerate while vertical as the actual F-16C can do. I Compared to the flight data provided to me from my FalconBMS install and FreeFalcon install and the data provided in KSP RO AJE. The thrust level falls off faster then expected. I think my data is most likely for the newer PW engine. My question is how does the real F-16C Block 52 accelerate while climbing at 80+ deg when the engine should be dropping power like a stone at that rate.

The .bat file is just a batch file compiler. All it does, is send the changes that Skillful damage mod is needed to the cfg files for the models that have some damage state installed on them. This also prevents duplicate parts from showing up in the parts catalog. All you do is double click on the .bat file and it will open a "DOS" like prompt window, follow the on screen directions and you will be fine.

I had the same problem, go to the more aggressive ATM mode. If that does not work drop the planet factory plugin.

I have to say that is one of the best looking SSTOs I have seen. Better looking then most of mine and I love mine.

I think by default the signal delay is set to false in the cfg file or the career save file. I can't remember which I haven't messed with it in so long.

What I would love is a procedural system for the mk2 parts. That would be GREAT, then I could cut down on even more parts that I actually use.

I have to ask, where did you find that cockpit and nose pack?

You know what would be awesome... Procedural Mk2 parts for those nice aerodynamic aircraft parts.

Ok step 1, place the hard point Step 2, right click on hard point. Step 3, choose warhead type Step 4, Choose ordance type. (250lb, 500lb, 2000lb bomb etc.) Step 5, Choose LOAD ORDANCE Done you now have a weapon on the hard point, rinse and repeat as needed.

100% intake area if you want want full power, but sometimes reduced power is needed. I shoot for anything above 75%.

Struts have no drag. The B9 struts have no drag and I don't think the stock struts do either. At least not in FAR. I have tested and tested. If you place your struts right they can be invisible.

1 word... well really two.. Air brakes. Slow down before you drop below 10km. I like to be going less than 200m/s when I am landing.

First off cant see the craft in your post... Now that I have seen it.... Your control surfaces are HUGE for that aircraft, try reducing the control angle of the control surfaces first, and second you may want to slowdown a LOT more before thinking about using them. Right now it is like sticking a billboard into tornado when you try and use them.