Search the Community

Showing results for tags 'linux'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General
    • Announcements
    • The Daily Kerbal
  • General KSP
    • KSP Discussion
    • Suggestions & Development Discussion
    • Challenges & Mission ideas
    • The Spacecraft Exchange
    • KSP Fan Works
  • Gameplay and Technical Support
    • Gameplay Questions and Tutorials
    • Technical Support (PC, unmodded installs)
    • Technical Support (PC, modded installs)
    • Technical Support (PlayStation 4, XBox One)
  • Add-ons
    • Add-on Discussions
    • Add-on Releases
    • Add-on Development
  • Community
    • Welcome Aboard
    • Science & Spaceflight
    • Kerbal Network
    • The Lounge
  • International
    • International
  • KerbalEDU Forums
    • KerbalEDU
    • KerbalEDU Website
  • KSP Pre-release
    • 1.2.9 Pre-release Branch
    • 1.2.9 Pre-release Modding Discussions
    • 1.2.9 Pre-release Bug Tracker


  • Developer Articles

Found 47 results

  1. Hi there. I've noticed that none of my batteries in game have any mass. They are all listed as 0.0, even the 1K rechargable I am running KSP 1.3 in Ubuntu Linux My game was started in KSP 1.22 The mods I am running are: Kerbal Engineer Redux Maneuver Node Evolved X Science Kerbal Alarm Clock Lab Upgrade Mod - six Kerbals instead of two I noticed the issue before I installed KAC and the Lab upgrade I can find no setting in the cheat menu that would be causing massless batteries nor in the game difficulty settings. Does anyone have any idea what might be causing this? Actually - I have just worked out part of the issue - The batteries DO have mass as the KER registers an increase in mass each time I add a battery. However the interface is telling me they are all 0 mass ( at least I don't feel ultra cheaty now and it's just an interface bug )
  2. I have been playing through a career game started in KSP 1.2.x After the 1.3 update, Kerbal names no longer appear in the text. Instead odd symbols are present which I guess are in the source file and are supposed to be replaced at run-time. All the Kerbals are now named: "<<1^n>>" That's not a weird code, that's the name as it appears on screen. In addition there multiple choice substitutions that appear such as: "Ferry <<n:1[/%d]>> <<n:1[a VIP]/tourists]>> safely to <<n:3[destination/destinations/destinations]>><<n:4[./and back./ and back.]>>" for contract text. Looking in KSP.log I see the related error message (long paths have been shortened to $KSP_ROOT): [ERR 01:28:04.883] Couldn't open $KSP_ROOT/KSP_Data/Plugins/x86/, error: /usr/lib/i386-linux-gnu/ version `CXXABI_1.3.8' not found (required by $KSP_ROOT/KSP_Data/Plugins/x86/ I gotta say, it's pretty impressive that the game is still playable even when a shared object flat out fails to load. Nice work Squad! Two questions: * Does anyone know which version of libstdc++ implements the ABI listed above? * Is there any reason that the 32-bit version of the game should be launching instead of the 64-bit version when both are present? I have screen shots if needed, thanks for the help.
  3. Current version: 2.3. License - GPLv3+ Description Based upon known launch options of the Kerbal Space Program, I have created a small bash script. Well, it was small initially... It is not a GUI application on purpose - to keep it simple as possible and to allow integration in existing launchers (Steam, GOG Galaxy etc). How to install: Scroll down to the link, save and paste contents into new file, rename it to "" and make it executable; Then 1. Place the script in the same directory as KSP binary and run. Or, 2. Change the shortcuts/desktop file, usually pointing to KSP - to this script instead. Or, 3. If you use GOG offline installer, in "" replace strings "KSP.x86_64" and "KSP.x86", with "" For help: run the script with any parameter ("--help" or similar) How to modify settings: run help, edit the script, change the variable values, save. What script currently allows: - debug/dry run mode - force LC_C to fix disappearing saves/forgetting settings - turn vsync on/off (nvidia and mesa/opensource radeon or intel) - force fullscreen or any video resolution at any time - specify opengl / gles settings - change R600_DEBUG variable - change Mesa options - start gallium benchmark mode - protect against memory issues - support for disabling the (massive KSP) log* and/or automatically rotating it - properly waits for KSP to end, even if it segfaults basically all known options that Linux users had to specify manually have been put in one convenient place. * you NEED a log for any kind of support question! Planned (not yet here): - checking how "-force-gfx-st" differs from existing "-force-gfx-direct" - "-adapter X" launch option Current version: previous version (2.2): previous version (2.0): Warning if you use the "download" button on, instead of copy-pasting raw contents into new text file, then you may encounter the error: "/bin/bash^M: bad interpreter: No such file or directory" To fix it, open this script in text editor and change the line end encodings from Windows to Unix. This done by "", I have no control over this. Heads up of the Linux problems I am aware of, being Linux player myself: - KSP runs hot on GPU Use either nvidia settings panel (for proprietary Nvidia) or radeon profile tool (for AMD, ubuntu PPA) to limit the performance mode of the GPU. In case of Radeon, switch it to manual and low. From my observations, only simulations in atmosphere require a lot of GPU. In VAB/SPH the GPU is perfectly fine in manual low-power mode, consuming 10-20% energy and running cool. Since KSP supports window switching (alt-tab), you can easily adjust performance as you need it. - KSP does not remember settings and always starts in window mode This is because LC_ALL=C is required, if the system locale is NOT us_US, because Unity uses comma delimiter set by locale and some locales have "," instead of "." Solution: KSP_unity_forceLC="on", which is default in my script - KSP starts with window of weird size This is because Unity fails to get screen size from window manager. This seem to be resolved with 1.2+. Solution: KSP_ksp_cleanprefs="on" which is default and will remove Unity's "prefs", and you can force the settings for one launch with KSP_unity_forceX, KSP_unity_forceY, KSP_unity_fullscreen variables. - KSP sometimes at loading crashes Xorg session, booting to login Solution: KSP_ksp_protect="on" , which is default in my script - KSP starts with black screen, noticed in Mesa 11 Solution: KSP_unity_glcore to "on" or "33" (or higher value, if your GL library supports it) - Bop and Minmus have terrain glitches, noticed in Mesa 12 Solution: KSP_unity_glcore to "on" or "41" - RasterPropMonitor shows has pink lines instead of IVA panels This is result of having "glcore" enabled, as it breaks the shaders. Here is the bug report. This has not been fixed. - KSP sometimes crashes I read about this bug being present on Intel opensource drivers. To solve, disable antialiasing in KSP settings. - VAB/SPH floor markers are weird (gradient - AMD, covered in flickering noise - Nvidia). This is connected with shader rendering and OpenGL library in the system. On AMD / Mesa 17, the system also freezes at random time and its connected with issue below. On AMD / Catalyst(depricated driver), its reported to be fixed by disabling PPFX edge shaders in settings. On Nvidia (proprietary driver), is reported to happen with driver 378.13 and later. Its possible to workaround this issue by installing Hangar Extender mod. - KSP freezes the system completely Freeze happens at random point. The freeze happens earlier, if there are Mods that require a lot of GPU work. After many attempts I have traced this issue to Mesa 17+. Solution: If you have OIBAF or PADOKA Mesa installed, try removing them and downgrading to "hwe" Mesa. This is likely DRI3 issue, but no option I know helped, its somewhere in the Mesa userspace stack. Upgrading kernel does not help. If this interests anyone, I am using x64 Kernel 4.12 and KDE Neon (Ubuntu 16.04 LTS-based) with "hwe" packages for Xorg and Mesa. For driver, I use opensource radeon driver, running with R9 280. Enjoy!!
  4. The white floor markings in SPH & VAB appear pixelated and they flicker madly. Is anyone else having the same issue?
  5. Hello guys, I'm a new user to the fourm. I've been playing KSP for quite awhile on Windows, and it works great, but when I try to run on Ubuntu with limited Mods, the game crashes half-way through loading. I will post my KSP.log below. [snip]
  6. Yesterday I wanted to launch KSP but nothing happened. Because there was no output, I tryed it from the terminal and got this output: Importing game controller configs Abgebrochen (Speicherabzug geschrieben)Set current directory to /home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program Found path: /home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/tobias/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 4 screens displaymanager screen (0)(DVI-D-0): 1600 x 1200 displaymanager screen (1)(DVI-I-0): 1280 x 1024 Using libudev for joystick management Importing game controller configs Aborted (core dumped) Please help. PS: My OS is Kubuntu 16.04 LTS 64-bit
  7. Running a brand new Steam install of KSP. Starting the game from the console shows: Set current directory to /home/greg Found path: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 6 screens displaymanager screen (0)(DisplayPort-0): 1680 x 1050 displaymanager screen (1)(DVI-0): 1600 x 1200 Using libudev for joystick management Importing game controller configs Aborted (core dumped) Player.log shows: Stacktrace: Native stacktrace: /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/ [0x7fae983fb772] /home/greg/.steam/steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/ [0x7fae9839e8e4] /lib/x86_64-linux-gnu/ [0x7fae9dcb7630] /usr/lib/x86_64-linux-gnu/ [0x7fae8df39f50] /lib/x86_64-linux-gnu/ [0x7fae9c4a72e0] /lib/x86_64-linux-gnu/ [0x7fae9c4a733a] /lib/x86_64-linux-gnu/ [0x7fae9c48d3f8] ./KSP.x86_64() [0x46f695] Debug info from gdb: ================================================================= Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. ================================================================= In dmesg I get these: [12780.399329] show_signal_msg: 24 callbacks suppressed [12780.399334] steamwebhelper[3171]: segfault at 4c ip 000055688ae25a54 sp 00007f3a3765f940 error 6 in steamwebhelper[55688adeb000+285000] [12780.489185] Chrome_ChildThr[1707]: segfault at 0 ip 000055d584dc0b11 sp 00007f1893afe370 error 6 in plugin-container[55d584dbc000+1a000] [13149.862363] KSP.x86_64[4882]: segfault at 7f711044bf78 ip 00007f7105f39f50 sp 00007fffd77d7610 error 4 in[7f7105825000+24f9000] [13309.725708] steamwebhelper[3746]: segfault at 4c ip 0000561b31a0fa54 sp 00007f62e1fc7940 error 6 in steamwebhelper[561b319d5000+285000] Any ideas?
  8. I'm on Linux: $ uname -a Linux metric 4.8.0-41-generic #44-Ubuntu SMP Fri Mar 3 15:27:17 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux This behaviour occurs from both the 32- and 64-bit launchers. The game is stock, from Steam, with no modifications at all. The game starts, some logs are generated, but the output is a black screen. Not even the loading screen appears. The program hangs like this until either terminated, or after a minute or two at which point it silently dies on its own. Unity Log $ cat ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log ../common/pipes.cpp (769) : Assertion Failed: fatal stalled cross-thread pipe ../common/pipes.cpp (769) : Fatal assert failed: ../common/pipes.cpp, line 769. Application exiting. Assert( Assertion Failed: fatal stalled cross-thread pipe ):../common/pipes.cpp:769 _ExitOnFatalAssert crash_20170319164726_2.dmp[6854]: Uploading dump (out-of-process) /tmp/dumps/crash_20170319164726_2.dmp crash_20170319164726_2.dmp[6854]: Finished uploading minidump (out-of-process): success = no crash_20170319164726_2.dmp[6854]: error: cannot open shared object file: No such file or directory crash_20170319164726_2.dmp[6854]: file ''/tmp/dumps/crash_20170319164726_2.dmp'', upload no: '' cannot open shared object file: No such file or directory'' _polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_square GL_NV_light_max_exponent GL_NV_texgen_reflection GL_NV_texture_env_combine4 GL_S3_s3tc GL_SUN_multi_draw_arrays GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_EXT_framebuffer_object GL_EXT_texture_compression_s3tc GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_MESA_window_pos GL_NV_packed_depth_stencil GL_NV_texture_rectangle GL_ARB_depth_texture GL_ARB_occlusion_query GL_ARB_shadow GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_mirrored_repeat GL_ARB_window_pos GL_ATI_fragment_shader GL_EXT_stencil_two_side GL_EXT_texture_cube_map GL_NV_depth_clamp GL_NV_fog_distance GL_APPLE_packed_pixels GL_APPLE_vertex_array_object GL_ARB_draw_buffers GL_ARB_fragment_program GL_ARB_fragment_shader GL_ARB_shader_objects GL_ARB_vertex_program GL_ARB_vertex_shader GL_ATI_draw_buffers GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_EXT_depth_bounds_test GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_MESA_pack_invert GL_NV_primitive_restart GL_ARB_depth_clamp GL_ARB_fragment_program_shadow GL_ARB_half_float_pixel GL_ARB_occlusion_query2 GL_ARB_point_sprite GL_ARB_shading_language_100 GL_ARB_sync GL_ARB_texture_non_power_of_two GL_ARB_vertex_buffer_object GL_ATI_blend_equation_separate GL_EXT_blend_equation_separate GL_OES_read_format GL_ARB_color_buffer_float GL_ARB_pixel_buffer_object GL_ARB_texture_compression_rgtc GL_ARB_texture_float GL_ARB_texture_rectangle GL_ATI_texture_compression_3dc GL_EXT_packed_float GL_EXT_pixel_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_rgtc GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_ARB_framebuffer_object GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_packed_depth_stencil GL_ARB_vertex_array_object GL_ATI_separate_stencil GL_ATI_texture_mirror_once GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_gpu_program_parameters GL_EXT_texture_array GL_EXT_texture_compression_latc GL_EXT_texture_integer GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_OES_EGL_image GL_AMD_performance_monitor GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_draw_instanced GL_ARB_half_float_vertex GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_texture_rg GL_ARB_texture_swizzle GL_ARB_vertex_array_bgra GL_EXT_texture_swizzle GL_EXT_vertex_array_bgra GL_NV_conditional_render GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_ARB_ES2_compatibility GL_ARB_blend_func_extended GL_ARB_debug_output GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_explicit_attrib_location GL_ARB_fragment_coord_conventions GL_ARB_provoking_vertex GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_shader_stencil_export GL_ARB_shader_texture_lod GL_ARB_texture_cube_map_array GL_ARB_texture_gather GL_ARB_texture_multisample GL_ARB_texture_query_lod GL_ARB_texture_rgb10_a2ui GL_ARB_uniform_buffer_object GL_ARB_vertex_type_2_10_10_10_rev GL_ATI_meminfo GL_EXT_provoking_vertex GL_EXT_texture_snorm GL_MESA_texture_signed_rgba GL_NV_texture_barrier GL_ARB_get_program_binary GL_ARB_robustness GL_ARB_separate_shader_objects GL_ARB_shader_bit_encoding GL_ARB_shader_precision GL_ARB_texture_compression_bptc GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_NV_vdpau_interop GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ARB_base_instance GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_internalformat_query GL_ARB_map_buffer_alignment GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_texture_storage GL_ARB_transform_feedback_instanced GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_transform_feedback GL_AMD_shader_trinary_minmax GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_clear_buffer_object GL_ARB_copy_image GL_ARB_explicit_uniform_location GL_ARB_framebuffer_no_attachments GL_ARB_invalidate_subdata GL_ARB_program_interface_query GL_ARB_robust_buffer_access_behavior GL_ARB_stencil_texturing GL_ARB_texture_query_levels GL_ARB_texture_storage_multisample GL_ARB_texture_view GL_ARB_vertex_attrib_binding GL_KHR_debug GL_AMD_pinned_memory GL_ARB_buffer_storage GL_ARB_internalformat_query2 GL_ARB_multi_bind GL_ARB_seamless_cubemap_per_texture GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_stencil8 GL_ARB_vertex_type_10f_11f_11f_rev GL_EXT_shader_integer_mix GL_NVX_gpu_memory_info GL_ARB_clip_control GL_ARB_conditional_render_inverted GL_ARB_derivative_control GL_ARB_get_texture_sub_image GL_ARB_pipeline_statistics_query GL_ARB_shader_texture_image_samples GL_ARB_texture_barrier GL_EXT_polygon_offset_clamp GL_KHR_context_flush_control GL_KHR_robust_buffer_access_behavior GLX Extensions: GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_create_context_robustness GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address GLX_ARB_multisample GLX_EXT_import_context GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_fbconfig_packed_float GLX_EXT_framebuffer_sRGB GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile GLX_MESA_copy_sub_buffer GLX_MESA_multithread_makecurrent GLX_MESA_query_renderer GLX_MESA_swap_control GLX_OML_swap_method GLX_OML_sync_control GLX_SGI_make_current_read GLX_SGI_swap_control GLX_SGI_video_sync GLX_SGIS_multisample GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_SGIX_visual_select_group GLX_EXT_texture_from_pixmap GLX_INTEL_swap_event Setting maxVSyncInterval to 4 GL: Detected 1024 MB VRAM AudioManager: Using PulseAudio: Default Output Device Begin MonoManager ReloadAssembly Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp-firstpass.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp-firstpass.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-CSharp.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript-firstpass.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript-firstpass.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Assembly-UnityScript.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.UI.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.UI.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.Networking.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/UnityEngine.Networking.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Mono.Cecil.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Mono.Cecil.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/KSPAssets.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/KSPAssets.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/TrackIRUnity.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/TrackIRUnity.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/xmldiffpatch.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/xmldiffpatch.dll into Unity Child Domain Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/XmlDiffPatch.View.dll (this message is harmless) Loading /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/XmlDiffPatch.View.dll into Unity Child Domain - Completed reload, in 0.074 seconds Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/System.Core.dll (this message is harmless) Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/System.dll (this message is harmless) Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/Boo.Lang.dll (this message is harmless) Platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed/System.Xml.dll (this message is harmless) Default vsync count 0 requesting resize 1680 x 1050 Selecting FBConfig GLX_FBCONFIG_ID=159 GLX_BUFFER_SIZE=32 GLX_DOUBLEBUFFER=1 GLX_RED_SIZE=8 GLX_GREEN_SIZE=8 GLX_BLUE_SIZE=8 GLX_ALPHA_SIZE=8 GLX_DEPTH_SIZE=24 GLX_STENCIL_SIZE=8 GLX_SAMPLES_ARB=2 GLX_SAMPLE_BUFFERS_ARB=1 GLX_STEREO=0 GLX_CONFIG_CAVEAT=NONE requesting fullscreen 1680 x 1050 at 0 Hz Desktop is 3280 x 1200 @ 60 Hz Using libudev for joystick management Importing game controller configs UnloadTime: 3.440000 ms Release Build (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [KSP Version]: (LinuxPlayer) ==================================== (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [Input Devices]: (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [Input Devices]: (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Launcher Settings File exists (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Launcher disabled? False (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Launcher after checking file: False (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) ******* Log Initiated for Kerbal Space Program - (LinuxPlayer) ******* (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Changing real window size to 1680 x 1050 Ignoring window size change to 1680x1050 : waiting for fullscreen at 1680x1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 Changing real window size to 1680 x 1050 PhysicsGlobals: Loading database (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) ActionCanvas MASK: 3458764513820540928 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AppCanvas MASK: 3458764513820540928 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) MainCanvas MASK: 3458764513820540928 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Load(Assembly): Squad/Plugins/KSPSteamCtrlr (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AssemblyLoader: Loading assembly at /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/KSPSteamCtrlr.dll (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Load(Assembly): Squad/Plugins/Steamworks.NET (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AssemblyLoader: Loading assembly at /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/Steamworks.NET.dll (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) AssemblyLoader: Loading assemblies (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) Non platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/KSPSteamCtrlr.dll (this message is harmless) Non platform assembly: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/GameData/Squad/Plugins/Steamworks.NET.dll (this message is harmless) VesselModules: Found VesselModule of type CommNetVessel with order 999 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) VesselModules: Found VesselModule of type FlightIntegrator with order 0 (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) VesselModules: Found 2 VesselModule types (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) ************************************************************************ Environment Info Unix 7FFFFFFFFFFFFFFF Args: KSP.x86_64 Mod DLLs found: Stock assembly: Assembly-CSharp v1.0.0.0 Stock assembly: KSPSteamCtrlr v0.0.1.35 Stock assembly: Steamworks.NET v9.0.0.0 / v9.0.0 Folders and files in GameData: Stock folder: Squad .DS_Store ************************************************************************ (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) [AddonLoader]: Instantiating addon 'KSPSteamController' from assembly 'KSPSteamCtrlr' (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42) KSP Log $ cat ~/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP.log [LOG 16:44:25.580] ******* Log Initiated for Kerbal Space Program - (LinuxPlayer) ******* Kerbal Space Program - (LinuxPlayer) OS: Linux 4.8 Ubuntu 16.10 64bit CPU: Intel(R) Xeon(R) CPU X5450 @ 3.00GHz (8) RAM: 30914 GPU: Gallium 0.4 on AMD CAPE VERDE (DRM 2.46.0 / 4.8.0-41-generic, LLVM 3.8.1) (1024MB) SM: 30 (OpenGL 3.0 [3.0 Mesa 12.0.6]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8 Log started: Sun, Mar 19, 2017 16:44:25 Launcher Output $ ~/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP.x86_64 Found path: /home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/greg/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 6 screens displaymanager screen (0)(DisplayPort-0): 1680 x 1050 displaymanager screen (1)(DVI-0): 1600 x 1200 Using libudev for joystick management Importing game controller configs Terminated
  9. My issue is basically identical to this one, but I decided to launch a new issue nevertheless since my version is 1.2.2 and I don't have an unmodded install (though it is almost umnodded, see lower). When KSP is launched a black empty window appears but is replaced in a few seconds with a new window with the white squad monkey and loading bar and after everything is loaded, KSP runs. The original issue I linked describes one type of crash - right before the monkey window appears. I experience the same issue (see video of it here). However, I experience also another kind of crash - when the loading bar reaches the end and the game is supposed to kick in (but it crashes in the same way) - see video here. There is also a third phenomenon I experienced - right about the time the first type crash happens, the window manager crashes but manages to recover and restart and the game loads fine (no video of that, I'm really not filming all my startups). Sometimes the game loads just fine, sometimes I experience the first type crash, sometimes I experience the second type crash and very very rarely I experience the third phenomenon. I'd say that the first type crash is the most common, the next in frequency is the fine loading of the game, the third is the second type crash and the third phenomenon is very very rare. I can't see any correlation with other stuff like running programs - it happens both right after system boot and when running a bunch of other programs like vscode, chrome, etc. Because of me being an idiot I forgot to store the logs. When this happens next time I'll save and publish the logs. My KSP is basically unmodded with the exception of kOS where I'm programming some stuff in (and because of this it really drives me crazy since I have to restart the game a lot). And no, my modifications to kOS don't cause the crash because it both crashes and not crashes with the same stuff. It is a copy of a steam-installed game that I use for working on mods. I'm running Ubuntu Gnome 16.10 with gnome-shell 3.20.4, X server version 1.18.4, nVidia GeForce 940M with driver version 367.57, I have dual screen setup (as you could have seen in the videos). Ask me for any other config info you need to know (apart from the logs, I'll post them as soon as I get them). I would appreciate any help, hint or trick to make it working consistently. Developing something with >50% of time crashing all the way to the login screen is really a hell. EDIT: I experienced the first type crash again, the log is here:
  10. having a crash that looks suspiciously like an out of memory crash, only when im launching certain ships. (an Apollo replica ive been trying to make. part count isnt that high yet) other ships, even one with large part counts, do not seem to be affected. at time of crash, only 7 GB of the 16 installed (not counting swap, another 20) is in use. here is the ksp.log: VERY large)
  11. I'm experiencing game freezes since 1.2. I can play for about 5 to 30 minutes and suddenly the game freezes. I can still move the mouse around, but cannot do any action in game. I can switch windows to my OS and the system is working normally. The only way to exit KSP is to kill the process. I'm thinking that maybe it is related to run it under XWayland. My system is: KSP x86_64 1.2.0 Build ID 01586 running from Steam. OS: Fedora 25 x86_64 Radeon HD 6870 with radeon driver. Gnome wayland session. These are the logs of a vanilla KSP installation, playing the scenario of Jool aerobreaking. When the ship exploded in the Jool atmosphere, the game freezed:
  12. I recently migrated to Linux (had enough of MS shenanigans) and restarted KSP. Now I tried to recreate my rover lander, but could not fit the 2.5 service bay UNDER the fuel tank, i have no idea why. Previously I tried to place the rover into the already fitted service bay with no success. Well, of course I could fit it in the bottom but not to the top. So I prefit the rover into the bay as sub assembly, which worked fine. Strangely enough: - I can fit the same stuff ABOVE, see screenshot, no matter how impossibly impossible it might be. Legit, eh? - when I tried to make a screenshot of the stuff when trying to place it under the tank (while it´s red cuz it never got green :P) the whole everything just crashed. I mean even the op system. Tried 2 times, then gave up. So no screenshot of that, but will make a video if needed. - I used the same design under win in the past, and it worked fine. So nothing else has changed ever since just linux. I´m using no mods, and don´t even want to. Any ideas how I could overcome this? Thanks in advance!
  13. The Linux install of KSP 1.2 appears to react badly to some configuration data that may be stored elsewhere by earlier versions of KSP. If you get a blank screen rather than the initial menu, this may be a cause 1: The data involved is stored in one or more subfolders of ~/.config/unity3d/ (This is on an Ubuntu-derived Linux, but I would expect it to be universal. This is a hidden folder and you might need to change a setting to be able to see it.) 2: On my system I found ~/.config/unity3d/SQUAD/ and ~/.config/unity3d/Squad/ , timestamped about three weeks apart in June 2016. They contained different sets of files. I made archives of both and deleted them. Both were related to Kerbal Space Program. 3: Deleting these files led to a normal startup of KSP, in a window rather than full-screen. 4: If you have an in-progress career or science game from an earlier version of KSP, I would not be at all surprised if you need to restore from the archives you made so as to run the earlier KSP version. 5: I am told Steam does things differently. I don't even know whether or not Steam supports Linux.
  14. I have a Logitech Extreme 3D Pro and although it is fantastic for KSP, the throttle has never worked on GNU/Linux for me. The throttle only goes up to half way and I think it's because the linux kernel is sending a range of [-Min, +Max] instead of [0, Max]. I've never been able to fix this, and although this isn't the main topic of this post, I'd be interested to know if anybody has successfully got this working (please no suggestions unless you've confirmed that it actually works on GNU/Linux - I've tried pretty much everything you could suggest right down to considering compiling a custom kernel). I was wondering if anybody has any suggestions for a better joystick that they can confirm does work on GNU/Linux and gives the full range of throttle. For example, I'm considering the Thrustmaster T-Flight Hotas X and a few others, but I won't buy anything unless I know for sure that it works.
  15. I've been a longtime fan of KSP, and I recently installed version 1.2. However, when I try to launch, the cursor turns into a loading circle for a bit and then reverts. Checking System Monitor shows KSP.exe running for a bit, and then stopping. I get no error messages or pop-ups of any kind. This happens when I run both the 32-bit and 64-bit launchers. I have looked into this problem elsewhere on the forum, but the standard bugfix, deleting ~/.config/unity3d/Squad/Kerbal Space Program, doesn't work because said folder doesn't seem to exist on my hard drive. Running KSP.exe via the terminal returns the following: [...]/Kerbal.Space.Program.v1.2.0.1586/KSP.exe fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:system:SetProcessDPIAware stub! wine: Unhandled stack overflow at address 0x7bc475b8 (thread 0009), starting debugger... err:seh:setup_exception_record stack overflow 832 bytes in thread 0009 eip 7bc475b8 esp 00230ff0 stack 0x230000-0x231000-0x330000 Running KSP_x64.exe via the terminal returns the following: [...]/Kerbal.Space.Program.v1.2.0.1586/KSP_x64.exe fixme:heap:HeapSetInformation 0x3c4000 0 0x22fda0 4 fixme:system:SetProcessDPIAware stub! err:seh:setup_exception stack overflow 2032 bytes in thread 0024 eip 00007f5d97b0718b esp 0000000000130e10 stack 0x130000-0x131000-0x230000 I am running KSP on the latest version of Zorin OS, a variant of Debian. It has an Intel® Pentium(R) 2117U CPU and Intel Ivybridge Mobile graphics.
  16. On HP EliteBook 8570w, under Linux Mint, the KSP demo works perfectly, but the full version either freezes at some point during launch, or if it does successfully launch, much of the graphical resources are missing from the screen. However, on the same HP Elitebook 8570w, under Windows 7, Windows 8.1, or Windows 10, both the KSP demo and full version work perfectly. Is there a solution for this or am I simply out of luck with the Linux Mint / KSP combination? Thanks in advance.
  17. I recently installed KSP on my arch linux laptop (System 76 Galago, i7-4750HQ, 16 GB RAM, intel iris pro 5200) via steam. I installed a few addons and launched it. The game started for a little bit, showed something about installing add-ons and then crashed. After that when I try to launch the game from steam nothing appears to happen. When I try and launch it from the command line with ./KSP.x86 or ./KSP.x86_64 I see the following at the terminal before the program exits: Set current directory to /home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program Found path: /home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/home/darren/.local/share/Steam/SteamApps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 displaymanager : trying .X11-unix client :0 has 1 screens displaymanager screen (0): 1920 x 1080 Using libudev for joystick management Importing game controller configs I then tried deleting the game and reinstalling it (without addons) and now the same thing still happens (I just see the above text in the terminal). I've also verified the game data and that hasn't found anything. I even deleted the game and redownloaded it one more time (again leaving it stock) and still it won't launch. The game doesn't create a new window and I don't get a KSP.log file, I just see the text from above in the terminal. The arch linux wiki mentions launching the game with "LC_ALL=C" so I've tried both "LC_ALL=C ./KSP.x86_64" and "LC_ALL=C ./KSP.x86" I also do have pulse audio running and the ttf-ms-fonts package installed from the AUR. Also I'm running Awesome WM for my window manager if that matters. Does anyone have any ideas on how I can get this to run on my machine?
  18. KSP Version: no longer work, I can't check version on splash screen but it's always updated by Steam and the buildID.txt is build id = 01289 2016-06-21_20-12-27 Branch: master What happen: I was playing all week nights, with a few random crashes but I'm not complaining on those, game was mostly running fine and then... - I paused the game while on rescue operation in orbit - Since music still plays after Alt-Tab to read docs on the web, I decided to set music volume to 0... Escape-> Settings -> Music volume 0 -> Apply After that no more music but the window app game is frozen and then gone... And I can NO LONGER START THE GAME in anyway. Tried after rebooting PC, nothing happen when I start the game from Steam. No splash screen, nothing. It was (mostly) fine before that setting change, I could play for hours. No mods, no add-on, Steam verified install Step to replicate: see description of what happened, but I'm enable to try to replicate: it no longer start. Last lines of KSP.log: [LOG 21:50:31.995] Game Paused! [LOG 21:50:45.826] Launcher start settings screen: False [LOG 21:51:10.296] Launcher here(in write): False [LOG 21:51:10.372] [MessageSystem] Reposition 12.0902 228753 [LOG 21:51:10.372] [GenericAppFrame] Reposition 12.0902 228753 [LOG 21:51:10.372] [GenericAppFrame] Reposition 12.0902 228753 [LOG 21:51:10.373] [GenericAppFrame] Reposition 12.0902 228753 [EXC 22:09:35.566] DllNotFoundException: CSteamworks Steamworks.InteropHelp.TestIfAvailableClient () Steamworks.SteamController.Shutdown () SteamController.KSPSteamController.OnDestroy () SteamController.KSPSteamController.OnApplicationQuit () Start by command line: user@mypc:/data/Steam/steamapps/common/Kerbal Space Program > LANC=C ./KSP.x86_64 Set current directory to /data/Steam/steamapps/common/Kerbal Space Program Found path: /data/Steam/steamapps/common/Kerbal Space Program/KSP.x86_64 Mono path[0] = '/data/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono path[1] = '/data/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono' Mono config path = '/data/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.4 client has 4 screens displaymanager screen (0)(DP-0): 1920 x 1200 Using libudev for joystick management Importing game controller configs And that's all. Nothing happen after. My system: PC Intel x86_64 + NVidia, Linux Mint KDE 17.3 64, 8GB RAM, French locale. Classic keyboard and mouse, no fancy controller or joypad. One screen attached to the graphic card. Steam games in custom directory, no problem before and no problem to start other Steam games. Lots of space on disk. My attempts: I edited settings.cfg to set back music to more than 0 (0.3), and I also put back Full screen and resolution that wasn't correct (that's strange). I have a copy of the unedited file. I changed Steam KSP startup option as suggested: LC_ALL=C %command%_64 My question / request: I would be very grateful to anyone would could help me or point me toward a bug solving process, but right now I can't even find a clue EDIT: looking into that thread that look promising... EDIT 2: SOLVED! (workaround) Just delete or rename that file: ~/.config/unity3d/Squad/Kerbal Space Program/prefs Here is the offending prefs file content, a bug in KSP has written crazy resolution: <unity_prefs version_major="1" version_minor="1"> <pref name="Screenmanager Is Fullscreen mode" type="int">0</pref> <pref name="Screenmanager Resolution Height" type="int">23</pref> <pref name="Screenmanager Resolution Width" type="int">1</pref> <pref name="UnityGraphicsQuality" type="int">5</pref> <pref name="UnitySelectMonitor" type="int">-1</pref> </unity_prefs>
  19. Recently I ran into a performance issue - when flying a vessel and when in map view of an active vessel the frame rate drops to very low number (1 to 5 FPS) and my nvidia control panel shows very low GPU utilization. However, in the KSC and in Tracking Station the game is nice and smooth and GPU is properly utilized. In detail When I start the game, in the KSC the game runs fine and smooth and it is clearly using the GPU as can be seen from this image (GPU uitilization can be read in the left window): GPU utilization in KSC When I go to the tracking station, the game still runs fine and smooth and is also using GPU: GPU utilization in Tracking Station And now it begins. When I fly the vessel (or Melina as in this example), the game drops to about 1 to 5 FPS. The weirdest thing is that now the GPU is almost idle (it fluctuates between 0% and about 20%): GPU utilization flying a vessel. More to that, the debug window shows 25 FPS but that is not true, it is painfully laggy with about 1 to 5 FPS as I have already written. The same happens when I switch to map view - again about 1 to 5 FPS, again very low GPU utilization: GPU utilization in Map View. Again the 25 FPS in the debug window is not the real frame rate. However this behavior started only recently (a day or two, maybe? I'm not entirely sure). I have neither modified any mods nor the KSP itself. Maybe some system updates happened but I'm not sure about that (since I didn't track this as I found out about this problem just as it happened). OS: Ubuntu Gnome 16.04 > uname -srvmpio Linux 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux KSP version: (from Steam) Installed mods: (all installed via CKAN) [x] Science! (xScience v4.20) CapCom - Mission Control On The Go (CapCom 2.4) Contract Parser (ContractParser 4.0) Deadly Reentry Continued (DeadlyReentry v7.4.7.1) Docking Port Alignment Indicator (DockingPortAlignmentIndicator 6.4) Ferram Aerospace Research (FerramAerospaceResearch 3: Kerbal Alarm Clock (KerbalAlarmClock v3.7.1.0) Kerbal Attachment System (KAS Kerbal Flight Data (KerbalFlightData R21) Kerbal Inventory System (KIS Magic Smoke Industries Infernal Robotics (InfernalRobotics v2.0.5) Magic Smoke Industries Infernal Robotics - Legacy Parts (InfernalRobotics-LegacyParts v2.0.0) MechJeb 2 (MechJeb2 ModularFlightIntegrator (ModularFlightIntegrator Module Manager (ModuleManager 2.6.25) NavUtilities (NavUtilities 0.6.1) PersistentRotation (PersistentRotation 1.6) Portrait Stats (PortraitStats 11.0) Procedural Fairings (ProceduralFairings v3.17) Progress Parser (ProgressParser 5.0) RemoteTech (RemoteTech v1.7.1) ShipManifest (ShipManifest Surface Mounted Stock-Alike Lights (surfacelights Toolbar (Toolbar 1.7.12) TweakScale - Rescale Everything! (TweakScale v2.2.13) Waypoint Manager (WaypointManager 2.5.3) GPU: Nvida NVS 4200M (a lot of info about the GPU can be seen in the screenshots) GPU driver: 364.19 (installed via Ubuntu's Additional drivers) Thanks for any help and hints.
  20. I recently started playing KSP after a break and the new patch. When I loaded the game, it stopped running, froze, and when I attempted to re-load the game I found that my save files had gone missing from the menu. After manually locating them and suspecting corruption, I made a new save game. The new save game -- default -- did not appear on the menu. In effect I cannot save any game. Weirdly, when I tried to save a new default game I was given an overwrite warning. I do not appear to have an output log. I am currently running Ubuntu.
  21. I can't see a lot of UI elements, such as most of the Settings screen or the Training menu. I've attached screenshots to show what I mean. Note that everything is there, just invisible, as when I click various parts of the list of training missions, the displayed name and description does change. I'm on 64-bit Linux, and this happens with both the 32-bit and 64-bit KSP binaries. I have version of the game through Steam. This is a completely fresh, clean, unmodded installation. I've tried this on two different computers with the exact same results: one running Ubuntu 16.04 with Intel graphics, and one running Kubuntu 16.04 with AMD graphics. I note this sounds like "No text shows up in the settings menu" in the list of common problems, but I confirmed that I already have the fonts installed that are supposed to fix it.
  22. I'm interested in the game.. Looks like lot of fun.. Too bad I didn't discover earlier. I have a skylake (i5-6500) CPU with 16 GB RAM with Intel graphics (integrated HD 530) running antegros Linux (like arch) I just want to know from the community if intel graphics would be sufficient and how does KSP generallly behave with Linux? -Thanks Vijay
  23. Hello Linux x86_64 here, Ubuntu 14.04 LTS, Gnome Classic (metacity, no compiz or other graphical crap), nvidia-340. I am seeing a fairly consistent crash on startup. I am running a 2x 1920x1080 setup, but the problem happens even in single-monitor mode. After launching KSP_x86_64, a black game window appears (sized to be about 1920x1080, plus window decorations). A few seconds later, the (still black) game window flickers, killing my window manager, all running Xorg clients, and my entire Xorg session, meaning that I have to log in again. This is quite reproducible. I found that the problem is a lot less likely to happen if I edit ~/.config/unity3d/Squad/Kerbal Space Program/prefs and delete any lines containing 'Screenmanager'. However, usually these lines will return if the game is restarted, meaning that I have to do this every time the game starts. Sometimes, even deleting the screenmanager lines does not prevent the game from crashing the whole graphical interface, but it generally helps. Any thoughts? Edit to add: These are the lines that I have to delete in 'prefs'. I imagine the actual resolution is a little lower than 1920x1080, due to sizes of window borders and window decorations. Perhaps Unity's initial attempts to attain this resolution (before KSP does its own internal window resize) is what's causing the disaster. <pref name="Screenmanager Is Fullscreen mode" type="int">0</pref> <pref name="Screenmanager Resolution Height" type="int">1053</pref> <pref name="Screenmanager Resolution Width" type="int">1912</pref> During the startup phase (before the screen with the progress bar and three kerbals), it is very easy to crash the game (and the window manager, and X) just by trying to move the game window or to resize it.
  24. It's hard for me to reproduce; I thought it might have been something to do with adding parts then removing them, but if I fiddle with a vessel in the VAB for a while, it pretty reliably crashes. There's a copy of what it spat out on the console and Player.log here. This line spits out on the console before a back trace and memory dump: *** Error in `./KSP.x86_64': double free or corruption (out): 0x00007f3a1fb414d0 *** So it's probably a double free. I'm running KSP.x86_64 on Debian: 4.4.0-1-amd64 #1 SMP Debian 4.4.6-1 (2016-03-17) x86_64 GNU/Linux
  25. If youre infuriated by the stupidly slow speed of the zoom in the VAB/SPH, you can fix it by changing VAB_CAMERA_ZOOM_SENS in settings.cfg. For some reason this defaults to 0.1, instead of 0.5 as it should be, and is for FLT_CAMERA_ZOOM_SENS (which is the same thing, but for when youre flying a ship). Sadly, there is still no known fix for the ineffectively slow rotation speed in IVA scenes.