Jump to content

Jockos

Members
 View Profile  See their activity

  • Content Count

    106

  • Donations

    $0.00 

  • Joined

  • Last visited

Posts posted by Jockos

  3. Posted

    Folks

    For those interested in procedures for Kai Tak, the latest Airac from Navigraph (1712) contain those procedures.

    Thanks go to Martin Stewart who worked very hard to produce this body of work in ARINC format for Richard Stephan of Navigraph to publish.

    Well done men.

    The real beauty of this is that VHHX procedures have been produced in many developer's format by Navigraph so many more Flight Simmers can enjoy the challenges of the old Kai Tak.

    Cheers

    • Like 1
    • Upvote 4

  5. Posted

    Men

    Thanks for the clarification/s.

    I was curious as PhilH had not mentioned that he had MSVCR120.dll crashes and I was trying to relate Robert's message to the two crashes that Phil had experienced, kernalbase and ntdll.dll's.

    My interest is in ntdll.dll and have never experienced a MSVCR120.dll.  I do use pop-ups and have flown up to 8 hours with no issues.  Well, occasional ntdll's.

    Is there a connection?  I suspect not but it is worth trying a long haul without pop-ups.

    Glad you are having some success, Phil

    Cheers

  8. Posted

    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.

  9. Posted

    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

  11. Posted

    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

  12. Posted

    Folks

    I am sensing some frustrations here that at least in part, is due to my incomplete manual instructions to install VHHX, as published at VAPAP.  Apologies.

    I will amend the instructions by the end of the week.  In the meantime, if you need the VHHX.txt file (the one missing in my instructions) email me via VAPAP and I will send you the file.

     

    Ken

    In addtion to what Mike said re messing the two files to be amended for VHHX, the other back-up is to simply re-run your latest version of the Airac.  That also will restore the files.

     

    Cheers

  14. Posted

    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

  16. Posted

    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

  17. Posted

    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

  18. Posted

    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)

  19. Posted

    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? 

  21. Posted

    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

  24. Posted

    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

×
×
  • Create New...