Deadweasel

Actually, no. Try to keep them along the CoM. putting them at the rear, above and below the wings or even along the body, still results in a huge tendency for the ship to nosedive.

Personally, I find this bugger a bit better than the Docking Cam, currently: http://forum.kerbalspaceprogram.com/showthread.php/43901-0-21-Docking-Port-Alignment-Indicator-%28Version-2-1-Updated-8-17-13%29%29

Well, I'm saying it is that hard, if your plane is twitchy enough to keep your eyes locked on the instruments, and your fingers busy at the WASD keys. For example, HSTAC-101 WhiteRaven- -is super twitchy and requires constant attention to get her down gently. HSTAC-102 Silverhawk- -will not tolerate any lapse on the controls. To be honest I have yet to actually get this one landed without some part or another coming off on touchdown. She's just too jerky to get a stable descent, and demands you play Tiddlywinks with the keys to keep her entertained. SDV-1 Mosquito- -as a VTO/L is not capable of lateral sustained flight, and relies on its engines to keep it aloft. When coming in to land with a full payload? Yeah, don't look away, don't fat-finger the keys, do not SNEEZE, or she'll dump everything over in retaliation.

The rule of thumb I've been able to figure out is this: If ksp.exe is running more than 3.3GB at the space center scene, you're running the potential for a crash-to-desktop scenario. While the game's memory usage is fairly stable, it does tend to spike when changing scenes or the vessel in focus. If you pull enough parts out to keep below the 3.3GB amount of used RAM, you should be able to run the game without issues for longer than you have free time to play.

Try taking a screenshot while landing one. Pain in the butt, it is. Best I've got are primarily of HSTAC-103 Banshee, which is the most stable for low level maneuvering. Everything else does well straight in or out, but are less than forgiving since the reaction wheels update. Buzzing the tower, running its aerobatics abilities to its max potential On Laythe, about to make an attempt on a chosen landing position Looking for the desert temple on Kerbin

All you have to do is create the directories; the plugin will roll from there Go to %KSP_ROOT%\PluginData\subassemblyLoader\subassemblies Folders you create in there will become available as "categories", using the folder names.

Actually, I had no idea they had a cumulative effect like that. Now I've got a whole fleet to mod further.

I still enjoy the visuals. It's a great "getaway" movie for pure science fiction value. I agree that there are some HUGE holes in that movie, but I liked it nonetheless. That said, I'm still looking forward with some hope as to what might be done with the sequel. Now that the whole xenomorph thing has been dealt with and kicked off for the rest of the Alien franchise, I'm interested to see if the smart decision is made to follow Elizabeth's journey to find the rest of the Engineers. There were some interesting angles I'd like to see expanded upon, in a completely different direction that isn't a 2 hour monolith to Alien fanservice and call-outs. Back on-track: I'd really like to see what comes of your latest effort!

Believe it or not, it's entirely on the honor system. http://forum.kerbalspaceprogram.com/showthread.php/24581

If the green line is to the right of the center, you need to translate to the right. Basically, assuming you are already oriented properly with both rings in the center, start nudging toward whichever direction the green lines are from the center lines.

One simple comparison will tell you why KSP can't work on a console without some serious differences: XBone controller: 14 buttons (almost forgot trigger and shoulder buttons) KSP key bindings: about 77 (not including duplications of existing keys in different modes, WSAD are counted once, though they're used in multiple scenes) How many button combos needed to fulfill all those?

Oh I see! So a little more blatant direction indicator when the difference is so small you can't see it graphically. Makes sense, but hoo boy that must be some powerful OCD! (totally kidding, I get your point)

This only applies if you're running an integrated video card that shares system memory. That said, there is still a system overhead that applies to RAM in computers with independent video cards, and it generally works out to about 300-400MB, so 32 bit programs will crash if they attempt to use more than 3.6-3.7GB of RAM.

https://www.youtube.com/watch?v=hA5Nu2B2uvM "Who speaks Latin?" "No one speaks Latin; it's a dead language."

Nothing else in the game tells you what you need to hit to do something, why would anybody need a reminder as to what to do to rotate? The only new information this mod provides in this particular case is which way you need to rotate to align with the current targeted port, and honestly that's really pretty self-evident. It just takes a moment to try the keys to see how the controls influence the markers, and their behavior matches perfectly with expectation. If you need reminders to tell you how to rotate, you probably just need a little more practice with maneuvering in general, first. Vertical marker is to the left of Top-Dead Center, rotate left toward it, etc.

