Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

6 Neutral

About Jockos

  • Rank
  • Birthday July 10

Profile Information

  • Gender
  • Location
    Melbourne, Australia

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Mark After our lodging reports to QW Tech Support of the issue, Lars has responded with:- Please try the following: Navigate to \Prepar3D v5\QualityWings\Redistributables\ and run the following file: Crash_Reporting_v1.4.0_P3Dv5.exe (it will be a hidden installation and not give you any kind of feedback but should be done within a few seconds) Please let me know if RemoteCDU works afterwards. Thanks, Lars These actions have been successful for me. Cheers Jock
  2. If I could join here with the same issues as Skip. I am running the latest ver of QW787 1.4 with P3Dv5.1 All I get of the CDU is the left hand keyboard with no keys etc. I have gone through the actions listed with the Dispatcher and high res indication, with no results. I agree with Skip re FSUIPC settings. I too, had to redo mine so QW have definitely done some work with the gauges on the 1.4 update. This might help you to troubleshoot the issue, Mark. Happy to send logfiles, if this helps. Cheers Jock
  3. Bruce I do believe that EZDOK Ver works well in 5.1 HF1 Cheers
  4. Thanks for the clarification and 'Panel tip'. I will give it a shot. Cheers
  5. Snapshot21, can you confirm that you have applied the soundpack to to AH DC-3/C47, please. The readme with the soundpack refers to the Manfred Jahn DC-3/C47. I guess that it could 'fit' with the AH model. Cheers
  6. Good description of what I am hearing. Very distracting. I have not been to AH's help area about it, yet. Cheers
  7. Hi Alex. Thanks for the report and vid. Can you elaborate on 'minor bugs', please? I am almost set to commit, perhaps. Cheers Jock
  8. Marius, hello I have had my Thrustmaster 16000M for over 4 years. Never missed a beat. I use the 'twist action' for tiller steering and I have CH peddles for the rudder. Can recommend the Trustmaster. Cheers
  9. Allow me to attempt to explain this, folks. It is all rather embarrassing! I did the 4.4 Client update only. Flushed the Shaders and deleted the p3d.cfg, as I believe you should. The following day, I decided to do ‘Content’ for 4.4. I did NOT do shaders and the .cfg. I think this is possibly where I erred. Since that time, I have had Blue Screens, CTD’s, NTDLL’s abound all pointing to Drivers. As my vid driver was rather old, I suspected that and updated to the latest release 417.35. I flushed the Shaders but continued to have all above mentioned errors. For some reason, I also decided to delete the p3d.cfg file as well. Reasoning can often lead to odd things at my age!! As already hinted at, on reflection, I believe that it is not necessary to delete the cfg file on a driver change, only Shaders. Well I did delete the cfg and I think that is what I should have done after the ‘Content’ upgrade. I guess that is luck but comes with considerable embarrassment. On the positive side, I have just completed a 2 hour flight YBBN-YMML without a hint of any sys problems. I am happy and my apologies for confusing the ‘masses’. Cheers
  10. Thanks for the response folks. So glad 417.35 is treating you well 'Mulgrave' I hold my head in shame! I did a clean install of 417.35 with DDU. Dumped the Shaders folder but forgot to delete the cfg!! Since done that and I have been flying for 45mins without a hitch. Not holding my breath but it is looking ok. Cheers
  11. I am running 417.35 and am having some issues. Just wanting to know if others are experiencing any problems. Probably did not explain myself that well. Sorry.
  12. Folks I am running Prepar at 4.4 Has anyone had any experience with 417.35 and 4.4? Alternatively, can anyone give me a fairly late driver version that they are have success with on Prepar 4.4 Appreciate any assistance. Cheers
  13. Alex. Thank you for your comments and considerations. Cheers
  14. Folks I have played around with this and it now appears to work! Perhaps a restart did it. Can you confirm that the smallest difference is 1NM. i.e. you cannot indicate 1.5NM radi. etc. Given that this is so, is there any chance that 0.5NM increments would be possible in future updates? Thank you for your attention. Great piece of software, Alex. Cheers
  15. Victor Thank you for your response. This is exactly where I am attempting to change the distance but any change from the default numbers does not appear to take. Perhaps I am changing the numbers incorrectly or in an incorrect format. Any assistance would be appreciated. Cheers
  • Create New...