Kerbin-Destroying Ferram Physics

[Samniss Arandeen]

EDIT I run the Steam version in Kubuntu 13.10 with KDE 4.11.5

When I updated to 0.25, I deleted EVERYTHING. I used Steam to uninstall KSP and wiped out everything remaining, reinstalled KSP, and obtained fresh downloads of all my mods.

-Kerbal Engineer Redux

-KW Rocketry

-Deadly Reentry

-Kerbal Attachment System

-Kerbal Alarm Clock

-Ferram Aerospace Research

All mods updated to their latest releases.

But when I launched a plane, this happened:

The physics kick in, the plane falls through the floor and blows up the whole frickin planet. Oh, and the navball goes ballistic.

I uninstalled all mods one at a time, and I only managed a successful physics load once Ferram was out of the picture. To make sure, I reinstalled everything EXCEPT Ferram, and that also worked successfully. Taking the "failure due to aerodynamic stresses" in the flight results as a hint, I disabled aerodynamic failures in FAR and tried again. Same error. "Clean environment test", where I used only Ferram and ModuleManager 2.5.1, also produced the error.

This is what the Ferram-free modded install looked like once the physics loaded:

Player logs of modded stock aero and Ferram Aerospace are both provided here.

How to reproduce the error:

1.) Install FAR 0.14.2 in KSP 0.25.0.0

2.) Launch a plane. Any plane.

3.) Watch said plane fall through the runway, suicide-bombing the planet into submission the instant the physics load.

Edited October 14, 2014 by Samniss Arandeen
System information

[ferram4]

First, your logs are incomplete; they do not extend past the loading portion of the game.

Second, your reproduction steps are incomplete; I have followed these steps multiple times and have not seen anything like this. Your reproduction steps are missing crucial information, or else the bug is caused by another mod / change to your install.

[Boomerang]

Also, I started .25 with NEAR and ended up deleting it. In both cases, I would occasionally have the glitch of things clipping entirely too easily through the runway or launchpad upon loading. If I had to guess, I'd say that the glitch lies with a buggy new collision mesh for those two areas with the advent of destructible infrastructure, not FAR/NEAR.

And the FAR thread would be packed with angry people if this was in fact a FAR bug.

[Samniss Arandeen]

First, your logs are incomplete; they do not extend past the loading portion of the game.

Second, your reproduction steps are incomplete; I have followed these steps multiple times and have not seen anything like this. Your reproduction steps are missing crucial information, or else the bug is caused by another mod / change to your install.

My reproduction steps are complete and accurate to the best of my knowledge. That literally is all I have to do in order to cause the problem.

I reproduced the problem again just to get the logs again, though. Here it is.

[ferram4]

The log does have some "Look rotation vector is zero" lines that hint that something is going wrong, but it doesn't hint what.

I just made another install of KSP 0.25. I installed FAR as it is included in the 0.14.2 download. I did not experience any of the behavior you describe. Your reproduction steps are, therefore, incomplete.

[Samniss Arandeen]

The log does have some "Look rotation vector is zero" lines that hint that something is going wrong, but it doesn't hint what.

I just made another install of KSP 0.25. I installed FAR as it is included in the 0.14.2 download. I did not experience any of the behavior you describe. Your reproduction steps are, therefore, incomplete.

You and I both. I uninstalled KSP .25 through Steam. I went into my SteamApps directory and nuked everything that remained of the KSP directories. After a computer restart, I reinstalled .25, and ran it stock with no issues. I made a fresh download of FAR .14.2 off GitHub and installed it per the instructions with ModuleManager 2.5.0. The problem returned, instant blowing up and all.

I had a guess that the wheels were acting like struts in a Danny2462 video, so I performed an experiment. In the SPH I put a Mk. 1-2 Command Pod facing straight up, then launched it.

Before the physics kick in:

Hey, this doesn't look so bad

HOLY CRAP! I think I found the most hilarious bug ever. The instant the physics load the Command Pod gets punted into the sky, and things escalate quickly.

Obviously stock doesn't have this problem.

Again, I run x64 KSP .25 in Steam for Linux, Kubuntu 13.10, KDE 4.11.5. I can try the Windows version in Wine if you want me to.

[ferram4]

I seriously doubt it's a Linux issue, something that bad would also pop up in stock. Go ahead, try it anyway, maybe there's something deeply screwed up there and I just don't have that many linux users.

Try moving the KSP directory outside of Steam and run it without using Steam at all. As if it were just another program.

[Samniss Arandeen]

I am happy to report that KSP .25 with FAR .14.2 runs beautifully...so long as you don't use Steam to run it.

[ferram4]

...well. That provides an explanation. I just have no idea what's going on. I'll try to look into it.

Could you attempt seeing if the same behavior occurs in the 32-bit linux build through Steam as well?

