Jump to content
The simFlight Network Forums

Recommended Posts

Dear Pete,

 

first of all I would like to thank you very much for having done the development of a 64-bit FSUIPC. This is appreciated so much.

I have just installed FSUIPC5 and registered it into a clean installation of P3Dv4 (no addons at all)

As soon as I start P3D, I see the startup screen showing the P3D logo. Then windows comes up with "Prepar3d stopped working".

At the moment it looks to me like it is directly related to FSUIPC5. It worked before the installation.

After I got the error I disabled FSUIPC5.dll in the DLL.XML and Prepar3D is starting up again. As soon as I set the disabled flag in dll.xml to false again, P3D crashes on startup.

 

Do you have any advice for me what I can do? Or anything I can do in order to help to locate the problem?

 

Many thanks

Daniel

Share this post


Link to post
Share on other sites

Hi Pete,

I just have read the thread "FSUIPC reg problem". I can also confirm that FSUIPC works fine as long as I dont register my version.

Are you still in need of logs regarding that or are the logs from the other users already sufficient?

If you need any logs, please tell me... otherwise we can delete this thread and I continue reading the other one regarding this problem.

Thanks

Daniel

Share this post


Link to post
Share on other sites
1 hour ago, AirSimTech said:

Do you have any advice for me what I can do? Or anything I can do in order to help to locate the problem?

There will be crash details in the Windows Event Viewer, Application Logs. I need those details please.

Also please show me the FSUIPC5.LOG file from the P3D4 Modules folder (not the Install log), and also the FSUIPC5.INI file.

Thank you,
Pete

 

Share this post


Link to post
Share on other sites
46 minutes ago, AirSimTech said:

Are you still in need of logs regarding that or are the logs from the other users already sufficient?

As yet, despite my requests, I have no actual FSUIPC.LOG for this problem. I also need the Windows crash details please. See previous message in this thread.

Thank you!

Pete

 

Share this post


Link to post
Share on other sites

Hi Pete,

 

here the FSUIPC log (I just put "xxx" to the user name and user addr. Both have been provided by the log)

