Jump to content
The simFlight Network Forums
mquaedflieg

P3D v4.1 is visible in taskmanager, but no splash screen

Recommended Posts

Moved to Main Forum !  Please send question always in Main Forum.

Dear Sir,

I am running Win 10, P3D v4.1 and  FSUIPC 5.122a (I use a lot of Goflight equipment).
When I start P3D v 4.1 the program is visible in the taskmanager.
But there is no splash screen, when I rename DLL.XML to "whatever"; P3D starts normally.

I deleted subsequently every input in DLL.xml and I found out that the issue is at FSUIPC.
However it is a bit more complex, when I reinstall FSUIPC 5.122  over the current version of FSUIPC, P3D v4.1 starts perfectly to the splash screen.
Every when I shutdown Win 10, I need to reinstall FSUIPC to get to the splash screen of P3D v4.1.
As you understand reinstalling FSUIPC everytime when I want to play P3D v4.1 is a bit annoying.
Would you be so kind to help me this issue.

Attached are the two key files of FSUIPC

Greetings Martin

 

FSUIPC5 Install.log

FSUIPC5.ini

Share this post


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

I deleted subsequently every input in DLL.xml and I found out that the issue is at FSUIPC.
However it is a bit more complex, when I reinstall FSUIPC 5.122  over the current version of FSUIPC, P3D v4.1 starts perfectly to the splash screen.

As Thomas says, the LOG is the most important file. It is made to show what is happening. And check: is a new log being made when youhave one of the failed loads? If so, we need a long form a "normal" run AND the one from the failed run.

Usually the reason for a problem on load which is fixed by a re-install indicates that the previous session of P3D did not terminate successfully, so the DLL gets "marked" in the registry.  This stops it loading, but SimConnect stupidly doesn't notice this and tries to enter it. The installer clears this 'black' mark.

1 hour ago, mquaedflieg said:

Every when I shutdown Win 10, I need to reinstall FSUIPC to get to the splash screen of P3D v4.1.

What about when you close P3D, without closing Win10?

Pete

 

Share this post


Link to post
Share on other sites
6 minutes ago, mquaedflieg said:

as requested:)

The log doesn't terminate. When was that made, after a bad start or a good one? If the latter you need to let P3D close first.

I see it doesn't get as far as even loading the GFDev driver for GoFlight.

Also it is a log from 5.122a, whereas the Installer only installs 5.122. How is that?

Oh, one other thing: try removing the GFDev64.DLL, see if you get problems without the GoFlight devices. 

Pete

 

Share this post


Link to post
Share on other sites

Dear Pete,

I would like to attach the new logs and the ini file after a full stop of P3D v4.1, when I reinstalled. But I cannot upload them (due to a limit). The previous files prevents me from uploading new files.

What I did till now:
I deleted FSUIPC.dll from the modules directory and reinstalled FSUIPC (the latest version from Shiratti).
I also removed GFDev64.Dll but that did not solve the issue either.
Hoping for a solution.
 

Greetings Martin

Share this post


Link to post
Share on other sites
2 minutes ago, mquaedflieg said:

But I cannot upload them (due to a limit).

Files? Only need the Log. If that's too big there's something badly wrong, as there's not much to it by default. You can ZIP it in any case, it ZIPS up well.

3 minutes ago, mquaedflieg said:

The previous files prevents me from uploading new files.

No way. That is simply not possible. you are doing something else wrong.

4 minutes ago, mquaedflieg said:

I deleted FSUIPC.dll from the modules directory and reinstalled FSUIPC (the latest version from Shiratti).

Replacing 5.122 with 5.122, no matter whether from here (in the Downloads subforum) or Scvhiratti won't change anything as the exact same file results!

Pete

 

Share this post


Link to post
Share on other sites

 

Dear Pete,

The log file is 6.5 kb

see what is visible in my account.

My Attachments

 

ATTACHMENT QUOTA

82%
 

You have used 16.39 kB of your 20 kB attachment limit.

Share this post


Link to post
Share on other sites

I've never heard of any such small limit, and certainly not a cumulative one! Just take a look at the many other posts in this forum with many and larger attachments. Maybe you are using some odd method? I'd check what you are doing if I were you, or if you are being victimised for some reason, post a problem report on your Simmarket account.

Anyway, if it is that small why not simply paste its contents into your message? Use the <> button above the edit area and paste it.

Pete

 

Share this post


