Jump to content
The simFlight Network Forums

FSUIPC 5 disables Ezdok v2 ?


Recommended Posts

Hello Mr. Dowson,

Yesterday I came back from my 2 week vacation and wanted to play some P3D v4. Everything was working fine before ( I use windows 10 with bitdefender but never had problems with it ). Before playing I found out about FSFX 777 Immersion so i bought it. Upon download it required from me to download FSUIPC, so i downloaded the latest fsuipc 5 5.103 ( unregistered version). After that i start p3d v4 and noticed that EZDOK v2.5  wasnt working anymore. I open ezdok  which starts along with p3d and it says connecting with simconnect. After 3-5min it says application getting initialized or something like that. I am not sure if its fsuipc fault or if its just a coincidence that it happend the same time i downlaoded fsuipc. As FSUIPC is shown in the drop down menu in p3d i am not sure if it is a simconnect issue. I will try to get in contact with EZDOK aswell. U will find the FSUIPC LOG ,.... below.

Thanks,

Ahmed Al-Dabbass

 

FSUIPC5.ini:

[General]
UpdatedByVersion=5103
History=1WYXXMJQMR4ILWDKJUN8D
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=No
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.0.28.21686
SimConnectUsed=4.0.0.0
ProvideAIdata=Yes
ProvideAIairports=Yes
Console=No

[WideServer]
WideFSenabled=Yes


 

FSUIPC5 Install.log:

Installer for FSUIPC5.DLL version 5.103


Looking in registry for Prepar3D v4 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\
===========================================================

INSTALLATION FOR Prepar3D v4:
SetupPath="D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\"
Checking version of the Prepar3D v4 EXE:
... Version 4.0.28.21686  (Need at least 4.0.20.21316)
Checking if there's already a version of FSUIPC5 installed in:
       D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL
... No previous valid version found.
Prepar3D v4 Modules folder already exists.
Okay -- installed FSUIPC5 into "D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Ahmed\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Ahmed\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Ahmed\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC5 section.
... FSUIPC5 section already exists but will be replaced.
... FSUIPC5 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\defaultuser0\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder created okay!
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC5 User Guide.pdf" okay
   Installed "FSUIPC5 for Advanced Users.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC5 History.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
===========================================================

All installer tasks completed.
Registration dialog 'not now' selected
*************** End of Install Log ***************

 

 

FSUIPC5.log:


********* FSUIPC5, Version 5.103 (26th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFE18D60000
Windows 10 Pro 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 4.0.28.21686
Checking the Registrations now ...
User Name=""
User Addr=""
FSUIPC5 not user registered
WIDEFS7 not user registered, or expired
        0 System time = 31/07/2017 12:16:20
        0 FLT path = "C:\Users\Ahmed\OneDrive\Dokumente\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.28.21686
        0             api.dll: 4.0.28.21686
        0        controls.dll: 4.0.28.21686
        0      fs-traffic.dll: 4.0.28.21686
        0             G3D.dll: 4.0.28.21686
        0        language.dll: 4.0.28.21686
        0            sim1.dll: 4.0.28.21686
        0        visualfx.dll: 4.0.28.21686
        0         weather.dll: 4.0.28.21686
        0          window.dll: 4.0.28.21686
        0 ----------------------------------
        0 FS path = "D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\"
       78 LogOptions=00000000 00000001
       78 SimConnect_Open succeeded: waiting to check version okay
       78 Opened separate AI Traffic client okay
     2281 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.28.21686 (SimConnect: 4.0.0.0)
     2281 Initialising SimConnect data requests now
     2281 FSUIPC Menu entry added
     2297 ... Using Prepar3D with Academic License
     2297 C:\Users\Ahmed\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     2297 D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    28610 D:\Program Files (x86)\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.air
    40203 User Aircraft ID 2 supplied, now being used
    40219 Aircraft loaded: running normally now ...
    40985 System time = 31/07/2017 12:17:01, Simulator time = 14:00:01 (19:00Z)
    47985 Starting everything now ...
    48016 ASN active function link set
    48016 Ready for ASN WX radar
    49156 Advanced Weather Interface Enabled
   573625 Sim stopped: average frame rate for last 533 secs = 144.7 fps
   573625    Max AI traffic was 0 aircraft
   600485 === Closing session: waiting for DLLStop to be called ...
   608453 === DLLStop called ...
   608453 === Closing external processes we started ...
   609453 === About to kill any Lua plug-ins still running ...
   610594 === About to kill my timers ...
   610594 === Restoring window procs ...
   610594 === Unloading libraries ...
   610594 === stopping other threads ...
   610594 === ... Button scanning ...
   610703 === ... Axis scanning ...
   610797 === Releasing joystick devices ...
   610797 === Freeing macro memory
   610797 === Removing any offset overrides
   610797 === Clearing any displays left
   610797 === Calling SimConnect_Close ...
   612906 === SimConnect_Close done!
   612906 === AI slots deleted!
   612906 === Freeing button memory ...
   612906 === Closing my Windows ...
   612906 === Freeing FS libraries ...
   613906 === Closing devices ...
   613906 === Closing the Log ... Bye Bye! ...
   613906 System time = 31/07/2017 12:26:34, Simulator time = 14:09:07 (19:09Z)
   613906 *** FSUIPC log file being closed
Minimum frame rate was 24.4 fps, Maximum was 154.1 fps
Average frame rate for running time of 546 secs = 144.4 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 272 Allocs, 272 Freed
********* FSUIPC Log file closed ***********

Link to comment
Share on other sites

I am sure that EZDOK does not use FSUIPC, and FSUIPC most certainly has nothing to do with EZDOK. You need the EZDOK support forum.

Furthermore, as your FSUIPC is not even registered it is really not doing anything except using SimConnect to populate its offsets. These are all data requests made during initialisation, and then left to SimConnect yo supply updated data as it occurs.

FSUIPC may also be servicing other applications, if you have any.  I suppose it is vaguely possible that other applications interact with EZDOK.

One thing I do notice is that your P3D is being allowed to run at an unnecessarily high average of 144 fps. I'm wondering if this is simply not allowing any time or processor power for EZDOK (or anything else) to do much. Try limiting the frame rate -- at least to your screen's refresh rate, lke 60.

Pete

 

 

Link to comment
Share on other sites

42 minutes ago, Ahmed Al-Dabbass said:

My Monitors refresh rate is 144 hz. Should i still limit the frame rate 60 ?(I have a pretty powerful pc with an 17700k).

It's worth a try.

43 minutes ago, Ahmed Al-Dabbass said:

If simconnect should be the problem what can i do to fix it? 

Sorry, but I've no idea what parts, if any, EZDOK uses.  Maybe it needs updating for P3D v4? You really need EZDOK support.

Pete

 

Link to comment
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
×
×
  • 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.