Jim Young

  • Content count

  • Joined

  • Last visited

  • Days Won


Jim Young last won the day on March 14

Jim Young had the most liked content!

Community Reputation

724 Excellent

About Jim Young

  • Rank
    Forums Administrator
  • Birthday 10/31/1944

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Profile Information

  • Gender
  • Location
  • Interests
    Golf, Computers, Corvettes

Recent Profile Visitors

5,028 profile views
  1. You can install Acceleration or you can install SP2 but not both. If you do install Acceleration, you must uninstall SP2. If you have Windows 10 you must have a version of the uiautomationcore.dll in your main FSX folder (see page 27, AVSIM CTD Guide). Best regards, Jim
  2. You are not the only user. Besides your user account, there's also a default user, a guest user, a system user, an Administrator, and Authenticated Users. Each one has certain privileges. If you click on the Security tab (next to the compatibility tab) you will see them. Comments like this on AVSIM is not considered appropriate and I will not tolerate such comments here on AVSIM. I hope you understand completely. Members try to help the best they can based on their knowledge. If the responses did not help you, then you take a deep breath and move on and try something else. If you did do a Google search for the G2D error you would see there are no computer experts who can fix this problem for you. There simply is no one solution. Did you run the Migration tool after installing the FTX products? You can force migration via FTX Central. Running it several times does no harm. You should post your question in the AVSIM FTX/Orbx Support Forum. I'll move this to that forum so those users can maybe assist you. I still wonder why you did not request official support for your products at FTX/Orbx. I say this because you did not request official support for your product at Orbx/FTX. If you look at their forums, they indicate whether the issue is active or whether it has been resolved. Again, there is no solution for the G2D error so they will not be able to fix this for you as the G2D.dll belongs to Lockheed Martin. People have errors using FTX/Orbx products all of the time and they are not all G2D errors. There could be a StackHash or NTDLL error too. Good luck!
  3. You had a dotnet 4.0.30319 error. Make sure you run the Microsoft.net Repair Tool (page 26, AVSIM CTD Guide). You should run the dotnet verification tool too to make sure you have the required dotnets installed. Dotnets are used by Microsoft to make sure an application runs in the way intended by the developer. This error might be a one-time error and you'll never see it again if you do nothing. Make sure you are running P3Dv4 with compatibility for all users (not just you). See page 10, AVSIM CTD Guide. You had one Exception code where it appears you terminated P3D abnormally. Did you click on the X in the upper right corner instead of clicking Ctrl+C? Lastly, the error/crash might have been an anomaly that might occur occasionally but you cannot reproduce it. If you get the error again with the same scenario, then there might be something truly wrong. Sometimes a Windows schedule decides to run while you are using P3D and taking up additional resources. I have seen where Windows Update does not like any applications running in the background when it is doing its thing. I guess that's why they try to find a time to run Windows Update that you will be happy with. Hope this helps. Best regards, Jim
  4. Anytime you have a problem with FSDT products, just download the latest Standalone Addon Manager. You can also click on the FSDT Live Update. It goes through each of your products and makes sure each is properly installed and up-to-date. Best regards, Jim
  5. FSX-MS

    See the recently updated AVSIM FSX Configuration Guide for the best settings. Best regards, Jim
  6. You reported the problem in this topic and we appreciate that. Best regards, Jim
  7. You need to install Acceleration or FSX SP2 - https://www.microsoft.com/en-us/download/details.aspx?id=8986. The version reported in your Event Viewer is FSX SP1. Best regards, Jim
  8. Great! We had a technical issue with the Library that was brought to our attention by several members, including you. Our tech has subsequently fixed the problem. Thanks for bringing to our attention. Best regards, Jim
  9. FSX-MS

    You need to download the complete product again. When I clicked on the PMDG Operations Center, it stated there were so many changes I had to go to my account and download the product again. When you run the new installer, it will remove the product you have on your system. Then, after removal, click on the installer again and it will install the new and complete version. I believe PMDG stated they will probably do this a couple more times. Of course, you do not need to update immediately but it did fix some bugs. Best regards, Jim
  10. Sometimes add-on scenery have modules that need to be loaded via the dll.xml. So, if you uninstalled the scenery and the add-on module still exists, then that could be the problem. Black textures indicate something is taking up all of your resources and the aircraft cannot load properly. Looks like you have major problems again. I don't own any of the things you have so will back out of trying to suggest some fixes. You did the right things by placing your fsx.cfg, dll.xml, scenery.cfg, etc., in a temporary folder and restarting FSX. Best regards, Jim
  11. FSX/FSX-SE?

    Welcome. Our throttle controller experts are in the Hardware Controller forum and they might be able to help.
  12. Nice images. Please place the name of the sim used in your Title or a tag in the future. See new pinned topic. Best regards, Jim
  13. Please enter some details of the image such as what sim you were using, the location, any add-on scenery. Thanks! Nice images!
  14. The one in Program Data is the default location (where the scenery.cfg is located) (use to be in the same folder as the P3D.cfg in earlier versions V1 and V2). Some add-on developers still use the old default location (where the P3D.cfg resides) (well their installers do) so you have two locations. Do not try to move the entries in the old default location and put them into the new dll.xml as I tried that once and had a lot of problems. Just leave things as is. Once of these days the installers will discover the new default location. Best regards, Jim
  15. The AVSIM CTD Guide provides some probable fixes for the G2D.dll error: G2D.dll - This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running any simulator and the plain text words in the respective Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items. Possible fixes – Rebuild the sim’s config, as appropriate (moving or renaming the config and then restarting the application). Uninstall/reinstall video card drivers or go back to previous version. Make sure drivers are not ‘beta’. Move the dll.xml to a temporary folder and see if this fixes the problem. If so, there is a module in the dll.xml that is causing the problem. These are solutions found based on searches around the Internet at all flight sim websites. I realize they are not all inclusive and there are obviously more solutions out there. The G2D and the G3D errors are common in flight simulation and very difficult to diagnose. The way I look at the error is the fact not everyone who owns Orbx Global Base/Vector for P3Dv4 has not suffered the consequences of having a G2D error. Therefore, it must be an issue with your particular installation of P3D. I personally suspect you do not have all of the permissions to run P3Dv4. P3Dv4 must have permission of all users as different users on your system have different privileges. To make sure every user on your computer has access to P3D and P3D add-ons, you need to go to Prepar3D.exe in your main P3D Folder, right click it and select Properties. Once open, go to the compatibility tab and select the Compatibility tab and make sure the application is run as an Administrator for ALL users. See page 11, AVSIM CTD Guide for images on exactly how to do this and further information. Hope this helps. Best regards, Jim