Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

solentflyer

Commercial Member
  • Joined

  • Last visited

Everything posted by solentflyer

  1. Pleased to report all is working fine again now.
  2. 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".
  3. 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
  4. 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
  5. 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
  6. Many thanks Gerald, the patch fixed the issue. Best regards, Dennis
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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?
  14. 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.
  15. I have been following the tutorial, but am finding that the J41 captures the ILS for runway 19L (I-SGC) at KIAD rather than the ILS for runway 01R (I-IAD). This is in spite of setting the course to 011 when it appears in magenta on pressing the V/L button.I have approached from the South and the North as I read elsewhere that, for runways that share the same ILS frequency, FSX will tune the ILS in the direction you're currently flying when you tune the ILS, but the result is the same i.e. it tunes the wrong ILS. HAs anybody else managed to tune the correct ILS for the tutorial? If so, what steps did you follow to achieve this?Thanks,DennisCore i7 940 2.93GHz ASUS P6 Deluxe | 12Gb DDR3 RAM | nVidia GeForce GTX 280 1024Mb | Windows 7 Ultimate x64
  16. Hi, is it possible to have a progress update on the GoFlight MCP-Pro interface for the 747-400X? I believe it was due to be released around the time of the 2.10 update?Many thanks,Dennis
  17. Hi Todd, was wondering if you have had a response from PMDG yet to this query? I'm also interested in when the FSX version of the interface might be released having previously purchased the FS9 version.Thanks, Dennis
  18. >Hello->>I've uploaded a newer version which takes care of the>SimObjectsAirplanesPMDG* folders as well.>>Thanks for noticing!Hi Lefteris,I downloaded and ran the latest version last night and it was unable to find fsx.exe or the pmdg modules even though the path displayed is correct. Please find the log file output below. Any ideas why it's not finding the exe file?Thanks, DennisOS Version:-----------Windows Vista (Business), (Multiprocessor Free), (x86-32 Processor) v6.0 Build:6000FSX Version:------------FSX Registry Key Detected - Registry Setup Path detected - No FSX.exe found in C:Program FilesMicrosoft GamesMicrosoft Flight Simulator XFSX Setup Path:---------------C:Program FilesMicrosoft GamesMicrosoft Flight Simulator XSimConnect Version:-------------------10.0.61259.0 (FSX SP2/Accel Pack)PMDG 747-400X Version:----------------------2.00.0031PMDGOptions.DLL Version:------------------------No PMDGoptions.DLL detected.PMDGSounds.DLL Version:------------------------No PMDGSounds.DLL detected.PMDGEvents.DLL Version:------------------------No PMDGEvents.DLL detected.
  19. Hi, I can confirm that I'm having this issue also. This problem certainly occurs with all flight plans beginning lhr* (London Heathrow).Dennis

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.