********* FSUIPC5, Version 5.10 (1st June 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
FSUIPC5.dll version = 5.1.0.0
Reading options from "E:\P3Dv4\Modules\FSUIPC5.ini"
Running inside Prepar3D v4 on Windows 10
Module base=7FFF7CE10000
User Name=xxx
User Addr=xxx
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
       32 System time = 06/06/2017 10:22:58
       32 FLT path = "C:\Users\danie\Documents\Prepar3D v4 Files\"
       32 ------ Module Version Check ------
       32        acontain.dll: 4.0.23.21468
       32             api.dll: 4.0.23.21468
       32        controls.dll: 4.0.23.21468
       32      fs-traffic.dll: 4.0.23.21468
       32             G3D.dll: 4.0.23.21468
       47        language.dll: 4.0.23.21468
       47            sim1.dll: 4.0.23.21468
       47        visualfx.dll: 4.0.23.21468
       47         weather.dll: 4.0.23.21468
       47          window.dll: 4.0.23.21468
       47 ----------------------------------
       47 FS path = "E:\P3Dv4\"
      188 ---------------------- Joystick Device Scan -----------------------
      188 Product= UMDF Virtual hidmini device Product string
      188    Manufacturer= UMDF Virtual hidmini device Manufacturer string
      188    Serial Number= UMDF Virtual hidmini device Serial Number string
      188    Vendor=BEEF, Product=FEED (Version 1.1)
      188 -------------------------------------------------------------------

Now the FSUIPC5.ini

[General]
UpdatedByVersion=5100
History=E2QERSPI3X6VX1BGX3WHO
InitDelayDevicesToo=No
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
ProvideAIdata=Yes
ProvideAIairports=Yes
Console=No

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0

[WideServer]
WideFSenabled=Yes

 

Windows crash log to follow in a minute

 

Share this post


Link to post
Share on other sites

Here is the HIDScanner result (I also monitor the other thread about this issue and thought it would be useful)

********* HidScanner, Version 2.00 by Pete Dowson *********
 
  Device at "\\?\hid#lenovovhid#1&632d18&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
  Vendor=BEEF, Product=FEED (Version 1.1)
  Manufacturer= UMDF Virtual hidmini device Manufacturer string
  Product= UMDF Virtual hidmini device Product string
  Serial Number= UMDF Virtual hidmini device Serial Number string
  Usage Page: 1
  Input Report Byte Length: 2
  Output Report Byte Length: 0
  Feature Report Byte Length: 0
  Number of Link Collection Nodes: 1
  Number of Input Button Caps: 1
  Number of InputValue Caps: 0
  Number of InputData Indices: 1
  Number of Output Button Caps: 0
  Number of Output Value Caps: 0
  Number of Output Data Indices: 0
  Number of Feature Button Caps: 0
  Number of Feature Value Caps: 0
  Number of Feature Data Indices: 0
  **************************************************************************

I am running P3Dv4 on my developer notebook without any external devices connected at that time.

Event logger shows this:

- System
   
- Provider
      [ Name] Application Error
   
- EventID 1000
      [ Qualifiers] 0
   
  Level 2
   
  Task 100
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2017-06-06T08:40:37.228919400Z
   
  EventRecordID 2794
   
  Channel Application
   
  Computer ASTNOTEBOOK
   
  Security
- EventData
      Prepar3D.exe
      4.0.23.21468
      59279be2
      ucrtbase.dll
      10.0.15063.0
      af2e320b
      c0000409
      0000000000072208
      668
      01d2dea08ef95874
      E:\P3Dv4\Prepar3D.exe
      C:\WINDOWS\System32\ucrtbase.dll
     

42d6d87a-cf89-4d91-a99f-da50e59550e0

Share this post


Link to post
Share on other sites

Followed by this 11 seconds later in the event viewer

- System
   
- Provider
      [ Name] Windows Error Reporting
   
- EventID 1001
      [ Qualifiers] 0
   
  Level 4
   
  Task 0
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2017-06-06T08:40:48.378161500Z
   
  EventRecordID 2795
   
  Channel Application
   
  Computer ASTNOTEBOOK
   
  Security
- EventData
      116388793891
      5
      BEX64
      Nicht verfügbar
      0
      Prepar3D.exe
      4.0.23.21468
      59279be2
      ucrtbase.dll
      10.0.15063.0
      af2e320b
      0000000000072208
      c0000409
      0000000000000005
       
      \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1831.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER18FD.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER191B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER193C.tmp.txt
      C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_c17212b249c99ab78b258b4e1fe69bd12b9bd8_900409ed_0f284377
       
      0
      42d6d87a-cf89-4d91-a99f-da50e59550e0
      268435456
     

9db7d9b12f954aa326f9c688212bdb90

 

 

Share this post


Link to post
Share on other sites

In all cases so far the Joystick Scan seems to show a device which is not of the Joystick type. It shouldn't even be told of those -- if there's no joysticks, it should simply be empty, no scan.

So, do YOU have any joystick type devices connected at all?

Please add these lines to the [General] section of the FSUIPC5.INI file:

Debug=Please
LogExtras=x200000

This will log the detail of the scan process and its immediate aftermath. Show m the resulting log after the crash, please.

Pete

 

Share this post


Link to post
Share on other sites

Hi Pete,

 

no, absolutely no joystick devices at all

New log is here

********* FSUIPC5, Version 5.10 (1st June 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
FSUIPC5.dll version = 5.1.0.0
Reading options from "E:\P3Dv4\Modules\FSUIPC5.ini"
Running inside Prepar3D v4 on Windows 10
Module base=7FFF7B0F0000
User Name=xxx
User Addr=xxx
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 06/06/2017 12:47:41
        0 FLT path = "C:\Users\danie\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.23.21468
        0             api.dll: 4.0.23.21468
        0        controls.dll: 4.0.23.21468
        0      fs-traffic.dll: 4.0.23.21468
        0             G3D.dll: 4.0.23.21468
        0        language.dll: 4.0.23.21468
        0            sim1.dll: 4.0.23.21468
        0        visualfx.dll: 4.0.23.21468
        0         weather.dll: 4.0.23.21468
        0          window.dll: 4.0.23.21468
        0 ----------------------------------
        0 FS path = "E:\P3Dv4\"
      188 #### Initialising Dlrectinput Axis Scanning ...
      188    (Entry from GetRegisteredOptions)
      188 ---------------------- Joystick Device Scan -----------------------
      188 Checking: \\?\hid#lenovovhid#1&632d18&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      188    Usage=12, UsagePage=1, =Flight Mode Switch
      188 Product= UMDF Virtual hidmini device Product string
      188    Manufacturer= UMDF Virtual hidmini device Manufacturer string
      188    Serial Number= UMDF Virtual hidmini device Serial Number string
      188    Vendor=BEEF, Product=FEED (Version 1.1)
      188 -------------------------------------------------------------------
      204 ****** Registry scanning: VID=BEEF, PID=FEED ******
      204 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_BEEF&PID_FEED\Calibration\0"
      204    ... and a "GUID" value
      204    GUID= {01918630-49FC-11E7-8002-444553540000}
      204        NB: not valid for this device according to GetConfig!

 

Share this post


Link to post
Share on other sites

There is no extra hardware connected or built in the notebook. It is just a Lenovo ideapad as it is out of the box.

No external keyboard, no external mouse, no joystick.

 

Let me know what I can do to assist.

Daniel

Share this post


Link to post
Share on other sites
1 hour ago, AirSimTech said:

no, absolutely no joystick devices at all

That seems to be the common theme amongst those with this problem. I've tried here on a PC with no joysticks, but it works fine. But that was on a Win7 PC. I'll try on Win10.

1 hour ago, AirSimTech said:

204 ****** Registry scanning: VID=BEEF, PID=FEED ******
      204 Trying: "HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_BEEF&PID_FEED\Calibration\0"
      204    ... and a "GUID" value
      204    GUID= {01918630-49FC-11E7-8002-444553540000}
      204        NB: not valid for this device according to GetConfig!

Looks like the non-Joystick device that DirectInput is giving me (I'm actually asking for "connected joysticks"!!!) causes the crash when I try to read its configuration (number of buttons, axes, and current values). This is part of my "validity" checking on devices before adding them to the scans for assignments.

1 hour ago, AirSimTech said:

It is just a Lenovo ideapad as it is out of the box.

Using Win10  I suppose?

I bet it's another bug in Win10 which I need to work-around! I've had several already.. :-(

Pete

 

Share this post


Link to post
Share on other sites

Good morning Pete,

you are right. It's win 10. Really bad if developers have to do work-arounds due to bugs not related to their software. I thought Win10 is the OS to go... even better than Win 7.

Daniel

 

Share this post


Link to post
Share on other sites
42 minutes ago, AirSimTech said:

you are right. It's win 10. Really bad if developers have to do work-arounds due to bugs not related to their software. I thought Win10 is the OS to go... even better than Win 7.

I'm not sure if it in Win10 adding it, or it got installed by some other driver, but I think the cause is that odd device "BEEF" "FEED". Even the VID and PID look phoney.

Anyway, now please try 

FSUIPC5101d_TEST.zip

still with these lines added to the[General] section of the FSUIPC5.INI file:

Debug=Please
LogExtras=x200000

and please show me the Log file after, no matter what the result.

This version attempts to weed out odd looking devices rather than ask them for more particulars.

Pete

Share this post


Link to post
Share on other sites

Hi Pete,

this time it works.

Here is the log:

********* FSUIPC5, Version 5.101d (7th June 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FFF76BC0000
Windows 10 Home 64 Bit reported as Build 15063, Release ID: 1703 (OS 10.0)
Prepar3D.exe version = 4.0.23.21468
Checking the Registrations now ...
User Name=xxx
User Addr=xxx
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 07/06/2017 11:09:56
        0 FLT path = "C:\Users\danie\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.0.23.21468
        0             api.dll: 4.0.23.21468
        0        controls.dll: 4.0.23.21468
        0      fs-traffic.dll: 4.0.23.21468
        0             G3D.dll: 4.0.23.21468
       16        language.dll: 4.0.23.21468
       16            sim1.dll: 4.0.23.21468
       16        visualfx.dll: 4.0.23.21468
       16         weather.dll: 4.0.23.21468
       16          window.dll: 4.0.23.21468
       16 ----------------------------------
       32 FS path = "E:\P3Dv4\"
      110 #### Initialising Dlrectinput Axis Scanning ...
      110    (Entry from GetRegisteredOptions)
      110 ---------------------- Joystick Device Scan -----------------------
      110 Checking: \\?\hid#lenovovhid#1&632d18&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
      110    Usage=12, UsagePage=1, =Flight Mode Switch
      110 -------------------------------------------------------------------
      110 -------------------------------------------------------------------
      110 ---------- Making INI JoyNames Section ----------
      110     wJoyIDsUsed=0000
      110 -------------------------------------------------
      110   Checking and assigning Joy Letters as needed
      110 #### Completed Dlrectinput Axis Scanning
      125 LogOptions=00000000 02000011
      125 SimConnect_Open succeeded: waiting to check version okay
      125 Opened separate AI Traffic client okay
    10188 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.0.23.21468 (SimConnect: 4.0.0.0)
    10188 Initialising SimConnect data requests now
    10188 FSUIPC Menu entry added
    10188 ... Using Prepar3D with Professional License
    10204 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    10204 C:\Users\danie\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    10204 E:\P3Dv4\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    59750 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    59766 Aircraft loaded: running normally now ...
    59782 User Aircraft ID 2 supplied, now being used
    59907 System time = 07/06/2017 11:10:56, Simulator time = 14:00:02 (19:00Z)
    59922 Aircraft="F-22 Raptor - 525th Fighter Squadron"
    65938 Starting everything now ...
    65938 Note: "E:\P3Dv4\Modules\PFCcom64.DLL", Error 126 (Das angegebene Modul wurde nicht gefunden. )
    65985 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    66375 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
    67688 === Closing session: waiting for DLLStop to be called ...
    75813 === DLLStop called ...
    75813 === Closing external processes we started ...

Share this post


Link to post
Share on other sites

Hi Pete,

 

I have the same problem a mentioned in the first post.

I installed everything as Admin:

Enclosed my log file:

Installer for FSUIPC5.DLL version 5.122


Looking in registry for Prepar3D v4 install path:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4
     Parameter"AppPath"
... >>>  OK! FOUND Prepar3D v4!  <<< ...
     AppPath=D:\Program Files\Lockheed Martin\Prepar3D v4\
===========================================================

INSTALLATION FOR Prepar3D v4:
AppPath="D:\Program Files\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 as:
       D:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL
... No previous valid version found.
Prepar3D v4 Modules folder created okay!
Okay -- installed FSUIPC5 into "D:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL"
Looking for the current user's Application Data path: 
... found as "C:\Users\Latte\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one
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\Latte\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Latte\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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Attempt to set the ACL entries for Modules access permissions failed, error = 1332
"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

 

But I have no enties in the.ini file.

What am I doing wrong ?

Thanks for help.

 

Rgds

Lars

Share this post


Link to post
Share on other sites

FSUIPC5 is no longer compatible with P3D version 4.0. You MUST update to P3D 4.1.

It does tell you this in the Change notes included with the FSUIPC downloaded installer!

And you are lucky I found your post! There are others, more recent, on exactly the same subject which you should have looked at first, but in any case, please NEVER add a new post to a very old thread or it will often simply not be seen, being hidden way down many pages deep!

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


×