Ulrich26

Thanks Owen, Does the uiautomationcore.dll-tweak alter anything within fsx, I mean if it doesn't work I simply delete the uiautomationcore.dll file from the directory again and everything is as before? Ulrich

Hi, I want to try out the uiautomationcore.dll tweak in order to cure my system from random fsx CTD crashes. In my fsx.exe- directory, there is a file called ui.dll. Do I need to delete/ rename it before pasting the uiautomationcore.dll in the same directory or I just leave it as it is? Thanks, Ulrich

Actually, even if the Navdata have changed meanwhile, it shouldn't be a problem since the restriction is coded '-FL200' at the relevant waypoint. It means, the plane can cross the waypoint at or below the restricted altitude. However, the FMC does interpret the restriction as 'at' only which causes the problems to reach the subsequent altitudes and restrictions in this particular case. So, the FMC always interprets the 'at or below' restriction as an 'at' restriction which causes the problems. That's why I asked somebody from PMDG to comment on the subject to clarify this.

During other flights with STARs, I noticed that the FMC seems always to interpret an 'at or below FLxxx' restriction as 'at FLxxx', because PROF always puts 'HOLD FLxxx' to honour the particular restriction during the descent. Could someone from PMDG comment on this? Thanks, Ulrich

Peter/ Fatback did you experience similar behaviour with altitude restrictions during descent at other flights? Clark, I will post a screenshot asap, however, all settings were as per the tutorial and the HOLD 20000 was in magenta colour, so the FMC commanded it right from commencement of the descent from 37000 as a part of the vertical profile. Ulrich

Jonathan, the altitude at the FCP was set to 4000 to capture the GS. The altitude constraint at BLM was entered as '-FL200' at F-PLN. Will post a screenshot as soon as possible. Ulrich

Dear all, I have a question regarding the vertical logic of the PROF descent. I was flying a fully automated descent from FL370 to ILS14 of LSZH via BLM2G STAR and GIPOL Transition. The STAR requires the following descent: BLM at or below FL200, ZH677 at or above FL120, GIPOL at or above 7000 and then to the IAF of RW14 at 4000. When starting the descent, PROF logic put a HOLD 20000 constraint in order to honour BLM. The 20000 was reached well ahead of BLM. After Passing BLM at 20000, the descent continued to 12000, however, due to the PROF 20000 constraint at BLM, the 12000 at ZH677 could not be reached as well as the altitudes of the following waypoints, ending up in a situation that the MD11 was to high at the IAF and the GS couldn't be captured. If PROF would have immediately continued the descent after reaching 20000, BLM would have been passed at a much lower altitude (without even violating the -FL200 requirement at BLM), BLM would have been passes at an altitude of approx 13500 and the altitudes of all subsequent waypoints/ IAF could have been reached as per the STAR and the GS of ILS14 could have been captured as per the charts (I tried this by manually manipulating the altitudes at BLM in the FMC during flying the approach). Question: Why PROF interpretes -FL200 in the FMC to cross BLM at 20000 and not to cross below in order to reach the other waypoints properly? In this case, would it be better to enter the altitude of BLM with 12000 (just like ZH677, doesn't hurt the at or below requirement of BLM), to be on the safe side, taking into consideration that the descent will commence a little bit earlier? Thanks, Ulrich

Thanks Swissflyer/ Mosteen. To which video package from AOA are you referring (Ground Work, Flight Work, Line Work)? Ulrich

Dear all, I also have the known problem with the PMDG 737 NGX that A/T and VNAV disengages randomly when the TOGA button is pressed and the throttle axis is calibrated through FSUIPC. The general recommendation to cure the issue is to turn off the calibration of the throttle axis in FSUIPC. What is the easiest way to turn off the calibration in FSUIPC? Just to uncheck 'Send direct to FSUIPC calibration' and to check 'Send to FS as normal axis' on the 'Axis Assignment' tab? Thanks for your help, Ulrich

Dear all, I also have the known problem with the PMDG 737 NGX that A/T and VNAV disengages randomly when the TOGA button is pressed and the throttle axis is calibrated through FSUIPC. The general recommendation to cure the issue is to turn off the calibration of the throttle axis in FSUIPC. What is the easiest way to turn off the calibration in FSUIPC? Just to uncheck 'Send direct to FSUIPC calibration' and to check 'Send to FS as normal axis' on the 'Axis Assignment' tab? Thanks for your help, Ulrich

Hi, I have the following problem: I am sitting in the VC, the NGX is setup for flight, my FPS is in the range of 35. When I open Views- Instrument Panel- Forward Overhead Panel, it does not open and the FPS unrecoverably crash to below 10 with stuttering graphics. Further, the mouse cursor appears permanently on the screen as a flickering ring (like the ring which appears in Windows when it's loading something. I still can click knobs, switches etc. but the symbols for the mouse actions do not appear). This does not happen when I open other panels via Views- Instrument Panels, like CDU, Aft OH Panel etc. They open up normal and can be closed without impact on the graphics. I am running W7 64bit, i7 3930k @ 4.7 Ghz, GTX680 with 2 GB in widescreen configuration (5760x 1080), 16GB RAM. Anybody else suffered this issue? any thoughts about it? Thanks for your help, Ulrich