Jump to content
The simFlight Network Forums

Recommended Posts

I have been reading this thread with interest. My problem is that no simple buttons and switches from Go-Flight modules are recognized in registered FSUIPC in P3D v4.1. Everything worked fine in P3D v3.4. Buttons are correctly recognized by FSUIPC from Saitek yoke and pedals and quadrant.

I purchased and installed FSUIPC v5.121b. Everything else seems to be working.

I installed the latest GFConfig as referenced above. Curiously there is NO v4 tab, just one P3D tab. I changed the directory to the new v4 install. 

The GoFlight bridge DLL is in the P3D v4  dll.xml file.

But, there was no GFdev64.dll anywhere. I downloaded that  file from the link above, and put it in the P3D v4 modules directory, along with the FSUIPC files. Still, makes no difference. Buttons are not recognized in the FSUIPC buttons assignments page, for GoFlight Modules.

What am I doing wrong?

* Orest

 

Share this post


Link to post
Share on other sites
On 11/10/2017 at 9:41 PM, oskrypuch said:

Is there anyone that has been successful in making definitions in FSUIPC, of GoFlight buttons, running in P3D v4?

Yes, I have 2 x GF-RP48s, 2 x GF-P8s and 2 x GF-T8s, with all switches and knobs working perfectly through FSUIPC using GFDev64.DLL. I have no other Goflight software installed, however. 

Does your FSUIPC5.LOG file show that GFDev64 has been located and loaded? My log shows:

   344747 Using "E:\Prepar3D v4\Modules\GFDEV64.DLL", version 2.2.8.0
   344747 GoFlight GFP8 detected: 2 devices
   344747 GoFlight GFT8 detected: 2 devices
   344747 GoFlight GFRP48 detected: 2 devices


The number on the left is just how many milliseconds since FSUIPC loaded.

Pete

 

Share this post


Link to post
Share on other sites

That is a negative -- to "Using...GFDEV64.DLL" in the LOG file.

Had a look, and indeed that DLL is not in the modules directory. I could have sworn I had put it there. Found it eventually in the GoFlight directory, so it got dumped into the wrong spot.

All working now. Thanks for helping out.

* Orest

 

Share this post


Link to post
Share on other sites

Hello Pete

Fsuipc 5 installed and registered.

GfDev64.dll copied modules folder.

But Gopflight pro mcp and efis not operate.

FSUIPC.log

 ********* FSUIPC5, Version 5.124 (27th February 2018) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FF86A160000
Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0)
Prepar3D.exe version = 4.2.21.24048
Reading options from "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="Ali BIDIK"
User Addr="sevgiali@msn.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 05/03/2018 09:06:34
        0 FLT path = "C:\Users\DigitAli\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.2.21.24048
        0             api.dll: 4.2.21.24048
        0        controls.dll: 4.2.21.24048
        0      fs-traffic.dll: 4.2.21.24048
        0             G3D.dll: 4.2.21.24048
        0        language.dll: 4.2.21.24048
        0            sim1.dll: 4.2.21.24048
        0        visualfx.dll: 4.2.21.24048
        0         weather.dll: 4.2.21.24048
        0          window.dll: 4.2.21.24048
        0 ----------------------------------
        0 Using PDK events
        0 Using DialogMode
        0 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
       94 ---------------------- Joystick Device Scan -----------------------
       94 -------------------------------------------------------------------
      109 LogOptions=00000000 00000001
      109 -------------------------------------------------------------------
      109 SimConnect_Open succeeded: waiting to check version okay
      109 Opened separate AI Traffic client okay
    90391 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.2.21.24048 (SimConnect: 4.2.0.0)
    90406 Initialising SimConnect data requests now
    90406 FSUIPC Menu entry added
    90406 ... Using Prepar3D with Academic License
    90422 C:\Users\DigitAli\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    90422 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   751203 Weather Mode now = Custom
   751891 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
   751891 PMDG 737 offsets enabled
   751891 C:\Users\DigitAli\Documents\Prepar3D v4 Files\LTBA-LTAR.fxml
   784609 Loading Complete ...
   785438 User Aircraft ID 2 supplied, now being used
   785438 Aircraft loaded: running normally now ...
   785750 System time = 05/03/2018 09:19:42, Simulator time = 08:45:45 (06:45Z)
   785750 Aircraft="PMDG Boeing 737-8F2 Turkish Airlines Winglets-JVZ"
   787656 -------------------- Starting everything now ----------------------
   787656 Using "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\GFDEV64.DLL", version 2.2.8.0
   787656 GoFlight GFMCPPRO detected: 1 device
   787656 GoFlight GFEFIS detected: 1 device
   788984 Advanced Weather Interface Enabled
   828422 Sim stopped: average frame rate for last 43 secs = 52.3 fps
   828422    Max AI traffic was 0 aircraft
   829844 === Closing session: waiting for DLLStop to be called ...
   834219 === DLLStop called ...
   834219 === Closing external processes we started ...
   835219 === About to kill any Lua plug-ins still running ...
   835375 === Closing global Lua thread
   836391 === About to kill my timers ...
   836578 === Restoring window procs ...
   836578 === Unloading libraries ...
   836578 === stopping other threads ...
   836578 === ... Button scanning ...
   836688 === ... Axis scanning ...
   836781 === Releasing joystick devices ...
   836781 === Freeing macro memory
   836781 === Removing any offset overrides
   836781 === Clearing any displays left
   836781 === NOTE: not calling SimConnect_Close ...
   836781 === AI slots deleted!
   836781 === Freeing button memory ...
   836781 === Closing my Windows ...
   836781 === Freeing FS libraries ...
   837797 === Closing devices ...
   837797 === Closing the Log ... Bye Bye! ...
   837797 System time = 05/03/2018 09:20:34, Simulator time = 08:46:27 (06:46Z)
   837797 *** FSUIPC log file being closed
Minimum frame rate was 10.1 fps, Maximum was 58.4 fps
Average frame rate for running time of 43 secs = 52.3 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 24 Allocs, 24 Freed
********* FSUIPC Log file closed ***********
Please help me.

Share this post


Link to post
Share on other sites
7 hours ago, combo2009 said:

Fsuipc 5 installed and registered.

GfDev64.dll copied modules folder.

But Gopflight pro mcp and efis not operate.

You added your post to a very old thread, you are lucky I saw it! Please, next time, start a new thread of your own rather than append to such an old one.

============================================================

What the the symptoms of this "not operate"? As you see from the log:

   787656 Using "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\GFDEV64.DLL", version 2.2.8.0
   787656 GoFlight GFMCPPRO detected: 1 device
   787656 GoFlight GFEFIS detected: 1 device


they are both detected okay, and so are operating via GFDev64, no problem.

The displays on the MCP are not driven this way. You either need to use GoFlight's own software, or program a Lua plug-in to handle the disaplys. FSUIPC natively only handles the buttons, switches and dial inputs, which you'd need to assign as needed.

Pete

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×

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.