Link to post
Share on other sites
********* FSUIPC5, Version 5.122 (17th November 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FF8AC3E0000
Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0)
Prepar3D.exe version = 4.1.7.22841
Checking the Registrations now ...
User Name="Martin Quaedflieg"
User Addr="m.quaedflieg@home.nl"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 08/01/2018 14:31:40
        0 FLT path = "C:\Users\mquae\OneDrive\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.1.7.22841
        0             api.dll: 4.1.7.22841
        0        controls.dll: 4.1.7.22841
        0      fs-traffic.dll: 4.1.7.22841
        0             G3D.dll: 4.1.7.22841
        0        language.dll: 4.1.7.22841
        0            sim1.dll: 4.1.7.22841
        0        visualfx.dll: 4.1.7.22841
        0         weather.dll: 4.1.7.22841
        0          window.dll: 4.1.7.22841
        0 ----------------------------------
       16 FS path = "D:\Lockheed Martin\Prepar3d v4\"
      141 ---------------------- Joystick Device Scan -----------------------
     1016 Product= Logitech Dual Action
     1016    Manufacturer= Logitech
     1016    Vendor=046D, Product=C216 (Version 3.0)
     2312    GUIDs returned for product: VID_046D&PID_C216:
     2312       GUID= {DFAA5960-4EC0-11E7-8008-444553540000}
     2312       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X255,Y255,Z255
     2312 Product= Saitek Pro Flight Yoke
     2312    Manufacturer= Saitek
     2312    Vendor=06A3, Product=0BAC (Version 3.2)
     2312    GUIDs returned for product: VID_06A3&PID_0BAC:
     2312       GUID= {E2A6A970-4EC0-11E7-800F-444553540000}
     2312       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
     2312 Product= TQ6
     2312    Manufacturer= GoFlight
     2312    Serial Number= 00080 7
     2312    Vendor=09F3, Product=0200 (Version 2.0)
     2312    GUIDs returned for product: VID_09F3&PID_0200:
     2312       GUID= {730D0CE0-4EE2-11E7-8006-444553540000}
     2312       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R223,U224,V227,X224,Y228,Z231
     2312       GUID= {7FF57E60-4EE2-11E7-800F-444553540000}
     2312       Details: Btns=4, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R223,U223,V228,X228,Y222,Z223
     2312 Product= TQ6
     2312    Manufacturer= GoFlight
     2312    Serial Number= 00080 7
     2312    Vendor=09F3, Product=0200 (Version 2.0)
     2328 -------------------------------------------------------------------
     2328 Device acquired for use:
     2328    Joystick ID = 1 (Registry okay)
     2328    1=Logitech Dual Action USB
     2328    1.GUID={DFAA5960-4EC0-11E7-8008-444553540000}
     2328 Device acquired for use:
     2328    Joystick ID = 3 (Registry okay)
     2328    3=Saitek Pro Flight Yoke
     2328    3.GUID={E2A6A970-4EC0-11E7-800F-444553540000}
     2328 Device acquired for use:
     2328    Joystick ID = 0 (Registry okay)
     2328    0=GoFlight GF-TQ6 Throttle System
     2328    0.GUID={730D0CE0-4EE2-11E7-8006-444553540000}
     2328 Device acquired for use:
     2328    Joystick ID = 4 (Registry okay)
     2328    4=GoFlight GF-TQ6 Throttle System
     2328    4.GUID={7FF57E60-4EE2-11E7-800F-444553540000}
     2328 -------------------------------------------------------------------
     2375 LogOptions=00000000 00000001
     2391 SimConnect_Open succeeded: waiting to check version okay
     2391 Opened separate AI Traffic client okay
    30000 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.1.7.22841 (SimConnect: 4.1.0.0)
    30000 Initialising SimConnect data requests now
    30000 FSUIPC Menu entry added
    30000 ... Using Prepar3D with Academic License
    30031 C:\Users\mquae\OneDrive\Documents\Prepar3D v4 Files\Prepar3D_Defaultmq.fxml
    30031 C:\Users\mquae\OneDrive\Documents\Prepar3D v4 Add-ons\A2A\SimObjects\Airplanes\A2A_C182\C182.air
   213094 Aircraft loaded: running normally now ...
   213094 User Aircraft ID 1 supplied, now being used
   214062 System time = 08/01/2018 14:35:14, Simulator time = 14:32:46 (13:32Z)
   214109 Aircraft="C182_ZK-SAR"
   221031 Starting everything now ...
   221125 ASN active function link set
   221125 Ready for ActiveSky WX radar with additional data
   223156 Using "D:\Lockheed Martin\Prepar3d v4\Modules\GFDEV64.DLL", version 2.2.8.0
   223156 GoFlight GFP8 detected: 1 device 
   223156 GoFlight GFT8 detected: 1 device 
   223156 GoFlight GF166 detected: 5 devices
   223156 GoFlight GFRP48 detected: 2 devices
   223156 GoFlight GF46 detected: 1 device 
   223156 GoFlight GFTQ6 detected: 2 devices
   223156 GoFlight GFMCPPRO detected: 1 device 
   223156 GoFlight GFSECM detected: 1 device 
   224375 Advanced Weather Interface Enabled
   225656 Weather Mode now = Theme
   238078 Sim stopped: average frame rate for last 25 secs = 22.3 fps
   238078    Max AI traffic was 13 aircraft (Deleted 0)
   239547 === Closing session: waiting for DLLStop to be called ...
   261547 === DLLStop called ...
   261547 === Closing external processes we started ...
   262547 === About to kill any Lua plug-ins still running ...
   262703 === Closing global Lua thread
   263703 === About to kill my timers ...
   263906 === Restoring window procs ...
   263906 === Unloading libraries ...
   263906 === stopping other threads ...
   263906 === ... Button scanning ...
   264016 === ... Axis scanning ...
   264109 === Releasing joystick devices ...
   264109 === Freeing macro memory
   264109 === Removing any offset overrides
   264109 === Clearing any displays left
   264109 === NOTE: not calling SimConnect_Close ...
   264109 === AI slots deleted!
   264109 === Freeing button memory ...
   264109 === Closing my Windows ...
   264109 === Freeing FS libraries ...
   265109 === Closing devices ...
   265109 === Closing the Log ... Bye Bye! ...
   265109 System time = 08/01/2018 14:36:05, Simulator time = 14:33:08 (13:33Z)
   265109 *** FSUIPC log file being closed
