vanislepilot

Hi, Just wondering if you would be open to developing a remote MCDU for the new A340? My understanding is Aerosoft is developing an API for such purposes. Thanks!

Thanks for the reply. Unfortunately, your suggestion doesn't seem to work. Really hope you can find a way to incorporate any font natively in the future, as the Pilots Deck plugin does. I think the AAO plug-in is far superior, and having custom fonts would be an added layer of immersion. Thanks again!

Hi, Maybe I'm missing something, but it would be wonderful if we could use whatever fonts we have available on our PC in the StreamDeck plug-in, instead of the few that are present at the moment. Are there any plans to implement this in future updates? Many thanks 🙂

Really hoping to see a 777 version as well!

+1 here for experiencing your "trim lag/jump" issue #2 Martin. The first thing I do with any aeroplane is learn how to hand fly it. This was the only apparent "issue" I've encountered so far with the aircraft itself. I'll be on approach, decelerating and extending flaps as per the sched and a few clicks of the trim doesn't help out and then it snaps into an overtrim. If it was real world, that would raise the hairs on the back of my neck a bit. Glad it's on the radar now.

The bottom line is simmers want to fly what they see at the airport, but while the A380 isn't exactly everywhere, its "wow" factor is on everyone's radar. I was at VHHH a few years ago, and many people in the terminal stopped by the A380's gate to snap a picture of it. A Cathay flight crew even told me when to see it fly. A PMDG A380 would indeed sell and very well at that. +1

Exactly sir. Avoid using a saved panel state, and use one of the PMDG pre-configured ones instead. If you have been using a saved panel state, and you only tend to disengage the autopilot after landing, then I imagine you are having the very same problem as I did.

After consulting with the PMDG support team, I can report that this is indeed an issue likely associated to using a saved panel state. A fix that worked for me is as follows: 1. Load one of the default T7 panel states, in my case '777 LONG', and set it to the default load-up state. 2. Restart FSX and ensure you are using the A/P Disconnect button to disengage the autopilot. Press it once to disengage, wait at least 1.5 seconds and then press it a second time to silence the wailer. The A/P disconnect wailer cuts out appropriately after the second press. According the support team, there have been several issues observed with saved panel states, so I imagine this will be corrected at some point down the road. For now though, this should do it. <<UPDATE>>: Just received an email from Mr. Paul Gollnick of tech support stating that these saved panel state issues have been corrected in the upcoming hotfix.

To be clear, are you suggesting a problem with the aircraft configuration or the simulation of the wailer itself? I have no cautions or warnings on the EICAS (aside from A/P disconnect) and all overhead indications are okay. I've tried disengaging in a variety of flight configurations. I don't see how the aeroplane would be upset in a straight and level clean configuration, 10000 MSL at 250 KIAS with no EICAS messages or other apparent issues... Thanks for the post.

Not working for me here. I've done the following: 1. Delete 'Z' default autopilot toggle mapping within FSX control menu. 2. Confirmed A/P Disconnect Button mapped to 'Ctrl+ Shift + Z' in PMDG key commands menu. 3. Mapped joystick button with 'Ctrl + Shift + Z' using FSUIPC. 4. Tried the "two-press" method at varying time intervals. I was about to assign "Z" to the A/P disconnect (from what I gather, wanabflyer has done), but I chose a test to see if something was up... 5. Clicked on the yoke button in the VC with the mouse as per "two-press" method. Nothing worked to silence the alarm. I'm not starting in cold and dark - using a custom start up state. I don't think this would matter in the real aircraft? Correct me if I am wrong. The development team (Mr. Maziarz) has posted the following under "not real issues" in the issue tracking thread: Ref: http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread/ "- Master warning siren/wailer doesn't turn off. This is a realistic feature that is an option on the airplane. Look for RESETTABLE SIREN in the EQUIPMENT section of the aircraft options in the FMC. With respect to the autopilot disconnect form of this sound, it takes two presses of the AP disconnect button/key to silence it. The second press must come at least 1.5 seconds after the first. Again, accurate to the real world airplane." At the risk of sounding like a heretic, I'm not so sure this is a non-issue anymore. Any help would be appreciated!

I wonder how many people there are out there who are actually in a position to be tempted by this... :lol: http://www.precisionmanuals.com/productcart/pc/viewPrd.asp?idproduct=99

http://forum.avsim.n...turns-nav-mode/ Hello all, With reference to the problem previously encountered by a few other people (see link), this issue has popped up for me recently on two successive flights. En-route from CYVR to CYEG, approximately half way through the flight, the aircraft began a right turn off course and exceeded the bank limit. I switched to the other autopilot; however, the same problem occurred again. The rest of the flight was flown manually. Then again from CYEG to CYOW, the problem resurfaced. Interested to see how unusual a configuration the autopilot would develop, I allowed it to proceed. The aircraft was unable to maintain altitude, and began to roll inverted. I understand this may have been corrected with various hotfixes and SPs. I have the latest SP1c installed, and have made no modifications to my set-up aside from installing REX Essential. My thoughts are this might be related to the weather engine, as both incidents occurred within minutes of your every-day high altitude FSX windshear. Thanks in advance for any thoughts,

My apologies, I can't quite recall the set-up process I used, as I became rather impatient with it. As I recall, nVidia's instructions were not quite clear as far as managing the different drivers, but I believe a standard GPU driver AND 3D driver are required to get the whole thing to work. Also, ensure that your GPU is compatible with nVidia's 3D vision. "3D autofocus" should be automatic if you've successfully installed everything on compatible hardware. I did not have to specifically activate that feature. I am not sure if it originates on Track IR's side or nVidia's, but I would imagine nVidia as you suggested. Thanks for the lighting fix, I'll give it a try here! Regards, Troy

Hey Jakub,I'm using nVidia's 3D vision with Track IR 5, and it works beautifully. As you translate your head up, down, forward, back and side-to-side, the "3D focus" automatically adjusts to ensure there is no distortion in the stereo image. A zoom of about 0.48 really accentuates the depth perception while giving you a slightly more natural but wider view. If, for example, you moved your head in close to the monitor to look at the throttle quadrant, or the magnetic compass, you would actually see it begin to pop out of the screen as if you had your nose up to it in real life. And in the 737NGX, you would actually see how the magnetic compass is in fact truly 3D!I have used nVidia 3D vision and Track IR 5 with several different payware add-ons including the PMDG 744, and it works flawlessly. The only issue with 3D is the fact that FSX does not model its lighting in 3D. You will find all lighting effects (runway, aircraft, PAPI, city lights) are positioned at screen depth, which makes night flying in the 3D somewhat distracting. Some other users have expressed concern about the reduction in light of the stereo image compared to the standard 2D visual. This doesn't concern me though, and it's easily ignored in most cockpits by switching the flood lighting on.I can't suggest trying this enough, despite FSX's shortcomings. It's totally worth it, and I wonder why other this really hasn't caught on yet.Hope this helps!Cheers,Troy

I'm not saying completely get rid of the exterior sounds - no way! I am wondering if there would be some easy way (perhaps even in a config file) to make this possible? Even though the viewpoint is technically an external one, as for the user experience, wing views are rarely enjoyed with earmuffs on :(. Thanks to PMDG for answering all our questions! Above and beyond guys!Troy