steve_v

What We Need: And some other details wouldn't hurt either. - - - Updated - - - Y u no use the 'kill' command?

The "younger generation" doesn't know more about computers, they are simply more familiar with the current technology... technology that is considerably more user-friendly and easy to master than it was only a few years ago. That said, there are (usually "older) people that have had little exposure to modern gadgets - but give an '80s or even early '90s pc to an ithing whiz kid ad he'll be just as lost. As for google, the thing that frustrates me is not that so much information is available to everyone, but that so much of it is utter BS... and people still believe it. I'll use the web, but a proper technical manual - or better yet some field experience - trumps a search engine every time. I every time I hear "I can hack into wifi" (with someone else's code and some copy-paste from google) or "There's this awesome cloud thing we should be using" (which I know sod all about, but the web page looks cool).

Use MJs "Advanced transfer to another planet" function, and you can pick your transfer burn on a pretty porkchop of dv / departure time / transit time ('tis a simplified version of the aforementioned in-game tool)

Makes sense, those rankings are only page hits. Reminds me, must do something about the 3-ish years with no updates Arch install on my netbook... could be an interesting upgrade.

There's no Debian, only "Debian-Based"?

Iceweasel, Konqueror & links (70/20/10%). Seen too many browsers come and go to get attached to any one in particular.

Ya, Ive used sed find/replace on my save far too often since 1.0.3... I'm pretty sure this is a stock bug, FAR just exacerbates it when it reduces the skin area for clipped parts.

Remove all the FAR example craft (Ships/*/FAR*) and any other old files, then try again. CKAN doesn't do a very good job cleaning up cruft on uninstall, or you had FAR installed manually at some point.

Zero your axes (throttle to 50%) before starting KSP.

Check permissions on /dev/js0 (which is the 'device' argument you would pass to jstest) what file is it missing, exactly? For evtest, you probably need to either be in the sudoers group or be root. 'su' or 'sudo su' if root login is disabled. If it works in flightgear, then it's a Unity thing... what's in Player.log?

Holy moly, that redefines "wall of text" What species of joystick / controller are we talking about here? Anything using the hid-generic driver should "just work", KSP/Unity requires that it is plugged in and axes are centred on app startup. For device details, easiest to catch the last few lines of 'dmesg' after you plug it in, e.g.: Sat Jul 11 20:34:04 2015 usb 1-1: new low-speed USB device number 2 using xhci_hcd Sat Jul 11 20:34:05 2015 usb 1-1: New USB device found, idVendor=0738, idProduct=1302 Sat Jul 11 20:34:05 2015 usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Sat Jul 11 20:34:05 2015 usb 1-1: Product: Mad Catz F.L.Y.5 Stick Sat Jul 11 20:34:05 2015 usb 1-1: Manufacturer: Mad Catz Sat Jul 11 20:34:05 2015 usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Sat Jul 11 20:34:05 2015 input: Mad Catz Mad Catz F.L.Y.5 Stick as /devices/pci0000:00/0000:00:1c.1/0000:06:00.0/usb1/1-1/1-1:1.0/0003:0738:1302.0003/input/input21 Sat Jul 11 20:34:05 2015 hid-generic 0003:0738:1302.0003: input,hidraw2: USB HID v1.11 Joystick [Mad Catz Mad Catz F.L.Y.5 Stick] on usb-0000:06:00.0-1/input0 To make sure it's actually working, try 'jstest' from the 'joystick' package, or 'evtest' from 'evtest'. Your DE may have a GUI calibration gizmo in settings somewhere. Also: Check permissions on /dev/input/js0. Post 'Player.log' from KSP startup.

You're referring to the CTD with "Attempting to use memory addresses from more than 16GB" (or something to that effect), no?That's an odd one, I have no idea what's causing it as there's nothing special about addresses >16GB as far as the OS is concerned. Also, going from 8GB -> 16GB over what period? that's a pretty big memory leak to me. As for dropping the disk cache, got anything (data) beyond "seems to create more stability"? KSP shouldn't even be aware of what the kernel does with it's memory allocations. Then again, Unity is a strange beast, if it's truly the case that the amount of free physical RAM impacts stability that could be an interesting lead.

So it's not FAR, in fact it's not mods at all, AFAICT (repro'd most occurrences in stock install). Small parts start overheating for no apparent reason, I've had docking ports, octo girders, SAS modules, batteries and solar panels do it so far - both stock and mod parts. The thermal system just goes mental - usually after a docking or staging event. No errors logged whatsoever, just insta-boom. This is getting pretty ridiculous. Where's 1.0.5? you know, the patch where SQUAD finally fixes the cluster f*** that was 1.x properly? Alternatively, where's the download for the non-broken version of the game? One we can actually play without stuff unexpectedly blowing up?

And you would want to drop the filesystem cache (thereby increasing load times) why? Disk cache is freed as needed, you should be able to leave it alone.

Yes, but there may be undiscovered bugs. Use the patch mentioned and force ckan to install the version you want: './ckan.exe upgrade KWRocketry=2.7'.

Downgrading Kopernicus works for me: ./ckan.exe upgrade 'Kopernicus=1:beta-01'. Probably this: [Kopernicus]: StarLightSwitcher: Set active star => Sun (Filename: /home/builduser/buildslave/unity/build/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 56) NullReferenceException: Object reference not set to an instance of an object at Kopernicus.Configuration.LightShifterComponent.SetActive (GameScenes scene) [0x00000] in <filename unknown>:0 at Kopernicus.Configuration.LightShifterComponent.SetStatus (Boolean status, GameScenes scene) [0x00000] in <filename unknown>:0 at Kopernicus.StarComponent.SetAsActive () [0x00000] in <filename unknown>:0 at Kopernicus.StarLightSwitcher.Update () [0x00000] in <filename unknown>:0

Hmm, seeing this too, as of today. What did you (we) recently update?

Why are you running the windows version in wine? You should be starting the native client: KSP.x86_64. The dead giveaway is the mention of DirectX and output.log, both of which apply to the Windows version only. Running via wine is slow, unsupported and only 32bit anyway. Get away from wine/playonlinux - there's a native Steam and KSP for GNU/Linux.

Confirmed blinking here, on Debian x86_64. Maybe best to simply disable this if on x64?

Crashes CKAN (latest release) with: Missing method CKAN.Registry::Installed() in assembly /home/steve/KSP_linux-1004-CKAN/ckan.exe, referenced in assembly /home/steve/KSP_linux-1004-CKAN/CKAN/Plugins/PartManagerPlugin.dll System.MissingMethodException: Method not found: 'CKAN.Registry.Installed'. at PartManagerPlugin.PartManagerUI.PartManagerUI_Load (System.Object sender, System.EventArgs e) [0x00000] in <filename unknown>:0

The executable is not in "/home/ricardo/Documentos/KSP/", as the error message states. Again: 'LC_ALL=C ./KSP.x86_64' must be run from the directory containing the KSP.x86_64 binary, Try /home/ricardo/Documentos/KSP/KSP_Linux_1.0.4. There is no "C:\" in *nix, there is only "/". Forget everything you know from Windows.

Edge highlighting is broken (or at least with regard to fglrx, says your log), is it turned off as it should be? You "tried do paste the full path of the KSP" into what, exactly? a console? What directory are you in when you execute that command: pwd If you are in a terminal/shell opened from the desktop menu etc. you'll probably be in /home/<username>, you want: cd <where KSP is installed> first. Or set "working directory" on your shortcut thingy / in a script. Funny things happen if you run KSP.x86[_64] from outside the installation directory, i.e. from home with full path to the executable.

Post you settings.cfg, or just the relevant bit: egrep 'CAMERA|SENS' settings.cfg. Again, but with instructions: Check your mouse polling rate, setting it (or having a mouse that defaults to) above 125Hz can cause issues with KSP. Also, what Desktop environment are you running?

Fun for a while, but it's no Total Annihilation. Meh, about what I expected.

I'll take a look if you upload to a non-obnoxious filehost... like Dropbox. It's usually a good idea to install mods one a few (or one) at a time for this reason, and... are all those mods rated for the KSP version you're running?