tipitout

I have had panel freezes after creating flightplans using the Simbrief menu within the simulator, then using the Simbrief import function on the flight selection screen. If I recall correctly, the freeze would happen after loading into the flight, then importing the Simbrief data on the EFB (PMDG 737 series). It doesn't happen if I create the flight via the Simbrief website, then just load into the flight without using the import button. I can also use the seperate Simbrief downloader without any issues. Edit: I am using MSFS2020.

What traffic packages, if any, do you have? At least one installs additional afcads which may conflict with others.

I seem to recall some developers doing this in order to stop default ground services vehicles appearing at the gates. I could be wrong, though.

Thanks for that. I have had this issue with P3D, so will try this when I next install it (currently only using FSX).

Which VABB is it? Is it from Thai Creations? At least some of their customers are reporting problems which sound similar to yours.

Glad to be of help, but did removing them or changing the file extension actually solve the problem you were having? If you get the same problem elsewhere, a quick and dirty test is to deselect the MyTraffic entry in the scenery library. If that works, then re-enable it and do as above. I have had the same problem at many payware airports, and a conflicting MyTraffic entry has always been the cause.

Are you running any version of My Traffic? That contains enhancements for many default airports. If so, search within its folder for any files containing the ICAO code of the problem airport. If you find any, back them up, then delete them or change the file extension to . BAK, for example.

Can we please have a screenshot taken at the TOD point, showing the MCP and main displays?

Also check out the VIB indications. Personally, I enjoyed the joke. In fact, given RSR's track record, I expected to find one here.

I just re-installed Aerosoft Maldives-X this morning, and flew the PMDG 777 out of there. I'm now suspect no. 1. Lets hope they don't travel back in time and catch me when I land in Kai Tak.

If MCE can be persuaded to support FSLabs Concorde, it would be worth an upgrade fee. How about it, FS++?

You can keep controllers enabled in FSX, just make sure that whatever individual axes you assign through FSUIPC are deleted from the FSX controls menu to avoid conflicts. This might be the problem with throttle lever one moving both throttles, if FSX has it asssigned simply as "throttle axis," as that will move all throttles together. The same goes for any joystic or throttle buttons to which you assign key presses through FSUIPC. Regarding the condition levers, if I recall correctly (I'm not at my FSX PC right now), you are looking for something like "propeller control" in FSUIPC for one axis to controll both at the same time, or "propeller 1/2" etc to set them individually. There are also options called "Axis prop (1/2 etc) set." Don't ask me what the difference is. Have a look at the FSUIPC documentation and read on how to set up profiles for individual aircraft types - and even individual paints. This way your controls can be set appropriately for every aircraft you use. The Majestic documentation explains how to use their set-up utility to calibrate your controls. If you get stuck, try the Majestic and FSUIPC fora, as well as back here.

I second the call for a Trident.

Does the flightplanner take account of one-way airways?

Not really. Lots of adults, male and female, enjoy watching AVG on their screens.

To get back on topic, the Flight1 registry repair tool might help here. It usually comes up in discussions about misaligned localisers. Of course, your registry might be fine, but it won't hurt to try.

I sometimes get the same problem, and EZDok seems to be at the root of it. Try pressing 2 on your number pad, followed by a minor adjustment of your viewpoint (perhaps zoom out or in, then put it back where it was), then press 2 again to re-save the camera. That usually works for me. When it doesn't, I just delete the offending camera and start again.

While cruising during a recent flight, I decided to pass the time by looking at the failures menu in the FMC. To my surprise, I saw "FAILED: 1" indicated. Upon further investigation, it was apparently an autothrottle failure, with the FMC indicating "AT INOP." However, the autothrottle remained engaged and continued to operate normally. I then tried flipping the AT switch off and on, and changing vertical modes, but it just behaved as if there was no failure. After landing normally, I rebooted my PC and started another flight. This time I programed an AT failure to occur after 30 seconds. When nothing happened, I re-checked the FMC to find, once again, that it thought the failure had occured. As before, the AT remained engaged and behaved normally. Both flights involved the 800WL model, the latter using the PMDG house livery with all default options. Is there any known issue with autothrottle failures?

Dave, thanks for the suggestions. All the dll's appear to be in the correct places, but I was unaware of the update to version 2.5.31. I was running v2.5.28. I can't see any changelog anywhere, but I've just downloaded the latest version, and I'll try it in a few days. Damn that real life, always getting in the way of simming!

Hi. I can confirm that UAC is disabled. It always has been, but I double checked anyway. Also, I am running V1.2 (in FSX). Something else to throw into the mix: I remembered another problem. Whenever I tell the FO to engage the autopilot, he does so, but then reports that it failed to engage. However, it actually does engage, and continues to work perfectly.

Hi. I have a minor problem with MCE for the QW Avro RJ. Whatever altitude I ask the FO to set, he simply takes that figure and increases the target altitude by that amount. For example, If I am cruising at Fl 280 and I say "set altitude six thousand," instead of turning the knob to 6000 feet, he will add that amount and turn it to 34000 feet. Any suggestions are welcome.

Another vote here for the FSL ConcordeX.

You might also consider the Angle Of Attack MD11 training course. You have to pay for it, but it is very thorough. Its entirely video based via streaming or download.

Thanks to the OP and all the contributors. I never knew about any of this until reading this thread. Now I have just freed up a whole bunch of space by using Junction Link Magic. I have two questions for those suitably knowledgeable. First, I do not see any special file in the original folder (as mentioned in post #9 by J van E) after creating the junction link with JLM. What I do see is the arrow symbol on the file icon in windows explorer, and the linked files and folders when I open the original folder (which do not show here if I delete the link). I have Win 7 64 bit set up to show both hidden files and folders, and protected operating system files. Should I be seeing any special file after using JLM as opposed to the manual method? Or at all, regardless of the method? Second, the following paragraph from the JLM help document has me a bit worried: "If a junction point is mounted such that the target folder and host folder are on different physical disk resources, the resources must be in the same cluster group. The physical disk resource that contains the host folder should be dependent on the physical disk resource that contains the target folder. If the drive that contains the target folder does not come online, the drive that contains the host folder does not start." That last sentence in particular is what I am talking about. The original folder is in my main FSX directory, which is on the same SSD drive © as Windows 7. The new destination folder is on another SSD (drive K). Does this mean that if the "K" SSD fails, then this somehow stops my "C" drive (and Windows 7) from loading? I certainly hope not.

1