Jockos

Thanks so much, all good after copying the 'lorbysi' folders from the AAO installation to the new Community Folder. There was not the need to reinstall AAO as it did not go down with the initial MSFS installation. Your guidance makes total sense. Just to clarify, I reinstalled the Fenix scripts via 'scripts import' of the relative Fenix.xml. Apologies for the misunderstanding. Thank you for your excellent support. Cheers Jock

For Fenix A320 only standard MSFS actions to controllers now work. Any actions allocated by scripts do not work. I reinstalled all the Fenix scripts in 'Scripts Editor' (AAO), but no luck. After reinstall, all AAO scripts for PMDG are working fine. I allocate blank profiles in MSFS Options for all my controllers and only use AAO, for control. Any assistance to resolve this, would be appreciated. Cheers Jock McIntyre

Previous quote from April 1st "You can call the ROTOR_BRAKE directly from the Button Assignment in AAO, and supply the desired value in the numerical field to the right of the event box. " I can't find any ref to ROTOR_BRAKE in the dropdown menu for Button Assignment. I am attempting to allocate a button for Arm Speed brakes in the PMDG B738 I have the Event numerical for this. Any assistance would be appreciated. Cheers

Thank you for your responses. martin-w, it is comforting that my PSU appears to be within spec and adequate for the GTX780 stans, I have monitored the temps on my card extensively over a period of time and they appear to be within considered limits. I have done a 'clean install' of the latest drivers after using DDU. I have just installed the Microsoft Fix It 50848 which addresses the TDR error directly at the Registry by increasing the wait time before resetting the vid card. Testing so far looks promising, but I shall not be satisfied until more time with P3D3 is spent.without this error raising its horrible head! Thanks again for your valued input.

I am having some persistent but irregular issues with 'Display driver nvlddmkm stopped responding and has successfully recovered', when using P3D3. One of the many issues related to this error is a problematic PSU. I have engaged 'HWMonitor' to check my voltages. At the time of the crash the min voltage was 11.808. Would this be considered too low to service my GPU (GTX 780) and therefore could be an issue related to the crash? My PSU is a Thermaltake DPS 850W Any assistance would be appreciated. Jock McIntyre

Thank you for your response, Kyle. Ticket raised as you have suggested. Cheers

I am having an issue with downloading SP1d as my purchase details for the NGX Base Package are not appearing in the 'Previous Purchases' section. My email address has changed since purchase in August 2011. Using the 'Order Review' does not pick up the purchase despite having all the relative detail - Order Code etc. In a bit of a bind at the moment in updating the 737 to SP1d. Any assistance would be appreciated Jock McIntyre

Good you have VHHX sorted, David Cheers

If you own Flight Sim Commander and bring up NZQN all the radius points for the RNP-Y's are there for you. They are designated 'RQNnnn') As Dan indicated (nice to see you back Dan) this is the hardest part in constructing RNP's for PMDG. The rest is just plain tedious!!! I have given the RNP-Y's a shot for both RWY's. You can download them at http://www.vapap.com/downloads/as-pmdg If you don't want all the other procedures in the download, just install to a folder outside of FSX and copy the NZQN.txt file into your 'sidstars' folder. Flying it, the NGX ND is horribly busy with all the user waypoints to keep the kite in the arc. Must keep the speed in hand for them to work Could be some overkill as Dan would say. Havn't had the time to go back and refine. For those interested the RNP's for NZAA are included in the above download. Cheers

David, hello Looks like you are having some issues with the manual install of VHHX . email me via VAPAP and I will see if I can guide you through the process. Cheers Jock McIntyre

Folks I have posted a detailed manual workaround at VAPAP while I repair the Kai Tak installers. Hopefully this will resolve some of the problems here. Regards Jock McIntyre Melbourne, Australia

Folks Looking at the current Navigraph Airac (1310), there are some issues with the way the SWIFT7 SID is written. I am not sure how this code looked with the Airac supplied with the T7 as I have updated my Airac since purchasing the T7. Nevertheless, the current code looks like this:- SID SWIFT7 RNW 15 TRK 149 UNTIL 400 TRK 030 INTERCEPT RADIAL 080 TO FIX CS TRK 080 UNTIL 4000 TURN RIGHT DIRECT FIX SWIFT There are 2 issues with this. 1. There is a speed restriction with this procedure up to tracking 030 of 190kts. This is not coded here and frankly most likely has no bearing on the direction of the turn, however it should be coded as such as the kite needs to turn through 119* to attain a track of 030. 2. The part of the code 'INTERCEPT RADIAL 080 TO FIX CS' should read 'INTERCEPT RADIAL 080 FROM FIX CS'. The radial 080 TO fix CS actually resides on the other side of the Cairns VOR (FIX CS) in the high terrain!! This is at least one reason why the T7 turns right in an attempt to meet this condition. OK so the quick fix is to break out the code in the sidstars folder under PMDG for YBCS and substitute TO for FROM in the SWIFT7 SID. Save it and it should work turning left after attaining 400'. Hope this helps Jock McIntyre Melbourne, Australia

Ryan, thank you for you clear and concise response I understand that the change would be huge for PMDG and that it is not just about if the information is available. Jock McIntyre Melbourne, Australia (apologies, forgot to sign my last post)

This is a long and informative thread. Thanks to all. However, now that we are in Beta for the T3, can any of the testers, or indeed PMDG, respond to the query as to if there is any change to the code structure to make the T3 more ARINC 424 compatible with Airport Procedures?