AmenRa
-
Posts
6 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Posts posted by AmenRa
-
-
Wheel are still broken as of 1.1.3.
-
KSP: 1.1.3 (Win64) - Unity: 5.2.4f1 - OS: Windows 10 (10.0.0) 64bit
Kerbal Inventory System - 1.2.12
KSP-AVC Plugin - 1.1.6.1
Infernal Robots - 2.0.2
SCANsat - 1.1.6.3
TarsierSpaceTechnology - 6.4
Anyone having issues with Kerbals not staying put on ladders? I am find it very frustrating that the Kerbals do not stay fixed to ladders when performing EVA's. The Kerbal either slides up or down the ladder or, just eventually lets go for no reason.
I am using the KIS (Kerbal Inventory System - 1.2.12) to build stations. It is extremely frustrating during times when I need more than one Kerbal in EVA to move parts because the Kerbals just keep floating off and eventually get out of range. They won't stay put on the ladders mounted to the station.
-
I am very disappointed that the wheels no longer function in V1.1.3. Some or all are BLOCKED. When they do work and I restore the came - BLOCKED. Very aggravating.
-
Having the same issue. KSP_X64 1.05 worked flawlessly. I upgraded to 1.1.3 and it crashes the X desktop when starting.
I performed a fresh install of 1.1.3 and removed my ~/.config/unity3d folder. Still have the issue.OS: Gnome Ubuntu Desktop16.04.00 LTS x64 (with all updates)
Build.txt
build id = 01289
2016-06-21_20-12-27
Branch: master/var/log/syslog
Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: disconnected Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): connected Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): Internal TMDS Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): 330.0 MHz maximum pixel clock Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: disconnected Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): connected Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): Internal TMDS Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): 330.0 MHz maximum pixel clock Jul 22 06:57:36 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:40 eerlon gnome-session[10481]: (gnome-shell:10539): Gdk-WARNING **: Native children wider or taller than 65535 pixels are not supported Jul 22 06:57:40 eerlon gnome-session[10481]: (gnome-shell:10539): Gdk-ERROR **: The program 'gnome-shell' received an X Window System error. Jul 22 06:57:40 eerlon gnome-session[10481]: This probably reflects a bug in the program. Jul 22 06:57:40 eerlon gnome-session[10481]: The error was 'BadAlloc (insufficient resources for operation)'. Jul 22 06:57:40 eerlon gnome-session[10481]: (Details: serial 52097 error_code 11 request_code 12 (core protocol) minor_code 0) Jul 22 06:57:40 eerlon gnome-session[10481]: (Note to programmers: normally, X errors are reported asynchronously; Jul 22 06:57:40 eerlon gnome-session[10481]: that is, you will receive the error a while after causing it. Jul 22 06:57:40 eerlon gnome-session[10481]: To debug your program, run it with the GDK_SYNCHRONIZE environment Jul 22 06:57:40 eerlon gnome-session[10481]: variable to change this behavior. You can then get a meaningful Jul 22 06:57:40 eerlon gnome-session[10481]: backtrace from your debugger if you break on the gdk_x_error() function.) Jul 22 06:57:40 eerlon kernel: [55299.299182] traps: gnome-shell[10539] trap int3 ip:7f935a53ca6b sp:7ffd09ecd4d0 error:0 Jul 22 06:57:40 eerlon gnome-session[10481]: gnome-session-binary[10481]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 Jul 22 06:57:40 eerlon gnome-session-binary[10481]: WARNING: Application 'gnome-shell.desktop' killed by signal 5 Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: disconnected Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): connected Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): Internal TMDS Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): 330.0 MHz maximum pixel clock Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: disconnected Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): connected Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): Internal TMDS Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): 330.0 MHz maximum pixel clock Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:40 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (II) NVIDIA(0): Setting mode "DVI-I-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}" Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (II) NVIDIA(0): Setting mode "DVI-I-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DVI-D-0: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}" Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: disconnected Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): connected Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): Internal TMDS Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-0): 330.0 MHz maximum pixel clock Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: disconnected Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): connected Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): Internal TMDS Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): ViewSonic VA2246 SERIES (DFP-2): 330.0 MHz maximum pixel clock Jul 22 06:57:41 eerlon /usr/lib/gdm3/gdm-x-session[10244]: (--) NVIDIA(GPU-0): Jul 22 06:57:41 eerlon gnome-session[10481]: current session already has an ibus-daemon.~/.config/unity3d/Squad/Kerbal Space Program/Player.log
Selecting FBConfig GLX_FBCONFIG_ID=167 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=0 GLX_SAMPLE_BUFFERS_ARB=0 GLX_CONFIG_CAVEAT=NONE Desktop is 3840 x 1080 @ 60 Hz Initialize engine version: 5.2.4f1 (98095704e6fe) GfxDevice: creating device client; threaded=1 GPU_MEMORY_INFO_DEDICATED_VIDMEM_NVX: 1048576 OpenGL: Version: OpenGL 4.5 [4.5.0 NVIDIA 361.42] Renderer: GeForce GTX 750/PCIe/SSE2 Vendor: NVIDIA Corporation VRAM: 1024 MB ..... Load(Texture): Squad/Parts/Aero/wings/Wings (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64) Load(Texture): Squad/Parts/Command/Mk1-2Pod/ladder (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64) Load(Texture): Squad/Parts/Command/Mk1-2Pod/mk 1-2 external shell Variant-Hatch NRM (Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 64)This solution seemed to work for me:
$ ./KSP.x86_64 --force-glcore -
I too have this problem. The orbit lines disappear in MAP mode.
KSP: 1.0.5 x64
OS: Ubuntu 14.04 LTS x64
CPU: i7-2600K
GPU: NVIDIA Quadro K4000
GPU Driver: Proprietary NVIDIA 352.63
Monitor 1: DVI
Monidor 2: Display PortOn 1/20/2016 at 7:14 PM, mianosm said:To add to the oddities, using the above command line works on a DVI connected monitor, but not on a Display Link connected display.....fingers crossed on the 1.1 update to have the fix/correction.
mianosm pointed out something I didn't try - DVI vs Display Port. When move the app to the DVI, the orbit lines appear at any zoom range however when I move the app to the Display Port the orbit lines disappear when I zoom out. So this may be an NVIDIA driver issue.
Action Groups - configure after VAB (launch)?
in KSP1 Gameplay Questions and Tutorials
Posted
Is it possible to configure action groups AFTER leaving the VAB (launching)? I forgot to configure one group and it's annoying to have to click all the items.