Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'p3dv4.4'.

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


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 1 result

  1. Hello Pete, This is the first time I can not properly operate your module in 10 years of use. I can not find the problem. 1. I recently uninstalled P3DV3 and fully installed P3DV4 on another hard drive. Everything works well. I can use widefs with planG on my remote PC for example. But when FSUIPC is present in the directory "modules", I can not open the doors of my A320 anymore (same for all planes), even with the keyboard and controls at the MCDU. Only the main door works. I also lost the operation of the auto-start engine right and left on the 2 buttons of my throttle (saitek yoke system). Same for gear toggle : Yoke button works fine only with a direct assignment into P3D. In fact, when installed, FSUIPC perfectly recognizes the button but nothing happens, while it works on the keyboard or P3D controls assignment. And worse, about the cargo door problem, I ask myself about many controls totally locked with their offsets invisibly forced. FSUIPC and wideFS are Registered (with an old mail adress, but it doesn't mind I hope) and installed as administrator with Windows defender disabled (not sure at each test). Joystick assignment is Inside P3D... I didn't tried with FSUIPC: Perhaps I would. Of course all the drivers are upgraded. My fps average is up than 80. 2. Here is all the files you probably need for a diagnostic. But everything seems to be correct. 3. I've noticed for exemple (Gear) : offset 3360 has no effect when tried with the LINDA console or FSUIPC button affected to FScontrol: Watching new offset: 3360:UB:DEC = 0 btn 06A30D670-1=00000000000001000010>>>00000000000001000001 rl: 06A30D670-1=00000000000001000010>>>00000000000001000001 bit 19 2 pr: 06A30D670-1=00000000000001000010>>>00000000000001000001 bit 20 [EVNT] OnPress Button detected PR:06A30D670:20 ++++++++ [hHID] Button OnPress 06A30D670_20/G: 0 [hHID] Button Repeat Cancel 06A30D670_20/nil ***** [hHID] Button Repeat Cancel 06A30D670_20/nil ***** [hHID] Button Repeat Cancel 06A30D670_20/nil ***** [hHID] Action unshifted 06A30D670/20 press call: nil [hHID] Button Execute 06A30D670/Gears_down btn 06A30D670-1=00000000000001000001>>>00000000000001000010 pr: 06A30D670-1=00000000000001000001>>>00000000000001000010 bit 19 rl: 06A30D670-1=00000000000001000001>>>00000000000001000010 bit 20 2 [EVNT] OnPress Button detected PR:06A30D670:19 ++++++++ [hHID] Button OnPress 06A30D670_19/G: 0 [hHID] Button Repeat Cancel 06A30D670_19/nil ***** [hHID] Button Repeat Cancel 06A30D670_19/nil ***** [hHID] Button Repeat Cancel 06A30D670_19/nil ***** [hHID] Action unshifted 06A30D670/19 press call: nil [hHID] Button Execute 06A30D670/Gears_up And Inside FSUIPC log I can read : 1482360 Button changed: bRef=0, Joy=2, Btn=19, Pressed 1482360 [Buttons] 1=P2,19,C65570,0 1482360 FS Control Sent: Ctrl=65570, Param=0 GEAR_TOGGLE 1482703 Button changed: bRef=0, Joy=2, Btn=19, Released Best regards. Christophe LEONARD (LFRC) FSUIPC5.ini FSUIPC5 Install.log
  • 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.