login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I assume you're talking about the Early Access version and not the demo version.
I added a new branch "audiotest" where I uploaded a version with the latest update to the audio system. Can you check if the problem persists with this version?
Branches are switched by rightclicking the game in the library -> Properties -> Betas. Steam should update the game then. If not, try restarting Steam.
Unfortunately the problem still persists.
I read up on initialization issues with the FMOD audio system but didn't come up with a clear solution. I posted on their forum to get more guidance on troubleshooting this, as so far I only see an error ERR_OUTPUT_INIT without any additional info, and past mentions of this didn't seem to lead to clear solutions. I saw a Kraken USB headset mentioned a few times having driver problems, but since you mentioned going through multiple audio outputs, I don't think that's the issue here.
For yourself I would recommend refunding the game through the Steam Support for now, as it's not clear if this will be solved, and if, when.
We could have an audio testing branch on the always available Demo version of the game, too.
Headphone out from motherboard / Gigabyte B550i Aorus Pro AX, Realtek ALC1220-VB codec
Audio pass through on USB microphone / Shure MV7
And a weird one, headphones or speakers through audio out on Xbox One controller, connected with the wireless adapter
There's no need for me to refund, I'll gladly have supported a dev who seems to care about his craft and is listening to feedback. :)
Thank you for the additional info.
The Player.log should be in this directory:
%UserProfile%\AppData\LocalLow\Crafting Legends\Death Trash
(you can paste it like that in the Windows explorer path display)
If you don't mind, running dxdiag once and saving its info to a text file might also be useful to us. ( https://support.microsoft.com/en-us/windows/open-and-run-dxdiag-exe-dad7792c-2ad5-f6cd-5a37-bf92228dfd85 )
The person from FMOD also mentioned it might be worth trying disabling the "Exclusive Mode" for each audio device in the Windows settings:
https://answers.microsoft.com/en-us/windows/forum/all/turning-off-exclusive-mode-in-windows-10-home/b724e917-aeec-4be4-b1aa-5ef655d85ded
(On my Windows 10 I needed to use the Control Panel -> Sound to get to the list of audio devices.)
I disabled audio output exclusive mode and tried both beta/normal branch and something seems to have gone right. Even re-enabling exclusive mode doesn't have an adverse effect on it.
I assume that Windows saves some additional info per audio device and that triggering that toggle made it save a new version of that data. But could be a lot of things. Don't know really what data Windows keeps about the devices and what settings info the drivers themselves save, too.
I'll keep this in mind when another person has the "no audio" problem.
There is indeed a problem with the audio system, which occured since we upgraded the audio system in the last months.
It occurs when one of the audio outputs on the system returns unexpected info and can't be initialized. While this is due to a local software issue or misconfiguration (old driver etc.) the bug here is that it would also fail initializing the audio system when one of the unused audio "devices" on the system, e.g. audio output towards HDMI monitor, failed to initialize.
As a temporary solution, if you're having no sound in Death Trash currently, try disabling the other audio outputs through the device properties.
We should also have a patch for this soon.