Jim Young

Ah! Okay! It should have installed properly. Still, if you rename that dll, you will not have any navdata unless you buy the GTN750.

The following topic will explain that the Phenom300 will not install into P3Dv3 so I explained how to do it in the following topic - http://www.avsim.com/topic/475719-prepar3d-version-3/. It also shows the required entry for the dll.xml. Since it will install into P3Dv2, some have created a folder called P3Dv2 and then instructed the installer there (same goes with the Navigraph Extension). Then they move the files over to the folders in V3. It will create a dll.xml in a folder in your Roaming/Lockheed Martin/Prepar3Dv2 folder. You just need to copy and paste the entry into the one in the V3 folder. It will be updated when v2.0 of the Phenom 300 is released. Meanwhile, everyone needs to do some manual installation. EDIT: Forgot to add, you can also rename the P3Dv3 folder to P3Dv2. Then it should install properly into that folder. After installation, you can rename it back to P3Dv3. Best regards,

Simconnect does not appear to be installed correctly. You need three versions installed as developers use different versions with their programs - http://www.avsim.com/topic/423835-in-search-of-simconnect-v61612590/

Then your navdata should have been installed properly. Your dll.xml should have an entry in it to load the carenavigraph.dll at startup. If you don't want any navdata or you want to install the $50 GTN 750 instead, then you should remove the entry from the dll.xml (if it is there). Best regards,

But, but, you have no navdata if you turn that .dll off! The aircraft is completely useless w/o navdata. I found absolutely no change to my frame rates or the amount of VAS with this change. This indicates to me you do not have Navigraph installed properly as the system cannot find the files it needs. Do you have the carenavigraph.db in the CarenadoNavigraph folder?

We have an excellent review of the Phenom 300 done by our reviewer, Ray Marshall and he did not indicate any issues like you are reporting. Tweaks, like those that came from Venetubo are really not needed today and your system is a little bit more powerful than mine. There are many YouTube tutorials on how to fly this aircraft and set it up too and they indicate no problems. In fact, mostly the opposite. High settings are not needed for awesome graphics for this aircraft. Check out the review and some of the great tutorials or flights with this aircraft. Is it perfect? No. Like the Phenom 100, they will soon be upgrading this aircraft to 2.0 too but it still won't be "perfect" or really frame rate friendly. It will all depend on what else you loaded and what you are flying over plus your fsx/p3d.cfg settings. Are you using it in P3D or FSX? Best regards,

Not a problem Mike. I've done the same thing over the years. It's just that we have received a lot of complaints from many sites and they have asked us to quit copying and pasting the info. So Tom wrote the current policy. Best regards,

The link is what we want!! Thanks Bill. Best regards,

That's pretty much impossible and something major is wrong with your computer or your installation. The link you provided was removed as that guide is not allowed here (member was banned) and his settings are pretty much out of sight. Even he admitted some of his settings are way too high.

Your laptop is almost at the bottom of the pile of all of the current "gaming" laptops - http://www.cpubenchmark.net/cpu.php?cpu=Intel+Core+i5-4210H+%40+2.90GHz. FSX is a really old game with really old programming. You might get 15-20 fps. This is why you should limit the fps to 20. Just because a computer says "gaming" on the package does not mean it will work well with FSX. FSX was never developed to take full advantage of the modern computer systems like current games like Team Fortress and Minecraft. Microsoft got rid of the team that was going to update it to take advantage of modern systems (yours is close to modern). We will never see updates. Dovetail did some modifications to try to help performance but they can only do so much without violating their license agreement with Microsoft. Same goes with Lockheed Martin's Prepar3D (which is FSX too). As new technology is found to increase the performance of a product, as update is released. VATSIM takes up a lot of resources too. You may have to scratch your enjoyment of VATSIM until you can upgrade to a more modern and powerful system. If you threw in any tweaks to your FSX-SE.cfg, that could be taking up resources too. If the tweak was not employed properly, it will do more damage to your enjoyment. One tweak setting does not fit all. Best regards,

That's correct. The latest and greatest navdata. I personally would not recommend anyone updating to the latest and just keep the default. The default is really not that old. How many years did we run FSX/FS9 w/o any navdata updates. Then Stefan showed up and made an outstanding product. I looked at the Citation Mustang for P3D forums and do not see any solutions yet. I just wanted to jump on board with your topic to say you're not the only one with this issue! Best regards,

I had the same crash/freeze after updating to the 1607 cycle from Navigraph. I have the latest version for P3D (just got it this AM after reading your sad story) and I had to check it out for myself. I moved the navdata out of the Navigraph folder and it worked with the PFD lighting up, etc., but then an instant CTD when entering a flightplan. Reinstalled the Mustang. Moved the data back to the Navigraph folder and it worked. So, think you have to startup P3D and load the Mustang a few times before it works. I am now able to enter a flightplan and it seems to be working great now.

