Jaunasse

Another problem still remains though, while using the ingame editor, only keys that aren't already assigned to an in-game command can be typed, the other will just affect the game outside of the editor. My current workaround is using an external IDE and save programs in the Archive EDIT: This might be unrelated, but the "lock steering" command doesn't seems to work. EDIT 2: Just dumb and forgot about SAS. Lock steering works fine.

I need to go to work so I haven't been able do to extensive tests, but it seems to work perfectly ! Thank you for reacting so quickly to a bug that wasn't even kOS related, I'm really impressed !

Sadly my ksp won't start up on 32 bit (crash during the loading). I don't know if it is because I am using too much resources or doesn't have the proper libraries to run in it 32 bit but I can't perform this test at the moment. Maybe kafuka could help us with this ?

Unfortunately, I could only find "Player.log" and "prefs" files in /.config/unity3d/Squad/Kerbal Space Program EDIT : there's 51 "KEYDOWN IN TERMINAL" entries in the player.log and there's a lot of lines about TextureReplacer in between, i've deleted them and after translating some of the unicode chars it actually corresponds to the test. KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x48 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x45 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x4c (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x4c (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x4f (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x2e (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0xff0d (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x53 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x6f (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x6d (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x65 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x20 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x53 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x70 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x61 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x63 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x65 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x73 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x20 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x48 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x65 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x72 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x65 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x2e (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0xff0d (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x31 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x32 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x33 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000116 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x34 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x35 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x36 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0xff0d (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x31 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x32 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x33 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000114 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000130 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) ff KEYDOWN IN TERMINAL: UNICODE CHAR: 0x34 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x35 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0x36 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: SPECIAL CODE: 0x00000113 (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) KEYDOWN IN TERMINAL: UNICODE CHAR: 0xff0d (Filename: /BuildAgent/work/d63dfc6385190b60/artifacts/LinuxStandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49) - the "enter" input seems to correspond to 0xff0d and / or 0x00000130 ?

@Steven Mading Thank you for answering so quickly, however, after trying multiple times, the new kOS.dll does not write any output_log.txt. I'm running on 64bits yet there were initially no "KSP_x64_Data" folder, only a "KSP_Data" folder. I deleted my old kOS.dll to be sure it wasn't interfering in any way. I created a "KSP_x64_Data" folder and tried running ksp with admin rights, but no output log were generated. Here is the result of typing the indicated commands: http://i.imgur.com/JSHzJFp.png Thanks.

Sure, thanks for the help. I'm glad to see it doesn't come from my keyboard settings, I've been trying to remap "enter" to other keys without any results

sorry double post.

Hello, I hope i'm not asking a dumb question : I play KSP 0.24 64bits on ubuntu and while the terminal opens and commands can be typed well, pressing enter only adds spaces after the typed command, is there a problem with my installation or am I pressing the wrong key ? thanks