jf_aero67

Dell Users - buzzing sound and video stutter/glitch/freeze momentarily every 60 seconds - since Feb 2015 - solved. Note this symptom also occurs on regular video playback - eg DVDs, YouTube and web video on demand etc, not just FSX. I started experiencing this on 12 Feb 2015 - and I have solved the issue, and wanted to share the solution in the hope that it will help some fellow simmers. If the above matches your experience, rest easy, It is not a hardware issue, you haven't overheated your graphics card, and it is not some odd FSX config issue. The culprits are 2 Dell Data Vault Services, pushed out to Dell users in Feb 2015. Dell Data Vault Dell Data Vault Wizard The solution: Press Start, type "Services" to show the system services. Sort by Name (click the Name header), find the 2 services, right click each in turn, select Properties. Set Startup type to "disabled" using the drop-down box. Re-launch FSX or a DVD or YouTube etc., and you should have a smooth stutter-free experience once again. I hope this is of assistance to some frustrated simmers! regards Jonathan Fyfe

Happy to report that this is issue is resolved! While investigating, I logged in as a different user (the guest account) and ran FSX - and I was pleasantly surprised - no scenery issues, everything smooth - which was a breakthrough moment. When I logged back in to my regular account, the issue was back. So I went digging in the user profiles and noted in C:\Users\Jonathan\AppData\Local\NVIDIA there was a directory called "GFExperience.exe_Url_tgm3mttmt5itflhj0kykoi5xkjy53x4g" that did not exist for the Guest user. In the directory was a directory "11.10.13" and within that an xml config file called "user.config". This had a recent create date, coinciding with the time I noticed the issue. Not sure what event had created this file. I renamed the "GFExperience.exe_Url_tgm3mttmt5itflhj0kykoi5xkjy53x4g" directory and restarted FSX - and the issue was gone. Hope this helps someone who may have this issue. cheers Jonathan

Thanks for posting. The thing is, I have been running for 18 months on this laptop with no scenery issues at all, achieving a pleasing 20+ fps most of the time. I usually fly the 737NGX and have FTX scenery. I've never had a need to run on "low" settings; I tried this in any case, and also put FSX into it's lowest resolution - but the problem is still demonstrated. I'm going to get the laptop serviced as it had recently been running at some very high temps due to a clogged air intake - and there seems to be a hardware issue with it as I have started to experience blue screens quite often (although strangely never when FSX is running). regards Jonathan

All, Recently I noticed that scenery around my aircraft is displaying as blank light blue tiles. (See images in this post). This occurs outside of a short radius from the aircraft. ie The immediate area around the aircraft, say 2 miles, is ok, then surrounded by a ring of blue as well as some random missing tiles further afield. It occurs in all global locations and airports - US, Australia etc. (Even in the default Friday Harbor flight now has the issue). The blank tiles do "fill-in" when I get close to them, however at the same time, other areas "blank out". I have a NVIDIA GeForce 555M and have reasonably good performance around 20fps. Just prior to seeing the issue I had updated to the latest NVIDIA driver - I was forced to update the driver because a Windows 7 patching update disabled my FSX - it would refuse to load. The dreaded "An error has occurred FSX will close" on startup. Updating the video driver then solved the problem of FSX not loading. I then ran a series of night flights and unfortunately may not have noticed if this texture issue occurred coincident with the NVIDIA driver update. Nevertheless I don't see how I can roll that back as FSX will then not load. I am running with DX10 off as recommended by PMDG. I have tried various graphic slider settings and resolutions but the problem will not go away. Finally, I also tried the FSX Acceleration "repair" install option, but again, no fix. Any thoughts? cheers Jonathan Fyfe https://www.dropbox.com/s/93eskrxlqd6qrg0/2014-4-5_21-17-2-566.png https://www.dropbox.com/s/gqla9z3naw7y502/2014-4-5_21-20-9-982.png

Sounds like battery discharge. Have you reviewed the introduction or tutorial pdfs? There's a lot of material to grasp - the NGX is not really a "quick load up and fly" aircraft. However the learning journey is fascinating - if you choose you can accumulate many hours on the ground digging into its systems. Tutorial 2 walks through a cold dark scenario. Cheers Jonathan Fyfe

Hi there You could take a look at http://support.precisionmanuals.com/KB/a59/fmc-custom-waypoint-entry-notes.aspx Also ARINC 424 Format http://www.bleedair.de/entering-oceanic-flight-plans-into-the-pmdg-b744s-fmc.html (747 article but can be used for 737) cheers Jonathan Fyfe

To clarify my answer, I had made additions to the PMDG navdata and that was the cause of the issue. The data was added without paying heed to the sorting requirement. (IE I just added new entries at the top of the data listings). Re-instating the original navdata files confirmed the issue was no longer demonstrated. I then once again added new data to the files, but inserted it in the correct positions in the files IE sorted by latitude. I tested again, and the issue was no longer demonstrated. Problem solved. cheers Jonathan Fyfe

Ok good news, problem solved, turns out it was my own doing. I added some additional navdata to the PMDG navdata files, but without sorting it by descending by latitude. -airports.dat -wpNavAID.txt -wpNavFIX.txt This sorting requirement is outlined in the PMDG Navdata Glossary in the knowledge base. Thanks to Ryan Maziarz at PMDG support for identifying the issue!

Hi All, I have just this last couple of days started encountering an issue with the GPWS / EGPWS on the -800 and -600 737NGX. On final approach, stabilised - gear down, 30 deg flap, approx 140 kt and 700' RoD, on localiser and glideslope, I get "Terrain" alerts on final, followed by "Pull Up" on short final. Same if I hand-fly or use the automatics where everything is on the numbers. I have tried various airports across the US and Australia - same deal. I should point out that this also occurs in flat terrain - eg flying into flat desert airfields If I have Terrain displayed on the ND, the airport is highlighted in solid yellow (I think this was the behaviour before) and there is also a solid red block (smaller) near it (don't recall this from before); There is also a full forward field of dotted yellow that I don't recall seeing before. The only changes I recall that I have made to my system recently: Re-downloaded & re-installed the updated FSUIPC (registered) after the recent code-signing problem that was announced by Sim Market on 6th May. Only way to suppress it is to pull the terrain inhibit switch on the co-pilots side. Any ideas anyone? Thanks for any input cheers Jonathan Fyfe