lodestar

Where exactly around the Sun? I remember it used to be very low, but it's impossible to get that close without exploding now.

Does anyone else feels like the engines 45º angle is too much? It's a 30% cosine loss. The SuperDraco is more like 25º, probably even less. Is it possible to change the angle without editing the model? An MM patch?

I had something like that in mind, more like the Terra Nova from Race to Mars. But then I realized the Terra Nova could spin during the cruise phase because it uses NTRs and a Hohmann transfer, unlike the Hermes.

Actually, in the book there's no centrifuge at all. The whole ship spins, with the reactor on one end, the crew area in the other, and the engines in the middle. This design made by a fan is a lot more accurate, but I understand general audiences would be puzzled by that. http://francisdrakex.deviantart.com/art/Hermes-Infographic-486185729

Same here, still happening in 1.1.

Yes, I had the same problem. I got BDAnimations as a dependency of Taurus HCV, but since all I want is the science lab and crew container, not the pod, I removed it.

Changing the poll rate helps, but it's a workaround, not a solution.

I am using the proprietary driver.

This works fine for the icons, but mess up the pod. I guess I am missing the pod, you are missing the 'enabled = true' field.

First, keep pointing to the surface retrograde vector. Click the label above the navball until it shows "Surface" and your speed, and then point to the retrograde marker. Apply thrust aiming for 10m/s in the last few hundred meters. Being top-heavy doesn't help, but you are tipping over because you have too much horizontal velocity on touchdown. If you do the above, you can kill all velocity a few meters above the ground, then you can simply point to the center of the navball and then proceed to a gentle vertical fall.

I decided to simply disable swap while playing KSP on linux. I prefer to get an OOM kill instead of getting the whole system unresponsive when memory gets full and the system swaps like crazy.

An issue experienced by some Linux x64 users is FPS drop or stuttering when dragging the camera around with the right mouse button. Yesterday I figured this also happens with the left mouse button and doesn't happen when moving the camera with the keyboard, which strongly suggests some UI event bug, and I further realized it doesn't happen when Mechjeb isn't loaded or when no window is visible. Should I report that as a Mechjeb issue, or there's an Unity UI toolkit being used?

This seems to be a bug with the UI used by MechJeb, Scansat and a few other mods. It happens when you hold ANY mouse button and drag around with a MechJeb window visible. The problem doesn't happen when you move the camera angle with the keyboard or a controller, it doesn't happen when you drag the mouse around with no MechJeb windows visible. On the other hand, it does happen when drag the mouse around holding the left button anywhere on the screen, even when there's no window. If I had to guess, I'd say the UI is getting bombarded with movement events as you drag the mouse around.

I've been experimenting with kOS and it's great that an alternative is coming up, but how hard can it be to embed a Lua or Python interpreter in KSP, instead of writing a new language from scratch?

Awesome mod, but the fuel tanks and combined fuel tank/engines really need some balancing. They carry way too much fuel for their size. For instance, the 1.25m Landing Lower Stage carriees 90/110 LFO, the same as the stock FL-T200 Fuel Tank, which is at least 4x the same volume. Also, there's an issue with using the Lander 1.75m engine/tank with the undercarriage landing gear. With the other engines it works fine, with the jet going through the middle, but with that engine I get a burst of thrust when I turn it on, then no more thrust.

You need a set of relay satellites in a lower orbit. I usually do that first, placing 5 or 6 satellites in a 141km orbit.

Take it easy, dude. I'm sure he just means he has too many mods already...

The same here. I removed the ASET Props and it's better now, but I'm not sure what I'm missing by doing that.

I did that as a workaround, but it's still annoying. For instance, I can't prevent the del key from switching to docking mode without reassigning it.

I'm having this weird problem where inputting values in a mod UI, like MechJeb or Crew Manifest, triggers action groups and other functions bound to that key. Is that a known Linux issue?

Sure, here is an ls from my GameData: ModuleManager.2.5.1.dll toolbar-settings.dat AnchoredDecouplerFix.dll ChuteQuickloadFixer.dll SymmetryActionFix.dll EVAEjectionFix.dll LargeCraftLaunchFix.dll 000_Toolbar 000_USITools AIES_Aerospace ART ASET BahaSP blackheart BoxSat alpha cfg_tweaks CIT CommunityResourcePack Contracts Window CrewManifest CrossFeedEnabler DeadlyReentry DibnahEngineering DMagic Orbital Science FinePrint Firespitter FreedomTex Hydrogen NTRs JSI KAS Kerbaltek Kerbice Group Klockheed_Martian_SmartParts kommit_octotruss Kotysoft KSO KSPX KWRocketry Landertron Lionhead_Aerospace_Inc MechJeb2 MechJeb2 Embedded by Dennis6492 ModsByTal ModuleRCSFX NASAmission NAU NavyFish NearFutureConstruction NearFutureElectrical NearFutureProps NearFuturePropulsion NearFutureSolar NearFutureSpacecraft ORSX PartCatalog ProceduralFairings ProceduralParts RCSBuildAid RealChute RemoteTech RLA_Stockalike Robau R&SCapsuledyne SCANsat SmokeScreen Squad StageRecovery TacFuelBalancer TacSelfDestruct TextureReplacer ThunderAerospace TriggerTech TweakScale UmbraSpaceIndustries UniversalStorage

I've been using RT for months, but I recently became so frustrated with some dish-pointing issues that I decided to change all antennas to omni range and give up on directional antennas for a while. I have to admit that I actually like it better now and it's a lot less frustrating.

I'm no longer running the open source drivers, but it worked fine with them. I recently started playing with a lot of mods, and after growing frustrated with the frequent crashes on Windows, I decided to give a try on Linux. I already had ubuntu 12.04 on the same PC, and I already had Steam on it, so I just installed KSP and everything was fine, except there was a small but noticeable FPS drop, like when I tried to use OpenGL on Windows. I decided to upgrade to Ubuntu 14.04 but it didn't helped much with that. Then I decided to use the proprietary driver, and it didn't helped either. I eventually realized it was much more stable and the small FPS drop was acceptable. It's a 4 year-old computer, quad-core with 6gb RAM, and a Radeon 6570, so I can't expect much from it. The most astonishing was the fact that I simply copied my GameData folder with 50+ mods and plugins from the Windows install to the Linux and it worked without a single hiccup.

Nobody is asking for anybody to spend time doing anything. I asked if it would be possible to do such a thing in KSP, and for some reason people understood it as a feature request for cloth physics, which is not the point at all.

Yes, but that is not so important, since it means the mission failed. Sure, you can try to get out of it, as you may try to get your craft upwards when it tilts by accident during landing, but you're more likely to revert the game and try again.