Arch Linux ksp 1.1 UI crash

[buljcron]

an hour ago I update my game to the 1.1 via steam, and now half of the UI include setting are invisible

I find some one have exact same problem as I have http://imgur.com/a/L4cj8

but unfortunately I didnt find his solution

I try reinstall whole game, but no luck.

any ideas?

[Squelch]

Hello there,

Could you attach your logs and hardware specification please? Certain graphics drivers are known for this, so please also let us know which you use?

[buljcron]

5 hours ago, Squelch said:

Hello there,

Could you attach your logs and hardware specification please? Certain graphics drivers are known for this, so please also let us know which you use?

Im using a i3-4160, no Graphics card， 8g ram

graphics driver is Intel Corporation 4th Generation Core Processor Family Integrated Graphics Controller i915

for log there are 2k line in the log file so I only cut out these line which have a "err" at front

[ERR 22:07:55.175] ConvexHullBuilder: convex hull has more than 255 polygons!
[ERR 22:07:55.175] Gu::ConvexMesh::loadConvexHull: convex hull init failed! Try to use the PxConvexFlag::eINFLATE_CONVEX flag. (see PxToolkit::createConvexMeshSafe)
[ERR 22:07:55.187] ConvexHullBuilder: convex hull has more than 255 polygons!
[ERR 22:07:55.187] Gu::ConvexMesh::loadConvexHull: convex hull init failed! Try to use the PxConvexFlag::eINFLATE_CONVEX flag. (see PxToolkit::createConvexMeshSafe)
[ERR 22:07:56.421] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:56.421] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.046] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.046] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.082] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.082] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.090] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.090] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.106] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.106] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.130] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.130] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.147] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.147] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.160] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.160] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.191] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.191] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.226] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.226] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.260] WheelCollider requires an attached Rigidbody to function.
[ERR 22:07:57.260] WheelCollider requires an attached Rigidbody to function.
[ERR 22:08:14.007] ConvexHullBuilder: convex hull has more than 255 polygons!
[ERR 22:08:14.008] Gu::ConvexMesh::loadConvexHull: convex hull init failed! Try to use the PxConvexFlag::eINFLATE_CONVEX flag. (see PxToolkit::createConvexMeshSafe)
[ERR 22:08:14.017] ConvexHullBuilder: convex hull has more than 255 polygons!
[ERR 22:08:14.017] Gu::ConvexMesh::loadConvexHull: convex hull init failed! Try to use the PxConvexFlag::eINFLATE_CONVEX flag. (see PxToolkit::createConvexMeshSafe)
[ERR 22:08:14.037] ConvexHullBuilder: convex hull has more than 255 polygons!
[ERR 22:08:14.037] Gu::ConvexMesh::loadConvexHull: convex hull init failed! Try to use the PxConvexFlag::eINFLATE_CONVEX flag. (see PxToolkit::createConvexMeshSafe)
[ERR 22:08:14.051] ConvexHullBuilder: convex hull has more than 255 polygons!
[ERR 22:08:14.051] Gu::ConvexMesh::loadConvexHull: convex hull init failed! Try to use the PxConvexFlag::eINFLATE_CONVEX flag. (see PxToolkit::createConvexMeshSafe)
[ERR 22:08:16.960] HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform!
[ERR 22:08:18.180] HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform!
[ERR 22:08:18.185] HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform!
[ERR 22:08:23.189] HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform!
[ERR 22:08:34.665] HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform!
[ERR 22:08:39.916] HighlightingSystem : Highlighting System has been disabled due to unsupported Unity features on the current platform!
 

[soulsource]

This is a known bug. There are currently two known workarounds, both with their own ugliness:

• You can edit settings.cfg in a text editor. Enable fullscreen mode and set a resolution lower than the native resolution of your screen.
• You can launch KSP with the -force-glcore command line parameter. This will allow KSP to run in your screen's native resolution with working menus, but this option will cause graphics glitches regarding shadows and in some menus. In Steam this can be done by right clicking the entry in the Steam library, open properties, and pressing the "set launch options" button. In the dialogue that pops up, you can enter "%command% -force-glcore" (without the quotation marks, of course).

Edit: It seems that the worst shadow-glitches that appear with -force-glcore can be made invisible by setting shadow cascades to zero. I'm aware that this makes shadows pretty rough, but I prefer rough shadows over shadows of things that aren't even there.

Edited April 20, 2016 by soulsource

[Squelch]

Thank you for the information.

It is indeed, and the reason why I asked for further information rather than making assumptions. It is an unfortunate reality of Linux support - in general - and we tried very hard to fix this issue for 1.1. A further upgrade to Unity3D promises to help with this somewhat, but the real results won't be known until that occurs. If the workarounds allow KSP to be played in the meantime, then please mark this as resolved so others may benefit?

TLDR: We are aware of the problems with some driver and hardware combinations on Linux. Partial workarounds are available.

[Edit to add]

Add the -force-glcore to the start up parameters on Steam, or to the commandline otherwise.

 

Edited April 20, 2016 by Squelch
Complete answer added

[buljcron]

54 minutes ago, Squelch said:

Thank you for the information.

It is indeed, and the reason why I asked for further information rather than making assumptions. It is an unfortunate reality of Linux support - in general - and we tried very hard to fix this issue for 1.1. A further upgrade to Unity3D promises to help with this somewhat, but the real results won't be known until that occurs. If the workarounds allow KSP to be played in the meantime, then please mark this as resolved so others may benefit?

TLDR: We are aware of the problems with some driver and hardware combinations on Linux. Partial workarounds are available.

sorry but how can I mark it as solved?

[Red Iron Crown]

2 minutes ago, buljcron said:

sorry but how can I mark it as solved?

Click the checkmark in a circle to the left of the best/most helpful answer.