FTL: Faster Than Light

FTL: Faster Than Light

View Stats:
[LINUX] Seven Jan 26, 2018 @ 3:30pm
engi med bots arent working in linux
with the second ship in the roster it has engi med bots pre installed but they don't seem to work. does anyone els heve this problem?
< >
Showing 16-28 of 28 comments
NoBoDy Jan 29, 2018 @ 7:52am 
+medbot augment isnt working
anarcher Jan 29, 2018 @ 11:07am 
Originally posted by Matthew:
Originally posted by anarcher:

It must have happened as I was closing the game, it saved and exited to main menu just fine.

Can you check for crash logs anyway? The game shouldn't segfault on close and it could be indicative of other potential problems.

There's a ton of crashlogs, because I run a lot of mods normally and as you'd expect crashes happen from time to time. None of them were from this month, and it didn't crash again so it must have just been a fluke.
[LINUX] Seven Jan 29, 2018 @ 1:09pm 
i dont use any mods
Skinny Pete Jan 30, 2018 @ 8:34am 
Originally posted by aidenpons:
I mean, it's not like you're missing anything, as the healing rate is so slow as to mark that augment for "scrap to be sold off ASAP"...
... it won't help you with boarders or fires, it's only good if your micro is lazy and you can't be bothered healing someone at 95 HP in the drone room...

It's actually reasonably good for giving you the advantage in marginal fights, turning close losses into close wins.

(It's still in "sell off for scrap" territory though.)
Originally posted by Skinny Pete:
Originally posted by aidenpons:
I mean, it's not like you're missing anything, as the healing rate is so slow as to mark that augment for "scrap to be sold off ASAP"...
... it won't help you with boarders or fires, it's only good if your micro is lazy and you can't be bothered healing someone at 95 HP in the drone room...

It's actually reasonably good for giving you the advantage in marginal fights, turning close losses into close wins.

(It's still in "sell off for scrap" territory though.)

But all my marginal fights occur onboard the enemy ship, where it doesn't work.

And marginal fights on my own ship don't happen - I either can beat them off with my own crew or open all airlocks and run to the medbay.
This seems to be a locale problem - try launching it with `env LC_ALL=C %command%` in the start properties. This also makes explosions et al work - this is a common issue with OpenGL, since my locale writes numbers as "123.456,789" - so if you have any string that's interpreted as a number, it'll fail.

Similarly, I've found that FTL now created a second directory in my ~/.local/share, so now theres "FasterThanLight" and "fasterthanlight" in there, which resulted in it not finding the savegames. Once I moved it to the lowercase version, I had my unlocked ships again.
[LINUX] Seven Feb 2, 2018 @ 10:09am 
env LC_ALL=C %command% seems to solve the problem, now engi med bots work .
thx alfabrot
anarcher Feb 2, 2018 @ 2:07pm 
Originally posted by LINUX Seven:
env LC_ALL=C %command% seems to solve the problem, now engi med bots work .
thx alfabrot

So why does opengl whatever affect a gameplay thing anyway?
anarcher Feb 2, 2018 @ 2:13pm 
Originally posted by alfabrot:
This seems to be a locale problem - try launching it with `env LC_ALL=C %command%` in the start properties. This also makes explosions et al work - this is a common issue with OpenGL, since my locale writes numbers as "123.456,789" - so if you have any string that's interpreted as a number, it'll fail.

Similarly, I've found that FTL now created a second directory in my ~/.local/share, so now theres "FasterThanLight" and "fasterthanlight" in there, which resulted in it not finding the savegames. Once I moved it to the lowercase version, I had my unlocked ships again.

So it f-ing was a CAPITAL letters in filename/path issue. :steamfacepalm:
To be clear: It's not _just_ OpenGL that can show that issue - anything that interprets a string as a number and isn't careful about locale will run into this. It's just that that tends to happen frequently with OpenGL.
Matthew  [developer] Feb 5, 2018 @ 1:35am 
We've fixed the engi nanobot issue on our end and it will be a part of the next update. @Seven was correct that it's related to how the game parses numbers in different locales.

And with FasterThanLight vs fasterthanlight -- That's an issue caused by Steam's Cloud system. They claimed it was fixed years ago but apparently it wasn't retroactive, so if you had the game before ~2015 it would still cause perpetual problems. I'm sorry about that one, I was only just made aware that the Steam fix wasn't universal.
anarcher Feb 5, 2018 @ 4:21am 
Originally posted by Matthew:
We've fixed the engi nanobot issue on our end and it will be a part of the next update. @Seven was correct that it's related to how the game parses numbers in different locales.

And with FasterThanLight vs fasterthanlight -- That's an issue caused by Steam's Cloud system. They claimed it was fixed years ago but apparently it wasn't retroactive, so if you had the game before ~2015 it would still cause perpetual problems. I'm sorry about that one, I was only just made aware that the Steam fix wasn't universal.

Please tell me the fix is a little more indepth than just adding that env variable in the start script?
[LINUX] Seven Feb 5, 2018 @ 9:59am 
thx for the heads up matthew! keep up the good work
< >
Showing 16-28 of 28 comments
Per page: 15 30 50

Date Posted: Jan 26, 2018 @ 3:30pm
Posts: 28