Edited October 14, 2014 by ferram4

[Samniss Arandeen]

...well. That provides an explanation. I just have no idea what's going on. I'll try to look into it.

Could you attempt seeing if the same behavior occurs in the 32-bit linux build through Steam as well?

I don't know how to force Steam to launch the 32-bit version, but without Steam, the 32-bit build skips the "fall through the runway, blow up Kerbin" bit and immediately crashes to desktop once the physics load.

[ferram4]

O_o

Alright, can you post a log from that run?

[Samniss Arandeen]

You got it!

[ferram4]

Hunh, the last thing is a NaN exception. That's interesting, maybe it indicates something useful.

[Samniss Arandeen]

Hunh, the last thing is a NaN exception. That's interesting, maybe it indicates something useful.

What is a NaN exception? On one of my reproductions of the original error the surface and orbit indicators on the Navball read out NaN m/s.

[*Aqua*]

NaN = not a number

Not all values of a floating point number are interpreted as a number to indicated special circumstances.

0/0 -> NaN

∞ -> NaN

√-1 -> NaN

etc.

[ferram4]

Samniss, if you wanna give it a shot, I made some changes in the FAR dev build that might help. Just go and download the repo, nuke your old FAR folder, and replace it with the one in the repo's GameData folder.

[skeevy]

I run FAR with quite a bit of mods on Mint 17 (Ubuntu 14.04) and I've never experienced this issue. Just letting Ferram4 know that FAR does indeed work on x64 Linux.

Core2Quad Q6600 (yea, it sucks)

8GB DDR2

AMD R7 260x with 14.9 Driver

XFCE 4.11

Kernel 3.15.10-031510-lowlatency from Ubuntu Trusty (14.10)

Xorg-Edgers for updated X goodness

KSP from Steam launched with the below script

To the OP: We had another linux user having issues playing stock, unmodded KSP on Ubuntu 13.10. Updating to 14.04 fixed it. Ubuntu 13.10 is known for being horrible with Steam games, and gaming in general. It's also no longer supported at all, which is reason enough to warrant an update. This guide should help you out with updating to 14.10 Kubuntu.

#!/bin/sh

LC_ALL=C LD_PRELOAD="libpthread.so.0 libGL.so.1"
[B]__GL_THREADED_OPTIMIZATIONS=1 [/B]
exec taskset -c 2-3 ./KSP.x86_64

that bold line is really only for Nvidia GPU's, but it doesn't do anything bad if it's there.

taskset -c 2-3 makes KSP run with my 3rd and 4th CPU cores

EDIT: I love that commit. Seems very KSP appropriate.

Edited October 15, 2014 by skeevy

[zuuhis79]

Hello.

I have been having this same problem with 32-bit linux version of KSP (default version Steam launches), only installed mod being FAR. 64-bit version works perfectly. I run it in Ubuntu 14.04 and FAR version is 14.3. I have tried to reinstall everything on a fresh install of game.

Besides already described problems, my ship sometimes disintegrates on launchpad when physics kick in and my plane has only a few parts. Or if my ship has only a command pod, and I tip it on it's side, it flies right out of kerbol system, it's speed being something like a billion m/s. The game might also crash.

Here is some log of the example launch, when command pod exploded right after physics kicking in:

Kerbal Space Program - 0.25.0.0 (LinuxPlayer) Steam

OS: Linux 3.13 Ubuntu 14.04 64bit

CPU: Intel® Core i5-4300M CPU @ 2.60GHz (4)

RAM: 7891

GPU: Mesa DRI Intel® Haswell Mobile x86/MMX/SSE2 (256MB)

SM: 30 (OpenGL 3.0 [3.0 Mesa 10.1.3])

RT Formats: ARGB32, ARGBHalf, RGB565, ARGB4444, ARGB1555, Default, DefaultHDR, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8

[WRN 16:58:07.793] [HighLogic]: =========================== Scene Change : From SPACECENTER to FLIGHT (Async) =====================

[LOG 16:58:08.395] FAR: save AG actionGroupSpoiler as Brakes

[LOG 16:58:08.395] FAR: save AG actionGroupIncreaseFlapDeflection as None

[LOG 16:58:08.396] FAR: save AG actionGroupDecreaseFlapDeflection as None

[LOG 16:58:09.294] AddonLoader: Instantiating addon 'FARGlobalControlFlightObject' from assembly 'FerramAerospaceResearch'

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing bool

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing bool

[LOG 16:58:09.297] Parsing int

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing int

[LOG 16:58:09.297] Parsing int

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing string

[LOG 16:58:09.297] Parsing rect

[LOG 16:58:09.323] ------------------- initializing flight mode... ------------------

[LOG 16:58:09.328] Target vessel index: 1 vessel count: 2

