Инсталирайте Steam
вход
|
език
Опростен китайски (简体中文)
Традиционен китайски (繁體中文)
Японски (日本語)
Корейски (한국어)
Тайландски (ไทย)
Чешки (Čeština)
Датски (Dansk)
Немски (Deutsch)
Английски (English)
Испански — Испания (Español — España)
Испански — Латинска Америка (Español — Latinoamérica)
Гръцки (Ελληνικά)
Френски (Français)
Италиански (Italiano)
Индонезийски (Bahasa Indonesia)
Унгарски (Magyar)
Холандски (Nederlands)
Норвежки (Norsk)
Полски (Polski)
Португалски (Português)
Бразилски португалски (Português — Brasil)
Румънски (Română)
Руски (Русский)
Финландски (Suomi)
Шведски (Svenska)
Турски (Türkçe)
Виетнамски (Tiếng Việt)
Украински (Українська)
Докладване на проблем с превода
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.
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.
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.
thx alfabrot
So why does opengl whatever affect a gameplay thing anyway?
So it f-ing was a CAPITAL letters in filename/path issue.
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?