Jump to content

ReyTigerLinux

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by ReyTigerLinux

  1. I have resolved my issue with the infinite loading on Arch Linux by setting the 'SDL_DYNAMIC_API' environment variable to the library provided by Arch's libsdl2 package: I used the steam launch options like so: SDL_DYNAMIC_API=/usr/lib64/libSDL2.so LC_ALL=C %command%_64 Evidently this an SDL compatibly feature for when is bundled with a game installed on a system which has a different version of libSDL2, detailed in this post: Hopefully that works for you too!
  2. Gotcha, here's the 64-bit logs: https://www.dropbox.com/sh/celbxfb97ilr432/AAAtTKbLcmNOHhYBbpzl3_vla?dl=0 I included ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log (Apparently called output_log.txt on Windows) and ~/.steam/steam/steamapps/common/Kerbal\ Space\ Program/KSP.log_64 Waited about 20 minutes on the loading screen, killed KSP, then gathered logs.
  3. Wonderful to see that you're maintaining this great mod, but unfortunately I'm having some difficulty running it on Linux. I am on a clean install via steam, using a fresh sandbox save and tried to put a stock craft onto the launch pad, and was able to load in with the prereq mods (ClickThroughBlocker, AVC, Toolbar Control). However when I added AFBW 1.8.0.2, loading a flight scene causes a segmentation fault under with the 32-bit client, and a some sort of spinlock under 64 bit i.e. a cpu was pegged at 100% usage, never makes progress even after ~30 minutes System info and logs: https://pastebin.com/mC1zEfLF (Put onto pastebin due to CloudFlare not liking the content, originally put into spoiler sections) I can file this on Github as well if you'd prefer.
×
×
  • Create New...