Maybe if there was a context menu method? Right-click: "Set as Target" or "Set as Alignment Target"

yesnaoplz!

Perhaps this one? http://nathannifong.com/FairingFactory/

Congrats! It's so cool isn't it? I wish there were more worlds where aircraft worked. Even better, I wish we could build aircraft on those worlds, just to have the challenge of adapting to new and different flight dynamics.

[TABLE=width: 1280] [TR] [TD]A lot of planning and effort completely undone in a heartbeat by that damnable vessel switching bug. > Today, multiple long-term missions were recalled and placed on indefinite standby, pending investigation into the tragic loss of the Duna expedition. The Duna mission's kickoff was highlighted by the maiden flights of a new long-range transport vessel and a matching variable cargo hull based on the Interplanetary Exploration Vehicle program. IPCV Ronin took to the skies and proceeded to perform a flawless orbital insertion. Even with all engines active, Ronin had more than enough delta-v to reach the Jolian system, though it must refuel in order to return. The mission plan was to perform a thorough flight testing of Ronin's systems, then launch its mission cargo vessel, Kalypso. Kalypso was designed to be unmanned, though it is initially piloted by two crew members, one of which would join the Duna mission. The cargo vessel contained two light Sun Sprite-class landers, as well as a modified and expanded version of the HSTAC Silverhawk program's experimental power station and fuel conversion system. The fuel converters were intended to resupply the landers upon return, but could also be used to replenish Ronin's supply in an emergency (though replenishment of such a large ship takes hours to complete). Upon arrival, the main engine and command sections were disengaged from Kalypso, the command pod then re-connected at the aft end, and completed Kalypso's docking with Ronin. Once final docking was complete, Kalypo's systems were brought fully online for integrity and status checks of the power station and the lander modules, to be completed by Nelnard, while his partner Elner departed to retrieve the disengaged Kalypso drive section, to de-orbit and return safely home. Kalypso's cargo and systems full tested and verified, Nelnard called Ronin to return all of the ship's systems to standby, and took his berth in one of Ronin's spacious crew compartments. The rest of their crew mates would be joining them soon. Two days later, a Goshawk automated transfer ship arrived to deliver the final crewmembers, who transferred to their berths aboard Ronin without incident. Ronin reached the transfer window to Duna a couple of hours afterward, and many aboard -as well as those on the ground- found themselves holding their breath, save for the Flight Director, who relayed the countdown to burn initiation. Mission commander Johnoly, at Ronin's helm, primed the main engines. At zero mark, he triggered the ignition sequence and began throttling up. After a couple of minutes at full main drive thrust, the final flight test was completed, and the mission designers' insistence that Ronin would require additional power to complete the transfer burn was now proven correct. Mission Kontrol advised ignition of Ronin's four secondary engines, which Johnoly triggered right away, having been prepared for just this eventuality. What nobody had been prepared for was just how sudden and strong the additional engines' power would begin to act. Within seconds, all aboard could hear the groaning of the hull under great strain, followed by what was later described as a blood-chilling "pop". Ronin lurched ahead, suddenly free of its burden. Kalypso's connection to Ronin had severed, and the cargo vessel was now floating free. The command channel was suddenly flooded with traffic from Mission Kontrol and the four mission specialists berthed on Kalypso, all screaming the same word: "ABORT!" Johnoly wasted no time and killed the drives immediately, then brought Ronin about to kill off the relative velocity to Kalypso. The mission's transfer window for this orbit had been shot, but that gave everybody an opportunity to asses the situation. It was determined that Kalypso's interia had simply caused the ship to break from its dock under the sudden acceleration of Ronin's secondary engines. After the docking ports were inspected, Kontrol gave assent to attempt to re-dock again. Johnoly guided Ronin in, painstakingly nudging the ship back in-line with Kalypso, which now had no command and control functionality of its own. At the final moment of the maneuver, however, none heard the expected telltale "ka-chunk" of a successful docking. Instead, they heard a soft, resounding "clong". The docking ports had contacted, but the locking mechanisms had failed to actuate. Further inspection of the docking ports revealed that while they were structurally-sound, the lock actuators themselves were damaged beyond their ability to repair. The mission was over before it had even begun. With the Goshawk now two days out from re-joining the mission to return the crew home, the decision was made for the specialists still aboard Kalypso to man the lander modules and abandon her for Ronin's service docks instead. They would be much more cramped aboard the landers, but at least they'd all be together and more assured of rescue, once Goshawk arrived. Their departure was marked by saddened silence, broken only by occasional automated positioning updates from Ronin's nav systems on the flight channel. Two days later, Goshawk obtained Ronin's beacon and began its approach, guided remotely by Mission Kontrol. At 5 keks away from rendezvous, alarms began to sound on the ground. Tracking flooded the Flight Director's local channel with information that Goshawk itself was currently confirming: the area had become suddenly filled with numerous scanner pings that should not have been there. Medical quickly joined in, calling out loss of connection with all of the crew members aboard Ronin. The command channel was largely unintelligible, filled with screams from the Kalypso crew, still aboard the landers -or according to tracking- what remained of them. It quickly became clear that for some unknown reason, Ronin had suffered a serious failure; one that had resulted in the ship's explosion and subsequent disintegration. For the second time in a year, the Black Shoal protocol was initiated at KSC. A broad, temporary media blackout was enacted, and all attention at Mission Kontrol was diverted to saving what lives they could. Tracking was able to lock on the lander pods, which had somehow survived the event intact, but tearfully informed the Flight Director that they were currently on terminal return trajectories, and they were now too far away for Goshawk to reach them before they re-entered the atmosphere. The entire crew of the Duna mission had been lost within a five minute span. After the lander pods fell silent, the Flight Director ordered Goshawk to begin searching the debris field. Kalypso, unmanned and at standby power, was discovered a short distance away. Its flight recorder hadn't captured the event that had befallen Ronin. Kalypso was left where it was, to act as a memorial to the fallen crew, and to offer support services for future missions on-orbit. Meanwhile, IPEV Tailwind, stationed at Münar orbit, had just overseen completion of yet another science mission on the surface. Tailwind, originally launched as a mobile exploration command station, had been temporarily re-purposed as a docking and service platform for the KSC's High-Speed Trans-Atmospheric Courier program. Expanded over a year ago with a disposable fueling and docking tower, Tailwind had not originally been expected to depart its orbit for another 18 months. Tailwind had also suffered some damage during its initial launch, destroying its on-board fuel conversion and power storage capabilities. Because of this, Tailwind would be unable to resume its rounds to the other bodies in the Kerbol system without returning home for patch work. With the still-unexplained destruction of Ronin, the decision was made to recall all fleet elements capable of returning home for a complete inspection and possible overhaul. The HSTAC program was temporarily suspended, and all crew on or near Tailwind ordered to secure testing hulls to the fuel tower, top off Tailwind itself before disconnecting from the tower, and burning for home. The fuel tower would remain powered and active to support possible future missions, with enough fuel still aboard to maintain the existing exploration vessels for another two years. Tailwind returned to Kerbin and assumed a high parking orbit, there to begin its long wait for inspection and service teams. The flight crew were retrieved by the still-deployed Goshawk for some well-earned R&R while Tailwind was otherwise indisposed. After an inspection crew had performed a thorough analysis of Tailwind's systems (or lack thereof in some cases), an ASV Sparrow-I was deployed with a module designed to replace Tailwind's missing equipment. Once rendezvous was completed, the repair procedure was initiated, and the Sparrow released its payload in preparation for re-orientation, and began lining up to install the module in Tailwind's forward cargo bay. Installation complete, Tailwind switched its power systems over to the new power plant, and the Sparrow returned to Kerbin to be discarded over uninhabited territory, fuel tanks dry. With Tailwind returned and repaired, efforts to determine the cause of the Duna mission disaster are scheduled to resume. Tailwind will be tasked to the site of the accident, and will be joined by a pair of recovery tugs to begin the work of collecting debris for analysis, though it's widely believed the KSC will never discover the true cause of the destruction of Ronin and her crew. [/TD] [/TR] [/TABLE]

Heh, IPEV Excursion and IPEV Tailwind have that aspect covered well Also, this latest rendition of the plugin is a massive improvement. Love love LOVE it! I can already handle docking very well with just the navball, but getting properly aligned and rotated before docking without having to cam all over the place? GENIUS!! <3

Well that's okay. It's still a sexy beast.

Too bad she can't ease production of video frames, amirite?

Kinda reminds one of Instagram, doesn't it? That incredibly unpopular and universally hated photo sharing site- oh, wait.... "Doesn't look real"? Really. YA THINK?!