Search the Community

Showing results for tags 'terrain'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • New Member Forums
    • Welcome New Members!
    • Help Using the AVSIM Forums
    • Help Creating an AVSIM Account and Logging on to AVSIM
  • AVSIM Fixed Based Operations (FBO)!
    • Hangar Chat
    • Virtual Reality (VR) Hardware and Games
    • Letters to the Editorial Staff of AVSIM
    • In Memoriam of Tom Allensworth
    • All About Us
    • Crash To Desktop (CTD) Forum
    • The Bargain Hunter's Shack
    • Classified Ads | Want Ads | Swap Meet
    • AVSIM's Round the World Race Forum
    • AVSIM User Surveys and Opinion Polls Forum
    • Review Feedback
    • The File Library General Forum
    • The Focus on Freeware Forum
    • Flight Sim & Aviation User Stories
    • In Memoriam
  • Microsoft Flight Simulator Forums
    • MS FSX | FSX-SE Forum
    • The Microsoft Flight Forum
    • The FS2004 (FS9) Forum
    • Flight Simulator Tips and Tricks
    • Shared Cockpits | Multi-Player Forum for FSX | FSX-SE | P3D
    • MS FSX | FSX=SE | P3D Simconnect Forum
    • MS FSX Missions Forum
    • MSFS Aircraft and Panel Design Forum
    • MSFS Scenery Design Forum
    • The Paint Shop - The Aircraft Painter's Forum
    • Mesh Scenery Design
    • The TerraBuilder Forum
    • TTools for MSFS Forum
    • Add On Developer's Forum
    • DX-10 Discussions, Hints and Help
  • The Prepar3D Forums
    • The Prepar3d Forum
    • Prepar3D Tips, Tricks and How To's
  • The X-Plane Forums
    • X-Plane Tips and Tricks
    • The X-Plane General Discussions Forum
    • The X-Plane Scenery Forum
    • The X-Plane Aircraft & Panel Design Forum
    • X-Plane Addons
    • X-Plane Add-On Developer's Forum
  • The Dovetail Games (DTG) Flight Simulator Forums
    • The Dovetail Flight Sim World
    • The DTG Flight School Forum
  • Screen Shots, Videos & The Gallery
    • The AVSIM Screen Shots Forum
    • Real Aviation Photos
    • Aviation and Flight Sim Video Forum
  • Hardware & Operating Systems Discussions
    • WIN10 OS Forum
    • WIN8 OS Forum
    • The Win7 OS Forum
    • MOBO | RAM | CPU | HDD | SSD | Desktops | Laptops
    • Monitors | Multi-Monitors | Video Cards | Drivers
    • Hardware Controllers | Joysticks | Drivers
    • Networks | WIFI | Routers | Ethernet | DSL | Cable Modems
  • Commercial Support Forums (Official)
    • The PMDG Support Forum
    • FS2Crew Support Forum
    • FSFX Packages Support Forum
    • Mindstar Aviation Support Forum
    • The RealityXP Support Forum
    • The Official DX10 Scenery Fixer Support Forum
    • Virtual Avionics Support Forum
    • Lorby-SI Support Forum
    • Pilot2ATC Users Forum
    • Icarus Development Forum
    • Remote CDU for Phone / Tablet Official Support Forum
    • Airline2Sim Support Forum
    • SX Airport Design Forum
    • P3D Tweak Assistant (PTA) and RealismShaderPack
    • The simPlugins Support Forum
    • SimSettingsManager Official Support Forum
    • simFDR General Support Forum
    • Blue Sky Star Simulations Support Forum
    • Capt. PERO Support Forum
    • Drawbridge Designs Forum
    • The SkyPilot FSXAssist | P3DAssist Support Forum
    • Mid-Atlantic Air Museum Simulations Support
    • Jane Rachel Whittaker - Blue Sock Studios Support Forum
    • FSReborn Series Support Forum
  • Commercial Support Forums (Unofficial)
    • Photo Scenery Support Forum
    • The Carenado Support Forum
    • The Alabeo Support Forum
    • The AS16 and ASCA | Active Sky | Active Sky Next | XPAX Support Forum
    • The OpusFSX Forum
    • The FTX | ORBX Support Forum
    • The Multi-Crew Experience (MCE) Support Forum
    • The Captain Sim Support Forum
    • Lionheart Creations Forum
    • The Majestic Software | Dash 8 Support forum
    • The Commercial Level Simulations (CLS)
    • The AeroSim Support Forum
    • The VOXATC Support Forum
    • The I-Fly Support Forum
    • Flysimware Forum
    • The MILVIZ Support Forum
    • Radar Contact Support Forum
    • The Level D 767 | Wilco PIC 767 Forum
    • Infinite Flight Forum
    • The Wilco B737 Support Forum
    • Night Environment | Black Marble | Blue Marble Forum
    • The SIM720 Forum
    • Infinite Scuba Simulation Forum
  • Virtual Airlines News and Discussion
    • VA News and Announcements
    • VA World!
  • Other Civil Aviation Simulators
    • Terminal Reality's FLY Series
    • FLY! Legacy
    • The Rise of Flight General Forum
    • The AeroFly Simulator
    • The Outerra 3D Planetary Engine
    • The Flight Unlimited Series
    • The ProPilot Forum
    • The FlightGear Forum
  • Combat Flightsims
    • Digital Combat Simulators (DCS) Forums
    • Falcon 4 - Allied Forces
    • General Combat Flightsims
    • 777 Studios!
  • Flight Schools
    • The Flight School Hangar
    • So You have Solo'd
    • Preflights
    • Weather - Understanding It and Safe Flight
    • Flight Planning
    • Mountain Flying
    • Float Plane Flying
    • Rotory Winged & Helicopter Flying
  • Freeware Support Forums
    • General Freeware Discussions
    • Ready for Pushback Forum
    • Little Navmap | Little Navconnect | Little Logbook Support Forum
    • The ProController and Squawkbox Support Forum
    • The VATSIM | vPilot | FSInn Support Forum
    • The Sweet FX Support Forum
    • Terminal Procedures Forum
    • The TinMouse Forum
    • The TileProxy Project Forum
    • LINDA
    • Desk Pilot
    • Mario Noriega Designs
    • The FS9 Evolution Forum
    • SimLauncherX
    • FreeMeshX Global Support Forum
    • FSLaunchPad
    • PSXseeconTraffic for FSX | P3D
  • International Language Forums
    • Deutsches Forum fuer die Flusi Gemeinde
    • Türkler için Flight Sim forumu
    • Forum de la Communauté francophone de Simulateur de vol
    • Foro de vuelo virtual en español
    • Forum della Comunità Italiana di Flight Sim
    • O fórum em português
  • Other Forums
    • The Unofficial PSS Forum
    • Russian Flight Simulation and Aviation
    • VictoriaPlus [Canada] Scenery Forum
    • Other Flight Simulation Software
    • Helicopter and Rotor Head Forum
    • Orbiter and Space Sims
    • Home Cockpit Builders
    • Racing Fools Forum

Categories

  • Articles
  • AVSIM News
  • File Library News
  • AVSIM Reviews
    • Hardware
    • Aircraft
    • Scenery
  • Product Announcements & Press Releases
  • What's New @ AVSIM
    • Contests
  • Interviews
  • AVSIM Editorials
  • Guest Editorials
  • Obituaries

Categories

  • New Features
  • Other

Categories

  • AVSIM Publications

Blogs

  • Tom Allensworth's Blog
  • Gaiiden's Scroll
  • Brandon's Box
  • Jess B's X-plane blog thingy
  • Tom_Test's Blog
  • Alpha Floor's Logbook
  • GolfPilot
  • adi518's Blog
  • Chase's Blog
  • The Big Tour
  • Tales of a Wannabe Pilot
  • Farmer Looking Skyward

