Jump to content

Kerbin-Destroying Ferram Physics

Samniss Arandeen
 Share

Recommended Posts

zuuhis79

zuuhis79

Posted
Posted

I tried it today with FAR, and my spaceship didn't explode this time. Instead all the joints fail at the same time when ship touches ground (or physics kick in), and I have a bunch of separate parts on launchpad. They fall quite slowly, so they are not exploding. Maybe NEAR works because it won't cause disintegration or something like that.

Same log lines generate to log file than before. Still a lot of lines that say "An invalid object handle was used".

Link to comment
Share on other sites
zuuhis79

zuuhis79

Posted
Posted

Sorry, I didn't know there was another log file... here is an example of a launch from the moment ship hits ground. It flew right out of kerbol system...

[untitled Space Craft]: Ready to Launch - waiting to start physics...

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Crewmember Bill Kerman assigned to Command Pod Mk1, seat # 0 (crew seat index: 0)

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[FLIGHT GLOBALS]: Switching To Vessel Untitled Space Craft ----------------------

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

setting new dominant body: Kerbin

FlightGlobals.mainBody: Kerbin

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Reference Frame: Rotating

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

stage manager resuming...

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Vessel assembly complete!

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

stage manager starting...

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

all systems started

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

An invalid object handle was used.

(Filename: Line: 311)

...many same lines...

An invalid object handle was used.

(Filename: Line: 311)

[scenarioDestructibles]: Started. 39 objects registered

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

An invalid object handle was used.

(Filename: Line: 311)

[Progress Node Reached]: AltitudeRecord

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[PlanetariumCamera]: Focus: Untitled Space Craft

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Flight State Captured

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Saving Achievements Tree...

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Saving Achievements Tree...

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Game State Saved as persistent

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[untitled Space Craft]: ground contact! - error: 0.038m

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Unpacking Untitled Space Craft

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Stagnation Pressure Coefficient Curve Initialized

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[00:00:00]: Structural failure on linkage between LV-T30 Liquid Fuel Engine and FL-T200 Fuel Tank.

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[00:00:00]: Structural failure on linkage between RT-10 Solid Fuel Booster and FL-T200 Fuel Tank.

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[00:00:00]: RT-10 Solid Fuel Booster collided into the surface.

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

solidBooster Exploded!! - blast awesomeness: 0.5

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[solidBooster]: Deactivated

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

recalculating orbit for mk1pod: Kerbin

rPos: [8028545996171.27, 8127333666594.5, 1376809466664.14] rVel: [197176009424797, 201513691512688, 34214472843264] |284001367446886|

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

recalculated orbit for mk1pod: the Sun

rPos: [8036075472835.66, 8116086643683.51, 1376809466664.14] rVel: [197173645277444, 34214472843264, 201516026936881] |284001383194455|

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[Progress Node Reached]: Escape

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[Progress Node Complete]: Escape

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[Progress Node Reached]: Flyby

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[Progress Node Reached]: Sun

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

[Progress Node Complete]: Flyby

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

recalculating orbit for fuelTankSmall: Kerbin

rPos: [1604464429226.37, -721877971753.883, 215806400761.608] rVel: [26239205388016.7, -35129966618928.8, 1012521762816] |43859271019497.8|

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

recalculated orbit for fuelTankSmall: the Sun

rPos: [1612041188936.65, -733171703019.792, 215806400761.608] rVel: [26239205393011.6, 1012521762816, -35129966612534.6] |43859271017364.4|

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

setting new dominant body: the Sun

FlightGlobals.mainBody: Kerbin

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Vessel mk1pod velocity resumed. Reference body: Sun vel: [197173645277444, 34214472843264, 201516026936881]

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Vessel fuelTankSmall velocity resumed. Reference body: Sun vel: [26239205393011.6, 1012521762816, -35129966612534.6]

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Vessel liquidEngine velocity resumed. Reference body: Sun vel: [-82392152801280, 16899112960000, -87526282887168]

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Vessel solidBooster velocity resumed. Reference body: Sun vel: [522993839112192, 2953131065344, -152661743632384]

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Look rotation viewing vector is zero

(Filename: Line: 57)

An invalid object handle was used.

(Filename: Line: 311)

An invalid object handle was used.

(Filename: Line: 311)

An invalid object handle was used.

(Filename: Line: 311)

An invalid object handle was used.

(Filename: Line: 311)

An invalid object handle was used.

(Filename: Line: 311)

An invalid object handle was used.

(Filename: Line: 311)

1 explosions created.

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

Look rotation viewing vector is zero

(Filename: Line: 57)

...many same lines...

Look rotation viewing vector is zero

(Filename: Line: 57)

Kerbin: Resetting

(Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

An invalid object handle was used.

(Filename: Line: 311)

Link to comment
Share on other sites
skeevy

skeevy

Posted
Posted
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.

See here for instructions on figuring out the 32bit libs needed. In that link, the libs go 64bit then 32bit (sorry, it's a bit hard to tell what's what because I was lazy and did * commands). Before all of that, run, as root, "apt-get update && apt-get upgrade" to make sure your system is updated. Then follow the instructions in the link; or you can try what I did which is just fire up Synaptic, search for "lib32", and install what's missing when you ldd the 32bit executable.

I used to be a big Mint 17 (Ubuntu 14.04) supporter, but recent updates to various projects make Ubuntu 14.04 and lower not worth using (especially if you have an AMD GPU). You really want to be on a distro like Arch, Manjaro, Sabayon...something bleeding edge with decent Steam support. Manjaro is the easiest of those three, what I run, and is based on snapshots of the Arch repos (it's Arch's Ubuntu in a sense; Ubuntu is based on Debian Sid snapshots). If you don't wanna leave the Ubuntu family, you should be running 14.10, period. Trust me when I say that KSP greatly benefits from the updated kernels, xorg, mesa, and more that you just can't get with Ubuntu 14.04.

Ferram4 -- FAR runs just fine on Linux provided it's up-to-date and KSP doesn't get ran directly from Steam (unless the user is using something like Manjaro's steam-native package; it replaces Steam libs with native system libs). I haven't ran NEAR, but I'm thinking about switching over to it since I don't really use FAR's menus or advanced features and hoping that I might save some CPU cycles since I wouldn't have to process FAR's stuff I'm not really using. Would changing from FAR to NEAR matter that much or is the difference negligible for CPU cycles used between the two?

Link to comment
Share on other sites
zuuhis79

zuuhis79

Posted
Posted

I tried those updates and installations, and they didn't change the behaviour of the game.

Other thing I tried was to install exactly same ubuntu with exactly same installations and upgrades to another computer to see if it behaves similar. It worked perfectly, no problems whasoever. So this might be a hardware issue (or a driver that relates to different hardware). Even though the game itself worked like a charm, the log it generated looked quite similar to the one I posted earlier. So not much difference in there.

I'll stick to the 64-bit version, or I might try that 14.10 at some point in the near future. Thank you all for assistance!

Link to comment
Share on other sites
ferram4

ferram4

Posted
Posted

@skeevy: Most of the GUI stuff doesn't require much processor power at all, so if you're not using that, you won't notice. If you like the difference in aerodynamics when you change Mach number, you're probably going to miss them if you switch from FAR to NEAR. Also, a lot of the wing shape effects are removed as well, which means a lot of your designs will fly a lot differently. It'll be less computationally intensive, sure, but it'll mostly be because the physics are differnet.

@zuuhis79: Np. I guess I'll just chalk this up to outdated Linux libs and call it a day.

Link to comment
Share on other sites
skeevy

skeevy

Posted
Posted (edited)

@Zuuhis79: One last thing you can try with 14.04 Ubuntu is to use the Xorg-Edgers PPA and a newer kernel. Using the two of those should help.

3.17.1 Kernel install instructions for 14.04

Xorg-Edgers PPA

Install the kernel, reboot, add the PPA, do an apt-get update followed by apt-get upgrade, reboot, play KSP.

This is exactly what I did back when I was using Ubuntu and it does help. Those two combined contain your GPU driver.

Link to 3.17 intel-drm-next Ubuntu kernel Instructions are the same as the other 3.17.1 kernel above, only different wget URLs. Never used that kernel, but you have an Intel GPU so it's worth a shot.

EDIT: Post back if you need those wget commands for the drm-next kernel.

@Ferram4: I'll just stick with FAR then. Thanks.

Edited by skeevy
Link to comment
Share on other sites
  • 1 month later...
Deddryk

Deddryk

Posted
Posted

If it helps, I experienced this exact issue.

Kerbal Space Program - 0.25.0.0 (LinuxPlayer) Steam

OS: Linux 3.13 Ubuntu 14.04 64bit

CPU: Intel® Core i5-3570K CPU @ 3.40GHz (4)

RAM: 15932

GPU: GeForce GTX 770/PCIe/SSE2 (2048MB)

SM: 30 (OpenGL 4.4 [4.4.0 NVIDIA 331.38])

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

Log of a flight is here. This particular one has FAR and Kerbal Joint Reinforcement installed.

Steps: Launch from steam

new sandbox game

vab, launch only a command pod

It gets launched into the atmosphere immediately.

The problem goes away in both the 32 bit and 64 bit versions if launched without steam.

The problem also goes away if you follow the steps at http://forum.kerbalspaceprogram.com/threads/86488-How-to-make-Steam-run-64-bit to force steam to run the 64 bit version.

Link to comment
Share on other sites
This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to topic listing
×
×
  • Create New...