Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'p3d v4'.

More search options

  • 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
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • simRussia
  • FSUIPC Client DLL for .NET


  • Community Calendar


There are no results to display.

Found 6 results

  1. Recently bought this update and when I was installing the aircraft, I ran into this issue at the very end: https://imgur.com/a/xYmcr After re-downloading and running the installer as an administrator, I cannot get around this problem. Because of this issue when I load up the sim, several panels are not functioning or not showing up. Thank you in advance for the help! -Emil
  2. Just after installing 5.12 my display window was 'moved' to the upper left corner and the rest is black??
  3. Hi, Since I switched to P3D v4 and FSUIPC5, on Windows 10, I have a crash problem. I have 5 game controlers (2 pokeys, 1 Saitek combat Rudder, 2 Saitek Throttle Quadrant) on the same USB self-powered HUB. On P3D v3 and FSUIPC4 all was good. I can install FSUIPC5 without problem, registration is ok, but when i start P3D v4 i have a CTD with error 0xc0000005 or 0xc0000374 Faulting application Prepar3d.exe Faulting module ntdll.dll If I start again P3D v4 and FSUIPC5, just after the crash, no crash P3D start ok. But when I reboot my PC, same problem: CTD then Ok on second start. Without FSUIPC, P3D v4 start all the time good and game controlers are logged. It's the same with Windows 10 (fresh install and up to date) and P3D V4 (fresh install without addons) and memory changed. I have done some tests and these are my conclusions. If I plug only 1 of the 5 game controlers P3D v4 with FSUIPC5 start all the time. If I plug 2 game controlers on the same HUB crash (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0004). If I plug 2 game controlers on HUB with differents ID (for exemple: Port_#0001.Hub_#0004 and Port_#0003.Hub_#0007) P3D v4 start without CTD. Do you see a solution ? Attached logs are after the install of FSUIPC5 Best regards. FSUIPC5.ini FSUIPC5.JoyScan.csv FSUIPC5.log
  4. MOVED FROM FAQ SUBFORUM!!! HELP!!! I mainly use FSUIPC 5 for autosave. In P3D v4, it works fine when I launch the scenario. In the menu bar I can find FSUIPC as usual. But after taking off some time, maybe 45 min(?), then I press the Alt key and check the menu bar, the FSUIPC tap just disappears!! In every flight!!!!! Appreciate any help!
  5. Hi Pete, You do awesome work for the whole sim community. here is what I have I use software to connect my iPad with P3D. ver 510 and 5101 non registered works great. after registering still seems good until after I use the axis calibration. Then I have problems with my iPad apps communicating with P3D v4. these app are stable on previous sim versions but the new 64 bit obviously takes some work. here is my log file. I Hope this helps. ive read through a couple threads and it seems its hard to get people to tell you what you need to know FSUIPC5.log
  6. Hello, Hope this is the right topic for this message. LM just made official that old plugin dll will not work in P3D V4. I was wondering if it would be feasible to create a "compatibility layer" which would translate 32bits calls in the 64bits API, allowing to "port" all our beloved aircrafts (using dll) which will not be updated. With your indeepth knowledge of SimConnect, you are probably the most capable person to develop such a tool if it makes sense. I am pretty sure it would be a winner. Thanks for your attention. Regards - Gérard Simconnect compatibility V3 vs V4 Postby Beau Hollis » Wed May 31, 2017 10:52 am If your plugin is a standalone exe (which many of the SDK samples are), then it is possible to stay 32-bit and target older SDK versions. If your plugin is a dll, then it must be updated to x64 and compiled against the v4 SDK in order to link and run properly. Beau Hollis Prepar3D Rendering System Lead