Jump to content
The simFlight Network Forums

Offset 0x1000 gives the wrong path


Recommended Posts

Dear Pete,

I only P3D V3.1 installed and, since installing FSUIPC 4.949, offset 0x1000 gives me the path of "Prepar3D v2 files" instead of "Prepar3D v3 files".

I did a search in the registry and found nothing with "Prepar3D v2 files"

Where FSUIPC find this information?

Below the "Install.log" and part of fsuipc4.log
 

 

Installer for FSUIPC4.DLL version 4.949


Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\DovetailGames\FSX
     Parameter"AppPath"
Not there, so looking in:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v3!  <<< ...
     SetupPath=F:\P3D\
===========================================================

INSTALLATION FOR Prepar3D v3:
SetupPath="F:\P3D\"
Checking version of the Prepar3D v3 EXE:
... Version 3.1.2.15831  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       F:\P3D\Modules\FSUIPC4.DLL
... Version 4.948g found.
Prepar3D v3 Modules folder already exists.
Okay -- installed FSUIPC4 into "F:\P3D\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Alain\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v3\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\Alain\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Alain\AppData\Roaming\Lockheed Martin\Prepar3D v3\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D2.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "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 "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" 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 "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================

All installer tasks completed.
Registration check for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************
 

 

********* FSUIPC4, Version 4.949 by Pete Dowson *********
Prepar3D.exe version = 3.1.2.15831
Reading options from "F:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0
Module base=5D040000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
      141 System time = 07/01/2016 14:33:31
      141 FLT path = "C:\Users\Alain\Documents\Prepar3D v2 Files\"
      141 ------ Module Version Check ------
      141        acontain.dll: 3.1.2.15831
      141             api.dll: 3.1.2.15831
      141        controls.dll: 3.1.2.15831
      141      fs-traffic.dll: 3.1.2.15831
      141             G3D.dll: 3.1.2.15831
      141            sim1.dll: 3.1.2.15831
      141        visualfx.dll: 3.1.2.15831
      141         weather.dll: 3.1.2.15831
      141          window.dll: 3.1.2.15831
      141 ----------------------------------
      141 Trying F:\P3D\Modules\SimConnectP3D2.dll
      219 Found it: trying to connect
      235 FS path = "F:\P3D\"
      422 ---------------------- Joystick Device Scan -----------------------
      422 Product= T.16000M
      422    Manufacturer= Thrustmaster
      422    Vendor=044F, Product=B10A (Version 5.0)
      422    Serial Number= Thrustmaster
      422 Product= CH PRO PEDALS USB
      422    Manufacturer= CH PRODUCTS
      422    Vendor=068E, Product=00F2 (Version 0.0)
      422    Serial Number= CH PRODUCTS
      422 Product= Saitek Pro Flight Quadrant
      422    Manufacturer= Saitek
      422    Vendor=06A3, Product=0C2D (Version 2.1)
      422    Serial Number= Saitek
      422 Product= CH ECLIPSE YOKE
      422    Manufacturer= S
      422    Vendor=068E, Product=0057 (Version 0.0)
      422    Serial Number= S
      422 -------------------------------------------------------------------
      610 LogOptions=00000000 00000001
      610 -------------------------------------------------------------------
      610 ------ Setting the hooks and direct calls into the simulator ------
      610 --- CONTROLS timer memory location obtained ok
      610 --- SIM1 Frictions access gained
      610 --- FS Controls Table located ok
      610 --- Installed Mouse Macro hooks ok.
      610 --- Wind smoothing fix is installed
      610 --- All links okay (except older global weather setting method)
      610 -------------------------------------------------------------------
      610 SimConnect_Open succeeded: waiting to check version okay
      610 Trying to use SimConnect Prepar3D
      625 VRI port 1 "com3" opened
    50172 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0)
    50172 Initialising SimConnect data requests now
    50172 FSUIPC Menu entry added
    50188 C:\Users\Alain\Documents\Prepar3D v3 Files\777_C&D_YSSY.fxml
    50188 F:\P3D\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air
    50641 VRI MCP2B ("MCP2 Boeing") detected on port com3
    78219 System time = 07/01/2016 14:34:49, Simulator time = 12:47:21 (02:47Z)
    78485 Aircraft="PMDG 777-228LR Air France (Fictional)"
    80172 Starting everything now ...
    80172 LUA.0: beginning "F:\P3D\Modules\ipcReady.lua"
    80172 LUA.0: ended "F:\P3D\Modules\ipcReady.lua"
    80172 Weather Mode now = Theme
    80188 LUA.1:
    80203 LUA.1: [iNIT]LINDA:: Loading...
    80266 ASN active function link set
    80266 Ready for ASN WX radar
    80406 LUA.1: LINDA:: Aircraft: PMDG 777-228LR Air France (Fictiona
    80422 LUA.1: LINDA:: Aircraft module detected: PMDG 777
    80469 LUA.0: LINDA:: AivlaSoft library loaded...
    80485 LUA.0: LINDA:: FSX standard library loaded...
    80516 LUA.0: LINDA:: IVAO library loaded...
    80516 LUA.0: LINDA:: RealityXP library loaded...
    80531 LUA.0: LINDA:: Weather library loaded...
    80547 LUA.0: LINDA:: A2A MAP library loaded...
    80672 LUA.0: F:\P3D\Modules\
    95750 Advanced Weather Interface Enabled
   103344 LUA.0: Doc :C:\Users\Alain\Documents\Prepar3D v2 Files\

 

Thanks in advance.

Best regards

Link to comment
Share on other sites

I only P3D V3.1 installed and, since installing FSUIPC 4.949, offset 0x1000 gives me the path of "Prepar3D v2 files" instead of "Prepar3D v3 files".

 

Good catch!

 

It is correct if the path is shared. For instance, on my PC the Documents path is shared so I get

 

FLT UNC path = "\\LEFT\Documents\Prepar3D v3 Files\"

 

where LEFT in my PC's name. Looks like I missed updating the path taken when folks aren't using sharing or regular networking.

 

Where FSUIPC find this information?

 

 

It doesn't find it anywhere. It has to make it up according to the version of FS it finds itself in.

 

I'll fix it now. Look out for an interim update (the DLL only) as 4.949a, in the Download Links subforum, later today.

 

Pete

Link to comment
Share on other sites

Dear Pete,

 

I just tested the 4.949a and, unfortunately, the path is always wrong.

 

********* FSUIPC4, Version 4.949a by Pete Dowson *********
Prepar3D.exe version = 3.1.2.15831
Reading options from "F:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0
Module base=5D9E0000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
      141 System time = 08/01/2016 15:58:56
      141 FLT path = "C:\Users\Alain\Documents\Prepar3D v2 Files\"
      141 ------ Module Version Check ------
      141        acontain.dll: 3.1.2.15831
      141             api.dll: 3.1.2.15831
      141        controls.dll: 3.1.2.15831
      141      fs-traffic.dll: 3.1.2.15831
      141             G3D.dll: 3.1.2.15831
      141            sim1.dll: 3.1.2.15831
      141        visualfx.dll: 3.1.2.15831
      141         weather.dll: 3.1.2.15831
      141          window.dll: 3.1.2.15831
      141 ----------------------------------
      141 Trying F:\P3D\Modules\SimConnectP3D2.dll
      172 Found it: trying to connect
      188 FS path = "F:\P3D\"
      359 ---------------------- Joystick Device Scan -----------------------
      359 Product= T.16000M
      359    Manufacturer= Thrustmaster
      359    Vendor=044F, Product=B10A (Version 5.0)
      359    Serial Number= Thrustmaster
      359 Product= CH PRO PEDALS USB
      359    Manufacturer= CH PRODUCTS
      359    Vendor=068E, Product=00F2 (Version 0.0)
      359    Serial Number= CH PRODUCTS
      375 Product= Saitek Pro Flight Quadrant
      375    Manufacturer= Saitek
      375    Vendor=06A3, Product=0C2D (Version 2.1)
      375    Serial Number= Saitek
      375 Product= CH ECLIPSE YOKE
      375    Manufacturer= S
      375    Vendor=068E, Product=0057 (Version 0.0)
      375    Serial Number= S
      375 -------------------------------------------------------------------
      547 LogOptions=00000000 00000001
      547 -------------------------------------------------------------------
      547 ------ Setting the hooks and direct calls into the simulator ------
      547 --- CONTROLS timer memory location obtained ok
      547 --- SIM1 Frictions access gained
      547 --- FS Controls Table located ok
      547 --- Installed Mouse Macro hooks ok.
      547 --- Wind smoothing fix is installed
      547 --- All links okay (except older global weather setting method)
      547 -------------------------------------------------------------------
      547 SimConnect_Open succeeded: waiting to check version okay
      547 Trying to use SimConnect Prepar3D
      563 VRI port 1 "com3" opened
    48672 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.1.3.1 (SimConnect: 3.1.0.0)
    48672 Initialising SimConnect data requests now
    48672 FSUIPC Menu entry added
    48688 C:\Users\Alain\Documents\Prepar3D v3 Files\777_F_GSSU_C&D_SCCI.fxml
    48688 F:\P3D\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.air
    49141 VRI MCP2B ("MCP2 Boeing") detected on port com3
    71344 System time = 08/01/2016 16:00:08, Simulator time = 22:43:47 (02:43Z)
    71531 Aircraft="PMDG 777-228LR Air France (Fictional)"
    75922 Starting everything now ...
    75922 LUA.0: beginning "F:\P3D\Modules\ipcReady.lua"
    75922 LUA.0: ended "F:\P3D\Modules\ipcReady.lua"
    75953 LUA.1:
    75953 LUA.1: [iNIT]LINDA:: Loading...
    75984 ASN active function link set
    75984 Ready for ASN WX radar
    76172 LUA.1: LINDA:: Aircraft: PMDG 777-228LR Air France (Fictiona
    76188 LUA.1: LINDA:: Aircraft module detected: PMDG 777
    76219 LUA.0: LINDA:: AivlaSoft library loaded...
    76234 LUA.0: LINDA:: FSX standard library loaded...
    76266 LUA.0: LINDA:: IVAO library loaded...
    76266 LUA.0: LINDA:: RealityXP library loaded...
    76281 LUA.0: LINDA:: Weather library loaded...
    76297 LUA.0: LINDA:: A2A MAP library loaded...
    76422 LUA.0: F:\P3D\Modules\
    77078 Advanced Weather Interface Enabled
    90328 LUA.0: Doc :C:\Users\Alain\Documents\Prepar3D v2 Files\

With a hard link between "Prepar3d v2 files" and "Prepar3d v3 files", I get what I want but it's not very clean and I would prefer that the offset 0x1000 gives me the right path.

 

Thanks for the job.

 

Best regards.

Link to comment
Share on other sites

I just tested the 4.949a and, unfortunately, the path is always wrong.

 

Hmm. That's very strange. I'll try disabling WideFS and see if I get the same. The construction of the path is based on FSUIPC's knowledge of the version you are using, and this is definitely confirmed as v3 by this line:

 

Running inside Prepar3D v3 on Windows 8.0

 

It isn't the sharing which makes it use UNC paths so much as whether WideFS is enabled or not.

 

I'll get back to you.

 

Pete

Link to comment
Share on other sites

Aha! I've found another way t gets the name -- from P3D itself, in the "Language.DLL". It is stored there as string number 36864. I must have added this as a much more reliable (!) and efficient way of getting it.

 

This SHOULD be the same name as actually used by P3D. Does your normal flight selection in P3D v3 work properly?

 

Here's the RESHACKER decompilation of the relevant part of my Language.DLL:

 

STRINGTABLE
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US
{
36864, "Prepar3D v3 Files"
36867, "SCENERY"
36869, "SOUND"
36870, "TEXTURE"
}
 
You see #36864 is correct here.
 
So, have you got a different Language.DLL? Mine reports file and product version 3.1.2.15381. dated 17/12/2015 08:15. Please check.
 
Pete
Link to comment
Share on other sites

Dear Pete,

 

Again, you are right.

I modified this dll to delete the green band at the opening closing doors.
When I updated to 3.10, I took this dll from a backup but it was the wrong version (2.5).

Thank you, I never would have thought.

Best regards

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.