Jim Young

I would suspect a software developer, say HiFi (ASN), would develop their product to work efficiently with FSX/FSX-SE/P3D w/o additional addons. It seems to me HiFi and PMDG and REX and GEX and FTX/Orbx developers work to get their 'individual product' to work with the flight simulator it is being developed for and not necessarily for other addons that one might purchase to also use with a simulator. I suspect they think you will just buy their addon and that will be it. However, it is usually a combination of all of these addons that cause problems and not necessarily one individual addon. Now I see that the P3D simulator also has Carenado and Milviz addons included with their product so I would assume those would be okay. The developer tests with the simulator and not with a bunch of addons. They made their product for one product and not for many current and future addons. So, when you crank up your hardware to run P3D, ASN, Orbx/FTX products, a PMDG aircraft like the 777 or the iFly 747, then your computer might have some difficulties running all of them together with high settings, or sometimes even in moderate settings depending on the length of the flight. Because the longer the flight, the more addons installed, the more likely you will have difficulties landing at a commercial addon airport 3 or 4 hours later no matter how powerful your computer. That's the facts. I remember when FSX first came out many upgraded to the latest and greatest hardware at the time and also upgraded to Vista. They found they had to lower their settings or else get a crash. Then someone discovered the /3GB switch where we could get another GB of VAS when employing the switch and we had fewer crashes and more addons were produced and installed and things started going downhill again. Then came the "tweaks".... (I won't discuss those as that's another long story but it got ugly...). Best regards,

A possible fix, although with P3D, can be found at the following link - http://www.avsim.com/topic/471574-black-screen/ Most of these problems with black screens are caused by the display drivers. If you recently installed new display drivers, you should roll them back to the previous version or install the previous version. I personally have never had any problems with installing the latest and greatest display drivers but many people who have suffered with black screens have fixed their problem just by rolling back the display driver. Why they get black screens and I don't with the latest and greatest is unknown but it is a solution that you should consider. The AVSIM CTD Guide (see my signature for the link to this file) has many other suggestions you can try. For instance, most problems with FSX can be fixed by deleting the fsx.cfg, restarting FSX and letting the config rebuild. Delete/Rebuild your Facilities/Scenery Indexes and Shader Folders – These are temporary folders and should be deleted periodically (they will be rebuilt): Facilities/Scenery Indexes are located in C:\Program Data\Microsoft\FSX\(hidden). Delete the Facilities and Scenery folders. They will be rebuilt. Delete the Shader folders located in C:\Users\(your username)\AppData\Local/Microsoft\ FSX\Shader10 and Shader folders (hidden). The Shader 10 folder is created when you enable DX10 Preview in FSX. The Shaders folder for DX9 will always be created. When you restart FSX/P3D, these folders will be rebuilt. Deleting these temporary folders has also been known to fix some CTD’s. You stated you did a "repair" of FSX and then, when you tried to access FSX it crashed. When you do a repair of FSX, you must do a repair of FSX deluxe (which is the basic version of FSX); then if you have Acceleration installed, you must also do a repair by inserting those disks and doing a repair there too. If you did not install Acceleration, then you must have installed SP1 and SP2 to FSX. In that case you must also do a repair of SP1 and SP2 before you can restart FSX. If you need any further assistance, please let us know and we will try to help. We know that everyone is not a computer expert or that knowledgeable of computers and FSX so don't be concerned and let us know if you need additional help. Best regards,

The wife of member, Newcombe (Ron Freer), has informed me that her husband passed away one year ago. Our sincere condolences to her and her family. May Ron rest in peace.

AA has always been a problem in FSX. The settings in the AVSIM FSX Configuration Guide will definitely remove any jaggies though. Best regards,

Good find Kenz! The search engine is not totally broken and it might make it easier to find the code that isn't working properly. Best regards,

If there's an entry in the Add/Remove Programs, then use that. If not, just go to FSX\SimObjects\Airplanes\ and delete the aircraft. Best regards,

Looks like it will be down for some time. Chase is looking for a fix in the code. Apologize for the inconvenience. Best regards,

That's a program like MyTrafficX. It puts realistic aircraft at airports and the aircraft follow flight plans. Realistic aircraft = American Airlines, United, Delta, Lufthansa, etc. The default does the same and follows flight plans. So, if you did not purchase MyTrafficX or some other commercial program that enhances the default depiction of aircraft around your airport, then most likely you have the default program running. This means you might have static aircraft located in the area of your aircraft. Static aircraft are those that developers placed at airports to make their airport more realistic. They do nothing more than that. You can tell whether it is the default aircraft or commercial AI program by looking at the aircraft around your airport. If you have American or United Airlines in or around your airport, it is most likely a commercial program. If you have aircraft with names you have never heard of, then it is most likely the default as they use names like World Airlines. "How can I disable it in cfg?" MyTrafficX is enabled/disabled in the Scenery Library or Scenery.cfg. You cannot. You are correct in stating simconnect comes with an addon software. Sometimes the software installs it properly, sometimes not. If you did not disable UserAccessControls (UAC) or your anti-virus program during installation, one of those programs probably stopped proper installation of your addons as UAC and any anti-virus program is there to protect you from evil people around the world and they will not allow you to install the product properly. This is why most experts recommend you disable UAC and any anti-virus program before you install FSX-SE or any addon. Hope this helps. Best regards,

