Possitive Feedback + minor issue

[mstoykov]

Hello,

First the positive: the game works, no problems that I can find on hardware that supposedly is not supported:
Acer laptop with Intel celeron 560@2.13GHZ, X3100 with 256 MB with 2 GB of ram. I haven't seen any issues I didn't have to do anything and it just worked on my Fedora 17 64bit - GREAT JOB .

My only issue is that when I run it from terminal it works fine and just spills the last line indefinitely, which probably uses resources for redraw on the screen that should not be needed . I haven't seen anything in the game that actually suffers from this but it might be something I haven't tried. I though it might be because I play in window mode and going in and outside of the window every now and again but it's the same in fullscreen. I got 30 lines of it when I killed the moment it loaded.

Code: Select all

$ ./FTL 
Loading Arch = amd64
Initializing Crash Catcher...
Initializing Video
Video Initialized
Opengl version = 2.1 Mesa 8.0.3
Starting audio library...
Audio Initialized!
Resource Preload: 33341
Initializing animations...
Animations Initialized!
Loading Ship Blueprints....
Blueprints Loaded!
Initializing Sound Data....
Generating world...
Loading achievements...
Loading score file...
Running Game!
SDL Error: no input method could be opened
SDL Error: no input method could be opened

Once again thanks a lot for the great game and the good Linux support (for me) and waiting for w/e you come up with next

[Matthew]

Hi. Good to hear it works well! I haven't heard much feedback from Linux users, but it seems like the majority aren't having any problems. It's very encouraging.

I'm not sure what could be causing that error but you're right that constantly printing it is probably not helping anything. I'll make sure when we have the time to push our first update that I'll at least cap the error printing to prevent it from being silly like that.

[overzealot]

Hey, kinda missed this post, but I get the same SDL error. I'm running Sabayon (gentoo based distro).
Didn't really think it was an issue until tonight, when I left FTL running for about 5 few hours and filled my hard drive (a 20gb .xsession-errors file is nothing to laugh about!). While it made X unable to start, the biggest downer is that FTL tried to save even though there was no space - so my save is lost as well :'(
That was with the initial release - I've update to the newest, but it still seems to spam like crazy. I'm going to try piping the output to /dev/null for the moment, but a fix for this would be nice.

[Matthew]

I had put in something to block error spam but apparently it didn't work. I'll make sure it gets fixed in future updates. Sorry about this, you really experienced the worst possible scenario for what could happen with such a problem!

[fresnik]

Hey, it's been a year since this thread was active, but this is the only page that comes up when you google the error message "SDL Error: no input method could be opened".

So, yeah, I just purchased the game as part of the Humble Bundle 9 and wanted to try it, but got swamped with this error message. Any ideas what's causing it?

EDIT: I found this thread, where it is suggested to set LC_ALL=C. That seemed to work for me, but the game still eats 100% CPU, even with just the main menu up.

[Matthew]

re: Fresnik

I thought the error was fixed, sorry about that. I'll try to get it solved in the next patch.

About the 100% CPU, try enabling the V-Sync and/or Frame Limiter in the FTL options menu, that should help.