steve_v

A thread that is pinned to always appear at the top of the forum index, prefixed with "Sticky:", and the place to look first for known issues. That said, far be it for me to argue with a mod but a casual glance at the unmodded support forum shows 4 sticky threads, and none of them actually mention this issue in the OP.

Sometimes things go horribly wrong, backups are good. Automating said backups with something like this helps. I haven't had that particular kraken for a long time... and even then it was a mod issue IIRC.

It's supposedly fixed in the dev version on github (not yet released), or roll back to 2.4.5.

Not a security issue, or anything against MS specifically. It's because stuff in that repository is non-free or "not open source". It might "taint" your free software system. The Ubuntu "Multiverse" name is silly IMO, in Debian it's called... "non-free"

Open a "terminal emulator", type (or paste) 'sudo apt-get install ttf-mscorefonts-installer' (without quotes) and hit enter. what does it say? (after asking for your password that is). You should get a bunch of output as it downloads several .exe files from sourceforge and extracts them. When it's done you should have a bunch of fonts in '/usr/share/fonts/truetype/msttcorefonts/' Apt is the primary tool for installing software on all debian based systems, there are GUI frontends such as "ubuntu software center" and (better) Synaptic. However, if you do it from a terminal/command-line it's easier to see what's going on, and I don't have to guess what desktop you're running or what dialogs you're seeing.

So, what does 'apt-get purge ttf-mscorefonts-installer; apt-get install ttf-mscorefonts-installer' say?

Downloaded from where? and fails how? Been here? Why are you not using the package manager? -> 'apt-get install msttcorefonts' or 'apt-get install ttf-mscorefonts-installer'

Who cares? if you don't want it, tweak it out. I'd vote but there's no option for "nice to have but no big deal". IMO, the EVA packs have plenty of fuel but the monoprop is handy for docking small landers.

Thanks muchly, have some rep. It would be awesome to see something like this in the pack.

Wanna share? This is exactly what I've been looking for, but I'm feeling particularly lazy today

You lucky sod, pics or it didn't happen

That Player.log just ends, with no usefull information in it at all. Can you get system logs (via SSH?)? What happened to Minecraft? something similar? Were the keyboard LEDs flashing (kernel panic)? Do the magic SysRq keys work? (Ctrl-Alt-SysRq-k etc.) I see you have an AMD card... With catalyst v13.35 driver, yes? Others have had similar issues with AMDs driver, might be worth investigating other/newer/beta versions or trying the open-source radeon driver (performance will probably suffer though). IME, lockups like this are usually a: hardware b: kernel bugs or c: GPU drivers. My money's on the last one.

Just guessing here, but that sounds like the fairly common problem of controller 'wind-up' in RL, where the controller is still active but is unable to produce any change in the process state. Many RL PLCs have built-in code to detect this, which often doesn't work very well. I tend to insert various error checking (is this valve responding etc.) blocks anyway, in case someone turns off something they shouldn't , or, ya know, some wires escape... Since KSP disallows any kind of control without a pilot / probe core it might be worth shutting down the the autopilot / putting the PID controller to sleep if the pilot goes AWOL, as counter-intuitive as this sounds.

Or, more accurately, when KSP would otherwise delete them.

This is a known & extremely annoying issue, as far as I can tell nobody knows what's causing it. For me, restarting the game before loading the quicksave fixes it. Nice spaceplane BTW If anyone knows what's actually going on here, please pipe up.

If periapsis is below ~22km (greater than 0.1 atmospheres) when going on-rails, IIRC they should be recovered. Otherwise they'll keep "orbiting", possibly dipping into atmo with no effect. 'tis just the way KSP works unfortunately, there's no orbital decay while on rails unless it encounters >0.1 atmo, whereupon it magically dissapears & StageRecovery kicks in.

Are you both running KJR? If so, get the latest from github.

Cheers for the handy explanation, I was thinking the 'scalar' might be er.. backwards, hence I haven't been using it Was about to ask, but beaten to the punch

Agreed, the H60 is a good unit but IME you'll still get better cooling performance per dollar from a high end air cooler, with less complexity and fewer moving parts. Then there's pump noise, which I personally find more irritating than a fan. Unless you intend to run GNU/Linux or BSD on it, where AMDs drivers are horrible or non-existant.

Sooo, I see this is a "known issue" and it looks like it's still around. My spaceplane just "collided" with the launchpad on landing... while ~1/2 way down the *runway* Does anyone know what's causing this?

Meh, I went through a big debugging session with this not long ago (and there are my logs a few posts back). Maybe later I'll look into it. If it works for you, disregard.

"DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!" I thought as much. How much system RAM do you have? assuming >4GB: Try ActiveTextureManagement, if you haven't already, or reduce texture quality in the game settings. Otherwise you're just going to have to drop some mods or run 64bit on GNU/Linux

That thread is hilarious. Understanding orbital mechanics: Fail. Understanding perspective: Fail. Understanding time-lapse: Fail. All on page 1... Jeez. OTOH, I once had a grown adult ask me: Given a conveyor belt, powered by an electric motor (traveling uphill too FWIW), why can't you just put a generator on the other end and get some free power? The people I have to work with .

At first glance, I'd say you may be out of memory. -> "96% memory in use." Please upload output.log / Player.log somewhere (dropbox?) as per The Bug Reporting Guide. Also, FWIW, using CODE tags to make long output more readable will help prevent scaring off the TL,DR crowd

Go have a look on the KJR thread, there are a bunch of issues with the curent release, one of which sounds a lot like what you're seeing. IIRC it's fixed in GIT but not the current release. As a quick fix / test, roll back to KJR v2.4.5 & see if it still happens. If you feel like helping ferram4 out, try out the current version from GIT & report findings in the appropriate thread