Jockos

Thank you for your response and subsequent follow-up. I will reassign this and see how I go. Cheers Jock

I am having issues attempting to assign ‘Brakes’ in the iFly. The generic sim commands in 2024 are not working using Landing gear/Brakes – Brakes (increment brake pressure Parameter N/A). That works perfectly with the PMDG aircraft. I understand that the iFly interface is quite different to PMDG. I was hopeful that some learned folk here may be able to point me in the right direction to create a script to achieve this. I use the trigger function on my Thrustmaster 16000 joystick with the ‘repeat’ function ticked in ‘Assigned Buttons’. As an aside, I have installed your Honeycomb Bravo Quad template for the ifly MAX. It works a treat. Thank you. Any help would be appreciated. Cheers Jock.

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

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?

I drink (moderately, of course). Hopefully, real pilots do not. Always brightens up the approach.

Hi James As you are aware there has been a complete 'makeover' of the procedures at ZQN. Since the relative data has been made available I have produced all the new procedures at ZQN including the RNP approaches and departures. Yes it is cumbersome attempting to produce ARINC type procedures with the current PMDG code. The ND looks very busy with all the User created Waypoints to keep the NGX on track with RF parts of the procedure. Glad you are giving it a shot. I will soon publish the new ZQN procedures at VAPAP (http://www.vapap.com/), but if you would like to have a look at what I have done, happy to send you the NZQN file. Just PM me with your email address. Cheers Jock McIntyre Melbourne, Australia

I am considering buying a BenQ monitor in the GW series. Either 24"" or 27". They come with a VA panel type. It appears that they are in between TN and IPS panels in terms of quality however may suffer on the response time side of things. Has anybody here had experience running FSX and a VA monitor? Appreciate any feedback Regards Jock McIntyre

Hello Derek,Late reply here. Hope you haven't given up.After Airac 1003, 3 extra fields were added to the TerminaLegs table in the nd.mdb Database. This virtually renders the xes 1.3 beta program , useless. Reason is that xes 1.3 beta uses ftnd.exe (FeelThere freeware executable). I think it, (ftnd.exe) looks at that table's structure and when it has changed, errors. Two ways around this.1. Ask the FeelThere developers for the souce code of ftnd.exe so it can be amended to cope with a different table structure. 2. Delete the 3 fields in Access before introducing to xes and all should be fine.Option 1. I would think would be extreamly remote!!Option 2. Can assure you this works. Of course you need Access or some program that can manipulate .mdb. The catch is that these new fields are about Track Code RF (Radius to Fix) If your model airframe from Wilco is able to use this Track Code you will need to restore the fields and data. This takes some more time!Hope this helps.Jock McIntyreMelbourne, Australia

Etienne, Thank you for your advice.RegardsJock McIntyre (YMML)

Folks, I wish to OC my trusty stock E6600. I would be happy with 3.0 Ghz and from the good reading on this forum, that looks very possible.However, I may have struck a snag with RAM. I am running 4x1Gb DDR2 PC2-5300 (333Mhz) Kingston. All the OC advice appears to recommend DDR2 800.Where does this place me in terms of overclocking?Motherboard GA 965P-DS4 (Rev1)Any advice would be most appreciated.RegardsJock McIntyre (YMML)

Mark, Fantastic pics. You have almost convinced me!!KIWI, ehh? Didn't pick the accent!! Just Jocking.RegradsJock McIntyre (YMML)

Men, Thanks again for your responses. Have d/loaded the latest driver and will install.I have made a startling discovery!!! 99% of the time I use PMDG model/s in both FS9 and FSX. Just of late, I have had the need to test some sofware using the default models. This is when I realised the sound issue. Last night I flew the PMDG 737 (in FS9) for an hour without one sound distortion. I am assuming the same in FSX after you get past the splash screen/intro music scenario and select PMDG. So, possibly I have had this issue for some time and not realised it. I have not used FSX recently for PMDG so haven't heard the music stuff on boot up. I guess this means that a different set of sound files are being used with the PMDG add-on, over the default set. Intrigued that both FS versions are affected. Well, there is still something wrong and I would like to fix. It sort of takes it away from being a video card problem and back to sound, perhaps. Have I got all the audio codecs for MSF?? How do I know that?? The thought of uninstalling/reinstalling both FS versions would induce heavy drinking and I would live with the problem given that I use the default aircraft rarely.Still like to fix. I will go through the video card and sound 'swaps' to see what I come up with.RegardsJock McIntyre (YMML)

Guys, Thank you for your replies.I updated my vid driver to 84.21, the current ver reccommended by Gigabyte for the 7900GT. Unfortunately, no change to the sound quality!!!!The only thing I can think of now is to swap out the 7900GT with anything else to disprove or otherwise, the video card. I may be able to do that next week. I could aso disable the onboard Realtek and reinstall the Creative X-Fi Extreame Audio cardAnyone got any other ideas???RegardsJock McIntyre (YMML)

Folks, I have had both FS9 and FSX running fine on my rig. Smooth running and acceptable frame rates.OK the problem now:- On booting into FSX at the splash screen when 'THE' music starts, the sound is distorted. Some 'crackling' and hesitation in the music sounds. When the defaults come up and you begin to select an aicraft the distortion continues. With the aircraft selected and engine running (music has stopped)the distortion continues sparodically. On applying throttle distortion increases with stutters occuring in sync with the sound issues.I have similar issues in FS9 but not to the same extent.What I have done:-1. Uninstalled and reinstalled the latest drivers for Realtek ALC 883 for the onboard sound.2. I completely removed both drivers and card for SB X-fi Extreame Audio. Creative are having problems with these cards and 4Gb RAM. I did not, but have removed it from the equation. I previously ran on the Realtek successfully before the promlem arose.3. Defraged all my drives. I am running both verions of FS on one dedicated drive.4. At some stage, I am not sure when (possibly after removing the old Realtek and Creative drivers) Some yellow(!)'s appeared under 'Sound video and Game Controllers' in Device Manager. They were against the audio and video codecs that are installed with XP. Hopefully, I have restored them correctly.I guess some obvious questions:- 1. Is sound OK everywhere else? Well I have played Windows Media Player in audio for ages trying to induce the issue. It has only happened once, with similar distortion as in FSX. I have been unable to induce this again, so a bit uncertain here.2. Are other games affected? Unfortunately I only 'play' FS!3. Are all the audio and video codecs in place? Not sure what FS uses here to check this out.As you can gather, I am assuming (pretty dangerous!!) that I do have a sound problem. Maybe it is something else and that is why I have come to you learned folks on this forum. Trust you can assist.My system specs:-Mobo GB GA-965P-DS4Intel E66004GB RAMVideo Card 7900GTOS XP Home SP2RegardsJock McIntyre (YMML)