You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When launching KSP via 'KOS: Start Kerbal Space Program', KSP loads files at a drastically reduced rate. During loading, KSP seems to stall and no further loading progress is made. In older KSP versions (1.3.1) this stall occurs when the loading bar is full. On newer versions (1.8.1 and 1.9.1), this stall occurs when the bar is ~75% full. The backgrounds continue to cycle, as does the loading text, but no further loading occurs and the main menu is never reached. Somehow, it also fails to produce it's own log file when called from VS Code as well, so I'm not sure how to troubleshoot. Works fine if VS Code is launched as administrator. Game loads at full speed, reaches menu, performs as normal.
To Reproduce
Configure "kos-vscode.kerbalSpaceProgramPath" to point to desired location (or don't, doesn't seem to matter)
While editing a .ks file, open command palette and select the command to start KSP.
Observe slower than normal file loading
Get stuck after all files have loaded, have no log to read.
After closing the stuck KSP, open it by hand via Windows Explorer. Loads quickly, reaches menu, writes log.
Expected behavior
KSP launches the same as if it were manually launched.
Editor (please complete the following information):
OS: Windows 10
Editor: vscode, system install
Extension Version: 1.1.2
Additional context
I have tried multiple versions of KSP, in custom directories on multiple drives and the default Steam install. This issue occurs with all of them. All of them load successfully when launched normally (via Windows Explorer or a shortcut).
I have checked the Event Viewer (no events), double-checked file permissions. The only Extension Host log item in VS Code for your extension is it's initial activation for that session, and the only contents of it's own log are warnings about references to other KS files in my kerboscript files that it can't resolve, all of which are valid errors. Those .ks files are, in fact, absent.
The text was updated successfully, but these errors were encountered:
I suspect the slow load time is the same issue as being unable to write it's own log file, and that it is caused by some sort of permission error. I just don't know enough about Node to be helpful in diagnosing. I think I remember seeing a forum thread years and years ago with a similar issue and the root cause was permissions, but I can't seem to locate it again.
Describe the bug
When launching KSP via 'KOS: Start Kerbal Space Program', KSP loads files at a drastically reduced rate. During loading, KSP seems to stall and no further loading progress is made. In older KSP versions (1.3.1) this stall occurs when the loading bar is full. On newer versions (1.8.1 and 1.9.1), this stall occurs when the bar is ~75% full. The backgrounds continue to cycle, as does the loading text, but no further loading occurs and the main menu is never reached. Somehow, it also fails to produce it's own log file when called from VS Code as well, so I'm not sure how to troubleshoot.
Works fine if VS Code is launched as administrator. Game loads at full speed, reaches menu, performs as normal.
To Reproduce
Expected behavior
KSP launches the same as if it were manually launched.
Editor (please complete the following information):
Additional context
I have tried multiple versions of KSP, in custom directories on multiple drives and the default Steam install. This issue occurs with all of them. All of them load successfully when launched normally (via Windows Explorer or a shortcut).
I have checked the Event Viewer (no events), double-checked file permissions. The only Extension Host log item in VS Code for your extension is it's initial activation for that session, and the only contents of it's own log are warnings about references to other KS files in my kerboscript files that it can't resolve, all of which are valid errors. Those .ks files are, in fact, absent.
The text was updated successfully, but these errors were encountered: