solentflyer

Pleased to report all is working fine again now.

Hi, I purchased the Q400 First Officer training yesterday, but when I go to view the training courses, for each one I receive this error message "Oops! It looks like there was an error".

Many thanks Thomas/Kyle for the link - very enlightening. I am assuming from this that the impending release of the PMDG 777 on P3D is definitely aimed at student pilots involved in training, instruction and learning and therefore excluded from members of the general public, such as myself, who were contemplating purchasing for their own entertainment? Pity, as I would definitely have been a purchaser otherwise. As it is, I suspect that LM employ rather more expensive lawyers than I can afford and will therefore have to give it a miss. Best regards, Dennis

Hi Kyle, please can you point me to the Lockheed Martin article that confirms what you're saying here - I seem to have missed it. Many thanks, Dennis Elmes

Many thanks Bryan - much appreciated.

Hi Bryan I purchased the Airbus Voice Control edition and RAAS Professional as part of the Special Collection Set. Will the set be updated to include the latest versions also? Best regards Dennis

Many thanks Gerald, the patch fixed the issue. Best regards, Dennis

When changing airports within the Prepar3D Training Scenario Setup area, after selecting an airport (e.g. EGLL) and returning to the setup page, P3D is crashing with a fatal error. I have narrowed it down to fsinsider.dll after disabling all dlls within dll.xml and then enabling them one by one. The version of fsinsider.dll in the P3D folder is 2.6.1.61 (18/08/2014 13:51). Is anybody else suffering this error? Best regards Dennis

No need for a full 2.1 install...the exit menu problem is simply a window size setting in the uisettings.xml file, which is in one of the folders that should have been emptied prior to running the patch (please read the patch install instructions). Wes at LM has posted a simple solution on the Prepar3D support forum. The patch works perfectly if you aren't using the Migration Tool. Best regards Dennis

Gerald, Before you slag off Avast any further, I suggest you read the article below written by experts in their field: http://www.pcpro.co.uk/reviews/software/379729/avast-free-antivirus It may be prudent if, in future, you restrict your views to software within the games industry, rather than provide ill-informed views on software from a more professional sphere. Best regards, Dennis

Steve, I'd definitely second Frank's request The GFConfig software causes my 2 GF166s to constantly lock up, as per the other modules I have, including the MCPPRO. Your interface software on the other hand works perfectly with all of the GF modules every time, so if you were to find time to add the GF166 to your program, it would be very much appreciated. Kind regards, Dennis

Yes, I would also like to second what Francky said - to give up your spare time to develop such an excellent, professional piece of software and make it available for free is just fantastic and very much appreciated by everybody who's downloaded it I'm sure. Many thanks Steve. Kindest regards Dennis

At last, I have now tracked down the cause of this issue. It was being caused by a problem with the AFX_KIAD.bgl file supplied with the Traffic X add-on by Just Flight. Renaming this file to .bak resolved the issue.I have now raised this problem with Just Flight as it seems to affect a number of airports where they have supplied a corresponding .bgl file.Sincere apologies to PMDG for suggesting in an earlier post that this may have been an issue with the J41...I should have known better.Kind regards,Dennis

Yes, I opened the KIAD airport in Airport Design Editor and the backcourse approaches were indeed turned on. I turned them all off, and saved the compiled airport in the Addon Scenery folder, but unfortunately it made no difference as the aircraft is still tuning the I-SGC ILS approach. Thanks for your comments though Dan, it probably does have more to do with the idiosyncrasies of FSX rather than a problem with the aircraft. Perhaps the developers could confirm this when they have a moment?

Thanks for the prompt reply Dan.I've tried setting the LOC when south of the approach (infact as an experiment I've taken off from an airport south of KIAD so that it's permanently south of the approach) but still the J41 insists on tuning the I-SGC localizer for runway 19L rather than I-IAD for runway 01R.I believe this may be a bug in the J41 software, which is a shame as otherwise I've been extremely impressed with the aircraft, particularly in light of the fact it's one of PMDG's 'lite' versions.On reflection, maybe it's just unfortunate that KIAD was chosen for a tutorial as it shares frequencies for all of it's runways, otherwise this problem may never have come to light.