xtoro

Is it me or does it take way more dV to capture around Dres now(post-1.0)? I swear I was able to with 1500dV but today it took me over 2500!! I can only imagine what Moho is like now! Unfortunately it's still just as boring, and the added roids don't make it a place I want to keep going back to....

Thanks for the input guys. I played sandbox the first couple years and now I'm trying to challenge myself more. I find the real grind is just the first few tiers, and I don't mind grinding afterwards if I can actually at least get probes to other planets to get science. Oh and I'm using RT as well so I have to setup a good network as well...

64gigs I quite overkill unless you do heavy video editing or work with extremely large images that you process... But to answer your question,.my build: CPU: i7 4790K overclocked at 4.5Ghz RAM: 16GB HyperX Fury ocverclocked @ 2400 Motherboard: MSI Z97-GD65 Gaming board GPU: 2x Radeon HD 5830's crossfired and overclocked PSU: Thermaltake 750W HDD #1: 1TB Western Digital Black HDD #2: Three Spinpoint S4's in RAID 0 config Case: Coolermaster CM690II lined with sound-deadening Spire Soundpad matting on both side panels Case Cooling: 5 fans for case controlled by Scythe fan controller CPU Cooling: CPU is watercooled with Corsair H80i watercooler. So.... Yes, yes I am.

Just curious what the old timers do. I'm bored with grinding the first 2-3 tiers everytime I start, and finishing the tech tree by the time I get to Duna. I'm tinkering with a setup that starts me off with enough science to unlock the first 2-3 tiers, and 1,000,000 funds. Yes, my space program is well funded I'm thinking of setting funds rewards to 60% and science to 40% so that I actually GET to explore most of the system before unlocking everything. It will likely be mostly probes at first, like real life. What do you other vets do for settings? Is 40% science too high?

If it's a spaceplane, eyeballing it works well enough and you can adjust as you glide in. As for rockets it's a bit trickier to eyeball, but can still be done in map view by watching your trajectory.

If you can get into orbit using one tank, then just lockout the fuel from the front tank so that the center tank gets used first. Once you're coasting to AP, unlock it. I suggest mods already suggested above, but if you don't want to use mods then locking should work fine.

Isn't there a debug menu option to show aero data on parts? I've never clicked it but wouldn't that give useful data?

Added procedural part and sxt along with a few non-part mods, and deleted most stock parts. So my answer is E.

Wouldn't an SSTO spaceplane without wings be just an SSTO rocket that launches horizontally? I mean, planes have wings right?

Hmm, I seem to be one of the few that does trial and error? Math is one of my strong points but for some reason I prefer sending probes, even though it does cost more in my career, its more interesting for me. I see it as this: KSC knows the orbit of Sarnus, and that's it. So I use MechJeb to find a launch window and to fine tune my approach because I hate fiddling with maneuver nodes. I send a probe to do a flyby and gather science, and I try to use my remaining fuel to circularize. Using the dV spent in trying to circularize, I'll guestimate what I need and then double it so that I might be able to also visit a moon or two. I know it's not cost-efficient but its fun going into the unknown not knowing if the mission will succeed or not. And I think of the early days of NASA's Moon exploration when they just sent probes to gather data doing flyby's and impacts dozens of times using the early Pioneer and Ranger probes, while the USSR was using their Luna probes. It was very Kerbal times back then, with launch failures, flybys and crashes into the moon, and that's how I play

I keep below 300 under 10k, after that it's full throttle. If my AP is where I want it and I'm getting close to 1900m/s orbital, I throttle back to save fuel. When burning at AP I'm not fighting gravity anymore so there's no sense it wasting vertical dV at that point.

I suspect it's because your wings extend out below your CoM. In the VAB you're seeing your CoM with full fuel tanks. Remove the fuel in the VAB and I suspect you'll see that your CoM has lowered. There is a mod called RCS Build Aid that shows you your CoM with empty fuel tanks (DCoM, DRY CoM). Give that a shot, or empty your tanks and see if that's the problem. A quick fix might be adding another reaction wheel to fight the offset.

The Surface is an all-in-one tablet/laptop built by Microsoft. The Terrain is a compact SUV built by GMC. That's all I got to say about that

Docking and undocking screws with the contracts sometimes. I ruined my Duna 6 challenge this way. Went to Mun, Minmus, Gilly, Duna, Ike, Bop, then undocked my ISRU rig to refuel, redocked, transferred fuel and returned to Kerbin. Incomplete...

I've landed EVA'd Kerbals on Kerbin and they didn't die, so I imagine they'll be fine on Duna... And I'm talking with no ship at all, just plopped into the ocean

Good info Claw. And for the record, my post was about fuel balancing using fuel in the wings and not lift or drag. I was just pointing out an advantage to using them...

Wings with fuel in them make balancing easier. As you use fuel, your CoM changes. Using a tool like RCS Build Aid shows you your Dry CoM(DCoM). Place your fuel, or wings with fuel in them so that your CoM and DCoM are as close to each other as possible. If you find your CoL is still too far behind, use the rotation widget to angle your wings up a bit. This will bring your CoL forward. Don't forget to check that your engines are level if they're mounted on the angled wings by using the rotation widget on them too.

1-Place long girder above your capsule 2-Place airbrakes at the top of the girder, as many as you can fit. 3-Land on your feet like a boss.

I see only one way to build easily with joysticks and touchscreens... First, parts won't float around in the air. Everything will be like using widgets. You pick a part and it gets attached to the last node in the part tree. From there you would have an option like holding ALT where it snaps from node to node. Or, widget style where it will slide along the surfaces and you place it where you want, then add symmetry or rotate, and then press the attach button. For joysticks it's easy. One stick moves the part, the other rotates the camera. Pressing the left and right triggers rotate on one axis, and the Dpad rotates the others. Hold A(or PS4 symbol) to snap to node like holding ALT on PC. Press B for symmetry. Holding Y while rotating gives more precision. Pressing X attaches the part in place. The second set of trigger buttons zoom in and out. Wii touch screen will have to adapt some other way.

As mention, the SPH has free movement. If you're having trouble in the VAB, save, go to SPH and open your rocket there. On the open menu there's a button that says SPH and one that says VAB. Press the VAB button to access your rockets. Now you have free movement. If parts try to attach with mirror symmetry, press R to switch to VAB style symmetry.

Oooo! Less time in Windows for me! Now to finish the engines I've been working on....

Or the console versions will be completely different than the PC version. Used to see things like that with the old PSP. Killzone on playstation, awesome first person shooter. But on PSP it was a third person view from above like playing the original legend of zelda, horrible...

I use AMD drivers... Kubuntu with AMD 7690x graphics card. Good combination I guess?

KSP always ran better on Linux so I have every reason to assume it always will. Graphics are also smoother on max everything, so I'm not sure what other people who complain about graphics are talking about. Just look at all the Avalon screenshots from my sig, those are in Linux...

1080p. Had it higher but because of the textures, it didn't benefit the game at all and made UI too small. It really all just comes down to preference here. KSP isn't exactly a beautiful game compared to others out there.