Minimum frame rate was 22.0 fps, Maximum was 28.5 fps
Average frame rate for running time of 25 secs = 22.3 fps
Maximum AI traffic for session was 13 aircraft
Memory managed: 18 Allocs, 17 Freed
********* FSUIPC Log file closed ***********

Dear Pete,
Here it is.
Greetings Martin

Share this post


Link to post
Share on other sites

Dear Pete,

 

Just for your info when P3D v4.1 is only in the taskmanager (no splash screen appears) there is no FSUIPC5.log file generated.

Share this post


Link to post
Share on other sites
15 hours ago, mquaedflieg said:

Dear Pete,
Here it is.
Greetings Martin

That's the log from a good working sessio, no problem.

13 hours ago, mquaedflieg said:

Just for your info when P3D v4.1 is only in the taskmanager (no splash screen appears) there is no FSUIPC5.log file generated.

In that case FSUIPC isn't actually being loaded, as it starts the Log immediately. This is exactly the sort of problem which occurs when the previous session ended with a problem which is somehow attributed to FSUIPC. So my guess is that something you are using is causing a hang or crash in one of the many threads, or possibly in a lower level (driver).

12 hours ago, mquaedflieg said:

And when I make another user account in win 10 with admin rights, everything works fine....

Are you saying you don't have admin rights when you run P3D normally? That's a mistake. Many things need it to be run in your main owner-administrator account.

So, perhaps that's the solution?

Pete

 

Share this post


Link to post
Share on other sites

 

Dear Pete,

I transferred all my personal files to that new account made by me, (by the way both had admin rights and P3D ran with admin previleges).

Finally, I just removed the first account, it was maybe corrupted.

Now everything just works fine like it should do.

This PC is my simulation PC only:)

Anyway thanks for the quick support.

Greetings Martin

Share this post


Link to post
Share on other sites

Hilfe!

Ich kaufte gestern FSUIPC5 installierte es auf 64bit für den P3D V4. Jetzt lässt sich P3D nicht mehr starten. Ich habe gelesen, man muss die neue dll 5.122 gegen die ältere Version ersetzen. Wo finde ich diese DLL?

Danke für jeden Hinweis.

Edited by Pixelman

Share this post


Link to post
Share on other sites

In my new profile I I now have the same issue again, P3D goes in the taskmanager and no splash screen again.

When I reinstall FSUIPC again every thing works fine.

There was also an entry of FSUIPC in  HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers\

there is a key for "Prepar3D.exe" in there with a value of "$ IgnoreFreelibrary<FSUIPC5.dll>" should it be there?

FSUIPC5_prev.log

Share this post


Link to post
Share on other sites
5 hours ago, mquaedflieg said:

There was also an entry of FSUIPC in  HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers\

there is a key for "Prepar3D.exe" in there with a value of "$ IgnoreFreelibrary<FSUIPC5.dll>" should it be there?

No, and the FSUIPC Installer removes it. Also I believe the next update for P3D4 will delete them.

Those entries are made by windows when a program crashes on exit. Windows blames the last component of that program still running, which is sometimes a thread of FSUIPC -- things like tidying up WideFF connections, Lua plug-ins and so on, is done whilst P3D is closing. Some Lua plug-ins, like those used by LINDA for some devices, use other external DLs and device drivers which sometimes don't shut down properly.

Check the Windows Event Viewer to see if Windows has logged crashes or other errors in P3D. They will be the reason and may help identify which add-on is really causing the problem. However, quite often P3D seems to "crash to desktop" as if it has closed, and with no error information at all!

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.