[LOG 16:58:09.330] [FLIGHT GLOBALS]: Switching To Vessel Untitled Space Craft ----------------------

[LOG 16:58:09.331] setting new dominant body: Kerbin

FlightGlobals.mainBody: Kerbin

[LOG 16:58:09.332] Reference Frame: Rotating

[LOG 16:58:09.358] [untitled Space Craft]: landed - waiting for ground contact to resume physics...

[LOG 16:58:09.360] Camera Mode: AUTO

[LOG 16:58:09.370] stage manager resuming...

[LOG 16:58:10.759] all systems started

[LOG 16:58:10.902] [scenarioDestructibles]: Started. 39 objects registered

[LOG 16:58:10.919] [VesselSpawner]: No new objects this time. (Odds are 1:2)

[LOG 16:58:10.995] [PlanetariumCamera]: Focus: Untitled Space Craft

[LOG 16:58:11.361] Flight State Captured

[LOG 16:58:11.361] Saving Achievements Tree...

[LOG 16:58:11.365] Game State Saved as persistent

[LOG 16:58:13.370] [untitled Space Craft]: ground contact! - error: 0.019m

[LOG 16:58:13.370] Unpacking Untitled Space Craft

[LOG 16:58:13.393] FAR Raycast mask: 557059 557063

[LOG 16:58:13.410] Stagnation Pressure Coefficient Curve Initialized

[LOG 16:58:13.414] [Progress Node Reached]: AltitudeRecord

[LOG 16:58:25.601] [00:00:00]: Command Pod Mk1 collided into the surface.

[LOG 16:58:25.602] mk1pod (Untitled Space Craft) Exploded!! - blast awesomeness: 0.5

[LOG 16:58:25.604] [mk1pod (Untitled Space Craft)]: Deactivated

[LOG 16:58:25.620] Added -9.999606 (-10) reputation: 'VesselLoss'.

[LOG 16:58:25.621] [00:00:00]: Jebediah Kerman was killed.

[LOG 16:58:25.622] Reference Frame: Inertial

[LOG 16:58:25.773] 1 explosions created.

[LOG 16:58:25.854] Look rotation viewing vector is zero

...about 100 lines of same notification and a few others...

[NathanKell]

Try launching directly, not using Steam.

[zuuhis79]

Well, I run it now in 64 bit, so not a problem for me. I haven't managed to run the 32-bit version without steam, don't know why.

I thought to post my problem just to report, that it is not a problem of only one player. It might also be a bug in the 32-bit linux version of KSP that occurs only with FAR.

How much of NEAR and FAR code is identical? Maybe I could try this with NEAR and see if it has the same problem. Or is this type of behaviour so marginal, that there is no point of researching it any further?

[ferram4]

NEAR and FAR are virtually identical in the code that applies forces, and if the error is in there it should occur for both.

You can also try using the dev build in the github repo to see if that fixes it, and I do need people who actually suffer from the problem to test it, since I haven't been able to cause it at all.

[steve_v]

Well that is pretty wierd, I can't reproduce any of this on either the 64 or 32 bit builds. I am, however, not running steam.

What command-line & environment does steam use to launch KSP?

I haven't managed to run the 32-bit version without steam, don't know why.

How does it fail?

You're 64bit native right? just guessing here, but I'm thinking maybe you don't have all the 32bit libraries installed, so steam is loading it's own copies from the steam 'runtime'... which may well be where the problem lies.

EDIT: looks like I've been beaten to it

Steam does preload old libs, very old - from ubuntu *12*.

Edited October 19, 2014 by steve_v

[zuuhis79]

Ok, that explains why the 32-bit version was not running without steam. I have a 64-bit version of ubuntu. I didn't have any other than default setting of libraries. I managed to find some hints with google how to find out which libraries are missing, and installed them. Still I don't know if they are the proper versions of those libraries, but the game runs in 32-bit now.

The problem itself still persists, when running the game without steam in 32-bit. The moment problem occurs, KSP generates these two lines to the log file:

[LOG 23:24:13.315] [untitled Space Craft]: ground contact! - error: 0.019m

[LOG 23:24:13.315] Unpacking Untitled Space Craft

After that my ship explodes.

I tried NEAR also. Everything works fine, but it generates same log lines on ground contact. Ship stays in one piece, and it flies. There are also a lot of lines in log that says "An invalid object handle was used".

Is there a way to update all those libraries with one or a few commands, there are quite a lot of them? I don't know if those are old versions of them.

[ferram4]

zuuhis, try this then: load up FAR, clear the runway and launch pad, and launch a vehicle that does not have a command pod or probe core. Basically, nothing for it to command with. See what happens then.

[zuuhis79]

Ok. I'll try it tomorrow, I don't have access to my linux machine today.