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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
Even from a "rule out the biggest possible causes first" perspective, using something like pasuspender and/or restarting the Pulse server before running the application are a much more appropriate as first steps for gathering information on what's relevant and what's not.
Back on topic, regarding the pilot portraits, they're consistently behaving for me with two generic pilots after a fresh install, which (assuming that it's a fresh install of the game being discussed) suggests that the Steam issue I linked to is not relevant.
The base sprites for 1hp unit portraits are in resources/resources.dat (its md5sum should be c199cd7a826184af092bdb13c1f453e9), but a quick look makes it appear that a script or a shader is providing the glitch effect on top of that.
er, what're your system specs?
The game outputs log.txt and error.txt that might include some relevant information to the ~/IntoTheBreach/ (that's in your home folder). Is there anything in those that appears relevant to the problems you're experiencing?
In particular, log.txt includes lines starting with "Opengl version" and "Using Opengl" that would be worth checking against the game's system requirements in case that's responsible for missing graphics.
There are better first troubleshooting steps - in almost all cases, pasuspender will reveal the same information that uninstalling Pulse will, but without changing the system state (although since the user hasn't indicated that they're running Pulse, this wouldn't be a good first step either).
I am not spreading misinformation. I am trying to let you know about something you seem to not be aware of. As one example, there is a Steam package for Fedora out there that marks the pulseaudio-libs as a dependency, and when uninstalling Pulseaudio without using additional options to prevent the removal of dependent packages, the package manager will mark Steam for removal as well.
Regardless of whether that's good packaging practice (in the above example, it should arguably be marking pulseaudio-libs as a dep instead), it's still a real-world situation that some users will be in. That's not a half-truth, that's an unfortunate pitfall to be wary of inadvertently sending strangers into when trying to help them.
Anyway, apologies to all for the thread derail.
Everything you need is to uninstall pulseaudio package, and then, if needed, correct volume levels through alsamixer(part of alsa tools, if not installed).
pulseaudio libraries =/= pulseaudio package. There are no hard dependencies for pulseaudio, and will never be. Because it's against POSIX standards, and core design principles of GNU/Linux. Stop spreading misinformation and fearmongering with half-truth.
Contrary to your claims pulseaudio is still the most common reason for sound problems in Linux. One, that should be checked first.
Pulseaudio IS a dependency of Gnome (In my case not of Steam but apparently it is in other distros).
fearmongering? Stop being paranoid. You just hate Pulseaudio because that's cool among GNU zealots.
What both of you do to contribute to Linux gaming? Porting games? Making holy war against Pulseaudio?
Why don't you REALLY try to help with the sound issue or any help at all with the graphic one (Like Cheeseness is doing), otherwise why don't you just stop with the off-topic diatribe.
You would be surprised, but I was actually trying to help, because pulseaudio actually being common cause of sound issues. It's not me, who started writing walls of text, because he saw the word pulseaudio.
To test, if pulse is being source of trouble, all is needed is to simply remove the package with one command, reboot and run the game.
If pulse is not the case, it might be reinstalled just as easy with one command.
It's a dependency of Gnome if you use Gnome It. Is. Not. That. Simple.
Also seems it's not that simple with Steam in Fedora, and i'm sure that there are other distros or Desktop Enviroments or installed packages by the user where it is not that simple.
You may want to help but you're not doing the right way. Why remove Pulseaudio package? Why not do sudo rm -rf for the files in the pulseaudio package?
Correct way to help, in case you missed it (just the relevant part):
I've pointed possible direction to troubleshoot. Which is highly likely scenario, judging the described symptoms.
It's details. And yes, that's one way to work around hard dependency rubbish. Might require to check install scripts, thou.
I don't advice this method, because I don't know about it. I rely on tools that I know, methods that work. ;)
Besides removing pulseaudio is the correct way. Because it guarantees that pulseaudio doesn't get in the way.
Thx for helping.
I didn't check checksum yet. *edit* md5sum was ok
I'm using Lenovo E495 laptop with Ryzen 3500u. My log files are found under ~/.var/app/com.valvesoftware.Steam/data/IntoTheBreach/. I'm using flatpak installation for steam.
There was nothing interesting on log.txt. About Opengl there was this:
Opengl version = 4.6 (Compatibility Profile) Mesa 20.3.1 (git-d90622910b)
Using Opengl 2.0 rendering path
error.log:
ERROR: ld.so: object '/home/USER/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/USER/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
[S_API] SteamAPI_Init(): Loaded '/home/USER/.local/share/Steam/linux64/steamclient.so' OK.
Setting breakpad minidump AppID = 111111
Steam_SetMinidumpSteamID: Caching Steam ID: 111111111111111 [API loaded no]