Forms

  • I need help with the AVSIM Site...
    • Name
    • E-Mail
    • IP Address
    • Details
  • Submit News or a Press Release
    • Your name
    • Your Email Address
    • Link to URL
    • News Category
    • News Item

Found 30 results

  1. Hello folks, The open beta for FreeMeshX USA has begun. This is a 50 GB LOD12 (9.5 m pixel size) terrain mesh that enhances the topography of the continental 48 United States. Note, Hawaii and Alaska are unfinished. The source data used is from the US Geological Survey's National Elevation Database and is the highest quality data we've worked with. The USA mesh is unfinished. We have not optimized the level of detail for the plethora of terrains found in the CONUS. For example, the Great Plains are also rendered at LOD12, which is a bit of a waste of data, so we will likely cut down the LOD to LOD11 in the future and increase the compression for the flatter areas of the country. This could save quite a bit of HDD space in the end. We have also filled in gaps between the CONUS and neighboring countries with LOD11 data based on SRTM and CDED data. So the entire world should now be completely replaced with FreeMeshX Global and FreeMeshX USA. The mesh is compatible with all versions of FSX and P3D. Flight Sim World is not supported -- that's not a permanent declaration -- we just don't know enough about it and haven't tried using FreeMeshX with it. About the airport plateau problem: I have not finished my solution to the airport plateau problem, but I've made much progress in that direction. I've withheld the release for this very reason until now because it can break the immersion. As many know, the airport plateau problem is a fundamental issue that affects all meshes. Since the ESP engine forces airports to lie flat on undulating or sloped terrain, these artifacts at airports become quite significant at higher LOD. There is no thorough workaround yet. FTX Vectors can only do so much by adjusting the elevation of a small fraction of the airports. The only true way to fix this issue is by DTG or LM rewriting how airports lie on terrain, but I have not seen any inkling of motivation from them to solve it. Until then, I am working on my own solution that will adjust the mesh around each airport so that the airport blends in seamlessly with the surrounding terrain. It's not an easy task for me. It's an elusive problem that requires thorough planning and testing. I originally withheld release until I had the solution working, but time commitments to my PhD research and limitations of my own has not allowed me to solve it yet. You all have been very patient, and I have decided to release an open beta for those who understand the airport plateau problem and won't report to me every time they see an airport affected by it. Trust me, I'm working on it! New installer method: Due to popular demand, we have forgone the 'manual' method of installing for a 'less manual method' FreeMeshX has converted to automatic installers. See for yourself. As you can see, the installer basically does the job of extracting the FreeMeshX folders into a location of your choice. There is no impact on your system elsewhere. No registry entries. No BS. To uninstall, you just delete the installed folder. Done. Note, you are still required to add the folders to your Scenery Library. Trust me, you don't want us to modify your scenery.cfg, and we don't want to be the culprit if it messes up Downloading: The USA expansion is huge. Downloading it will take a long time. Usually 12-24 hours for broadband users when downloading directly without any kind of download accelerator. On top of that, the new installer method can only work with 2.0 GB chunks at a time. That means the installer uses 27 parts. To simplify the direct download, I have put together a barebones downloader based on wget -- a download manager that will automatically retrieve all parts of the installer with full stop/resume capability. All one has to do is unzip the downloader, double-click on a batch file I provide, and it will run wget to retrieve each file. A command prompt with a bunch of gibberish will come up, but at the bottom will be the name of the file you are downloading and a progress monitor. Once it has finished one file, it will automatically move onto the next until all files are downloaded. If you want to stop the download, exit out of the command prompt, or hit CTRL + C. To resume, just double click on the batch file, and the installer will resume from where it had stopped. Note, the files will be downloaded into the location where you have run the batch script, so make sure you have enough space first! We have created installers for the other regions of the world -- fully updated. They aren't uploaded yet, but will be ready soon. Bit Torrent users: For Bit Torrent users, the USA mesh will not come with an installer. It is not needed. The entire folder structure can be downloaded intact with Bit Torrent, like it is for the FreeMeshX Global 1.0 release. Download the torrent below. http://www.mediafire.com/file/2pcecgcd4s4i9n4/FreeMeshX_-_USA.torrent FTX compatibility: The FTX regions with the USA come with their own mesh and they are also rendered at LOD12. We have not tested compatibility extensively, and we would like to see reports from the beta users on how the FTX meshes and FreeMeshX USA mesh conflict. Since they are both the same level of detail, there may be some conflict. If there is, the likely suggestion would be to uncheck FMX - USA from your Scenery Library when flying in the FTX regions. We highly encourage the use of FTX Vectors. Any good mesh needs a good vector replacement package. IMPORTANT TIPS: 1. Defragment your mechanical HDD. The rendering of the highly detailed mesh requires a fast CPU and quick access to the data on the HDD. Obviously, if the data is fragmented and scattered all over the HDD, then that can slow the rendering down, i.e. blurries. 2. Install the mesh on a fast HDD for similar reasons. 3. Do not expect your computer to keep up if you're doing Mach 1.2 over the terrain unless your computer is very quick! The HDD has to stream the data and then process it via your CPU. That takes some time! 4. Place the FreeMeshX USA folder above the other FreeMeshX folders, including the FreeMeshX Patches folder if you have one, and below any FTX regions in the Scenery Library. 5. To reduce mesh popping (where higher LOD mesh pops in -- another limitation of the ESP engine), use a higher LOD_Radius in your fsx.cfg or p3d.cfg. We recommend a minimum of 6.5. I personally use 8.5 which is a nice compromise between performance, memory, and visuals. The higher the LOD_Radius, the further out the mesh will be drawn at its maximum LOD, less mesh popping, and the better it looks! 6. Obviously, feel free to use your texture and landclass solution. We use FTX Global and openLC USA/Canada. Because it's beautiful. Great! You read everything and are ready to download! Or tl;dr -- how do I download? http://www.mediafire.com/file/w9srqqa31a7hckk/fmx_usa_downloader.zip Unzip the above file, and follow the above instructions to begin downloading.Or download each file manually through the links provided in the raw_links_usa.txt file. Hot Fix 1 (809 MB) Fixes the error in the N40W085.bgl file where some terrain was mistakenly set to sea level. https://www.mediafire.com/file/cmub7ndrc6ygcnw/FreeMeshX - USA HotFix 1.7z Thanks! Nine Two Productions
  2. X-Life's ATC doing its best to ensure that my 300-plus virtual holidaymakers and I do indeed end up being ex-alive, as it insists on vectoring me into the 11,500 foot high Sierra Nevada mountains whilst being told to descend to 2,600 feet on the approach to Malaga. It's a good job that A350 has a terrain profile radar lol... Passing Bilbao at 38,000 feet, before the fun ensues... Coming down into the mountain range and suspecting those vectors aren't going to end well... Hmmm, down to 2,600 feet eh?, well that doesn't look too good on the PFD's terrain profile display, and the cockpit audio alert is telling me I'm getting pretty low too... Firewalling the thrust levers and pulling up over the mountain whilst the 'terrain, pull up' warning goes off. Well, at least I know that terrain warning works now...
  3. Version 1.0

    703 downloads

    This is a review of Pilot Global Ultimate NG.
  4. FSX-SE

    I am having a problem with terrain in FSX steam. When I open FSX it loads up and then I go to free flight and click "fly now". It loads to 33% then it slows down and loads about 1% every 3 minutes or so. When it finally loads the plane, runways, taxiways, but everything else is black! I recently purchased from steam Rex 4 Textures Direct and the problem started about 4 days after I installed it. I uninstalled Rex and FSX, then reinstalled them both. When I opened FSX and loaded up a flight, EXACTLY THE SAME THING HAPPENED! The only thing i can think of that I might have done to make this happen, is I had some new scenery so i deleted the old scenery i had for that airport in settings-scenery library, and I may have accidentally deleted something more important by accident. 1 other small thing, when I close FSX steam still registers it as "running" and if I try to close steam it will not close because it apparently i need to close FSX so to close steam I have to end its task in task manager. I have no idea what to do so if anyone has any idea please help me. Cheers
  5. Hey. ​This is actually my first ever post here in this forum, because usually I've got all the help I've needed the last couple of years by googling my problems, and I always end up in this forum, so I've decided that it's time for me to step out of the dark, and ask a question my self. ​After swearing allegiance to Microsoft and their flight simulators since Microsoft Flight Simulator 2000, I've last year took a jump over to Prepar3D, after reading a lot of positive feedbacks and reviews of that simulator. ​But after spending hours, days, weeks and months on tweaking, and testing the settings to get the smoothest simulator possible regarding my computer specs, I've decided to turn of all autogen (vegetation and buildings), and also turn Scenery Density to the lowest, because I don't really need that eye-candy flying at 33 000 feet. ​I use ORBX Europe and Global Vector, so I can't really complain regarding my high-altitude flying, but to come to my question. ​By turning of Scenery density, I also lose all of the airports-buildings on the default airports, and that takes away the realisme while on ground taxiing before takeoff or approaching the airport for landing. ​ ​So I wonder if there is a possibility to have the airport-buildings visible, without getting all the other buildings (city skyscrapers, etc)? ​The reason I wonder, is because of my FPS, the airport-buildings have no impact what so ever on my fps, but as soon as I takeoff, as an example, from KJFK, flying over New York, or other big cities for that matter, my FPS drops way low, and major stutters occur, but I don't experience any of that with the scenery density turned off. ​Even though I thought my computer would be good enough for FSX or P3D when I bought it a year ago. ​I also have one other problem, at the start of a flightplan, taxiing and takeoff, I usually don't get any stutters, with FPS steady at 30 FPS, but after between one and three hours of flight, when I come back after eating dinner or watching a movie or something, P3D stutters like crazy, with FPS fluctating between 1 and 20, and when I click on the setting-button, P3D just close down, and I end up back at my desktop. ​Anyone know what could be the problem? ​Addons I use, and system specs is listed down below. ​Tessellation is turned of, as I didn't see any terrain-improvements with it turned on, and I've put my monitor refresh rate to 30Mhz, via Nvidia Control Panel, and Vsync and triple buffering turned on in P3D-settings. ​PS: I really don't know if I publish this at the right place, but keep in mind, this is my first post here, and I hope I've described my problem as best as possible. ​Btw, it's sad that flight sims are so addictive, since I use to much time with the settings, rather then fly a stutterfree trip. ​Addons: ASN & Aivlasoft (on a remote computer). ​Aerosoft Airbus A321 ORBX Open LC, ORBX Europe and ORBX Global Vector. ​Radar Contact. FSPassengers. ​System Specs. ​Windows 10, x64-bit. ​Intel Core i7-4790 CPU @ 3.60GHz (non-k, so overclocking is out of the picture, but with turbo-boost on 4.0GHz) ​Hyperthread turne ​Nvidia GeForce GTX 770, 2GB memory (Driver 364.51, haven't installed the latest driver yet, 364.72). ​20GB Ram. ​Btw, my Affinitymask is set to 84. Best regards Erlend Falck
  6. In the beginning days testing my computer with FSX, I got so bad performance that I decided to spend some money into the new hardwares (new CPU and VGA). However with the help from a friend I got to know about tweaking the fsx.cfg and wow, it DOES boost the performance that I managed to run quite smooth PMDG 777/Aerosoft Airbus with some detailed airports. Of course settings only at dense and normal. Now I'm thinking about not buying new computer parts and use those money into some scenery addons. After days of reading topics and googling, I'm going for Fsglobal Ultimate and FTX Global. From what I've read these 2 shouldn't impact my fps much? So I'm done for mesh and ground texture. How about FTX Vector vs UTX? Topics dicussion between these 2 mainly from last 1 or 2 years in the early stage of Vector so there are many bugs, don't know about how is it now. Just thinking that because I use FTXglobal, using Vector should work better? No price talking here of course Vector is much cheaper comparing to all UTX packages. Last thing I want to ask is the X series of cities from Aerosoft, Aerosoft Manhatan X. What are the differences between these and the FTX Vector/UTX? Do all of them work well together and harm significantly the performance? I'm the kind of person that despite flying 99% IFR high altitude, I can sit for hours on the computer looking at the ground when crusing, let autoland do its job and panning around in spot view looking at the city below... Thanks for helping me and sorry for my bad English BTW, my specs i5 3570k@4Ghz, 8GB ram, Nvidia GTS450 (yeah, I know, horrible). With those new addons I think I should get 750Ti or 660Ti, should help me load the texture better. Buy 2nd also save some more money into the addons.
  7. Hello! Using FSX deluxe edition (not -SE) I have recently had some issues with soma "anty" textures on my terrain. It doesn't seem to affect addon scenery, but on the normal terrain there appears some boxes like those in the images. I can post my .cfg if necessary, just let me know in that case. (on approach) (top down)
  8. Hi Bryan, I'm pleased to say that so far v1.2 works well indeed. One minor issue, is that whilst I'm pleased to report that the FO will engage his EFIS Terrain as per the Dep Brief, but he never dis-engages it for the entire flight. I gather there is a point whereby the FO would disengage the Terrain radar in rw ops. Is there a voice prompt you can program for v1.3 whereby we can instruct the FO to disengage terrain, weather, or any other EFIS gauge on his side? It might be difficult to set parameters for the FO to disengage automatically due to airport terrain, elevation, transition, etc - so I figure being able to voice command him may be the most suitable and flexible?
  9. Hello . The title will tell my problem instantly. And I have read your CTD Guide as well. and it says this - "Terrain.dll - Usually indicates high scenery/terrain settings in FSX/P3D, especially Autogen" Tried it and failed it! *sigh* Problem happens approximately 2 hours into flights ! No changes to FSXCFG except widescreen enable. PMDG 777 aircraft and default scenery . no mesh addons whatsoever Any help?Has anyone found a fix? here is Appcrashview's log- Version=1 EventType=APPCRASH EventTime=130670693637617895 ReportType=2 Consent=1 UploadTime=130670693640189723 ReportIdentifier=f24fc931-a840-11e4-beeb-94de80a54a51 IntegratorReportIdentifier=f24fc930-a840-11e4-beeb-94de80a54a51 WOW64=1 NsAppName=fsx.exe Response.BucketId=e0e61976f37ccfc9444036541416fd08 Response.BucketTable=1 Response.LegacyBucketId=73798284701 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.62608.0 Sig[2].Name=Application Timestamp Sig[2].Value=54abe5b4 Sig[3].Name=Fault Module Name Sig[3].Value=terrain.dll Sig[4].Name=Fault Module Version Sig[4].Value=10.0.62608.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=54abe5e1 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00059be8 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.3.9600.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=16393 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=f304 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=f304717eeed43189b7c0d7c053f4a949 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=7ebc DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=7ebcf995f7a3c4bc1c9043de621f745a UI[2]=E:\FSX\steamapps\common\FSX\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=E:\FSX\steamapps\common\FSX\fsx.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\Program Files\Bitdefender\Bitdefender\Active virus Control\Avc3_00291_034\avcuf32.dll LoadedModule[5]=C:\WINDOWS\system32\apphelp.dll LoadedModule[6]=C:\WINDOWS\AppPatch\AcLayers.DLL LoadedModule[7]=C:\WINDOWS\SYSTEM32\msvcrt.dll LoadedModule[8]=C:\WINDOWS\SYSTEM32\USER32.dll LoadedModule[9]=C:\WINDOWS\SYSTEM32\GDI32.dll LoadedModule[10]=C:\WINDOWS\SYSTEM32\SHELL32.dll LoadedModule[11]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll LoadedModule[12]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll LoadedModule[13]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[14]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll LoadedModule[15]=C:\WINDOWS\SYSTEM32\sfc.dll LoadedModule[16]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[17]=C:\WINDOWS\SYSTEM32\RPCRT4.dll LoadedModule[18]=C:\WINDOWS\SYSTEM32\combase.dll LoadedModule[19]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\SspiCli.dll LoadedModule[21]=C:\WINDOWS\SYSTEM32\sfc_os.DLL LoadedModule[22]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[23]=C:\WINDOWS\SYSTEM32\sechost.dll LoadedModule[24]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll LoadedModule[25]=C:\WINDOWS\AppPatch\AcSpecfc.DLL LoadedModule[26]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17415_none_7c5769eaaa0aa358\COMCTL32.dll LoadedModule[27]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[28]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll LoadedModule[29]=C:\WINDOWS\SYSTEM32\ole32.dll LoadedModule[30]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\DDRAW.dll LoadedModule[32]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[33]=C:\WINDOWS\SYSTEM32\COMDLG32.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\IMM32.dll LoadedModule[35]=C:\WINDOWS\SYSTEM32\WS2_32.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[37]=C:\WINDOWS\SYSTEM32\msi.dll LoadedModule[38]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[39]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll LoadedModule[40]=C:\WINDOWS\SYSTEM32\profapi.dll LoadedModule[41]=C:\WINDOWS\SYSTEM32\SHCORE.DLL LoadedModule[42]=C:\WINDOWS\SYSTEM32\MSCTF.dll LoadedModule[43]=C:\WINDOWS\SYSTEM32\NSI.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[45]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[46]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll LoadedModule[47]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll LoadedModule[48]=E:\FSX\steamapps\common\FSX\steam_api.dll LoadedModule[49]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[50]=E:\FSX\steamapps\common\FSX\language.dll LoadedModule[51]=C:\Program Files (x86)\Steam\steamclient.dll LoadedModule[52]=C:\WINDOWS\SYSTEM32\CRYPT32.dll LoadedModule[53]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL LoadedModule[54]=C:\WINDOWS\SYSTEM32\imagehlp.dll LoadedModule[55]=C:\WINDOWS\SYSTEM32\PSAPI.DLL LoadedModule[56]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[57]=C:\Program Files (x86)\Steam\tier0_s.dll LoadedModule[58]=C:\Program Files (x86)\Steam\vstdlib_s.dll LoadedModule[59]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[60]=C:\WINDOWS\SYSTEM32\MSASN1.dll LoadedModule[61]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[62]=C:\Program Files (x86)\Steam\steam.dll LoadedModule[63]=C:\Program Files (x86)\Steam\Steam2.dll LoadedModule[64]=C:\WINDOWS\SYSTEM32\DbgHelp.dll LoadedModule[65]=C:\Program Files (x86)\Steam\CSERHelper.dll LoadedModule[66]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll LoadedModule[67]=E:\FSX\steamapps\common\FSX\API.DLL LoadedModule[68]=E:\FSX\steamapps\common\FSX\ablscpt.dll LoadedModule[69]=E:\FSX\steamapps\common\FSX\acontain.dll LoadedModule[70]=E:\FSX\steamapps\common\FSX\ai_player.dll LoadedModule[71]=E:\FSX\steamapps\common\FSX\atc.dll LoadedModule[72]=E:\FSX\steamapps\common\FSX\controls.dll LoadedModule[73]=E:\FSX\steamapps\common\FSX\demo.dll LoadedModule[74]=E:\FSX\steamapps\common\FSX\facilities.dll LoadedModule[75]=E:\FSX\steamapps\common\FSX\fe.dll LoadedModule[76]=E:\FSX\steamapps\common\FSX\flight.dll LoadedModule[77]=E:\FSX\steamapps\common\FSX\fsui.dll LoadedModule[78]=E:\FSX\steamapps\common\FSX\g2d.dll LoadedModule[79]=E:\FSX\steamapps\common\FSX\g3d.dll LoadedModule[80]=E:\FSX\steamapps\common\FSX\gps.dll LoadedModule[81]=E:\FSX\steamapps\common\FSX\livingwater.dll LoadedModule[82]=E:\FSX\steamapps\common\FSX\main.dll LoadedModule[83]=E:\FSX\steamapps\common\FSX\multiplayer.dll LoadedModule[84]=E:\FSX\steamapps\common\FSX\panels.dll LoadedModule[85]=E:\FSX\steamapps\common\FSX\sim1.dll LoadedModule[86]=E:\FSX\steamapps\common\FSX\simprop.dll LoadedModule[87]=E:\FSX\steamapps\common\FSX\simscheduler.dll LoadedModule[88]=E:\FSX\steamapps\common\FSX\sound.dll LoadedModule[89]=E:\FSX\steamapps\common\FSX\symmap.dll LoadedModule[90]=E:\FSX\steamapps\common\FSX\terrain.dll LoadedModule[91]=E:\FSX\steamapps\common\FSX\fs-traffic.dll LoadedModule[92]=E:\FSX\steamapps\common\FSX\ui.dll LoadedModule[93]=E:\FSX\steamapps\common\FSX\util.dll LoadedModule[94]=E:\FSX\steamapps\common\FSX\visualfx.dll LoadedModule[95]=E:\FSX\steamapps\common\FSX\weather.dll LoadedModule[96]=E:\FSX\steamapps\common\FSX\window.dll LoadedModule[97]=E:\FSX\steamapps\common\FSX\xuipc.dll LoadedModule[98]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[99]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[100]=C:\WINDOWS\SYSTEM32\POWRPROF.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[102]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17415_none_dad8722c5bcc2d8f\gdiplus.dll LoadedModule[103]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll LoadedModule[104]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[105]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll LoadedModule[106]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[107]=E:\FSX\steamapps\common\FSX\sdkencryptedappticket.dll LoadedModule[108]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[109]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[110]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[111]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[112]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll LoadedModule[113]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[114]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[115]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[116]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[117]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL LoadedModule[118]=C:\WINDOWS\SYSTEM32\clbcatq.dll LoadedModule[119]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[120]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[121]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\nvd3dum.dll LoadedModule[123]=C:\WINDOWS\system32\nvspcap.dll LoadedModule[124]=C:\WINDOWS\SYSTEM32\D3DCompiler_34.dll LoadedModule[125]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[126]=C:\WINDOWS\SYSTEM32\d3d10_1.dll LoadedModule[127]=C:\WINDOWS\SYSTEM32\d3d10_1core.dll LoadedModule[128]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[129]=C:\Windows\SYSTEM32\dxdiagn.dll LoadedModule[130]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[132]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[133]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[134]=C:\WINDOWS\system32\winbrand.dll LoadedModule[135]=C:\WINDOWS\SYSTEM32\WINTRUST.dll LoadedModule[136]=C:\WINDOWS\system32\nvapi.dll LoadedModule[137]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[138]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[139]=C:\Windows\SYSTEM32\gameux.dll LoadedModule[140]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17415_none_a9ed7f470139b3c1\COMCTL32.dll LoadedModule[141]=C:\Windows\SYSTEM32\XmlLite.dll LoadedModule[142]=C:\Windows\SYSTEM32\msxml6.dll LoadedModule[143]=C:\WINDOWS\System32\Wpc.dll LoadedModule[144]=C:\WINDOWS\System32\NETAPI32.dll LoadedModule[145]=C:\WINDOWS\SYSTEM32\Normaliz.dll LoadedModule[146]=C:\WINDOWS\System32\wevtapi.dll LoadedModule[147]=C:\WINDOWS\System32\netutils.dll LoadedModule[148]=C:\WINDOWS\System32\srvcli.dll LoadedModule[149]=C:\WINDOWS\System32\wkscli.dll LoadedModule[150]=C:\WINDOWS\System32\SAMCLI.DLL LoadedModule[151]=C:\Windows\System32\Windows.Globalization.dll LoadedModule[152]=C:\Windows\System32\Bcp47Langs.dll LoadedModule[153]=C:\Windows\System32\Windows.Web.dll LoadedModule[154]=E:\FSX\steamapps\common\FSX\uiautomationcore.dll LoadedModule[155]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[156]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[157]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[158]=C:\WINDOWS\SYSTEM32\RICHED20.DLL LoadedModule[159]=C:\WINDOWS\SYSTEM32\USP10.dll LoadedModule[160]=C:\WINDOWS\SYSTEM32\msls31.dll LoadedModule[161]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[162]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[163]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[164]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[165]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[166]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[167]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[168]=C:\WINDOWS\SYSTEM32\dinput.DLL LoadedModule[169]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[170]=E:\FSX\steamapps\common\FSX\PMDG\DLLs\PMDG_Interface.dll LoadedModule[171]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[172]=E:\FSX\steamapps\common\FSX\RAASPRO\RAASPRO.dll LoadedModule[173]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[174]=C:\WINDOWS\SYSTEM32\winhttp.dll LoadedModule[175]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[176]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[177]=C:\Windows\System32\rasadhlp.dll LoadedModule[178]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[179]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[180]=C:\WINDOWS\SYSTEM32\MSDART.DLL LoadedModule[181]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[182]=C:\Windows\SYSTEM32\comsvcs.dll LoadedModule[183]=C:\Windows\SYSTEM32\msjetoledb40.dll LoadedModule[184]=C:\Windows\SYSTEM32\msjet40.dll LoadedModule[185]=C:\Windows\SYSTEM32\msjter40.dll LoadedModule[186]=C:\Windows\SYSTEM32\mswstr10.dll LoadedModule[187]=C:\Windows\SYSTEM32\MSJINT40.DLL LoadedModule[188]=C:\WINDOWS\SYSTEM32\DPAPI.DLL LoadedModule[189]=C:\Windows\SYSTEM32\mstext40.dll LoadedModule[190]=C:\WINDOWS\SYSTEM32\mlang.dll LoadedModule[191]=C:\WINDOWS\SYSTEM32\RAASAUDIO32.DLL LoadedModule[192]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\xactengine3_4.dll LoadedModule[194]=C:\WINDOWS\SYSTEM32\XAudio2_4.dll LoadedModule[195]=E:\FSX\steamapps\common\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll LoadedModule[196]=E:\FSX\steamapps\common\FSX\VistaMare\ViMaCoreX.dll LoadedModule[197]=E:\FSX\steamapps\common\FSX\Modules\FSUIPC4.dll LoadedModule[198]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll LoadedModule[199]=C:\WINDOWS\SYSTEM32\mfc100.dll LoadedModule[200]=C:\WINDOWS\SYSTEM32\MSVCR100.dll LoadedModule[201]=C:\WINDOWS\SYSTEM32\MSVCP100.dll LoadedModule[202]=C:\WINDOWS\SYSTEM32\MFC100ENU.DLL LoadedModule[203]=C:\WINDOWS\system32\propsys.dll LoadedModule[204]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[205]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[206]=C:\WINDOWS\system32\msimtf.dll LoadedModule[207]=C:\WINDOWS\SYSTEM32\d2d1.dll LoadedModule[208]=C:\WINDOWS\SYSTEM32\DWrite.dll LoadedModule[209]=C:\WINDOWS\SYSTEM32\d3d10warp.dll LoadedModule[210]=C:\Windows\SYSTEM32\uiautomationcore.dll LoadedModule[211]=e:\fsx\steamapps\common\fsx\GAUGES\PMDG_777X.DLL LoadedModule[212]=C:\WINDOWS\SYSTEM32\WSOCK32.dll LoadedModule[213]=C:\WINDOWS\SYSTEM32\XAudio2_7.dll LoadedModule[214]=E:\FSX\steamapps\common\FSX\Gauges\PMDG_777X_2.dll LoadedModule[215]=C:\WINDOWS\SYSTEM32\snmpapi.dll LoadedModule[216]=C:\WINDOWS\system32\napinsp.dll LoadedModule[217]=C:\WINDOWS\system32\pnrpnsp.dll LoadedModule[218]=C:\WINDOWS\system32\NLAapi.dll LoadedModule[219]=C:\WINDOWS\System32\winrnr.dll LoadedModule[220]=C:\WINDOWS\SYSTEM32\icmp.Dll LoadedModule[221]=C:\Windows\SYSTEM32\msjtes40.dll LoadedModule[222]=C:\WINDOWS\SYSTEM32\VBAJET32.DLL LoadedModule[223]=C:\WINDOWS\SYSTEM32\expsrv.dll LoadedModule[224]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll LoadedModule[225]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[226]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=E:\FSX\steamapps\common\FSX\fsx.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=7912059C691EC53D52465B2D04ABD1E8 Here is another one from day before yesterday , And I have no Idea if this is also a terrain.dll problem so I need confirmation. Version=1 EventType=AppHangB1 EventTime=130670956687812709 ReportType=3 Consent=1 UploadTime=130670956703774041 ReportIdentifier=316f9efd-a87e-11e4-beeb-94de80a54a51 IntegratorReportIdentifier=316f9efe-a87e-11e4-beeb-94de80a54a51 WOW64=1 NsAppName=fsx.exe Response.BucketId=64673cc1af3429d30727bbae3f815ac9 Response.BucketTable=5 Response.LegacyBucketId=50 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.62608.0 Sig[2].Name=Application Timestamp Sig[2].Value=54abe5b4 Sig[3].Name=Hang Signature Sig[3].Value=d705 Sig[4].Name=Hang Type Sig[4].Value=134217728 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.3.9600.2.0.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=16393 DynamicSig[22].Name=Additional Hang Signature 1 DynamicSig[22].Value=d7057f7f650f42c7eba63e86631750cf DynamicSig[23].Name=Additional Hang Signature 2 DynamicSig[23].Value=3c2d DynamicSig[24].Name=Additional Hang Signature 3 DynamicSig[24].Value=3c2d5e7c2ecf0f905cb741fd01eef8bb DynamicSig[25].Name=Additional Hang Signature 4 DynamicSig[25].Value=d705 DynamicSig[26].Name=Additional Hang Signature 5 DynamicSig[26].Value=d7057f7f650f42c7eba63e86631750cf DynamicSig[27].Name=Additional Hang Signature 6 DynamicSig[27].Value=3c2d DynamicSig[28].Name=Additional Hang Signature 7 DynamicSig[28].Value=3c2d5e7c2ecf0f905cb741fd01eef8bb UI[3]=Microsoft Flight Simulator® is not responding UI[4]=If you close the program, you might lose information. UI[5]=Close the program UI[6]=Close the program UI[7]=Close the program LoadedModule[0]=E:\FSX\steamapps\common\FSX\fsx.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\Program Files\Bitdefender\Bitdefender\Active virus Control\Avc3_00292_035\avcuf32.dll LoadedModule[5]=C:\WINDOWS\system32\apphelp.dll LoadedModule[6]=C:\WINDOWS\AppPatch\AcLayers.DLL LoadedModule[7]=C:\WINDOWS\SYSTEM32\msvcrt.dll LoadedModule[8]=C:\WINDOWS\SYSTEM32\USER32.dll LoadedModule[9]=C:\WINDOWS\SYSTEM32\GDI32.dll LoadedModule[10]=C:\WINDOWS\SYSTEM32\SHELL32.dll LoadedModule[11]=C:\WINDOWS\SYSTEM32\SHLWAPI.dll LoadedModule[12]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll LoadedModule[13]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[14]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll LoadedModule[15]=C:\WINDOWS\SYSTEM32\sfc.dll LoadedModule[16]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[17]=C:\WINDOWS\SYSTEM32\RPCRT4.dll LoadedModule[18]=C:\WINDOWS\SYSTEM32\combase.dll LoadedModule[19]=C:\WINDOWS\SYSTEM32\CFGMGR32.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\SspiCli.dll LoadedModule[21]=C:\WINDOWS\SYSTEM32\sfc_os.DLL LoadedModule[22]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[23]=C:\WINDOWS\SYSTEM32\sechost.dll LoadedModule[24]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll LoadedModule[25]=C:\WINDOWS\AppPatch\AcSpecfc.DLL LoadedModule[26]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17415_none_7c5769eaaa0aa358\COMCTL32.dll LoadedModule[27]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[28]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll LoadedModule[29]=C:\WINDOWS\SYSTEM32\ole32.dll LoadedModule[30]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\DDRAW.dll LoadedModule[32]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[33]=C:\WINDOWS\SYSTEM32\COMDLG32.dll LoadedModule[34]=C:\WINDOWS\SYSTEM32\IMM32.dll LoadedModule[35]=C:\WINDOWS\SYSTEM32\WS2_32.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[37]=C:\WINDOWS\SYSTEM32\msi.dll LoadedModule[38]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[39]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll LoadedModule[40]=C:\WINDOWS\SYSTEM32\profapi.dll LoadedModule[41]=C:\WINDOWS\SYSTEM32\SHCORE.DLL LoadedModule[42]=C:\WINDOWS\SYSTEM32\MSCTF.dll LoadedModule[43]=C:\WINDOWS\SYSTEM32\NSI.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[45]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[46]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll LoadedModule[47]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll LoadedModule[48]=E:\FSX\steamapps\common\FSX\steam_api.dll LoadedModule[49]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[50]=E:\FSX\steamapps\common\FSX\language.dll LoadedModule[51]=C:\Program Files (x86)\Steam\steamclient.dll LoadedModule[52]=C:\WINDOWS\SYSTEM32\CRYPT32.dll LoadedModule[53]=C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL LoadedModule[54]=C:\WINDOWS\SYSTEM32\imagehlp.dll LoadedModule[55]=C:\WINDOWS\SYSTEM32\PSAPI.DLL LoadedModule[56]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[57]=C:\Program Files (x86)\Steam\tier0_s.dll LoadedModule[58]=C:\Program Files (x86)\Steam\vstdlib_s.dll LoadedModule[59]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[60]=C:\WINDOWS\SYSTEM32\MSASN1.dll LoadedModule[61]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[62]=C:\Program Files (x86)\Steam\steam.dll LoadedModule[63]=C:\Program Files (x86)\Steam\Steam2.dll LoadedModule[64]=C:\WINDOWS\SYSTEM32\DbgHelp.dll LoadedModule[65]=C:\Program Files (x86)\Steam\CSERHelper.dll LoadedModule[66]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll LoadedModule[67]=E:\FSX\steamapps\common\FSX\API.DLL LoadedModule[68]=E:\FSX\steamapps\common\FSX\ablscpt.dll LoadedModule[69]=E:\FSX\steamapps\common\FSX\acontain.dll LoadedModule[70]=E:\FSX\steamapps\common\FSX\ai_player.dll LoadedModule[71]=E:\FSX\steamapps\common\FSX\atc.dll LoadedModule[72]=E:\FSX\steamapps\common\FSX\controls.dll LoadedModule[73]=E:\FSX\steamapps\common\FSX\demo.dll LoadedModule[74]=E:\FSX\steamapps\common\FSX\facilities.dll LoadedModule[75]=E:\FSX\steamapps\common\FSX\fe.dll LoadedModule[76]=E:\FSX\steamapps\common\FSX\flight.dll LoadedModule[77]=E:\FSX\steamapps\common\FSX\fsui.dll LoadedModule[78]=E:\FSX\steamapps\common\FSX\g2d.dll LoadedModule[79]=E:\FSX\steamapps\common\FSX\g3d.dll LoadedModule[80]=E:\FSX\steamapps\common\FSX\gps.dll LoadedModule[81]=E:\FSX\steamapps\common\FSX\livingwater.dll LoadedModule[82]=E:\FSX\steamapps\common\FSX\main.dll LoadedModule[83]=E:\FSX\steamapps\common\FSX\multiplayer.dll LoadedModule[84]=E:\FSX\steamapps\common\FSX\panels.dll LoadedModule[85]=E:\FSX\steamapps\common\FSX\sim1.dll LoadedModule[86]=E:\FSX\steamapps\common\FSX\simprop.dll LoadedModule[87]=E:\FSX\steamapps\common\FSX\simscheduler.dll LoadedModule[88]=E:\FSX\steamapps\common\FSX\sound.dll LoadedModule[89]=E:\FSX\steamapps\common\FSX\symmap.dll LoadedModule[90]=E:\FSX\steamapps\common\FSX\terrain.dll LoadedModule[91]=E:\FSX\steamapps\common\FSX\fs-traffic.dll LoadedModule[92]=E:\FSX\steamapps\common\FSX\ui.dll LoadedModule[93]=E:\FSX\steamapps\common\FSX\util.dll LoadedModule[94]=E:\FSX\steamapps\common\FSX\visualfx.dll LoadedModule[95]=E:\FSX\steamapps\common\FSX\weather.dll LoadedModule[96]=E:\FSX\steamapps\common\FSX\window.dll LoadedModule[97]=E:\FSX\steamapps\common\FSX\xuipc.dll LoadedModule[98]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[99]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[100]=C:\WINDOWS\SYSTEM32\POWRPROF.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[102]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17415_none_dad8722c5bcc2d8f\gdiplus.dll LoadedModule[103]=C:\WINDOWS\SYSTEM32\d3dx9_34.dll LoadedModule[104]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[105]=C:\WINDOWS\SYSTEM32\d3dx10_34.dll LoadedModule[106]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[107]=E:\FSX\steamapps\common\FSX\sdkencryptedappticket.dll LoadedModule[108]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[109]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[110]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[111]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[112]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll LoadedModule[113]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[114]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[115]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[116]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[117]=C:\WINDOWS\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL LoadedModule[118]=C:\WINDOWS\SYSTEM32\clbcatq.dll LoadedModule[119]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[120]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[121]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\nvd3dum.dll LoadedModule[123]=C:\WINDOWS\system32\nvspcap.dll LoadedModule[124]=C:\WINDOWS\SYSTEM32\D3DCompiler_34.dll LoadedModule[125]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[126]=C:\WINDOWS\SYSTEM32\d3d10_1.dll LoadedModule[127]=C:\WINDOWS\SYSTEM32\d3d10_1core.dll LoadedModule[128]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[129]=C:\Windows\SYSTEM32\dxdiagn.dll LoadedModule[130]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[132]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[133]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[134]=C:\WINDOWS\system32\winbrand.dll LoadedModule[135]=C:\WINDOWS\SYSTEM32\WINTRUST.dll LoadedModule[136]=C:\WINDOWS\system32\nvapi.dll LoadedModule[137]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[138]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[139]=C:\Windows\SYSTEM32\gameux.dll LoadedModule[140]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17415_none_a9ed7f470139b3c1\COMCTL32.dll LoadedModule[141]=C:\Windows\SYSTEM32\XmlLite.dll LoadedModule[142]=C:\Windows\SYSTEM32\msxml6.dll LoadedModule[143]=C:\WINDOWS\System32\Wpc.dll LoadedModule[144]=C:\WINDOWS\System32\NETAPI32.dll LoadedModule[145]=C:\WINDOWS\SYSTEM32\Normaliz.dll LoadedModule[146]=C:\WINDOWS\System32\wevtapi.dll LoadedModule[147]=C:\WINDOWS\System32\netutils.dll LoadedModule[148]=C:\WINDOWS\System32\srvcli.dll LoadedModule[149]=C:\WINDOWS\System32\wkscli.dll LoadedModule[150]=C:\WINDOWS\System32\SAMCLI.DLL LoadedModule[151]=C:\Windows\System32\Windows.Globalization.dll LoadedModule[152]=C:\Windows\System32\Bcp47Langs.dll LoadedModule[153]=C:\Windows\System32\Windows.Web.dll LoadedModule[154]=E:\FSX\steamapps\common\FSX\uiautomationcore.dll LoadedModule[155]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[156]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[157]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[158]=C:\WINDOWS\SYSTEM32\RICHED20.DLL LoadedModule[159]=C:\WINDOWS\SYSTEM32\USP10.dll LoadedModule[160]=C:\WINDOWS\SYSTEM32\msls31.dll LoadedModule[161]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[162]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[163]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[164]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[165]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[166]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[167]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[168]=C:\WINDOWS\SYSTEM32\dinput.DLL LoadedModule[169]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[170]=E:\FSX\steamapps\common\FSX\PMDG\DLLs\PMDG_Interface.dll LoadedModule[171]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[172]=E:\FSX\steamapps\common\FSX\RAASPRO\RAASPRO.dll LoadedModule[173]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[174]=C:\WINDOWS\SYSTEM32\winhttp.dll LoadedModule[175]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[176]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[177]=C:\Windows\System32\rasadhlp.dll LoadedModule[178]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[179]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[180]=C:\WINDOWS\SYSTEM32\MSDART.DLL LoadedModule[181]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[182]=C:\Windows\SYSTEM32\comsvcs.dll LoadedModule[183]=C:\Windows\SYSTEM32\msjetoledb40.dll LoadedModule[184]=C:\Windows\SYSTEM32\msjet40.dll LoadedModule[185]=C:\Windows\SYSTEM32\msjter40.dll LoadedModule[186]=C:\Windows\SYSTEM32\mswstr10.dll LoadedModule[187]=C:\Windows\SYSTEM32\MSJINT40.DLL LoadedModule[188]=C:\WINDOWS\SYSTEM32\DPAPI.DLL LoadedModule[189]=C:\Windows\SYSTEM32\mstext40.dll LoadedModule[190]=C:\WINDOWS\SYSTEM32\mlang.dll LoadedModule[191]=C:\WINDOWS\SYSTEM32\RAASAUDIO32.DLL LoadedModule[192]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\xactengine3_4.dll LoadedModule[194]=C:\WINDOWS\SYSTEM32\XAudio2_4.dll LoadedModule[195]=E:\FSX\steamapps\common\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dll LoadedModule[196]=E:\FSX\steamapps\common\FSX\VistaMare\ViMaCoreX.dll LoadedModule[197]=E:\FSX\steamapps\common\FSX\Modules\FSUIPC4.dll LoadedModule[198]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll LoadedModule[199]=C:\WINDOWS\SYSTEM32\mfc100.dll LoadedModule[200]=C:\WINDOWS\SYSTEM32\MSVCR100.dll LoadedModule[201]=C:\WINDOWS\SYSTEM32\MSVCP100.dll LoadedModule[202]=C:\WINDOWS\SYSTEM32\MFC100ENU.DLL LoadedModule[203]=C:\WINDOWS\system32\propsys.dll LoadedModule[204]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[205]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[206]=C:\WINDOWS\system32\msimtf.dll LoadedModule[207]=C:\WINDOWS\SYSTEM32\d2d1.dll LoadedModule[208]=C:\WINDOWS\SYSTEM32\DWrite.dll LoadedModule[209]=C:\WINDOWS\SYSTEM32\d3d10warp.dll LoadedModule[210]=C:\Windows\SYSTEM32\uiautomationcore.dll LoadedModule[211]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[212]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL LoadedModule[213]=e:\fsx\steamapps\common\fsx\GAUGES\PMDG_777X.DLL LoadedModule[214]=C:\WINDOWS\SYSTEM32\WSOCK32.dll LoadedModule[215]=C:\WINDOWS\SYSTEM32\XAudio2_7.dll LoadedModule[216]=E:\FSX\steamapps\common\FSX\Gauges\PMDG_777X_2.dll LoadedModule[217]=C:\WINDOWS\SYSTEM32\snmpapi.dll LoadedModule[218]=C:\WINDOWS\system32\napinsp.dll LoadedModule[219]=C:\WINDOWS\system32\pnrpnsp.dll LoadedModule[220]=C:\WINDOWS\system32\NLAapi.dll LoadedModule[221]=C:\WINDOWS\System32\winrnr.dll LoadedModule[222]=C:\WINDOWS\SYSTEM32\icmp.Dll LoadedModule[223]=C:\Windows\SYSTEM32\msjtes40.dll LoadedModule[224]=C:\WINDOWS\SYSTEM32\VBAJET32.DLL LoadedModule[225]=C:\WINDOWS\SYSTEM32\expsrv.dll LoadedModule[226]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped responding and was closed ConsentKey=AppHangXProcB1 AppName=Microsoft Flight Simulator® AppPath=E:\FSX\steamapps\common\FSX\fsx.exe ReportDescription=A problem caused this program to stop interacting with Windows. NsPartner=windows NsGroup=windows8 ApplicationIdentity=7912059C691EC53D52465B2D04ABD1E8 I hope someone will able to fix it ! Thanks in advance! Windows 8.1 Pro, Intel i7 4770k (no overclocking) ,NVidia GTX650ti , 8GB DDR3 RAM,1TB Seagate SSD.
  10. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  11. Has V2.4 fixed your terrain shadows? I've just spent an hour flying around Biarritz and Bilbao enjoying the new V2.4. All is well apart from my terrain shadows. When I turn them on the shadowing pops on and off and redraws itself ahead of me (in sharp jumps not smoothly). This is with all settings on the slider. Looks awful so have switched it off again! I thought this was supposed to be one of the main fixes in V2.4? Or could this be my PC and GPU showing their (4yr old) age? Any thoughts?
  12. Good evening all, I usually fly jetliners in Europe mainly, sometimes in North America and Asia..I now want to do some General Aviation flying around Alaska.. Because i now am going to fly a lot lower than with the jets, i would like to know which freeware and payware add ons there are to enhance the flying in Alaska..I don`t exactely know the difference between terrain and mesh, so if anyone would like to fill me in a bit i would appreciate it.. Thanks..
  13. Hi guys! I've experienced a blue weird terrain problem in my fsx. I used ENB but deleted it because i thought maybe that was the problem but its still blue. You can see here: http://gyazo.com/36bcb03a5421052e1bf73082f5319857 Thanks guys and have a good day! /Jacob
  14. So I have just found out that the terrain at some of the airports is covering the runway, making it had to taxi and takeoff: Has anyone else had this problem? is there a solution for it? thanks for your help.
  15. This needs the GPWS warning system for the planes including the 'woop woop, pull up' sound. ALSO I beg for you guys to light up the cockpit in planes at nightime because it is too dark
  16. I am looking for basically three things to run as addons with my FSX installation: Realistic Terrain (mountains, valleys, rivers, streets, buildings, etc.) Realistic weather (clouds, skies, sun, day/night, weather,etc.) Realistic crew (flight attendant custom announcements) I've seen ORBX but not sure which one to get...seems to be too many options... just need one that will handle all the terrain. I've seen REX but also Active SKy - which performs better (san francisco fog appearance) I've seen FS Cabin Crew and FSPassengers... are these outdated? are there better ones?
  17. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  18. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  19. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  20. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  21. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  22. Hi all, I have spent quite a few hours with the PMDG 777 now and I am still delighted by this magnificient aircraft. So first of all, it's time to say thanks from my side for creating this impressive simulation. On of the aspects I really love about the latest PMDG aircraft is the EGPWS simulation. Back, in old Aerowinx PS1 days, I made myself familiar with loads of technical details on EGPWS and I still love this system. That's why I would like to discuss a few things I noticed. I think I found two bugs and a few things which do not "feel" correct. Read on for more, please. 1) First of all, let me start with an issue I found comparing the PMDG 777 EGPWS display with real world photos (simulating them in PMDG). Generally, the 777 compares very well but: This particular image shows the first issue quite well - note the high and low values from the PEAKS MODE display just below the TERR announciation. (Numbers 143 and 000). You might remember: this indicates the highest (14.300') and lowest terrain points shown on the ND. Now, let's switch off the Water Display in CYAN: Note that the figure indicating the lowest terrain figure on the ND terrain display has changed from 000 to 072, indicating the lowest terrain point has an elevation of 7.200'. I think, there is a bug - namely the value showing 000 with water display turned on. Whenever Water in CYAN is switched on and water is visible the lowest terrain value is 000. This is not correct. While I understand this from software programmers point of view - the lowest point IS indeed 000 (and shown in blue) - it does not make sense from the EGPWS logic point of view - the pilot is still interested in the terrain and not in the sea level elevation. In the real world, even with sea level water in CYAN display, the aircraft shows 073 on the peaks mode display, see here. (My apologies for showing an Airbus cockpit. :lol: ). Of course, you'll note the excellent agreement between simulation (PMDG) and real world (Honeywell EGPWS). By the way, the position shown in the images should be obvious. 2) My second "bug" results from pure chance and not from systematic observation. Recently I was flying the ILS34 approach into Wellington, New Zealand (NZWN) (before Wordlflight 2013 and during WF.) Two issues here: on the approach, I got a spurious TERRAIN PULL UP warning and an obviously incorrect terrain display. To demonstrate this, I'll show a couple of screenshots from the approach on the ILS34. First image: on ILS34, at 560', 1.8 DME out. You can already see that I have received a PULL UP warning although I am well established on the ILS. This may be something worth looking into - the warning is false. But notice - again - the SEA WATER display in CYAN is on and shown correctly. Second Image: A few seconds later, on the ILS at 0.4 DME and 110'. I still have the TERRAIN message and the PULL UP warning on the PDF, but notice that the sea level display in CYAN is gone and replaced by all yellow colour. This is clearly not correct. Just to show that the incorrect 'all yellow' display of the sea level is not related to the TERRAIN message, here is the ND during taxi into the ramp. Again, sea level display in CYAN is not shown were it should be shown. Okay, this concludes my first section on things where I think that something is wrong. 3) In this third section, I will show a few things where I think that the EGPWS terrain display is not entirely correct. But is more like a "feeling" - I cannot really prove nor do I have images or documentation to show that something is wrong. I initially discovered this next issues while flying on airway L888 from KCA in Western China towards SANLI. This is an airway which runs directly across the Tibetian plateau over terrain of typically 15.000' or more (with peaks up to 20.000') and with sector minimum altitudes in the 25.000' to 29.000' range. Approaching LUVAR intersection, I noticed this display by the EGPWS computer. Now, this looks strange to me because: - it clearly shows that EGPWS is in a PEAKS MODE display (only green) - the highest terrain figure (198) indicated the highest terrain of 19.800' is clearly well below the airplane cruising at FL370 - the terrain elevation below the aircraft is about 14.500' (and not 107) - and the display is all green This is very confusing to the pilot and kind of violates the principle of the EGPWS Peaks Mode display to show only the highest peak elevations (e.g. mountain tops) around and not flat terrain. From a situational awareness point of view, this does not look correct. As far as I know, there is no image anywhere in the literature, on the web, in a DVD/Blueway which shows an all green terrain display from EGPWS (from WX radar of course, but not from EGPWS). My feeling is that a lowest terrain elevation of something like 15.500' would be more appropriate and thus show peaks only. The bottom line of this section is: I think that an entirely green EGPWS terrain display is not shown on a real world aircraft. Obviously, this image changes when the ND range is changed and I could continue showing images with different ranges. It looks better and different with a high ND range, but with a low (10 or 20 NM) ND range, I again get an all green display. There is probably no point in showing these images. Just one for the moment being... the issue of an all green display is not limited to the special case of flying along airway L888 over Tibet. Earlier on the same flight, around LASDO intersection (N46.5, E076 in Kazakhstan), I noticed a similar behaviour over essentially flat terrain. Here the low figure is 1100' (011) and the high figure is 1500' (015) of PEAKS display, which is basically a very flat desert. Or another example (without image), the same behaviour (all green) over flat terrain over Argentina, just 10 miles west of RYD VOR (approx. S34, W065). To conclude, I think that I have found a few issues within the EGPWS terrain display of the 777 (and possibly the 737NGX; my forum search has shown a similar post for the 737). I would appreciate some feedback, possibly from PMDG as well and wonder if this could be adressed in any upcoming service update for this great aircraft. Thanks a lot, Markus
  23. I started fsx two days ago, and all, and i mean ALL the land was shown as water with autogen on top. I reainstalled 3 times, deleted the files, repaired the registry with the flight1 tool. I dont use UTX or any terrain mods for that matter. I did in past use terrain mods, but never UTX. I only have a couple payware planes. Specs: Phenom II X4 965 @4 GHz, 8GB RAM, 1TB HDD, GTX 650 Overclocked w/ 2GB VRAM thanks-Morris
  24. Hi, I am new to the community and I am currently working on a photo scenery for Wick Airport - EGPC. I followed this brief tutorial: http://www.youtube.com/watch?v=M41bBEw7_OM And I have managed to get a brief photo scenery going. I know nothing about watermasks and/or blendmasks however, following a different tutorial, I used GIMP to create a watermask and blendmask. My blendmask doesn't seem to work - according to what I think it does, however, the water mask partially does I think. Basically, if anyone could help me solve this issue, I would be very appreciative. My next steps - after this is sorted - are to use ADE9X to re-align the AFCAD to the scenery and after that, use whisplacer to add houses/buildings etc. into the scenery. I would also like to create some winter, night, autumn and spring textures but, again, I have no idea how to do so. Any help would be much appreciated. Regards, TheFSFreak
  25. The manual shows two modes for the EGPWS terrain display, standard and standard+peaks. Has anyone found out how you switch between the two. Mine shows standard+peaks and I'd like to switch to standard mode. The only controls I've found switch between WxR and Terrain display and disable terrain. Also the control panel can be used in metric and imperial/US units, but the sim only seems to show imperial/US. Seems daft to allow weight and balance to be prepared in kilograms and then only use pounds in the sim. Have I missed something? Can't ask in the Majestic forum yet as I'm still waiting for them to approve my registration.