Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'ctd'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • FS Commander Support Forum
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • simRussia


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 9 results

  1. Hello, I unfortunately suffered an FSX CTD at 1,500 feet on my approach and I'd like to figure out what the issue was and if it was related to FSUIPC at all. Everything was going normally until the simulator locked up around 1,500 feet, froze for a minute or two, and then closed. This was on VATSIM in a busy airspace, though my sim will usually just stutter in such instances without crashing. The Windows crash details indicate FSRecorder as the faulting module, though it seems to always throw up the same .dll as the faulting module after a CTD. I was not using FSRecorder at the
  2. Hey, I recently reinstalled FSUIPC since I had some troubles with my sim and thought it could be related to FSUIPC. Now FSUIPC isn't working at all. So basically what's happening is that I click "fly now" in FSX-SE so it loads in, after it successfully loaded in, it crashes to desktop after a couple of seconds (about 5 secs). PS: Thanks for any help in advance (FSUIPC log is attached) FSUIPC4.log
  3. Hi, I've got a crash to desktop. Below you will find the event viewer report . I'm running Prepar3D v4.1.7 and FSUIPC5 5.122a. Any advice to avoid more of this? Thanks, Jose --------------------------- Nombre de la aplicación con errores: Prepar3D.exe, versión:, marca de tiempo: 0x59d67e95 Nombre del módulo con errores: FSUIPC5.dll, versión:, marca de tiempo: 0x5a19470e Código de excepción: 0xc0000005 Desplazamiento de errores: 0x0000000000046423 Identificador del proceso con errores: 0x250c Hora de inicio de la aplicación con
  4. Hello, I have bought a Saitek X52 Pro (replacing a Thrustmaster 4 HOTAS) and thinking that it will work flawlessly, I plugged it into USB slot, then installed the related software and the FSX-P3D and Xp11 plugins required from the manufacturer's website, which later I found out was a mistake. As the title suggests now P3Dv4.1 crashes to desktop while loading the main scenario screen. If I disconnect the controller, the application starts fine. I followed some steps that I found here in this forums, like uninstalling the software, removing the device and the drivers from Device Manager but
  5. I have been able to consistently reproduce a g3d.dll error, preceeded by a .NET error CTD, on a flight between KJFK and PHNL with Mytraffic 6; it happens at around the same location 22 32N 156 48W which is about 110 nm from PHNL. I have traffic set to 10% and no GA, Mytrafficmil.bgl has been renamed, if I set traffic to 0% then I can complete the flight. VAS is fine, aircraft is BBS A330, system is i4790 with 16 GB RAM Windows 7 x64, no antivirus or firewall Where do I start looking to solve this, could it be a corrupt Mytraffic flightplan, aircraft model, or something else?
  6. Hi there, well after fresh install of p3d.3.4 and all addons, there is time for testing. 3 tests without problem (average 7h duration, on PMDG738), then tongiht, 4th trial and baam - CTD. Checked the error log and that's what was there: Faulting application name: Prepar3D.exe, version:, time stamp: 0x57d9b14e Faulting module name: SimConnectP3D3.dll_unloaded, version:, time stamp: 0x571e4e28 Exception code: 0xc0000005 Fault offset: 0x13d41eb0 Faulting process id: 0x21e4 Faulting application start time: 0x01d22fd9dc19f48f Fault
  7. I purchased the Eaglesoft Cessna Citation X recently and was advised to purchase a registered version of FSUIPC along to have a fully functional fadec. I followed the advise and purchased a registered FSUIPC 4 and set up the joystick and throttle. Both are working fine with a throttle idle of 24% N1. I applied the axeswrongrange = yes, as advised in some online fora. My problem is that with the ES Cessna aircraft, FSX crashes to desktop randomly. Recently the crashes have become too frequent and happen right on the ground while setting up FMS. I have read some posts about this issue and u
  8. Hello. Sorry my poor English. I'm setting my joystick axis on FSUIPC Axis Assignment. (My joystick is Thrustmaster HOTAS Warthog and Saitek Pro Rudder Pedals) Setting Axis is here: http://imgur.com/TCPhs0N http://imgur.com/Gq3G4VD http://imgur.com/a8UWn5Q http://imgur.com/ECbj6lD http://imgur.com/Sr9s0NK http://imgur.com/BH6nQB9 http://imgur.com/ZSDcRSx http://imgur.com/681P5nA After setting few minutes, Prepar3D v3 is crashed. Eventlog code is here: Faulting application name: Prepar3D.exe, version:, time stamp: 0x560b4abe Faulting module name: DINPUT8.dll, version: 6.1.7600.
  9. Hi, I loaded FSUIPC latest version 4.938d for testing the FSFlyingSchool 2015 Demo. My Sim was working very well with FTX Global, Vector, OpenLC Europe and FS Global Ultimate. When I load a flight at daytime all is fine. But: When I load a flight at nighttime P3D says: FATAL ERROR and crashes to desktop. Removing the modules folder or just removing the FSUIPC_Loader.dll helps to prevent CTD --> it's an issue of FSUIPC. Windows event log doesn't help as there is no helpful information listed... Anyone who can please help me? A lot of Add Ons will use FSUIPC and I need also to
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.