Mine shows that too. P3D IS FSX only modified. Navdata is navdata. Good for you. Navigraph really has a hard time figuring out how to install navdata. Sometimes it installs it into Prepar3d_v3/NavData and then NavData/Proc. I just move the info all up to the Navigraph folder where it is read from. If you have your navdata and files installed like how I showed in the link I provided, then you should have no problems whatsoever. The next time you start up the Phenom 300 it will load the new navdata. I have no idea what you did here. There is only one place where Carenado is installed and that inside the P3D Folder. I do not have the file folder (my user name)/AppData/Roaming/Lockheed Martin/Program Files X86/ProgramData. I do have a folder (my user name)/AppData/Roaming/ProgramData . This folder has nothing to do with P3D or NavData and mine has one Windows file in it. You should have a folder (your user name)/AppData/Roaming/Lockheed Martin/Prepar3D v3 and that folder contains your p3d.cfg, etc. It has absolutely no navdata. This folder is normally hidden by your computer system so that one will not make changes to the files in it as it will mess up your computer system (and P3D) if you do the wrong things.

I apologize. I meant the Graphics tab in your settings screen. This is normal. FSX is not compatible with Windows Aero so it turns Windows Aero off and goes to Windows 7 Basic so that FSX will work properly. You should never ever change the compatibility settings in FSX (by right clicking FSX.exe and selecting the 'Compatibility' tab. There should be no tick marks in this section other than the last section where you want FSX to run in Administrative Mode. That should already be ticked (see the AVSIM FSX Configuration Guide for more information - link in my signature). Make sure you do not somehow have Aero running. Not good.... Best regards,

Sounds like the beta testing done at PMDG. It is extremely long too but they get it very close to being right on target when they do release the product or update (until us "beta testers" get hold of it with our thousands of different configurations/setups, etc.). :smile: Best regards,

Believe Charliearon has the fix - http://www.avsim.com/topic/402640-fsx-aircraft-initialization-failure-any-suggestions/

This would violate the AVSIM copyright rules Bill (see rules under Forums tab above). Steve is just going to have to figure out how to sign back up on FTX/Orbx. I saw on the FTX Forums that his username was the same as here but they changed it to spiritflyer_old which indicates to me they are working to get him a new account. Thanks Bill for the OP. A great heads-up for all of us! Best regards,

It almost sounds like you have your display set at 16 bit instead of 32 bit. Check that in the resolution section of the Nvidia display drivers. Make sure the refresh rate is at 60Hz, the color depth is 32 bit, the output depth is 8 bpc, the output format is RGB and the output dynamic range is Full. In your FSX settings, make sure the resolution on the General tab is correct and not set at 16 bit. Best regards,

I would not make a special effort to uninstall/reinstall FSX. As long as you keep UAC disabled, you should have no problems. I had it in the default folder for years w/o problems. But there is more and more security in the Windows Operating Systems due to many complaints around the world that malware somehow got installed. If you ever have to reinstall FSX, here's a guide I suggest reading - http://support.precisionmanuals.com/kb/a87/how-to-uninstall-and-reinstall-fsx.aspx Best regards,

There are the required files and gauges too. See my explanation at the following link - http://www.avsim.com/topic/490798-phenom-300-problem-p3d-32/?p=3444849 Best regards,

First of all, FSX is only capable to use DX10 Preview. It cannot use the DX11 technology (that's in P3D). There are some bugs in DX10 Preview and many have bought and installed Steve's DX10 Fixer. I am not sure what you mean by a 3D appearance. FSX is not capable of rendering in 3D. You need a special monitor and 3D glasses to view FSX in 3D. It does look great if you have the components for 3D but there are anomalies with that technology too. I have tried it and liked it but viewing FSX through 3D glasses can wear you out. If you are having crashes early in flight, you need to check out the AVSIM CTD Guide (see link in my signature) and look at the many investigative techniques you can try to determine the cause of your crashes. For us to help you, you would need to submit an AppCrashView report which is detailed in the AVSIM CTD Guide and/or an event from the Event Viewer. Best regards,

Welcome Fredric. I would start off with the FSX/FSX-SE forums. If you have any problems with FSX, that's where you want to post your questions. I think we have the best user-to-user support for FSX. I hope you enjoy our site. Best regards,

Glad you were able to get it fixed!

You can also delete your scenery.cfg and a new one will be rebuilt. Best regards,

VPilot has been a source of crashes if not installed properly. It appears you might have a problem with permissions. If you, the user, does not have permissions to use an application (say vpilot), it will crash when you try. The AVSIM CTD Guide provides some information on how to investigate your problems. The error message you provided belongs to your computer system and not FSX. You need to make sure you are looking in the proper locations in the Event Viewer as shown in the AVSIM CTD Guide. (see link in my signature or on the sidebar). You should also download AppCrashView as suggested in the AVSIM CTD Guide and it may show other crashes or sources of your crashes. When you installed FSX-SE, you did so with UserAccessControls (UAC) turned off and your anti-virus and/or malware programs disabled. You should have installed it in the non-default folder such as C:\FSX-SE. The default location is in C:\Program Files (x86). That folder has too much security and causes a lot of problems. Lastly, I moved your topic to the Crash to Desktop Forum. Hope this helps. Best regards,