Jump to content

Mattie941

Registered Users
  • Posts

    36
  • Joined

Mattie941's Achievements

Expert  Simmer

Expert Simmer (3/7)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

10

Reputation

  1. I thought it could have been the cause of my CTD. However I was wrong and the CTD is caused by something else...
  2. I have tried installing FSX in C:\FSX and to the D:\ drive but both still cause the CTD
  3. Thanks Jorgen. As you can see from my previous message, I have reinstalled Windows and FSX. The CTD occurs on the default install Thanks for the feedback. How do I do this?
  4. I have reinstalled Windows and then reinstalled FSX to a separate folder outside of Program Files (x86). The CTD still happens. My IT skills are not proficient enough to diagnose the exception code.
  5. Mine can be seen at the top of the thread. From Process Monitor, I can see that the last file FSX tries to read before the CTD is the kernel32.dll
  6. I recently tried running FSX again after the recent windows updates but I still get the API.dll CTD from a clean install of the game. Does anyone know of a fix?
  7. I thought that the version mismatch was the issue, but it was not. It has recently been confirmed that the API.dll crashes (IF no corrupt dll.xml file) are being caused by a Windows update from a few months ago. It’s a shame. I recommend everyone that is experiencing the issue to submit a support request with Microsoft: https://support.microsoft.com/en-us/home/contact This will help increase exposure to the issue and will hopefully expedite a hotfix.
  8. A complete reinstall of Windows has not fixed the issue. Therefore I'm out of ideas...
  9. Thanks. As I said in my first post. I am running a clean install of FSX, therefore no scenery or aircraft addons. The issue occurs when I try and connect an external program to the sim (vPilot, FSrealWX lite, etc.), which is why it has made me think it is a SimConnect issue. Regarding the install location. As I said in my first post, I have run the clean install in "C:\FSX" (SSD with my OS installed) and "D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X" (additional HDD not running the OS, therefore it is not a protected folder). The install location of FSX does not make a difference to the CTD. I tried installing from Just Flight and from the Acceleration SDK. I run through the steps to install Acceleration SDK but when i run the SimConnect.msi, it still installs SimConnect 10.0.6129.0. It's strange because when I run the SimConnect.msi file, the "run as administrator" pop up asks if I would like to install SimConnect 10.0.61637.0 but then when I click "yes", the installer window appears it says SimConnect 10.0.6129.0. When I check for the version installed it is SimConnect 10.0.6129.0 and FSUIPC is still reporting a mismatch. The file properties of the Microsoft.FlightSimulator.SimConnect.dll file in "...\Microsoft Flight Simulator X SDK\SDK\Core Utilities Kit\SimConnect SDK\lib\managed"says that it is version "10.0.616.37.0 (FSX-Xpack.20070926-1421)" and yet it does not install this version. I'm not sure what I'm doing wrong? Found here: https://support.justflight.com/support/solutions/articles/17000100065-simconnect-files-for-fsx-p3d
  10. Hello, I keep running into an API.dll crash. I have completely reinstalled FSX. Therefore the FSX.cfg, DLL.xml and EXE.xml are all stock files. I have not been able to recreate the crash from the fresh reinstall at the moment.I have UAC turned off. I run on very minimal settings and I have monitored VAS and it is peaking at 2GB and yet I am still running into API.dll crashes according to the event viewer log. The sim also sometimes CTD with an API.dll error on start-up, before I get to the loading screens. The same issues persist with the sim installed on the SSD in C:\FSX and in it's current location on the HDD. Example crash log: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58 Exception code: 0xc0000005 Fault offset: 0x0003afa2 Faulting process ID: 0x2fa4 Faulting application start time: 0x01d9aeaeab4a9ebe Faulting application path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL Report ID: 310022d2-51c7-41ac-acaa-e6bdbc0050e5 Faulting package full name: Faulting package-relative application ID: I have a 2017 Medion P6661 gaming laptop: GeForce GTX 950M Graphics card 15.6 Inch Screen Intel Core i5 6200U Processor 8 GB RAM 1TB Hard Drive + 128GB SSD Windows 10 I can only recreate the crash once I have installed FSUIPC and some addons to run using it: FSrealWX lite, FSFO v3, vasFMC 2.1, vPilot and Skytrack (my VA ACARS). The API.dll CTD does not seem to be related to any single one addon or combination of addons (I have tested with individual addons and combinations of addons). From Process Monitor, the last file FSX tries to read before "Thread Exit" is the kernel32.dll file. The last file before "Process Exit" is the quartz.ttf file in the "Fonts" folder. However, in the Result column in Process Monitor, it reads "SUCCESS" for both. I'm not too sure what this means though... John Dawson noticed that there is a mismatch between my FSX version and the Simconnect version: 31844 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) I tried uninstalling SimConnect but the latest version on the FSX Acceleration SDK is 10.0.61259.0. When I reinstall and start the sim, I still have the same mismatch. Therefore: How do I remove 10.0.61637.0 so that the FSX version matches? Or where do I find/download 10.0.61637.0 to update my SimConnect version
  11. I thought that the texture fallback in FSX only worked within the main FSX root folder because it doesn't accept absolute paths. This is different in P3D. This thread summarises it nicely: https://www.fsdeveloper.com/forum/threads/texture-cfg-fallback-works-in-p3dv4-but-not-in-fsx.446284/
  12. Thanks for the replies. Yes I do not use GEX. The solution is on Avsim for those that are looking for the same fix: https://www.avsim.com/forums/topic/615668-fsx-black-ground-vehicles/?do=findComment&comment=4731856
  13. Hi - yes I uninstalled GSX via the control panel. I even reinstalled it to uninstall it again to see if that would fix the problem but no fix so far. I decompiled the vehciles_airport.bgl to see what models were being pulled and I couldn't see any without a texture.
  14. Hi, I recently installed the trial version of GSX and uninstalled once I had checked it out. However, some airport ground vehicle models still exist without textures (see image). I've tried reverting to a backup of my Simobjects/Groundvehicles folder and restored old backups of the veh_air_*** files in the Scenery/Global/Texture folder, but the black models still remain. Where can I find and delete these ground vehicle models to restore the FSX default vehicles? Cheers, Matt
  15. Hi guys, My PC recently had an issue and was repaired in a PC shop. They've fixed it so all seems well. However, I now have an issue where FSX saves my save files, setting files, etc. The files used to be stored in "D:\Users\[uSER]\Documents\Flight Simulator X Files" but now they are being saved in "D:\Users\[uSER]\OneDrive\Documents\Flight Simulator X Files" Being saved in OneDrive is causing some issues with locked files, etc. How has this happened? How do I changed it back to how it was before? I think this is a Windows issues because the same thing has happened for save files for other games and vpilot VMR files. Thanks in advance.
×
×
  • Create New...