Developing Duna (pic heavy) - ^_^ with Part 11 ^_^

[Geschosskopf]

2 hours ago, Brotoro said:

Arrrrggghhh! I had forgotten how frustrating the constant crashes are. I see people with dozens and dozens of mods, but KSP chokes and dies for me so quickly with less than a dozen. 

It's not the number of mods, it's which ones, plus your other settings.  The more graphics, the more CPU time a mod imposes, the bigger its impact.  EVE is an extremely resource-hungry mod---it says so on the label.  It's probably the worst offender currently in existence.  I don't plan on using it myself until KSP goes 64-bit in 1.1.

Another mod that can cause problems, at lest for me, is Trajectories, at least the version I use (haven't checked on an update lately).  But you can turn it on and off from within the game instead of it always running, so I have it off unless I need it.

Part mods aren't so bad these days.  The big hit with them was always their textures but now nearly all stock and most mod textures are DDS, which use a lot less memory.  Active Texture Management doesn't do anything for DDS files so its value is now quite limited---it's mostly just for those mods that haven't been converted to DDS yet.

Texture Replacer nowadays claims to have dynamic texture loading.  I don't know if this affects everything or just textures used by Texture Replacer.  But anyway, having a bunch of custom Kerbals, which all use their own textures, is no longer the huge hit it used to be, especially if those textures are DDS.

So then there's your other settings.  I myself have terrain scatter turned off and use 1/2-resolution textures, but otherwise have high-quality effects, high terrain detail, and a huge number of pixel light sources.

Also, I recently bought a new video card, a GeForce GTX 980.  Out of the box, this made KSP's framerate atrocious and the game frequently crashed.  But you can get a program called GeForce Experience from Nvidia that configures the vidcard for each of your games.  I had it do that for KSP and problem solved there.

[Brotoro]

Developing Duna - Part 10

Cockpit Change

At the end of the last episode, I mentioned that the new Mark1 Cockpit was messing up many of my old designs because kerbals could no longer enter or exit the cockpit (because of the repositioned hatch). I'm not sure what I was doing wrong with trying to carry over the Mark1 Cockpit files from 0.90 to 1.0.5, but I was getting a plain white cockpit that wasn't working quite right. I received some suggestions to look on KerbalStuff for a mod that restores that old part.

It turned out that KerbalStuff had been shut down that very day, but on Curse.com I found the Kerbal Historical Institute pack that has files for many old parts. I copied over only the parts for the old Mark1 Cockpit (I have enough problems with KSP crashing without adding dozens of old parts) and its internal space. In my old save game sfs file, I did a find & replace of all occurrences of Mark1Cockpit with Mark1Cockpit2, and now all my old ships have their working cockpits again. Huzzah! Plus, I can still use the new cockpit if I want to on other designs (I see that it has two pilot control positions in it...that's cool).

 

 

Some Simulations

Before sending out new ships to Duna, I first needed to test which ones no longer worked as designed in version 1.0.5 of KSP (and which of the replacement ships I built in 1.0.1, etc., still worked in 1.0.5). This involved a lot of "simulations" using the software that I use to simulate flight conditions in KSP...which is, of course, KSP itself. Let me just do an F5 before we have some alternate universe fun...then we can visit Nelemy, Hellou, and Kurt in their Duna Lander sitting on Duna's southern polar cap by the SSTV Pyramid.

 

Nelemy: "Dudes, I'm really enjoying our vacation time while the engineers and scientists back home figure out how Physics is working nowadays. We should have vacation time more often."
Hellou: "Well...they did spend a lot of money sending us here, so it would be nice if we could get back to doing some Science."
Nelemy: "Sure. Hey...that new hairstyle doesn't look as weird on you as I thought it would, Hellou-Dude."
Kurt: "You really know how to sweet-talk the ladies, don't you Nelemy?"

Then, suddenly, Nelemy starts screaming!

 

Nelemy: "Arrrrrggghhh! Arrrrgghhhhhh!"
Kurt: "Um...what's wrong?"
Nelemy: "Zombies! Zombies are attacking!"
Kurt: "Zombles?"
Nelemy: "Arrrgggh! Kurt-Dude! You get the shotguns and hold them off! I'll head to high ground!"

With that, Nelemy scrambles through the top hatch of the habitation module up into the control cabin on top of the lander.

 

Hellou: "What craziness are you guys up to now?"
Kurt: "Hey, don't blame me for his antics."
Hellou: "Why not? Aren't you the one who always makes a point of checking for Creepers first thing every time you go out on EVA?"
Kurt: "Well...you never can be too safe."
Nelemy (over intercom): "Dudes! Prepare for emergency acceleration in 10 seconds!"
Hellou: "Nelemy! Calm down. There's no such thing as zombies."

 

Nelemy: "There are! I can see them coming! Arrrrggghh!"
Kurt: "Nelemy...listen..."
Nelemy: "Arrrggghhhh! Liftoff!"

 

Hellou: "Arrrrggghh!"
Kurt: "Arrrrggghh!"
Nelemy: "Ha ha! You can't get me, Zombies!"  

One of the big changes I found during testing was that the landing profile I had previously used on Duna in 0.90 was not going to work in 1.0.5. That procedure was: Drop in from orbit...wait for any signs of entry flames to disappear (usually there weren't any flames from low orbit)...then deploy the parachutes at about 5 km and let them do almost all of the braking...then settle the slowly-descending ship under its many parachutes onto the surface with a little rocket braking burn.

The problem in 1.0.5 was that the parachutes now get destroyed if they are deployed at high velocities. Some of my Duna ships have a lot of drag and relatively low mass, and the thin Dunan atmosphere can actually slow down those ships to safe speeds in time to deploy the parachutes (assuming a lowland landing site). But many of my Duna ships have a high ballistic coefficient because they are carrying a large mass of fuel, and those ships were still screaming in through the thin air at over 600 m/s when it was time to deploy the chutes...and that just wasn't going to work in 1.0.5.

The other problem in 1.0.5 was the nerfing of the thrust and specific impulse ratings for many of the engines compared to 0.90 (especially the 48-7S engine). So I was concerned that some of my ships would no longer function as designed when used in 1.0.5. The Duna Landers, for example, come in with a full load of fuel (minus what gets used for the deorbit burn) because those lander/habitat/labs are supposed to be able to hop back to orbit, refuel, and land at different locations. So...were they still useful in 1.0.5?

 

Happily, I had chosen to abandon the 48-7S engine (the engine I had been using extensively in my landers) in favor of the Mk-55 Thud engine back when I built the Duna Landers...specifically because I expected the Mk-55 to get less of a nerf when 1.0 hit. And as we see below, Nelemy was able to get the Duna Lander back to polar orbit with a lot of delta-V to spare.

 

Nelemy: "Dudes! We are safe in orbit with 635 m/s of delta-V to spare. Take THAT, Zombies!"
Kurt: "Nelemy...unlock the hatch."
Nelemy: "Um...You sound upset, Dude."
Kurt: "UNLOCK the HATCH!"
Nelemy: "Um...Maybe after you've had time to cool down, Dude."

Of course, Nelemy had an unfair advantage with this boost: That Lander had been landed back in 0.90 with parachutes doing almost all of the braking (even at the 3,000+ meter elevation of the SSTV Pyramid site). How much fuel would the old lander design have if it had landed in 1.0.5? This would require some testing.

Nelemy: "See...I said I'd let you up here eventually. Don't hit me, Dude."
Kurt: "I'm not going to hit you. But what have you done to us?"
Nelemy: "Dude...I got us safely to orbit."
Kurt: "And how are we going to land again? Did you wait until the right time when we were under the orbital plane of one of the refueling stations?"
Nelemy: "Um...No...Dude, there wasn't time. There were Zombies!"
Kurt: "So we can't refuel to land again. Great job, Nelemy."
Nelemy: "No, Dude, it's all right. All I need to do is press this button on this HyperEdit control panel, and the ship is instantly refueled!"
Kurt: "What? I've never seen that control panel before..."

So, with some renaming of old Quicksave files, and some additional F5 action, some landing tests were made. And, indeed, it turns out that even if targeted to a lowland landing site, the fuel-heavy Duna Lander comes in too fast, and its parachutes get stripped away by the supersonic airstream (this as the air is). But the Lander can land safely with just engine propulsion alone (see below).

 

Unfortunately, that leaves the Lander with only 39.5% of its fuel remaining, which is far too little to fly back to orbit (Unless it happens to land at a location where a Refueling Station and Fuel Fido are available to refuel it). So let's try another landing profile:

 

I again targeted to a lowland site, I let the Lander come screaming in (we now get entry flames from a 90 km orbit in 1.0.5), letting the aerodynamic drag act as long as possible to slow the ship. But at 6,000 meters, the ship was still streaking along at almost 700 m/s, so I fired the two Thud engines at 100% throttle. As soon as the parachute icons in the staging display changed to the grey background color of "safe to deploy," I popped the chutes and cut the engines. The ship had slowed to safe-chute-deployment-speed at 1,600 meters (things were happening fast, so I wasn't as quick on the draw as I could have been in deploying the chutes and cutting the engines...see below).

 

But once the chutes were out, they very quickly slowed the ship and got it descending vertically at an altitude of about 900 meters (about 310 meters above the surface), and the touchdown after that required a little low-thrust engine braking (the lander drops at about 15 m/s under its six parachutes with no engines firing at this elevation).

 

The result of this landing profile (below) left the Lander with 69% of its fuel remaining.

 

But is that enough fuel for the Lander to return to orbit? Let's find out...

Me: "Hey, Nelemy."
Nelemy: "Uh...What, Narrator-Dude?"
Me: "Zombies."
Nelemy: "Aarrrgggghhh! Liftoff!"

And we see below that the Lander can indeed make it back to a 90 km polar orbit with some fuel to spare.

 

So the old landers are still usable, if one is careful. But replacement Landers could be improved by the inclusion of two modifications: 1) The addition of drogue parachutes that can be deployed at higher speeds to help slow the Lander sooner, saving more fuel during landing; and, 2) slightly more efficient engines (the Aerospike is superior to the Thud on 1.0.5 Duna). New Landers with these modifications will be sent to Duna.

Also, I have decided that while moving the habitat/lab Landers around from site to site works fine for initial exploration, once you have determined some interesting locations it might be better to leave the heavy Landers in place, and shuttle the Kerbals around with a smaller, more fuel-efficient transport. So, the next shipments to Duna will include smaller Runabout landers to move the crew from base to base.

But let's get our universe back to normal...

 

 

Hellou: "Zzzz..zz*snort*..Huh?"
Nelemy: "Wow, Hellou-Dude...You must really be tired to have fallen asleep during supper!"
Hellou: "Um...Oh. Yeah. Um. What happened to the zombies?"
Nelemy: "Dude, you were dreaming. There's no such thing as zombies on Duna. Hey...if you aren't going to eat your baked potato, can I have it?"
Hellou: *Yawn* "Oh, sure, Nelemy. I'm not very hungry."
Nelemy: "Great! I love these special potatoes. It was a great idea to send along potatoes that eat perchlorates so we could experiment with growing them in Duna dirt."
Hellou: "The potato doesn't eat perchlorates. It's the symbiotic bacteria in them that convert the perchlorates to safe chemicals."
Nelemy: "Yeah...those midi-perchlorians. A great idea."

 

The testing of some of my other Duna ships did not go as well as the Lander tests. The Duna Fido rover, for example, was originally designed to be able to hop back to Duna orbit for refueling, then land again at a new location. Or, as Adly and Kelby had done, just hop the rover some distance across the surface to be refueled at a surface Refueling Station.

But, alas, in KSP 1.0.5, the nerfing of the 48-7S engine left the Duna Fido woefully underpowered. As shown below, it struggles to lift off from Duna. It is very slow to accelerate and push its very draggy frame through the Dunan atmosphere, and it falls far, far short of reaching orbit.

 

 

 

So the Duna Fidos are going to be limited to surface operations from now on, and I'll have to live without the connivence of being able to hop out of a long, boring rover expedition. The rovers to be sent in the next shipment to Duna will be designed purely for surface operations once landed, and they will be positioned in interesting locations around the planet. The old Duna Fido that is still in orbit will also be useable -- it turns out that the high drag of the rover allows it to slow down to safe parachute deployment speed when dropped in from orbit to a lowland site.

For the Surface Refueling Stations that are still in orbit, the outlook is not as good. These stations have a very high ballistic coefficient (being mostly full tanks of propellants) and their now-weak 24-77 Twitch engines may not be able to slow them down enough to land safely. Replacements sent from Kerbin will implement drogue chutes and stronger engines.

The Fuel Fidos that are still in orbit will have an easier time landing because of their draggy frames, and they can have their propellants removed to lighten them even more if needed. But replacements from Kerbin will have more thrust and drogue chutes to ensure that they will work  for landing on 1.0.5 Duna.

 

Diagnosing DunaDog

Not all of the ship testing needed to be done with "simulations." Aldner was able to test the capabilities of the DunaDog plane for real.

Aldner: "Aldner calling Duna Base. Yo, Thompbles, are you awake over there?"
Thompbles: "Yes, Aldner, I'm awake. But I'm surprised you're up...it must still be before noon in Fido Canyon where you are. What inspired you to roll out of bed?"
Aldner: "I feel like going for a flight."
Thompbles: "The big wigs at KSC still have us stood down. They say the new Physics means your DunaDog isn't going to perform very well."
Aldner: "Yeah, yeah. I read the reports. But they say the plane will still fly. And those eggheads are going to need real data if they're going to modify the next set of DunaDogs to work for us. I won't go far."
Thompbles: "It wouldn't do me any good to tell you 'no', would it?"
Aldner: "Nah. Sometimes a guy just has to fly."
Thompbles: "Be sure to do a complete system check. They say there may also be computer glitches."

 

Aldner: "Control systems are green. Huh...the parachutes are all triggered for immediate deployment as soon as I move...good thing I noticed that. I'm disarming them all. Make note of that problem, Mr. T. You might want to check the parachute settings on our other ships."
Thombles: "Roger. I'm making notes."
Aldner: "Huh. The 48-7S rocket engine systems are green, but the ion engines aren't responding to the activation toggle switch. I'll check the sfs code in the flight computers."
Thompbles: "I have the backups of the code on file here."
Aldner: "No problem...I've done this tweak before. Why the hell do the action settings get messed up, anyway?"

 

Aldner: "OK, I'm ready to roll. The power output from the solar panels is pretty lame, even with the sun right overhead. Brakes off. Rear 48-7S is activated. Full throttle. Ooops...almost forgot my SAS."

 

Aldner: "Oh, the thrust from the 48-7S is so weak. No wonder they re-named it the Spurt."
Thompbles: "That's 'Spark'."
Aldner: "Whatever. A lame motor by any other name. Ah. Lifting up at 30 m/s...the old plane still has good lift. 550 meters. Lets see what the ions do. Hey, they buzz now. I'm getting 1.9 kilo-Newtons of thrust from each of them at full throttle...but they're drinking the batteries must faster than the solar panels can replenish the power at 100% throttle. Specific impulse for the ions is a little under four thousand."

 

Aldner: "Approaching fifteen hundred meters. Batteries are nearly dry. Annnnd...flameout on the ions...switching them off. I'll continue to climb on rocket power as the batteries recharge and see if I can get any kind of sustainable cruise at altitude."

 

Aldner: "Leveling off below four thousand meters. Rocket fuel at 70%. I'm switching off the Spurt and turning on the ions. At two-thirds throttle, they drink the electricity faster than the solar panels can supply. Hmm...same at half throttle. Specific impulse of the ions registers a little over four thousand. OK...At one-third throttle, the solar panels can supply electricity as fast as the four ions drink it... but with that thrust, I'm not able to maintain level flight. And that's even with the sun right overhead."
Thompbles: "Copy that. So it looks like we're going to have to retire the planes."
Aldner: "Yeah. I'm going to bank around and try it at a higher altitude."

 

Aldner: "Banking around back toward base. The plane is still fairly maneuverable when all the engines are on full throttle...but the batteries are nearly dry again, so I'm switching back to rocket power to climb again."

Aldner: "OK... Rocket fuel down to 46%. Altitude fifty four hundred. I'm back on just the ions again. The Isp of the ions is up to four thousand and fifty...but it's still not enough. I'm unable to hold altitude at one-third throttle...and any higher throttle setting drains the batteries faster than the solar panels can supply."
Thompbles: "Watch your fuel levels to be sure you can get back to base."
Aldner: "Not a problem, Momma Hen. I flew out about 20 klicks east of my base, but I turned around and have been heading back during the recent climb...I'm going to over fly the base area and head around again."

 

Aldner did another figure-8, heading out west, then back east, as he lost altitude. Then, approaching his base area from the east (about 3 km out at about 875 meters AGL), he deployed the parachutes to attempt a landing.

 

There was a concern that the thrust of the 48-7S belly engine would no longer be sufficient to land the DunaDog safely, but since Aldner had burned off most of the propellants (the rocket propellants were down to 25%...the Xenon had been hardly used at all, but there is a lot less of that to begin with) the belly engine was sufficient to slow the descent to 8.2 m/s for a safe landing. But it could be a problem with a fully fueled DunaDog.

 

The drive back to the Lander base was tedious (the heavier DunaDog does not climb shallow hills as well as the lighter BirdDog plan on Laythe), but Aldner successfully concluded the test and got back to base to have a nap.

 

I'm confident that the replacement version of the DunaDog that was already in the works (using Fuel Cells for power) will work OK on Duna if the engineers slap on a few more ion engines. 

 

Rocketing Replacements

With more data on the performance of ships under the new Physics, and by skipping the next Duna launch window, the engineers at KSC were ready to start launching the modified hardware on rockets for the next armada to Duna. Below, the launch of the replacement Duna Landers. Hey...now with real aerodynamic fairings for boost! We don't have to imagine them anymore.

 

The launch vehicle is a two-booster varient of the new FUBARR (Flyback Upgraded Booster Advanced Reusable Rocket). The Duna payloads are more bulky than heavy in most cases (the Duna Lander 2 payload was 74 tons, for example), so the two-booster varient has more than enough lift capacity to do the job. Below, the boosters separate to flyback and land at KSC for re-use (or so I envision).

 

The shallower trajectory used by the two-booster FUBAR resulted in the aerodynamic forces (and flaming effects) persisting until after the first main engine cut-off, so the fairing wasn't jettisoned until after MECO1 (this is still before the burn that puts the ship into orbit).

 

Below we get a view of the new Landers after the faring is gone, during the orbital insertion burn. The landers are quite similar to the previous Duna Landers, but with two Aerospike engines instead of Thuds, drogue chutes, and Resources scanners. On the top of the stack is a Resource Scanner satellite that will scan Duna for the best places to exploit the indigenous resources of the planet.

  

The FUBARR sustainer dropped off the payload into an 85 km orbit. The sustainer had plenty of fuel left to return to KSC, but I'll take care of that later.

  

For every payload launched, of course, we are going to need to launch a BANT 3 (Big Advanced Nuclear Tug version 3 -- now with stupid radiators! Don't get me started on the goofy NERV overheating problem in KSP...just don't). This version of the nuclear tug has liquid-fuel-only central tanks, since NERVs now can't use oxidizer. The NERV engines are mounted on Rockomax X200-16 Fuel Tank side tanks (which have the oxidizer removed).

 

I used to mount the nuclear engines of my Tugs on ejectable side pods equipped with parachutes to allow the nukes to be separated and recovered in case of launch failures (or later in the lifetime of the Tug for recycling), but the new goofy heat problems (don't get me started...just don't) dictate that the NERVs be mounted in a way that allows good thermal contact to allow heat to flow into the rest of the ship where it can be dissipated (and the ejectable side nacelles weren't good for this).

The forward aerodynamic fairing (nose cone) also includes lots of parachutes to recover the un-fired NERVs intact in case of a launch failure. How does that work? Well, let's sidebar here and have a look below. In the event of too many engines failing during boost, or loss of guidance, or whatever, the first step is to shut down all engines, then wait a bit for the jet engines to spool down, then jettison the side boosters and the side aerodynamic fairing cones and the sustainer core, and then drop the rear tank of the BANT.

 

As parts rain down for a series of exciting explosions, the parachutes on the central aerodynamic fairing deploy and lower the Tug to a somewhat rough, but quite survivable, 9 m/s landing so that the precious nukes can be recovered for re-use.

 

In a simulation where the Tug landed offshore, it was interesting to see that the side tanks of the Tug were destroyed by the landing (I guess water is still tougher than land in 1.0.5), but the detached NERV engines settled safely to the sea floor to await recovery.

 

 

BUT the need for an abort never happened during this launch, and the FUBARR continued on its way, eventually dropping the flyback side boosters, then later separating the aerodynamic fairing on the Tug's side tanks (seen below). The sepatrons on the side cones are mounted slightly off center so that they cause the jettisoned cones to arc off to the side of the rocket and tumble away. The central aerodynamic fairing cone with all of its parachutes is jettisoned after MECO (since even if there is a failure of the sustainer after that point, the Tug could finish the orbital insertion burn).

 

 

After the circularization burn, the sustainer separates and the BANT is free to do its work in orbit. The sustainer will later be returned to KSC.

 

The BANT was placed into a higher (90 km) orbit than the Lander payload so that the Landers could catch up, and then the BANT dropped down and matched velocities with the Landers.

 

Hey, lookie what I've got! A docking camera! I was sad when the Lazor Docking Cam mod that I'd been using for so long finally failed to work in version 1.0, so I was really happy to find the "Docking camera (KURS style)" mod to replace it (Thanks, DennyTX!). With all the docking I'm going to have to do, the docking cam makes me a much happier camper. It allows color or black & white views, and also an "infrared view" (shown below). The docking display shows all of the distances, velocities, and angles to the target to allow precision docking.

 

OK! That's one Duna Armada ship ready...and only SIX more to go.

  

 

Minmus Mission

But before I rocketed the rest of the Duna Armada payloads into orbit, I needed to do a side mission to Minmus to pick up some of the crew that would be aboard the Second Duna Armada. The commander of the Armada will be Rondorf Kerman, most recently the chief pilot of the Guardian Project that protects Kerbin from stray asteroids. The other two experienced kerbalnauts for the Armada will be Fredoly Kerman and Dunsel Kerman, who were currently on longterm deployment to Minmus Base.

So, to pick up those two guys, and to test out the new version of the Asteroid Guardian ship (which is basically BANT with crew capsule and Claw equipment), a crew of rookies headed by Magchelle Kerman (who is slated to become the new Project Guardian prime pilot) took off in the Guardian Mk3.

 

Ooops. Bit of a staging error below -- the side aerodynamic cones got jettisoned along with the side boosters (instead of at 40 km where they normally would get dumped), but no harm done. Just a little extra drag during part of the boost.

 

After the Guardian was deposited into orbit, Magchelle first did a plane shift maneuver to match planes with Minmus (Magchelle: "I'm just gonna pretend it's a BIG asteroid to rendezvous with!"), then burned to transfer to Minmus. The transfer burn took 6 minutes, which is shorter than the BANTs will need to do for Duna injection -- but the Tug temperatures stayed fairly cool.

 

 

Below: The capture in low Minmus orbit required a one-minute burn of 159 m/s.

 

Ah, the minty ice cream moon. I remember it well.

 

Jenlan Kerman volunteered to fly Fredoly and Dunsel up to orbit in the Minmus Runner. The seven 40-7S engines of the Minmus Runner still work fine in Mimmus's low gravity (although they wouldn't be as good anymore for a high-speed sprint back to Kerbin to outrun solar flares, which was the original purpose of this design).

 

 

Magchelle practiced her rendezvous skills to match orbits with the Minmus Runner, but Jenlan handled the final docking since the matching port was on the side of the Guardian.

 

The side tanks of a BANT would normally not carry any oxidizer, but two of those tanks DID carry oxidizer on this mission so that the Guardian could refuel the Minmus Runner to replace the propellants used during this transfer. Meanwhile, the two rookies Joene and Geneman, transferred to the Minmus Runner, and Dunsel and Fredoly transferred to the Guardian.

 

While Jenlan returned to Minmus Base with the two rookies, Magchelle headed back to Kerbin with her passengers.

 

Another important test for this mission was to see how well the BANT end of the Guardian stood up to aerobraking at moderately high (if not quite interplanetary) speeds. Lots of flames...but it appears that I may be able to continue to use aerobraking as before to capture payloads at Duna.

 

 

Once the Guardian was safely in a circular 90 km orbit, Bobgan Kerman launched in the the SSTO Crew Carrier 9e to retrieve the Duna Crew members.

 

His trajectory was not a shallow as some of the test flights, so he achieved orbit with 538 m/s of delta-V remaining.

 

After docking with the Guardian, Dunsel and Fredoly transferred over to the Crew Carrier.

 

 

Bobgan landed the Crew Carrier west of KSC. Dunsel and Fredoly then began a half-year of intensive training with the new ISRU hardware designed for the upcoming Duna Amarda 2.

 

Magchelle remained in orbit aboard the Guardian to continue her extended mission testing out the new Guardian and practicing orbital maneuvers. One way she practiced was to rendezvous with the FUBARR sustainers in orbit. Because the Duna payloads were fairly light (if bulky) compared to the lifting capacity of the FUBARR, the sustainers often made it to orbit with excess amounts of propellants (more than they needed to return to KSC). So Magchelle's job was to recover some of that propellant for transfer to the Space Station orbital fuel reserve.

 

 

Rocketing Replacements Redux

The next payload ready to go for the Duna Armada were the improved Surface Refueling Stations and their associated Fuel Fidos......because Squad STILL has not given us refueling hoses.

 

At 92 tons, this was the heaviest of the Duna payloads, and a two-booster FUBAR would not quite suffice for lofting it, so it used the version with four flyback boosters (even though this would leave lots of extra fuel in the sustainer once it reached orbit...but that gives Magchelle something to do).

 

I blew off the confetti at about 40 km. Wow! I just heard that we're getting proper clamshell fairings in version 1.1. That'll be nice.

 

Here's a closeup of the payload. These ships didn't receive a lot of updating (which is why they were ready so soon)... added drogues and more powerful engines to the Fuel Stations (two Thuds each) so they can be decelerated to safe parachute deployment speed. And drogues and double the number of 48-7S engines for the Fuel Fidos. Also, the Fuel Stations and Fuel Fidos are equipped with the new, larger Xenon tanks, so there will be a lot less right-clicking involved in selecting tanks for Xenon transfers.

 

This, of course, required another BANT to be lofted on another FUBARR (it's a good thing that these are designed to be reusable, no?). Some nighttime rendezvous and docking (love that docking cam!), and the second payload is ready to go to Duna.

 

 

 

The next payload ready to go was the Duna Science Base payload. This only required a two-booster FUBAR.

 

This stack consists of four parts. First, a Surface Refueling Station, just to add mass to an otherwise lightweight payload...and you can never have too much fuel. Next, the Science Base expansion module for adding more SCIENCE capacity to our exploration, with added drogues and an extra deorbit tank and two more 48-7S engines slapped on the bottom to ensure a safe landing. Then the Interplanetary Crew Habitat to provide living quarters for the crew during the transfer to Duna -- mostly the same as the previous IP Habs, but with the addition of a couple 48-7S engines for emergencies...say, if the Tug does lose its engines during aerobraking and we need to circularize the orbit before the next braking pass. Lastly on top is a spare copy of the Resource Scanner satellite, just in case. And if both Scanner Sats arrive safely to Duna, the other one can be moved to Ike. There is no crew aboard the ship for this launch; they'll come up months later when the whole Armada is ready.

  

And now that we placed another payload safely in orbit, this means (you all know the song by now...feel free to sing along!) it's time for another Big Advanced Nuclear Tug launch and some assorted orbital maneuvers and docking.

 

I always align my big, laggy payloads to Normal or anti-Normal for docking maneuvers because it makes it easier to dock when it takes a long time (and you don't want the docking axes of the payloads shifting constantly).

  

 

Next payload: The improved Duna Fido 2 rovers that are designed purely for surface use. I'm going to have these things scattered all over Duna eventually, so that there's always one handy. In addition to the rovers, there is yet another Fuel Station, and on the top of the stack is one of the Duna Runabouts that can carry five Kerbals between the surface of Duna and Duna orbit (for less fuel than the Lander Hab/Labs use).

 

 

And another payload into orbit means (yes boys and girls!) another Nuclear Tug delivered to orbit, followed by more maneuvers and docking. And if you think it takes a long time to READ about all this, imagine how long it takes to DO it. And all this docking is why DockingCam is my dear friend.

 

 

 

Next up: The replacement DunaDog planes. At 55 tons, this is the lightest of the Duna payloads, so it was launched on a Rockomax Reuasable Rocket with two flyback side boosters (rather than the larger Kerbodyne FUBARR). The two DunaDogs sit on either side of the central tank.

 

There's not a ot of clearance with all those wings and canards and such, so it was a bit tricky to arrange for a clean booster separation.

 

Once in orbit, the sustainer separates into sections (with the two DunaDogs mounted securely onto a big orange tank that is over half full of propellants), and then the ends of the sustainer dock back together so that it can be returned to KSC for re-use. The rear tank of the sustainer retained only the minimal amount of fuel required to deorbit and land using the parachutes (so that the orange tank attached to the DunaDogs could have as much fuel as possible).

 

 

And you know what comes next? Of course you do! A BANT 3 is going to be overkill for a payload this light, and I'd previously have re-used one of my older smaller Tugs for this job, but those Tugs were not designed for the modern world of 1.0.5.

 

 

I've been waiting a LONG time for this next payload, ladies and gentlemen. Waiting since KSP version 0.19, to be precise. And now it's finally coming to an orbit near you, lofted by a two-booster FUBARR. Ladies and gents, let's pop the party confetti and reveal: an ISRU payload! Applause, applause! RESOURCES! HUZZAH! The only thing that could make me happier would be fuel transfer hoses.

 

  

So what have we got here? On the bottom of the stack is a special rover for exploring Ike (based partly on the rovers I used for Bop & Pol, and partly on the new Duna Fido 2 design). Above that is the ISRU Lander complete with tanks, drills, converter, ore containers, and a cabin for an engineer to monitor the experimental systems. It's solar powered, of course, because I have respect for the Second Law of Thermodynamics, so I won't be doing any of that "running your ISRU converter powered by fuel cells using the propellants made by that converter" nonsense. And on the top is another Duna Runabout for transferring kerbals hither and yon.

  

Then the BANT and the ballet, and another ship is ready to join the Duna Armada.

  

 

One more payload for the Armada! What could it be? Even though the payload masses only 69 tons, I needed to fly it on a four-booster FUBAR because of its lonnng fairing (the rocket would be unstable after booster separation if it used a two-booster version...but the four booster version gets it high enough before all the stabilizing power of the wingéd side boosters is lost at separation).

 

The payload? Another ISRU ship! On the bottom is a Refueling Station (mostly to fill out the mass of an otherwise light ship). Next comes a mobile version of the ISRU payload (standing on end in the long payload fairing). On top is a ship designed to carry propellants made on the surface of Duna into Duna orbit. We'll see later if any of this ISRU stuff works out well.

  

How about a haiku?

A payload flies free.
Just as Spring follows Winter
Another BANT boosts.

 

So, the final payload is ready for the Duna launch window. The crew will ride up shortly before the launch window opens.

 

Maybe I'll wait to see if 1.1 breaks anything terribly before I take all the time to boost this hardware off to Duna. For now, here's a montage of FUBAR sustainers landing at KSC:

 

Edited May 5, 2016 by Brotoro

[Angelo Kerman]

Nice to see your space program is up and running again.

[Geschosskopf]

5 hours ago, Brotoro said:

Developing Duna - Part 10

Bravo!  Way to pick up the pieces and go on!  I particularly liked the neat trick of taking the center section out of the airplane lifter and gluing the loose ends back together.

EDIT:  Aerocapture at Duna is certainly doable in 1.0.5, provided you don't try to go from a fast, bad transfer into a very low Duna orbit all in 1 pass.  Getting down below 12km or so is only necessary in such cases, and only that seems to melt engines.  Otherwise, no problem that I've found.

Glad there are no zombies on Duna.  But there are some at Sarnus, so beware

 

 

Edited March 8, 2016 by Geschosskopf

[Bev7787]

I see a martian reference.

[Scotius]

Poor Nelemy - he was apparently hit by a sudden case of... Space Madness!!! Luckily it was a short episode, but he'll need to be watched in the future.

And yes. Finally! Resources! ISRU! Home-made fuel! No more hauling ungodly amounts of LFO from Kerbin across the system. Fanfares!

Laythe? Will you spare a moment to review and upgrade equipment of this mission before 1.1. Supernova event?

[Brotoro]

On March 8, 2016 at 10:09 AM, Scotius said:

Laythe? Will you spare a moment to review and upgrade equipment of this mission before 1.1. Supernova event?

I have tested some of the ships on Laythe. I checked the BirdDogs extensively, and the SSTO Crew Carriers (the old one can't reach orbit...the newer RASSTO maybe can reach orbit). A version of the SSTO Crew Carrier 9e I'm using on Kerbin should work on Laythe, so they need that sent as a replacement. I haven't checked the SSTO planes (but I think they won't make orbit). Better crew transport planes would be nice with the new inline cabin. 

But Laythe is suffering from some strange pox that discolors parts of its surface now (when down low...but not when viewed from orbit) when I use the newer E.V.E....but I can't get any response about what's causing this. 

[Kelidoskoped]

Reusable! Pah. I reach orbit (with my 30 ton chemical tug, awaiting trial debris retrieval) with a full sustainer that slammed into my tug. Rocket parts are cheap- in sandbox..

AND my boosters have 76 m/s of Delta V. Or they did before I decided that they were good targets and fired missiles at them.

Edited March 25, 2016 by Kelidoskoped

[The Optimist]

12 hours ago, Kelidoskoped said:

Reusable! Pah. I reach orbit (with my 30 ton chemical tug, awaiting trial) with a full sustainer, using a regular path. Rocket parts are cheap, Brotoro.

AND my boosters have 76 m/s of Delta V.

This is not how you make friends, kids.

[Kelidoskoped]

On 3/23/2016 at 10:11 PM, The Optimist said:

This is not how you make friends, kids.

I forgot to mention that it ran out of fuel trying to get to the Mun. And the sustainer promptly accelerated and slammed into my newer tug, because I forgot to shut the engine off.

Edited March 25, 2016 by Kelidoskoped

[The Optimist]

27 minutes ago, Kelidoskoped said:

I forgot to mention that it ran out of fuel trying to get to the Mun. And the sustainer promptly accelerated and slammed into my newer tug, because I forgot to shut the engine off.

Well, the damage has been done already. Try to be more courteous next time. Have a nice day!

[Kelidoskoped]

1 minute ago, The Optimist said:

-snip-

You're slightly irradiated.. I've got about half a thousand rads. I'm a Kerbal flashlight.

Edited March 25, 2016 by Kelidoskoped

[Mister Dilsby]

Topic of the thread is @Brotoro's mission, folks. Usual culture I've observed in Mission Reports is that a thread about the OP's mission to X is for the OP's mission only, and not a catch-all for discussion of all missions to X. General "Mission to X" threads appear elsewhere in the Forum, for example in the Challenges section. Around here, you might suggest ways the OP could solve problems they're facing in the mission, but if you think you did it better, you make your own thread--and expect the same kind of courtesy from your fellow forum-goers.

[Dark Junior]

Finally! The series (The Laythe one, to be exact) that got me to play KSP!

[max_creative]

Can't wait for more developing Duna and long term laythe! And please send something to Dres soon! 

[Brotoro]

Developing Duna - Part 11 

What's What in One point One

This episode is just a quick update on how the Duna Mission has fared the transfer of my ancient Save game to KSP version 1.1...plus some messing around with rovers. You can read about some of my other experiences with version 1.1 in my recently-posted episode 45 of my Long-term Laythe mission.

I loaded up my old Save and all the mods it uses (with versions of the mods that had been updated for 1.1 compatibility, if available). The first thing I tested was my SSTO Crew Carrier 9e rocket, a vital piece of my space infrastructure because it carries my kerbals up and down from low Kerbin orbit. I ran into a weird bug where the ship would sometimes fly away from the center of the window (almost as if the CG point was shifting rearward beyond the bottom of the rocket). After removing various mods and reinstalling them a few at a time, the culprit that seemed to cause me several problems was the KURS Style Docking Cam mod...so I removed that and haven't had this problem reoccur. (But, "Wahhh!", no Docking Cam!)

 

The Crew Carrier was able to make it to orbit with 450 m/s of Delta-V remaining, and I was able to return it to KSC and manually landed it using the parachute/engine combo. So all was well there.

 

Then I hopped over to Duna to see what was up with the crew there, checking on the crew near the Duna SSTV Pyramid first because they were in daylight.

Nelemy: "Dudes...Did you feel something?"
Kurt: "It felt like Lander/Hab settled lower. Maybe there was a quake?"
Hellou: "I'll check the seismic data. Is the ship OK, Nelemy?"
Nelemy: "Umm...All systems are reading green. But there is some chocolate smeared on the navball."
Kurt: "Gee...I wonder who could have done that?"

 

OK...So the Lander/Habs are still OK...or as OK as they were after the change to 1.0.5...which is to say, they could still make it to orbit and land safely if done carefully...but new ones will be sent that have upgraded systems, as described in the previous episode (I'm assuming the aerodynamics have not changed a lot since those previous tests in 1.0.5).

Unfortunately, looking around the rest of the SSTV Pyramid landing site revealed a couple problems. Problem #1: The flag planted on the pyramid fell over. It turned out later that ALL of my previously planted flags are falling over in 1.1.

 

Problem #2 is much worse: Four of the eight wheels on the Duna Fido rover are "blocked" so they will not operate. The four wheels in the center are still clear, but the front and rear wheels are blocked:

 

It's not clear to me why this is happening. I thought that in KSP, different parts of your ship can't collide with each other (something I thought was implemented way back when to keep ships from exploding). So why are the wheels even checking for collisions with other parts of the same ship?

This is particularly bad, because even though the Duna Fidos were no longer going to be useful in their previous "hop to orbit" mode, I was still going to do some roving exploration while the replacement rovers were sent to Duna.

Uh oh... What about the replacement rovers? One of the payloads I launched last episode to be sent to Duna has three of them on board. Below you can see a copy of the Duna Fido 3c that I plopped out on the launch pad to check (since you apparently can't check for wheel blocking in the VAB)...and, alas, the front and rear wheels are blocked on the replacement rovers as well. Bugger. Well, if that doen't get fixed with some update soon, I'm going to have to ask the judges for a do-over on that launch so I can replace the rovers waiting in orbit.

 

Ah...But what about the other roving vehicles I have on Duna? So I hopped over to Duna Main Base to check out the equipment there. Below, the Duna Base rover (with Thompbles and Emilynn onboard) has unblocked wheels. Good. Also, a quick test drive showed that it actually handles better than before (it is somewhat top-heavy, so you had to be very careful stopping...but it does much better now).  

 

The DunaDog roving wheels are unblocked...so I assume that the replacement DunaDogs will also be OK in that regard, since I didn't change anything in that area when I added the fuel cell power.

 

The Fuel Fido, alas, has one set of wheels blocked. Oddly, the corresponding set of wheels on the other end are NOT blocked, so I guess I didn't build this vehicle's wheels exactly the same in front and back.

 

The Fuel Fido can still work with only six of its eight wheels unblocked, so these can still be used, if not as efficiently as before. But, sadly, there are a few more of these on the replacement payloads waiting in Kerbin orbit...so I may need a do-over there as well before I send them off to Duna. Happily, the Fuel Fido has MUCH less of a tendency to try to flip over when braking (I had to be very careful driving these in 0.90 because of that...it was important to slow down before trying to brake).

The payloads waiting in Kerbin orbit also contain a variation of the Fido meant for use on Ike (shown below), which happily has no blocked wheels. The wheels on the large mobile IRSU vehicle are also not blocked, so no need to replace either of those payloads.

 

 

Replacement Rovers

So I needed to make some versions of the rovers to replace the ones waiting in orbit that have blocked wheels (assuming that this doesn't get fixed by an updated version of KSP soon). I also wanted to test out the new version 1.1 wheels, which have been completely redone.

Below is the reworked version of the Duna Fido 3c, named the Duna Fido 3d. I just slid some of the structural plates inward or fore/aft to get maximum clearance from the wheels (which are still in the same locations to get the maximum wheelbase in the 6-meter-diameter stackable format).

 

I wanted to test out the rover to see how it handled with the new wheels. I was also worried about whether the RTGs (there is one RTG per wheel) were going to provide enough power. To test the rover, I drove a remote-controlled version out to the mountain peak West of KSC. How high up the mountain would the rover be able to climb?

 

The drive across the grassland and rolling hills west of KSC went fine. The eight standard rover wheels (with default settings) handled well and reached speeds of around 25 m/s without drawing more energy than the RTGs could provide (so the batteries stayed near full charge). The rover could easily handle 2X Phys Warp, so the trip went quickly. I had tried 3X Phys Warp briefly, but that lead to violent jitteriness, spin outs, and blown tires. 4X lead to certain destruction. The SAS was also in use, with frequent taps of the F key to reset the SAS as the rover went up and down slopes to minimize the SAS fighting the incline.

 

When I got to the foothills of Mount RoverDeath (oh, wait...is that foreshadowing too obvious?), the wheels began using more energy than the RTGs could supply, and the batteries drained fairly quickly...so I was going to have to pause and let the batteries recharge (it only took a couple minutes for the batteries to fully recharge when the rover was stationary).

 

I parked the rover at right angle to the slope for the recharging period...but it turned out that even with this moderate slope, the rover was sliding sideways downhill. Well, that wasn't good.

 

So I started messing with the wheel settings. Ah! If you change Friction Control from "Auto" to "Override", then you can crank the Friction Control up from a value of 1 to a value of 5 (see below). Cool. I guess those wheels have lots of little gripper claw studs that can be extended with the flip of a switch. Maybe this would make the rover use more energy to cover the flatlands...but it stopped the sideways sliding on the hillside, so I went for it.

 

Below we see the rover (about 50 minutes into its mission...but less than that for me because of the 2X drive over, and the fact that "seconds" take less than one second for my machine running the new 1.1 version...nice optimization improvement, Squad!). I could generally drive for several minutes (more if angling along the slope...less if straighter up slope), and then I'd put on the brakes and let the RTGs recharge the batteries for a couple minutes (using time warp, so very quick for me). Not bad.

 

As I got higher up the mountainside, the driving got trickier. I had to be careful to get the rover into a sideways position and put the brakes on BEFORE the batteries ran completely dry (otherwise the rover would start rolling backward, and it would be easy to wipe out if you let it get going too fast backward). All of the driving at this point is at fairly shallow angles to the slope. But I often drove my Bird Dogs on Laythe on the sides of these kinds of slopes, so I have the technique down pretty well.

 

Below is a view back toward KSC from a point 2730 meters up the side of the mountain. This was at about an hour into the mission.

 

Below, the rover reaches the really steep stuff. The last picture I got documenting my height is shown below at 2960 meters. I managed to get above 3000 meters, but started running into slopes steeper than 45 degrees...and I fumbled a switchback move...and the rover went smashing down the mountainside.

 

 

 

So...For my replace rovers (if it turns out that I need to replace the Duna Fido 3c rovers waiting in Kerbin orbit), I'll probably use the Duna Fido 3e version below, which has two additional batteries so that the rover can run on slopes for longer periods between recharge breaks).

 

For the Fuel Fidos waiting in Kerbin orbit, I'll just tweak the position of those two blocked wheels and add a couple more RTGs...but leave them mostly unchanged.

 

Fuel Cell Fido Change?

In my Long-term Laythe thread, Geschosskopf was expounding upon the wonders of setting Traction Control to zero, and the use of fuel cells to power rovers (instead of RTGs). So I wanted to see what kind of range my Duna Fido could get using fuel cell power. Below is the test vehicle, Duna Fido 3fc. All of the RTGs were removed and a six-pack of fuel cells was added to the right side structure. A single small Oscar-B propellant tank was added on the left side.

 

 

Shelwing Kerman was assigned to the mission (since there wouldn't be any dangerous mountain climbing), and he headed off southwest over the rolling flatlands. The fuel cells provided plenty of energy for the plains, and the rover could cruise along at over 27 m/s (and handled just fine at 2X Phys Warp).

 

Oh, here's something I don't like: The cloud shadows in E.V.E. make the surface dark and dreary (as expected, but not really pleasing), but they also cause the light from the illuminators on the rover to be dim and washed out as well. That's silly and ugly. I have to remember to turn off those cloud shadows...or at least crank that effect way down.

 

The test drive ran for a little over 30 minutes (mission clock time) until the fuel tank was half-full (you see that I'm a half-full kind of guy, and not a half-empty kind of guy). The rover had traveled about 49 miles and used 9 units of liquid fuel (and a corresponding amount of oxidizer)... so that comes out to about 5.4 km per unit of liquid fuel.

 

 

Interesting. And for a lot of people who don't do a lot of rover driving, sticking on a couple extra Oscar-B tanks for a total range of around 290 km would probably be all the range they need out of a rover. But I like to do more epic drives, and having to mess with refueling rovers (as well as all the other ships) would just be too annoying. Unless, of course, Squad would give us handy refueling hoses. Have I mentioned before that I think that refueling hoses would be a fantastic addition to stock KSP? Please, Squad? Pretty please??

 

Going Grippier

I've traditionally been a fan of the original rover wheel (as opposed to the later ruggedized wheels), mostly because I had gotten very familiar with the handling of the original wheels, and I always found the ruggedized wheels to be more prone to mysteriously grabbing the ground and causing rovers to flip (hopefully that ground-snagging bug is gone from the new rover wheel physics). I did use the ruggedized wheels on my rovers for very low gravity worlds where more traction was necessary. So I wanted to try out the ruggedized wheels in 1.1...

...therefore I built and tested the Duna Fido 3g (the "g" is for "grippier!") shown below. It's basically the same design but with eight ruggedized wheels, plus some extra RTGs (a total of 12 RTGs) because the grippier wheels are more power hungry.

 

I set the Traction Control to zero in honor of Geschosskopf, and set the Friction to 2.5 for extra grippy fun. Then I sent the rover off toward the ominous music playing from Mount RoverDeath to see what it could do. It was able to go considerably faster than the standard wheel version over the rolling lowlands (up to 45 m/s)...but it would slowly drain the batteries at that speed.

 

Sadly, the rover could not handle 2X Phys Warp without jittering and occasionally spinning out, so I had to keep it at a boring 1X warp.

The grippy rover could handle the slopes more head-on (at the expense of faster battery depletion, of course), and could maintain good speed up the foothills...

 

...but this speediness lead to me making the classic rover blunder (even more classic than "Never get your rover involved in a land war in Asia)... which you can see coming up ahead of the rover in the picture below: The deadly "going to fast into the V-trough" scenario... Which resulted in EXPLODING the right-front wheel. Not popping the tire... exploding the wheel.

 

 

Arrgh. So...Do I give up and send out a new rover? Nah...I was already at over 50 minutes on the clock (at 1X no less). So I decided to see what it could do with only seven wheels. I cranked up the Friction setting to 5.0 to maximize the grippy goodness.

 

The rover could make slow, power-hungry headway straight up 30 degree slopes...but it did better and required less-frequent recharging pauses by attacking the slope at an angle. It easily surpassed the 3000 meter mark and kept going.

 

 

Soon I was driving at levels where the clouds were passing across the mountain, and into the realm of slopes greater than 50 degrees that demonstrated the awesome power of +5 Grippy Tires. 

 

 

Things got very tough at around 3660 meters, where even the +5 Grippy Tires showed some slipping. It was very important to watch the battery charge and time the recharging pauses at places the rover could stop without sliding.

 

Getting the rover over the lip onto the ridge top just above 3700 meters was very tricky, but a final recharge gave the power necessary to bull over the top.

 

That left only the final steep peak to tackle... Perhaps I could spiral up around it at a shallow angle...

 

But, alas...the sharp change of slope above 3980 meters was my downfall (literally) when I couldn't keep all of the wheels in contact with the surface and ended up back-rolling...and the rover plummeted down the far side of the mountain.

 

 

So...The Duna mission is going to have to wait until the problems with rover wheels are resolved before I will move forward. So let's end with a picture of one Duna Lander/Hab 1, with my flag symbolically lying in the dust after the 1.1 upgrade.

 

 

[Angelo Kerman]

I am having similar problems with my modded wheels for the Buffalo mod and had to build some creative solutions for Pathfinder to get things to work the way I want. And while I don't like this method that Squad provided, @nli2work discovered some settings in settings.cfg pertaining to wheels:

I hope Squad fixes the wheel blocked issue in the next update.

[Scotius]

Update 1.1.1. is out! Check it out guys - plenty of wheel fixes in the changelog. Hopefully all whell-related woes were adressed (and not many new bugs slipped in )

[Brotoro]

3 hours ago, Scotius said:

Update 1.1.1. is out! Check it out guys - plenty of wheel fixes in the changelog. Hopefully all whell-related woes were adressed (and not many new bugs slipped in )

Rover wheels: Still blocked in 1.1.1. No help there.

Um... HOW do I move the navball around? I thought there was a way to do that added to 1.1.1, but I can't figure it out.

Edited April 29, 2016 by Brotoro

[Scotius]

So. Another day, another patch Did wheels got fixed for good this time? I can't check for myself yet, because i'm still downloading 1.1.2. Seriously, when SQUAD intends to fix the Patcher?

[Brotoro]

2 hours ago, Scotius said:

So. Another day, another patch Did wheels got fixed for good this time? I can't check for myself yet, because i'm still downloading 1.1.2. Seriously, when SQUAD intends to fix the Patcher?

No, the wheel collision problem is apparently an issue with Unity...so 1.1.2 did nothing for that.

I'm suffering from "update fatigue" again, just as happened after the release of 1.0 and subsequent patches. Install..get all the settings set the way I like...see what mods are broken...test stuff again in the new version... ...I need a break.

Edited April 30, 2016 by Brotoro

[Galileo]

16 minutes ago, Brotoro said:

No, the wheel collision problem is apparently an issue with Unity...so 1.1.2 did nothing for that.

I'm suffering from "update fatigue" again, just as happened after the release of 1.0 and subsequent patches. Install..get all the settings set the way I like...see what mods are broken...test stuff again in the new version... ...I need a break.

Yep.  Exactly.  I haven't played in so long.  Just constant testing of things. I'm just gonna wait a few weeks to get back into it.  How the modders just keep updating is crazy to me.  I would have walked away from modding at this point.  Those guys are better than me I guess hats off to them

[Brotoro]

After playing around in 1.1.2 tonight, I haven't seen anything that improves any problems that I had in 1.1.1.

But 1.1.2 has added a tendency for my planes to veer in yaw when trying to take off or after landing. Same plane designs, unchanged since 1.1.1.  Sigh.

[Commander Zoom]

All of my sympathies.

[Kiwa]

On 29.4.2016 at 2:24 AM, Brotoro said:

Rover wheels: Still blocked in 1.1.1. No help there.

Um... HOW do I move the navball around? I thought there was a way to do that added to 1.1.1, but I can't figure it out.

It's a bit hidden, but.. in the settings, same place where the UI scaling is/was. Not sure whether the settings are available outside the Flight scene though, so probably best to start on the launchpad and then open the settings.

Spoiler

 

Edit: see screenshot above.

Edited May 4, 2016 by Kiwa
added screenshot