Hi Ed, Sorry to hear you continue to have problems. The ai_player.dll is connected to your default or commercial AI program. If commercial, disable it in the scenery.cfg and see if this fixes the problem. If so, then there is a problem with the AI program. I recently had this error while flying from Palm Springs to LAX. I had UTX 2.1 installed and discovered 4 or 5 entries in the scenery.cfg were not enabled. I enabled them and so far the problem has not reoccurred. One of the entries was "UT Exclusions for Default Scenery". So maybe there was a conflict between the default scenery and UTX. Impossible to know for sure but the problem is gone. Many of the AFCAD's in MyTrafficX or 6 have static aircraft and maybe that caused a problem. The ai_player.dll error sometimes just goes away too. But, it is important to know if the error occurs in the same area (like in my experience). That indicates there is something in that area and you will have to troubleshoot. For instance, if it occurs constantly over a commercial airport, disable the airport and see if the problem goes away. If there's a non-commercial airport below the area of your crash, get the name of the airport and disable it in MyTrafficX or 6 (I'm assuming you have MyTraffic). It is impossible for me to tell what caused the EZDOK crash but the error mentions network server problems and I would assume you did not have the correct version of Simconnect installed or it was installed improperly. Your system may still have remnants of EZDOK running and you should run a program like CCleaner to removed any unwanted system registry entries. This is really required if you simply deleted EZDOK w/o using the uninstall program (if they have one). One thing you can do is to do a driver check. You state you have Windows 10 and you should make sure all of your hardware drivers are up-to-date. I use a freeware program called Driver Booster - http://www.iobit.com/en/driver-booster.php. It is freeware even to download and install updated drivers but it has a lot of nags to try to get you to register the program. I think everyone who installs Windows 8 or 10 should run a program to check for updated hardware drivers. Windows does it occasionally but their updates are more tuned to Windows. You should also scan your drive for corrupted system files - https://support.microsoft.com/en-us/kb/929833 Best regards,

Hi Lamar, If there was a solution to this problem that fix everyone, then it would have surely been posted by now. I think Pete has an excellent suggestion. Worth trying for sure! Here's one link that might help in making this image - http://pcsupport.about.com/od/software-tools/a/create-iso-image-file.htm Best regards,

I would send a bug report to the developers of Concorde X so they can fix this anomaly in future updates. Best regards,

You're not the only one. This is one of the most common errors reported here since FSX was first released. Something gets caught in memory and messes up the install. I would scan your system for corruption - https://support.microsoft.com/en-us/kb/929833 If that does not work, you may have to do a clean install of Windows 10 (ugh!). Best regards,

It takes a super long time for the Navigraph loading. If you believe it really is hanging, then reinstall. Make sure the navigraph data is in the right folder - K:\FSX\CarenadoNavigraph\Navigraph\NavData. There should be a PROC folder under NavData which contains the SID/STARS. Best regards,

Do not need to purchase Smart PC Fixer. That's just another name of a commercial product that does things like in CCleaner. So, did you try the fixes on the Microsoft link - https://support.microsoft.com/en-us/kb/910816 ? They do have a fixer whereby they rename the installshield folder for you and you can try to reinstall. Best regards,

Members are reminded to follow the AVSIM rules regarding using the signature space in your profile - http://www.avsim.com/index.php/AVSIM%20Pages/sig.html Members are encouraged to place information about their computer system in their signature as well as their favorite flight simulator and the addon's installed with your computer. Please remember you cannot exceed five lines of text. Placing your system specs in your signature will help other members assist you in the event you have problems with your flight simulator. It may also help members decide on future computer hardware purchases when they see what others are using to run their simulator. A sample entry of system specs is in my signature. Best regards,

Yes. Do not uncheck the scenery where you won't be flying. It will not load unless you are within approx 100 miles of the scenery. If it is photoscenery (and Orbx/FTX stuff is not), then that scenery should be disabled if you are not flying in that region as all photoscenery enabled will load. If you want verification of my comments, run Process Monitor but configure it to only monitor FSX, FSX-SE, P3D, or X-Plane as shown in the AVSIM CTD Guide, page 4: Startup FSX/P3D/FS9, as appropriate, to the Setup Screen. Open Process Monitor Click on the Filter tab and then Filter…. Click on Architecture and scroll down to Process Name Click on blank box and select FSX/P3D/FS9, as appropriate Click Ok or Apply The scenery configuration editor should not be used to disable/enable Orbx/FTX stuff too. That could cause problems. If you want to disable/enable Orbx/FTX stuff, you need to use FTX Central otherwise your scenery.cfg will get corrupted. Best regards,

My mistake. In your OP, I failed to read where you were indicating post #5 in the link you had posted. When I went to that link you posted, I immediately saw the following: https://mega.nz/#!rgRxWY6J!kvSfOr6tfAIanzkXkqZzshTU7iTooTjxfXt-LXdkAdQ Thus I thought you were having a problem posting a link. I did not read your post completely and that was my error. I have no idea why post #5 appeared like it did. I have little or no knowledge of computer coding. Perhaps one of our members or another moderator who has computer code knowledge will be able to provide you an answer. Best regards,

You have to provide specifics in order for us to help. It does not occur all of the time but in just certain searches. What did you do to get the error? I need to replicate in order to see if there is a problem with our system or with your system. Best regards, Okay, I'm getting the error message every time I'm on the main forum page and then enter flight as the search term (and any word) so there is definitely a problem. I'll pass it to our tech. Thanks to all for bringing it to our attention. Best regards,

I apologize for the confusion. I made my comments because of your following comments, "Editing a post often (well, sometimes, not often, but this is by no means a one off) causes this. As a courtesy to readers I clean it up in a text editor, but it can take a while..". Is your problem solved with my recommendation? Best regards,

That's what I was talking about too. Editing one's own post. You can do that w/i 24 hours (I think) but outside that it is not possible. Best regards,

I get this message all of the time and I'm an Admin! There is obviously a glitch somewhere on our system. In order for me or anyone else to assist you, please provide us exactly what you tried to do. For instance I clicked on the Search button and looked for Store (meaning the AVSIM Store). I immediately got the message because the information and any links to the Store have been removed as we shutdown the store some time ago. I then went into the Advanced search and click on to search just the Store and it came back with there were no hits for what I was searching for. So we need something to replicate your error message so that our techs can take a look at it and try to duplicate. Best regards,

Whenever you post a link (or edit a link), you should click on the "link" button in the menu and copy and paste the link into the link box. That allow integration using BBCode. I did have HTML format authorized where allowed in the settings and removed that option in the forum settings. Wondering how you have the ability to edit a post. Only moderators are allowed that option. Best regards,

It's obviously caused by the Estonia Migration Tool (maybe, perhaps). P3D works great out of the "box" and then you begin to add addons that were not made for P3D and P3D freezes or crashes (whichever comes first). IMHO, you should never ever fly a 10 hour flight with a product that was added using the EMT. Not even a flight longer than 2 hours as you will be frustrated. If there was no event in the Event Viewer, then that means it was caused by your computer system. Your system cannot handle what is being thrown at it. It cannot render textures fast enough. It does not have the virtual address space to accomplish a task. Of course there will be no Event as there was no memory available for your computer to record the event. You simply ran out of VAS and the AVSIM CTD Guide provides some solutions for running out of VAS like turning down all of your settings. You had everything running for 10 hours with no problems whatsoever so you can be almost assured none of your addons, alone, caused your crash. You just ran out of VAS. I run out of VAS after 2-3 hours as I begin my descent about two hours out and I'm flying into a storm and hi res airport scenery. I get an OOM 99.9% of the time. There is no fix for this problem for me other than to turn off ASN and use a default weather setting and turn down my P3D.cfg settings. I have REX too and you cannot use 32 bit textures with much success as it can bring your system to its knees pretty quick. There is currently no computer in the world that can run P3D or FSX for any length of time with high settings and lots of eye-candy like addon scenery and commercial weather engines. I think you should only use ASN for local area flights to place flying in rough weather but never any long flights. Again, this is not P3D's issue, this is a computer system issue and it occurs in FSX and FSX-SE too. Microsoft only provides 4 GB's of virtual address space (VAS) with their operating systems. When VAS runs out or gets very low, your application will freeze or crash. You can monitor the amount of VAS usage by following the instructions in the AVSIM CTD Guide using a freeware utility called FSUIPC. Best regards,

Glad that fixed your problem. A lot of people keep their old fsx.cfg and use it in a new install and the "experts" (I'm not one of them), say that you should never use an old config and I think they are right. Let's hope FSX continues to work great for you and you can enjoy this little hobby. Best regards,

I agree. I also recommend getting the following app - http://blog.ultimateoutsider.com/2015/08/using-gwx-stopper-to-permanently-remove.html Best regards,