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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
When you start on the runway or midair, this whole process is skipped. So your aircraft will start with a blank squawk code in the transponder, even though technically your flight already has a transponder assigned.
That's why the ATC asks you to reset your transponder. So you need to be familiar where the transponder is located. And enter the number manually. As soon as you enter it correctly, the ATC should stop bothering you with it.
Check out my 787-10 guide on troubleshooting the transponder. I know it's for a different aircraft as yours but the concept is generally the same across all aircrafts.
I understand this but I selected to start the flight in question from the ground. I don't know why it started me off in flight since that wasn't what I selected. It seems to be an issue with this plane specifically. It hasn't happened in any other plane after selecting a runway for departure. The transponder issue is less a problem but still of note since I shouldn't have to manually reset my transponder in midair when my flight has been logged and my transponder code has been squawked already. Normally I would agree that it was pilot error, and that I should just reset my transponder, unfortunately this seems to be a rather big bug since I selected a departure airport and runway in my pre-flight menu, yet it still started me out in midair instead of on the ground.
What I always do is I zoom in to the airport, and pick a gate dot and select it as a departure. Then I do the same with the arrival airport, zoom in and pick a gate dot and select it as an arrival.
Then I select which departure pattern and arrival/approach pattern as well. Making sure that everything is properly selected, the gate, both departing and arrival is still correct. Then just click Fly now.
That's exactly what I did, though. That's why I'm saying it was a bug.
I'll have to try that and see it it fixes the issue with the aircraft in question the next time I play.