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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
The headset started outputting sound again when I did a 'Test' on the 'Headset' component of my bluetooth (the one for making calls, there is a separate stereo device 'Headphones'). I had a YouTube video playing in the background and the audio suddenly came through when the test sound was triggered.
Something is really jacked up with the way Asobo is using the Microsoft APIs for sound devices. I have hundreds of other Steam games in my library and many of them work flawlessly with this audio output.
I've also noticed that if you quit out of the game through the menu the sound instantly comes back, but if you Alt-F4 out of the MSFS window while it's loading the sound doesn't come back. So it seems like MSFS is hijacking something with the Windows sound system and isn't releasing whatever it's holding onto that messes everything up.
"Bluetooth comes with two connections. One for a phone, one for stereo sound. MSFS picks the wrong one. Go to control panel -> sound Look for Headset -> *your headset name* Hands Free AG Audio (note the difference: headset versus headphones). Disable the headset hands free one. Then try again."