FlightMB · 26-Июн-24 17:57(1 год назад, ред. 13-Июл-24 12:26)
PMDG 777-300ER для Microsoft Flight Simulator. Созданный экспертами для удовольствия как экспертов, так и обычных любителей, PMDG 777-300ER порадует новых энтузиастов авиасимуляторов, которые ищут свои первые настоящие впечатления от авиалайнера, и одновременно отвечает требовательным ожиданиям опытных игроков, ищущих ту глубину и аутентичность, которая только PMDG может предоставить. Боинг 777-300ER, легко признанный одним из самых успешных авиалайнеров, поднимавшихся в небо, является крупнейшим двухмоторным самолетом в эксплуатации авиакомпаний и обеспечивает операторам авиакомпаний огромную эффективность и пропускную способность, эффективно обслуживая дальние, средние и короткие маршруты. Избыточность, продуманная ремонтопригодность и высокие эксплуатационные показатели делают Боинг 777 фаворитом руководителей авиакомпаний, а его комфорт и просторный салон высоко оцениваются клиентами. Если вам нравится моделировать полеты по маршрутам, охватывающим весь мир, PMDG 777-300ER быстро станет вашим фаворитом в вашем ангаре для симуляторов, но вы обнаружите, что он одинаково хорошо подходит для более коротких региональных рейсов, когда в ваши планы симуляции вписывается что-то более короткое. . Или вы моделируете полеты на большие расстояния, используя инновационный механизм Auto-Cruise от PMDG, который гарантирует, что полет и ваша платформа моделирования останутся стабильными даже при выполнении полета со сжатием времени, чтобы сократить длинные сегменты круиза в соответствии с вашим личным графиком. Для дополнительной информации: https://pmdg.com/pmdg-777-300er-for-microsoft-flight-simulator/#product-tab-description Требования:
ОС: Windows 10/11.
Симулятор: Microsoft Flight Simulator.
Системные требования: такие же, как и у симулятора. Установка:
Перетащите файл в папку 'Сообщество'.
ВОТ И ВСЕ! Последнее обновление: 2.0.37
AIRAC входит: 2404
Всё хорошо. Видит рте. файлы pmdg aircraft 77w - config - flightplans
В этой пепке файл плана .rte есть, но FMC на подгружает его и полосы взлета не видит
Вы обновили свою версию до v2.0.34?
vado55661 писал(а):
86431358да, именно инсталлятор от разработчика
У меня нет этого. Я обновил файл до версии 2.0.34.
Попробуйте еще раз. *Чтобы обновить самолет, используйте Ops Center вместо загрузки отсюда.*
Загрузите программу обновления Ops Center здесь: https://www.mediafire.com/file/ho1ixjiaeo4cnyk/OpsCenterUpdater.zip/file Щелкните правой кнопкой мыши OpsCenterUpdater.exe и выберите «Запуск от имени администратора». Это позволит загрузить и установить все необходимые файлы.
Если кому-то интересно, обновление до 2.0.36 через OpsCenter работает без проблем. Тем не менее, у кого-нибудь еще есть серьезные проблемы с работой двигателя на крейсерской высоте на этом самолете? Я решил совершить испытательный полет этого самолета (от UUEE до UHPP), и даже на максимальной мощности (CON) он не смог приблизиться к установленной FMS крейсерской скорости 0,840 Маха на эшелоне FL310?
Edit: С обновлением .36 и точно такой же нагрузкой самолет поддерживает FL330/M .840.
Если кому-то интересно, обновление до 2.0.36 через OpsCenter работает без проблем.
Тем не менее, у кого-нибудь еще есть серьезные проблемы с работой двигателя на крейсерской высоте на этом самолете? Я решил совершить испытательный полет этого самолета (от UUEE до UHPP), и даже на максимальной мощности (CON) он не смог приблизиться к установленной FMS крейсерской скорости 0,840 Маха на эшелоне FL310?
У меня такой проблемы не было, но на CRZ я не смог снизить скорость через FMC
Я не пробовал после обновления.
86445697Если кому-то интересно, обновление до 2.0.36 через OpsCenter работает без проблем. Тем не менее, у кого-нибудь еще есть серьезные проблемы с работой двигателя на крейсерской высоте на этом самолете? Я решил совершить испытательный полет этого самолета (от UUEE до UHPP), и даже на максимальной мощности (CON) он не смог приблизиться к установленной FMS крейсерской скорости 0,840 Маха на эшелоне FL310?
Edit: С обновлением .36 и точно такой же нагрузкой самолет поддерживает FL330/M .840.
Кажется, здесь все в порядке. Какой у вас был TOW и сколько он стоил, когда вы заметили эту проблему.
Показывали ли N1 обоих двигателей достаточную тягу? edit: Я рад, что теперь это работает для вас.
samsarak писал(а):
86445720
Цитата:
Если кому-то интересно, обновление до 2.0.36 через OpsCenter работает без проблем.
Тем не менее, у кого-нибудь еще есть серьезные проблемы с работой двигателя на крейсерской высоте на этом самолете? Я решил совершить испытательный полет этого самолета (от UUEE до UHPP), и даже на максимальной мощности (CON) он не смог приблизиться к установленной FMS крейсерской скорости 0,840 Маха на эшелоне FL310?
У меня такой проблемы не было, но на CRZ я не смог снизить скорость через FMC
Я не пробовал после обновления.
Вы пробовали изменить через страницу CRZ в FMC? Любая картинка поможет.
Пробовали менять через окно скорости?
86445697Если кому-то интересно, обновление до 2.0.36 через OpsCenter работает без проблем. Тем не менее, у кого-нибудь еще есть серьезные проблемы с работой двигателя на крейсерской высоте на этом самолете? Я решил совершить испытательный полет этого самолета (от UUEE до UHPP), и даже на максимальной мощности (CON) он не смог приблизиться к установленной FMS крейсерской скорости 0,840 Маха на эшелоне FL310?
Edit: С обновлением .36 и точно такой же нагрузкой самолет поддерживает FL330/M .840.
Кажется, здесь все в порядке. Какой у вас был TOW и сколько он стоил, когда вы заметили эту проблему.
Показывали ли N1 обоих двигателей достаточную тягу? edit: Я рад, что теперь это работает для вас.
К сожалению, эта ошибка снова возникла через некоторое время на крейсерской высоте и после первых двух запланированных наборов высоты (до эшелона FL350). Может это и совпадение, но оба раза я это замечал после израсходования топлива в фюзеляжном топливном баке. В каждом случае, после возникновения этой ошибки, даже при полной (CON) тяге и обоих дросселях на максимуме, самолет мог ускориться обратно только примерно до 0,74М (на эшелоне FL350) и 0,79 (на эшелоне FL310). TOW: ~253t (203.6 ZFW)
FMC Rec FL/FMC OPT FL - FL350
FMC CRZ - LRC - M.840 (320kn IAS)
Попутный ветер: постоянный ~60kn
86445697Если кому-то интересно, обновление до 2.0.36 через OpsCenter работает без проблем. Тем не менее, у кого-нибудь еще есть серьезные проблемы с работой двигателя на крейсерской высоте на этом самолете? Я решил совершить испытательный полет этого самолета (от UUEE до UHPP), и даже на максимальной мощности (CON) он не смог приблизиться к установленной FMS крейсерской скорости 0,840 Маха на эшелоне FL310?
Edit: С обновлением .36 и точно такой же нагрузкой самолет поддерживает FL330/M .840.
Кажется, здесь все в порядке. Какой у вас был TOW и сколько он стоил, когда вы заметили эту проблему.
Показывали ли N1 обоих двигателей достаточную тягу? edit: Я рад, что теперь это работает для вас.
К сожалению, эта ошибка снова возникла через некоторое время на крейсерской высоте и после первых двух запланированных наборов высоты (до эшелона FL350). Может это и совпадение, но оба раза я это замечал после израсходования топлива в фюзеляжном топливном баке. В каждом случае, после возникновения этой ошибки, даже при полной (CON) тяге и обоих дросселях на максимуме, самолет мог ускориться обратно только примерно до 0,74М (на эшелоне FL350) и 0,79 (на эшелоне FL310). TOW: ~253t (203.6 ZFW)
FMC Rec FL/FMC OPT FL - FL350
FMC CRZ - LRC - M.840 (320kn IAS)
Попутный ветер: постоянный ~60kn
Прежде всего. Это не ошибка в самолете, я лично летал выше.
Во-вторых, я знаю, что пошло не так с вашим рейсом. Это называется "coffin corner"
Требуется изображение вашей страницы ND, PFD и PERF INIT и VNAV CRZ. Мне также нужно проверить, подняты ли у вас шасси.
Посмотрите на следующее: Желтые линии на вашей скоростной ленте будут очень близко друг к другу, а это означает, что вы слишком тяжелы, чтобы подняться выше. Также приходилось следить за профилем набора высоты в режиме VNAV или вручную.
Вы можете подождать и полететь на более стабильной высоте и набрать высоту, как только позволят характеристики набора высоты. Также возможно, что ваш "cost index" был выше, чем позволяет самолет, и вы, возможно, также поднимались на неэкономичной скорости. Также важно заключается в том, что вы столкнулись с попутным ветром скоростью 60 узлов, который резко снизил бы ваши возможности набора высоты из-за уменьшения вашего IAS. Вы использовали режим FLCH? Это бы не сработало, но можно было наблюдать некоторую разницу в высоте звука. Вы использовали Navigraph для планирования полета и точно начали подниматься по ступеням в соответствии с OFP?
Во-вторых, я знаю, что пошло не так с вашим рейсом. Это называется "coffin corner"
Since I don't want my half-forgotten high school Russian to make me come across as snarky or insulting (and not just as the intended "just confused as hell") , I'll respond this time around in English (you and everyone else here keep speaking Russian, since I have no problems reading the language, it's just that the grammar keeps causing me issues when I try speaking/writing).
Anyway, unless the flight instruments and FMC are misleading me badly, it's neither a coffin corner, nor a mis-trimmed aircraft (as there is no deflection on the control surfaces and the AOA was normal to have some sort of extra drag causing issues). Just in case, I checked other bits of suggested troubleshooting on the PMDG forums and it's neither an abnormally high OAT that's affecting the engines, nor it's a case of the wind suddenly shifting (which tends to happen from time to time with the MSFS weather model) pushing the plane into a stall. I even disconnected my throttle quadrant to ensure that it wasn't overriding the throttle for some reason (ie because of jitter) That's why I'm perplexed as hell about what else may be causing things (besides me making some sort of user error that I can't identify). At any rate, I've set up a new UHSS to UUEE flight to try and replicate this behaviour yet again, so I'll edit this post with the screenshots when this bug reoccurs, along with the SimBrief flight plan I'm using.
Edit: And here it is yet again - unable to maintain speed at altitude, in steady (and relatively low speed) wind despite the FMC and SimBrief plan both suggesting FL340 and .84M LRC setting. No inadvertent flaps, no weird trimming causing the AP to try and compensate with the control surfaces, no rapid wind shifts, no insane angle of attack. The end result is that with a supposedly sufficient reserve in performance, the plane could only maintain the speed in the screenshot at max continuous power. Ah, because if forgot to do a screenshot of PERF - 208.9t ZFW / 275.5t Gross / 67.6t Fuel/ CRZ FL340 / CRZ CG 7.5 / CI 85
Подтверждаю - у меня тоже не видит - всё обновлено, в папке файл есть, но FMC пишет что нет в базе данных Удалось решить проблему?
Всё работает. Для этого заполняем Икао коды портов, нажимаем route request , затем когда подгрузит ссылку, жмём load и наконец когда подсветится кнопка exec нажимаем для подтверждения. У меня это работало как на релизной версии , так и на крайней , утром проверял.
Во-вторых, я знаю, что пошло не так с вашим рейсом. Это называется "coffin corner"
Since I don't want my half-forgotten high school Russian to make me come across as snarky or insulting (and not just as the intended "just confused as hell") , I'll respond this time around in English (you and everyone else here keep speaking Russian, since I have no problems reading the language, it's just that the grammar keeps causing me issues when I try speaking/writing).
Anyway, unless the flight instruments and FMC are misleading me badly, it's neither a coffin corner, nor a mis-trimmed aircraft (as there is no deflection on the control surfaces and the AOA was normal to have some sort of extra drag causing issues). Just in case, I checked other bits of suggested troubleshooting on the PMDG forums and it's neither an abnormally high OAT that's affecting the engines, nor it's a case of the wind suddenly shifting (which tends to happen from time to time with the MSFS weather model) pushing the plane into a stall. I even disconnected my throttle quadrant to ensure that it wasn't overriding the throttle for some reason (ie because of jitter) That's why I'm perplexed as hell about what else may be causing things (besides me making some sort of user error that I can't identify). At any rate, I've set up a new UHSS to UUEE flight to try and replicate this behaviour yet again, so I'll edit this post with the screenshots when this bug reoccurs, along with the SimBrief flight plan I'm using.
Edit: And here it is yet again - unable to maintain speed at altitude, in steady (and relatively low speed) wind despite the FMC and SimBrief plan both suggesting FL340 and .84M LRC setting. No inadvertent flaps, no weird trimming causing the AP to try and compensate with the control surfaces, no rapid wind shifts, no insane angle of attack. The end result is that with a supposedly sufficient reserve in performance, the plane could only maintain the speed in the screenshot at max continuous power. Ah, because if forgot to do a screenshot of PERF - 208.9t ZFW / 275.5t Gross / 67.6t Fuel/ CRZ FL340 / CRZ CG 7.5 / CI 85
English works great for me as well, the forums still state to communicate in Russian though, so you know.
Okay so, there are 4 things I want to talk about that I also verified with a fellow of mine who flies the Boeing 777. So 1st thing is that although you are not overweight at all but you are definitely heavy (look at the stall buffet). That 'stall buffet' usually hovers around 240 kts, but yours is at 260 kts. So that is one thing. 2nd, your optimal altitude is lower by 300 ft which MIGHT help the aircraft very slightly creep its speed up to the cruise speed. 3rd thing, which is very important is that, as a pilot it is your job to monitor climb, cruise and everything in between and around. You most likely let the VNAV handle the climb which struggled in maintaining the speed and it consequently caused the speed to decrease and VNAV just levelled off at the set altitude and now the speed is lower than expected and not increasing (also your pitch is ever so slightly higher than in normal cruise condition; usually 2-3 degrees). Using V/S is something that really helps when you are climbing if the plane struggles to maintain the expected speed. The Boeing 777 is a slippery aircraft which is harder to manage during approach and the same goes when you are climbing, although then it is not slippery but rather sluggish which it typically is not due to huge engines. 4th thing is that your EICAS shows TAT as -15°C and approximating it to SAT (using this: TAT= SAT + (TAS/100)^2) it turns out to be ~ -38°C which is higher than what it usually is and that can explain the degradation in your engine thrust. Also the OFP you sent has the temperature being -45°C instead of -38°C, which is much more like it. Watch a few cruise videos and refer to EICAS and the PFD. You will see TAT being lower than -15°C. Happy flying and this is actually great for all, you and I, and anyone really can learn so much even though we could be veterans in aviation or any other subject for that matter. *NOTE:* Your problem seems like a climb management issue but anything can happen so: If you have FSUIPC installed then remove it, it causes all sorts of problems with PMDG aircraft. According to PMDG: It specially messes the climb performance by lowering the flaps without the aircraft realising and hence the FCTL shows the flaps fully retracted but they are not. I know of 2 people who had this issue and removing FSUIPC solve their climb performance issue. Edit: I forgot to add that once in FSX I was flying PMDG 747-8i for fun, with some healthy amount of load. I let the airplane climb on VNAV to FL350 and failed to notice that the airspeed had dropped by around 20-30 kts and no matter how much thrust I added manually it would just not go up and got stuck there, so I asked for a lower flight level and gained speed while descending and then started a very shallow climb of around 500-700 ft/min. Only then was I able to maintain that speed. This enabled me to learn a lot about energy management that mostly helps in non-normal operations and also in normal operations.
Во-вторых, я знаю, что пошло не так с вашим рейсом. Это называется "coffin corner"
Since I don't want my half-forgotten high school Russian to make me come across as snarky or insulting (and not just as the intended "just confused as hell") , I'll respond this time around in English (you and everyone else here keep speaking Russian, since I have no problems reading the language, it's just that the grammar keeps causing me issues when I try speaking/writing).
Anyway, unless the flight instruments and FMC are misleading me badly, it's neither a coffin corner, nor a mis-trimmed aircraft (as there is no deflection on the control surfaces and the AOA was normal to have some sort of extra drag causing issues). Just in case, I checked other bits of suggested troubleshooting on the PMDG forums and it's neither an abnormally high OAT that's affecting the engines, nor it's a case of the wind suddenly shifting (which tends to happen from time to time with the MSFS weather model) pushing the plane into a stall. I even disconnected my throttle quadrant to ensure that it wasn't overriding the throttle for some reason (ie because of jitter) That's why I'm perplexed as hell about what else may be causing things (besides me making some sort of user error that I can't identify). At any rate, I've set up a new UHSS to UUEE flight to try and replicate this behaviour yet again, so I'll edit this post with the screenshots when this bug reoccurs, along with the SimBrief flight plan I'm using.
Edit: And here it is yet again - unable to maintain speed at altitude, in steady (and relatively low speed) wind despite the FMC and SimBrief plan both suggesting FL340 and .84M LRC setting. No inadvertent flaps, no weird trimming causing the AP to try and compensate with the control surfaces, no rapid wind shifts, no insane angle of attack. The end result is that with a supposedly sufficient reserve in performance, the plane could only maintain the speed in the screenshot at max continuous power. Ah, because if forgot to do a screenshot of PERF - 208.9t ZFW / 275.5t Gross / 67.6t Fuel/ CRZ FL340 / CRZ CG 7.5 / CI 85
English works great for me as well, the forums still state to communicate in Russian though, so you know.
Okay so, there are 4 things I want to talk about that I also verified with a fellow of mine who flies the Boeing 777. So 1st thing is that although you are not overweight at all but you are definitely heavy (look at the stall buffet). That 'stall buffet' usually hovers around 240 kts, but yours is at 260 kts. So that is one thing. 2nd, your optimal altitude is lower by 300 ft which MIGHT help the aircraft very slightly creep its speed up to the cruise speed. 3rd thing, which is very important is that, as a pilot it is your job to monitor climb, cruise and everything in between and around. You most likely let the VNAV handle the climb which struggled in maintaining the speed and it consequently caused the speed to decrease and VNAV just levelled off at the set altitude and now the speed is lower than expected and not increasing (also your pitch is ever so slightly higher than in normal cruise condition; usually 2-3 degrees). Using V/S is something that really helps when you are climbing if the plane struggles to maintain the expected speed. The Boeing 777 is a slippery aircraft which is harder to manage during approach and the same goes when you are climbing, although then it is not slippery but rather sluggish which it typically is not due to huge engines. 4th thing is that your EICAS shows TAT as -15°C and approximating it to SAT (using this: TAT= SAT + (TAS/100)^2) it turns out to be ~ -38°C which is higher than what it usually is and that can explain the degradation in your engine thrust. Also the OFP you sent has the temperature being -45°C instead of -38°C, which is much more like it. Watch a few cruise videos and refer to EICAS and the PFD. You will see TAT being lower than -15°C. Happy flying and this is actually great for all, you and I, and anyone really can learn so much even though we could be veterans in aviation or any other subject for that matter. *NOTE:* Your problem seems like a climb management issue but anything can happen so: If you have FSUIPC installed then remove it, it causes all sorts of problems with PMDG aircraft. According to PMDG: It specially messes the climb performance by lowering the flaps without the aircraft realising and hence the FCTL shows the flaps fully retracted but they are not. I know of 2 people who had this issue and removing FSUIPC solve their climb performance issue. Edit: I forgot to add that once in FSX I was flying PMDG 747-8i for fun, with some healthy amount of load. I let the airplane climb on VNAV to FL350 and failed to notice that the airspeed had dropped by around 20-30 kts and no matter how much thrust I added manually it would just not go up and got stuck there, so I asked for a lower flight level and gained speed while descending and then started a very shallow climb of around 500-700 ft/min. Only then was I able to maintain that speed. This enabled me to learn a lot about energy management that mostly helps in non-normal operations and also in normal operations.
All valid points, except that I just discovered the culprit - for some reason using the SimBrief dispatch data directly (that you first request via the tablet, before you can use it via request on the FMC RTE page), that now allows you to click a "Load Fuel / Load Payload" to set up your plane for flight. Not sure what gets bugged by using that as intended, but if I use the options - the behaviour I mentioned earlier reoccurs regardless of temperature, wind conditions or even supposed load state of the plane. Furthermore, that bug also meant that even if I changed the payload to 0 in flight and then switched the weather to "perfect and cold" (to see if it'd affect the plane's behaviour). Using the SimBrief .RTE as "in the olden days" and manually inputting the ZFW and fuel load and everything's working as intended. Hell, I'm currently doing a Dubai to Berlin run and even close to max ZFW and in hot OAT, the 777's maintaining CRZ as it's supposed to do.
tl;dr: It was SimBrief's (apparently buggy) integration in the FMC that caused the problem Кроме того, извините всех, что мне пришлось ненадолго переключиться на английский, но мои навыки русского языка просто не соответствовали этой проблеме, с которой я столкнулся с PMDG777.
Подтверждаю - у меня тоже не видит - всё обновлено, в папке файл есть, но FMC пишет что нет в базе данных Удалось решить проблему?
нет, не удалось. Сырой самоль((( или они переделали экспорт флайтплана
Вот Решение: In case you already did a flight with the PMDG 777-300ER, delete the “Navdata” folder first, located here:
• Steam version: C:\Users\USERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\pmdg-aircraft-77w\work
• Microsoft Store version: C:\Users\USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-77w\work Потом обновляйте NavData UPD. Блин, я не о том, но пусть остается и это
На счет флайтплана тоже здесь ищите : C:\Users\USERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\pmdg-aircraft-77w\work\Flightplans
Во-вторых, я знаю, что пошло не так с вашим рейсом. Это называется "coffin corner"
Since I don't want my half-forgotten high school Russian to make me come across as snarky or insulting (and not just as the intended "just confused as hell") , I'll respond this time around in English (you and everyone else here keep speaking Russian, since I have no problems reading the language, it's just that the grammar keeps causing me issues when I try speaking/writing).
Anyway, unless the flight instruments and FMC are misleading me badly, it's neither a coffin corner, nor a mis-trimmed aircraft (as there is no deflection on the control surfaces and the AOA was normal to have some sort of extra drag causing issues). Just in case, I checked other bits of suggested troubleshooting on the PMDG forums and it's neither an abnormally high OAT that's affecting the engines, nor it's a case of the wind suddenly shifting (which tends to happen from time to time with the MSFS weather model) pushing the plane into a stall. I even disconnected my throttle quadrant to ensure that it wasn't overriding the throttle for some reason (ie because of jitter) That's why I'm perplexed as hell about what else may be causing things (besides me making some sort of user error that I can't identify). At any rate, I've set up a new UHSS to UUEE flight to try and replicate this behaviour yet again, so I'll edit this post with the screenshots when this bug reoccurs, along with the SimBrief flight plan I'm using.
Edit: And here it is yet again - unable to maintain speed at altitude, in steady (and relatively low speed) wind despite the FMC and SimBrief plan both suggesting FL340 and .84M LRC setting. No inadvertent flaps, no weird trimming causing the AP to try and compensate with the control surfaces, no rapid wind shifts, no insane angle of attack. The end result is that with a supposedly sufficient reserve in performance, the plane could only maintain the speed in the screenshot at max continuous power. Ah, because if forgot to do a screenshot of PERF - 208.9t ZFW / 275.5t Gross / 67.6t Fuel/ CRZ FL340 / CRZ CG 7.5 / CI 85
English works great for me as well, the forums still state to communicate in Russian though, so you know.
Okay so, there are 4 things I want to talk about that I also verified with a fellow of mine who flies the Boeing 777. So 1st thing is that although you are not overweight at all but you are definitely heavy (look at the stall buffet). That 'stall buffet' usually hovers around 240 kts, but yours is at 260 kts. So that is one thing. 2nd, your optimal altitude is lower by 300 ft which MIGHT help the aircraft very slightly creep its speed up to the cruise speed. 3rd thing, which is very important is that, as a pilot it is your job to monitor climb, cruise and everything in between and around. You most likely let the VNAV handle the climb which struggled in maintaining the speed and it consequently caused the speed to decrease and VNAV just levelled off at the set altitude and now the speed is lower than expected and not increasing (also your pitch is ever so slightly higher than in normal cruise condition; usually 2-3 degrees). Using V/S is something that really helps when you are climbing if the plane struggles to maintain the expected speed. The Boeing 777 is a slippery aircraft which is harder to manage during approach and the same goes when you are climbing, although then it is not slippery but rather sluggish which it typically is not due to huge engines. 4th thing is that your EICAS shows TAT as -15°C and approximating it to SAT (using this: TAT= SAT + (TAS/100)^2) it turns out to be ~ -38°C which is higher than what it usually is and that can explain the degradation in your engine thrust. Also the OFP you sent has the temperature being -45°C instead of -38°C, which is much more like it. Watch a few cruise videos and refer to EICAS and the PFD. You will see TAT being lower than -15°C. Happy flying and this is actually great for all, you and I, and anyone really can learn so much even though we could be veterans in aviation or any other subject for that matter. *NOTE:* Your problem seems like a climb management issue but anything can happen so: If you have FSUIPC installed then remove it, it causes all sorts of problems with PMDG aircraft. According to PMDG: It specially messes the climb performance by lowering the flaps without the aircraft realising and hence the FCTL shows the flaps fully retracted but they are not. I know of 2 people who had this issue and removing FSUIPC solve their climb performance issue. Edit: I forgot to add that once in FSX I was flying PMDG 747-8i for fun, with some healthy amount of load. I let the airplane climb on VNAV to FL350 and failed to notice that the airspeed had dropped by around 20-30 kts and no matter how much thrust I added manually it would just not go up and got stuck there, so I asked for a lower flight level and gained speed while descending and then started a very shallow climb of around 500-700 ft/min. Only then was I able to maintain that speed. This enabled me to learn a lot about energy management that mostly helps in non-normal operations and also in normal operations.
All valid points, except that I just discovered the culprit - for some reason using the SimBrief dispatch data directly (that you first request via the tablet, before you can use it via request on the FMC RTE page), that now allows you to click a "Load Fuel / Load Payload" to set up your plane for flight. Not sure what gets bugged by using that as intended, but if I use the options - the behaviour I mentioned earlier reoccurs regardless of temperature, wind conditions or even supposed load state of the plane. Furthermore, that bug also meant that even if I changed the payload to 0 in flight and then switched the weather to "perfect and cold" (to see if it'd affect the plane's behaviour). Using the SimBrief .RTE as "in the olden days" and manually inputting the ZFW and fuel load and everything's working as intended. Hell, I'm currently doing a Dubai to Berlin run and even close to max ZFW and in hot OAT, the 777's maintaining CRZ as it's supposed to do.
tl;dr: It was SimBrief's (apparently buggy) integration in the FMC that caused the problem Кроме того, извините всех, что мне пришлось ненадолго переключиться на английский, но мои навыки русского языка просто не соответствовали этой проблеме, с которой я столкнулся с PMDG777.
Well, this is new for me. Since I, of course, use SimBrief integration and everything works like a charm in various configurations and extreme temperatures. Tried reinstalling the plane?
Во-вторых, я знаю, что пошло не так с вашим рейсом. Это называется "coffin corner"
Since I don't want my half-forgotten high school Russian to make me come across as snarky or insulting (and not just as the intended "just confused as hell") , I'll respond this time around in English (you and everyone else here keep speaking Russian, since I have no problems reading the language, it's just that the grammar keeps causing me issues when I try speaking/writing).
Anyway, unless the flight instruments and FMC are misleading me badly, it's neither a coffin corner, nor a mis-trimmed aircraft (as there is no deflection on the control surfaces and the AOA was normal to have some sort of extra drag causing issues). Just in case, I checked other bits of suggested troubleshooting on the PMDG forums and it's neither an abnormally high OAT that's affecting the engines, nor it's a case of the wind suddenly shifting (which tends to happen from time to time with the MSFS weather model) pushing the plane into a stall. I even disconnected my throttle quadrant to ensure that it wasn't overriding the throttle for some reason (ie because of jitter) That's why I'm perplexed as hell about what else may be causing things (besides me making some sort of user error that I can't identify). At any rate, I've set up a new UHSS to UUEE flight to try and replicate this behaviour yet again, so I'll edit this post with the screenshots when this bug reoccurs, along with the SimBrief flight plan I'm using.
Edit: And here it is yet again - unable to maintain speed at altitude, in steady (and relatively low speed) wind despite the FMC and SimBrief plan both suggesting FL340 and .84M LRC setting. No inadvertent flaps, no weird trimming causing the AP to try and compensate with the control surfaces, no rapid wind shifts, no insane angle of attack. The end result is that with a supposedly sufficient reserve in performance, the plane could only maintain the speed in the screenshot at max continuous power. Ah, because if forgot to do a screenshot of PERF - 208.9t ZFW / 275.5t Gross / 67.6t Fuel/ CRZ FL340 / CRZ CG 7.5 / CI 85
English works great for me as well, the forums still state to communicate in Russian though, so you know.
Okay so, there are 4 things I want to talk about that I also verified with a fellow of mine who flies the Boeing 777. So 1st thing is that although you are not overweight at all but you are definitely heavy (look at the stall buffet). That 'stall buffet' usually hovers around 240 kts, but yours is at 260 kts. So that is one thing. 2nd, your optimal altitude is lower by 300 ft which MIGHT help the aircraft very slightly creep its speed up to the cruise speed. 3rd thing, which is very important is that, as a pilot it is your job to monitor climb, cruise and everything in between and around. You most likely let the VNAV handle the climb which struggled in maintaining the speed and it consequently caused the speed to decrease and VNAV just levelled off at the set altitude and now the speed is lower than expected and not increasing (also your pitch is ever so slightly higher than in normal cruise condition; usually 2-3 degrees). Using V/S is something that really helps when you are climbing if the plane struggles to maintain the expected speed. The Boeing 777 is a slippery aircraft which is harder to manage during approach and the same goes when you are climbing, although then it is not slippery but rather sluggish which it typically is not due to huge engines. 4th thing is that your EICAS shows TAT as -15°C and approximating it to SAT (using this: TAT= SAT + (TAS/100)^2) it turns out to be ~ -38°C which is higher than what it usually is and that can explain the degradation in your engine thrust. Also the OFP you sent has the temperature being -45°C instead of -38°C, which is much more like it. Watch a few cruise videos and refer to EICAS and the PFD. You will see TAT being lower than -15°C. Happy flying and this is actually great for all, you and I, and anyone really can learn so much even though we could be veterans in aviation or any other subject for that matter. *NOTE:* Your problem seems like a climb management issue but anything can happen so: If you have FSUIPC installed then remove it, it causes all sorts of problems with PMDG aircraft. According to PMDG: It specially messes the climb performance by lowering the flaps without the aircraft realising and hence the FCTL shows the flaps fully retracted but they are not. I know of 2 people who had this issue and removing FSUIPC solve their climb performance issue. Edit: I forgot to add that once in FSX I was flying PMDG 747-8i for fun, with some healthy amount of load. I let the airplane climb on VNAV to FL350 and failed to notice that the airspeed had dropped by around 20-30 kts and no matter how much thrust I added manually it would just not go up and got stuck there, so I asked for a lower flight level and gained speed while descending and then started a very shallow climb of around 500-700 ft/min. Only then was I able to maintain that speed. This enabled me to learn a lot about energy management that mostly helps in non-normal operations and also in normal operations.
All valid points, except that I just discovered the culprit - for some reason using the SimBrief dispatch data directly (that you first request via the tablet, before you can use it via request on the FMC RTE page), that now allows you to click a "Load Fuel / Load Payload" to set up your plane for flight. Not sure what gets bugged by using that as intended, but if I use the options - the behaviour I mentioned earlier reoccurs regardless of temperature, wind conditions or even supposed load state of the plane. Furthermore, that bug also meant that even if I changed the payload to 0 in flight and then switched the weather to "perfect and cold" (to see if it'd affect the plane's behaviour). Using the SimBrief .RTE as "in the olden days" and manually inputting the ZFW and fuel load and everything's working as intended. Hell, I'm currently doing a Dubai to Berlin run and even close to max ZFW and in hot OAT, the 777's maintaining CRZ as it's supposed to do.
tl;dr: It was SimBrief's (apparently buggy) integration in the FMC that caused the problem Кроме того, извините всех, что мне пришлось ненадолго переключиться на английский, но мои навыки русского языка просто не соответствовали этой проблеме, с которой я столкнулся с PMDG777.
Well, this is new for me. Since I, of course, use SimBrief integration and everything works like a charm in various configurations and extreme temperatures. Tried reinstalling the plane?
Yup, clean install on several machines with variations of the same abnormal behaviour. Eventually, it turned out that the root cause wasn't even in the sim itself, nor the PMDG module (with me blocking SimBrief turning out to be a placebo, proving that correlation=/= causation yet again), but a ChatGPT instance that we use at work (or rather, that we are forced to have open in the corner, 'cause it's not particularly useful 'cause our own "effective managers" bought hard into this AI hype), that's causing random latency spikes. When those happen in the exact wrong moment cause the PMDG module to partially freeze (with the previously mentioned odd behaviour). One week of testing later things seem to be fine now even on long-haul (MUHA to UUEE for example) flights not experiencing that abnormal behaviour.
Не управляется с клавиатуры (точнее не работают элероны). Это проблема с пираткой или на моей стороне? Upd
Оказывается самолет управляется, но нет анимации штурвала и элеронов.
