Jump to content
The simFlight Network Forums
Sumits81

FSUIPC Errors After Upgrade 4.9.6.1 (P3D)

Recommended Posts

Hi Pete,

I updated from v4.959 to 4.961 last night and have run into problems at sim (P3D) launch. Logs produced in Windows 10 are below:

Faulting application name: Prepar3D.exe, version: 3.4.18.19475, time stamp: 0x5851bfd2
Faulting module name: FSUIPC4.dll_unloaded, version: 4.9.6.1, time stamp: 0x58933f1b
Exception code: 0xc0000005
Fault offset: 0x00020f10
Faulting process id: 0x16b8
Faulting application start time: 0x01d27db53dcc0036
Faulting application path: E:\P3D\Prepar3D.exe
Faulting module path: FSUIPC4.dll
Report Id: e664d8ec-5763-4ba2-8d87-f753ff39efef
Faulting package full name: 
Faulting package-relative application ID: 

Following the Avsim CTD guide, when I change the disable option from 'false' to 'true' in the dll.xml file, P3D starts up fine. Enabling it again causes a crash.

Need your help please.

Thanks

Sumit

Edit: Apologies, just to add- I also (after reading your suggestion to another user) copied just the FSUIPC.DLL to the modules folder but that yielded the same result.

Also as the other user, if I reinstall FSUIPC (or GSX Addon Manager) the sim launches OK but doesn't after closing and relaunching.

Thought I should add that here.

 

Share this post


Link to post
Share on other sites

Apart from that offset in the crash report being for a different location in FSUIPC, this appears to be the same problem as dealt with at enormous length in the other thread. Please see that.  But some questions first:

1. Is there ANY log at all from FSUIPC4 for the session which crashes on loading?
2. Is the FSUIPC log complete from a good session -- i.e does it show it is closed? 

Maybe if you showed me either or both it would help more. I can't work in a vacuum with nothing to go on. 

Oh, one other little check you can do, please.  Try changing the OOM check option in the INI file to:

OOMcheck=N

(The very last change for 4.961 was to move the check into a separate thread).

Pete

 

 

 

 

Share this post


Link to post
Share on other sites

Hi Pete,

Thanks for taking the time. I have been following the other thread and will keep an eye on it. See response to your questions:

1)  No logs (WinEvents or FSUIPC.txt) are generated with CTD occurs.

2) ********* FSUIPC4, Version 4.961 (1st February 2017) by Pete Dowson *********
Windows 10 Enterprise N 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.18.19475
Reading options from "E:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=53390000
User Name="Sumits81"
User Addr="xxxxx@xxxxxxxxxx.xxx"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
      125 System time = 04/02/2017 01:22:33
      125 FLT path = "C:\Users\Sumit\Documents\Prepar3D v3 Files\"
      125 ------ Module Version Check ------
      125        acontain.dll: 3.4.18.19475
      125             api.dll: 3.4.18.19475
      125        controls.dll: 3.4.18.19475
      125      fs-traffic.dll: 3.4.18.19475
      125             G3D.dll: 3.4.18.19475
      125        language.dll: 3.4.18.19475
      125            sim1.dll: 3.4.18.19475
      125        visualfx.dll: 3.4.18.19475
      125         weather.dll: 3.4.18.19475
      125          window.dll: 3.4.18.19475
      125 ----------------------------------
      141 Trying E:\P3D\Modules\SimConnectP3D3.dll
      141 Found it: trying to connect
      141 FS path = "E:\P3D\"
      250 ---------------------- Joystick Device Scan -----------------------
     5250 Product= 
    10250    Manufacturer= 
    10250    Vendor=06A3, Product=0762 (Version 1.35)
    10250    Serial Number= 
    10250 -------------------------------------------------------------------
    10250 LogOptions=00000000 00000001
    10250 -------------------------------------------------------------------
    10250 ------ Setting the hooks and direct calls into the simulator ------
    10250 --- CONTROLS timer memory location obtained ok
    10250 --- SIM1 Frictions access gained
    10250 --- FS Controls Table located ok
    10250 --- Installed Mouse Macro hooks ok.
    10250 --- Wind smoothing fix is installed
    10250 --- SimConnect intercept for texts and menus option is off
    10250 --- All links okay (except older global weather setting method)
    10250 -------------------------------------------------------------------
    10250 SimConnect_Open succeeded: waiting to check version okay
    10250 Trying to use SimConnect Prepar3D
    10250 Opened separate AI Traffic client okay
    33937 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
    33937 Initialising SimConnect data requests now
    33937 FSUIPC Menu entry added
    33953 C:\Users\Sumit\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    33953 E:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
   124094 E:\P3D\SimObjects\Airplanes\PMDG 747-400\B747-400_RR.air
   145672 User Aircraft ID 2 supplied, now being used
   146094 System time = 04/02/2017 01:24:59, Simulator time = 08:00:01 (07:00Z)
   146094 Aircraft="PMDG 747-436 British Airways (G-CIVI | 2016)"
   149437 Weather Mode now = Theme
   150844 Starting everything now ...
   150844 ASN active function link set
   150844 Ready for ASN WX radar
   218984 **** No SimConnect events or states being received! Re-connecting now ... ****
   219078 SimConnect_Open succeeded: waiting to check version okay
   219078 Opened separate AI Traffic client okay
   228984 **** No SimConnect events or states being received! Re-connecting now ... ****
   229078 SimConnect_Open succeeded: waiting to check version okay
   229078 Opened separate AI Traffic client okay
   239000 **** No SimConnect events or states being received! Re-connecting now ... ****
   239109 SimConnect_Open succeeded: waiting to check version okay
   239109 Opened separate AI Traffic client okay
   249000 **** No SimConnect events or states being received! Re-connecting now ... ****
   249109 SimConnect_Open succeeded: waiting to check version okay
   249109 Opened separate AI Traffic client okay
   286531 === Calling SimConnect_Close ...
   286734 === SimConnect_Close done!
   287734 System time = 04/02/2017 01:27:20, Simulator time = 08:01:07 (07:01Z)
   287734 *** FSUIPC log file being closed
Minimum frame rate was 29.7 fps, Maximum was 32.9 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 68 secs = 28.3 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

I've changed  OOMcheck=No but that doesn't seem to have made a diff.

Thanks

 

Share this post


Link to post
Share on other sites
8 hours ago, Sumits81 said:

1)  No logs (WinEvents or FSUIPC.txt) are generated with CTD occurs.

"FSUIPC.log" I assume you mean. So, it is in fact identical to the later entries in the other thread. Something is causing a crash on a previous otherwise good session, when you exit. In the session where you get a CTD on loading, FSUIPC is in fact not being entered at all, it doesn't run therefore cannot crash.

8 hours ago, Sumits81 said:

   287734 *** FSUIPC log file being closed
Minimum frame rate was 29.7 fps, Maximum was 32.9 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 68 secs = 28.3 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

And this proves that, in fact, FSUIPC completed and closed successfully on the "good" session. So FSUIPC cannot actually be responsible. Something else is causing the problem in the "good" session. 

Surely the Windows event viewer shows something about crashes when you close P3D?

I think you need to conduct a process of elimination on all your add-ins and add-ons.

Pete

 

Share this post


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

Surely the Windows event viewer shows something about crashes when you close P3D?

Sometimes there are logs and most other times not. I'm trying to get my hands on FSUIPC v4.959 which worked great on my system. You wouldnt happen to have a download link to older versions, would you Pete? 

Share this post


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

Sometimes there are logs and most other times not. I'm trying to get my hands on FSUIPC v4.959 which worked great on my system. You wouldnt happen to have a download link to older versions, would you Pete? 

No, and I'm sure it isn't due to any change between 4.959 and 4.961 in any case. Moreover 4.959 wouldn't be compatible with the current P3D.

Pete

 

Share this post


Link to post
Share on other sites

Hi Pete,

Quick update- got my hands on v4.959 via a fellow pilot at BAV (thank you!) and it appears to be fine for now. I'm running P3D 3.4.18.19475 (haven't installed the latest HF as I don't run SLI GPUs) and v4.959 runs fine, just as it did before the upgrade a couple of days ago.

Might be a quick win for now.

Share this post


Link to post
Share on other sites
4 hours ago, Sumits81 said:

Quick update- got my hands on v4.959 via a fellow pilot at BAV (thank you!) and it appears to be fine for now.

I really need to get to the bottom of this, as I know of n significant difference which would account for this. It would be good if myself or my colleague Thomas could reproduce any such problems ourselves.

Pete

 

Share this post


Link to post
Share on other sites
6 hours ago, Sumits81 said:

Might be a quick win for now.

If I do some experimental backward updates, a section at a time, to the few things which changed between 4.959 and 4.961, would you be willing to test them for me? It's impossible for us as we cannot reproduce the problems.

Just one question first, though. Do you run ANY Lua plug-ins at all? (Including LINDA for instance)? If so, which ones? If you don't then it's an area I can ignore in this backward check.

Pete

 

Share this post


Link to post
Share on other sites

Another question (please also see the previous message). 

Can you try setting this parameter in the FSUIPC4.INI [General], please, and let me know:

CallSimconnectEnd=No

Earlier versions of P3D had a problem with crashes or hangs when closing which occurred when FSUIPC closed its connection. That seemed to have been fixed in 3.4 so I then defaulted it to "Yes", but mayby the more recent version(s) of P3D have re-introduced this bug. 9L-M have never admitted to a bug even though the crash was always deep into P3D code).

I still think making P3D close cleanly at the end of the session is the only way to fix the restart crashes, which are still a complete mystery as none of the software involved is running at the time of those crashes, and there's really nothing changed by reinstalling FSUIPC.

Pete

Share this post


Link to post
Share on other sites
10 hours ago, Pete Dowson said:

If I do some experimental backward updates, a section at a time, to the few things which changed between 4.959 and 4.961, would you be willing to test them for me? It's impossible for us as we cannot reproduce the problems.

Just one question first, though. Do you run ANY Lua plug-ins at all? (Including LINDA for instance)? If so, which ones? If you don't then it's an area I can ignore in this backward check.

Pete

 

Hi Pete,

Yes, sure. I'm happy to help. Will pm you my email address.

I don't use any Lua or Linda scripts at all.

Share this post


Link to post
Share on other sites
2 hours ago, Pete Dowson said:

Another question (please also see the previous message). 

Can you try setting this parameter in the FSUIPC4.INI [General], please, and let me know:

CallSimconnectEnd=No

Earlier versions of P3D had a problem with crashes or hangs when closing which occurred when FSUIPC closed its connection. That seemed to have been fixed in 3.4 so I then defaulted it to "Yes", but mayby the more recent version(s) of P3D have re-introduced this bug. 9L-M have never admitted to a bug even though the crash was always deep into P3D code).

I still think making P3D close cleanly at the end of the session is the only way to fix the restart crashes, which are still a complete mystery as none of the software involved is running at the time of those crashes, and there's really nothing changed by reinstalling FSUIPC.

Pete

OK, will give that a go and let you know. Did you mean trying it with the working v4.959 or shall I reinstall 4.961?

Share this post


Link to post
Share on other sites
1 minute ago, Pete Dowson said:

4.961

 

I've left the 4.961 dll in the modules folder and renamed it to FSUIPC.dll_4.961, after installing 4.959 last night. Do I need to re-run 4.961 installer or will it be enough to just change the name back to .dll?

Share this post


Link to post
Share on other sites
56 minutes ago, Pete Dowson said:

4.961

 

Re-installed v4.961 and added CallSimconnectEnd=No to the .ini file but hasn't made a diff unfortunately. What happens now is P3D launches, I then set up a free flight (PMDG 744 v3) but clicking on FSUIPC under addons doesnt bring up the FSUIPC menus.

Share this post


Link to post
Share on other sites
54 minutes ago, Sumits81 said:

will it be enough to just change the name back to .dll?

Yes. 

The installer only replaces it and checks the DLL.XML and replaces all the documents. It does nothing else at all.

I tend to just rerun the installer. You don't need to re-register in any case, and I just find it faster.

Pete

 

Share this post


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

Yes. 

The installer only replaces it and checks the DLL.XML and replaces all the ocuments. It does nothing else at all.

Pete

 

Thanks Pete. Have just posted my observations a post above yours.

Share this post


Link to post
Share on other sites

Just to add to that- all controls on my X52 pro don't work either as FSUIPC appears to be "unresponsive". Note all my axis and controls are calibrated via FSUIPC.

Share this post


Link to post
Share on other sites
14 minutes ago, Sumits81 said:

Re-installed v4.961 and added CallSimconnectEnd=No to the .ini file but hasn't made a diff unfortunately. What happens now is P3D launches, I then set up a free flight (PMDG 744 v3) but clicking on FSUIPC under addons doesnt bring up the FSUIPC menus.

The CallSimconnectEnd option is only relevant to the close down of the sesion, so that's nothing to do with iyt. something else has changed on your system. If there's no FSUIPC menu then either FSUIPC isn't loading (renamed incorrectly?) or Simconnect has stalled. If there's a log that will show. If there isn't then it isn't being loaded!

4 minutes ago, Sumits81 said:

Just to add to that- all controls on my X52 pro don't work either as FSUIPC appears to be "unresponsive". Note all my axis and controls are calibrated via FSUIPC

Of course, FSUIPC won't work if it isn't actually loaded or if SimConnect has stalled. It cannot work magic! ;-)

Pete

 

Share this post


Link to post
Share on other sites
7 minutes ago, Pete Dowson said:

The CallSimconnectEnd option is only relevant to the close down of the sesion, so that's nothing to do with iyt. something else has changed on your system. If there's no FSUIPC menu then either FSUIPC isn't loading (renamed incorrectly?) or Simconnect has stalled. If there's a log that will show. If there isn't then it isn't being loaded!

Of course, FSUIPC won't work if it isn't actually loaded or if SimConnect has stalled. It cannot work magic! ;-)

Pete

 

Just to clarify- I can see FSUIPC under the addons menu but clicking on it does not bring up the FSUIPC configuration menu. Please see logs from FSUIPC.log:

********* FSUIPC4, Version 4.961 (1st February 2017) by Pete Dowson *********
Windows 10 Enterprise N 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.18.19475
Reading options from "E:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=53930000
User Name=Removed
User Addr=Removed
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       15 System time = 05/02/2017 14:24:00
       15 FLT path = "C:\Users\me\Documents\Prepar3D v3 Files\"
       15 ------ Module Version Check ------
       15        acontain.dll: 3.4.18.19475
       15             api.dll: 3.4.18.19475
       15        controls.dll: 3.4.18.19475
       15      fs-traffic.dll: 3.4.18.19475
       15             G3D.dll: 3.4.18.19475
       15        language.dll: 3.4.18.19475
       15            sim1.dll: 3.4.18.19475
       15        visualfx.dll: 3.4.18.19475
       15         weather.dll: 3.4.18.19475
       15          window.dll: 3.4.18.19475
       15 ----------------------------------
       15 Trying E:\P3D\Modules\SimConnectP3D3.dll
       15 Found it: trying to connect
       31 FS path = "E:\P3D\"
      109 ---------------------- Joystick Device Scan -----------------------
      109 Product= Saitek X52 Pro Flight Control System
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0762 (Version 1.35)
      109    Serial Number= 
      109 -------------------------------------------------------------------
      125 LogOptions=00000000 00000001
      125 -------------------------------------------------------------------
      125 ------ Setting the hooks and direct calls into the simulator ------
      125 --- CONTROLS timer memory location obtained ok
      125 --- SIM1 Frictions access gained
      125 --- FS Controls Table located ok
      125 --- Installed Mouse Macro hooks ok.
      125 --- Wind smoothing fix is installed
      125 --- SimConnect intercept for texts and menus option is off
      125 --- All links okay (except older global weather setting method)
      125 -------------------------------------------------------------------
      125 SimConnect_Open succeeded: waiting to check version okay
      125 Trying to use SimConnect Prepar3D
      125 Opened separate AI Traffic client okay
    11859 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
    11859 Initialising SimConnect data requests now
    11859 FSUIPC Menu entry added
    11875 C:\Users\me\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    11875 E:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    51765 E:\P3D\SimObjects\Airplanes\PMDG 747-400\B747-400_RR.air
    70218 User Aircraft ID 2 supplied, now being used
    71046 System time = 05/02/2017 14:25:11, Simulator time = 14:24:51 (14:24Z)
    71062 Aircraft="PMDG 747-436 British Airways (G-CIVI | 2016)"
    73015 Weather Mode now = Theme
    77078 Starting everything now ...
    77140 ASN active function link set
    77140 Ready for ASN WX radar
   138828 Sim stopped: average frame rate for last 69 secs = 29.3 fps
   138828    Max AI traffic was 0 aircraft
   170109 === NOTE: not calling SimConnect_Close ...
   171109 System time = 05/02/2017 14:26:51, Simulator time = 14:25:58 (14:25Z)
   171109 *** FSUIPC log file being closed
Minimum frame rate was 29.9 fps, Maximum was 32.4 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 69 secs = 29.3 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 

Share this post


Link to post
Share on other sites
23 minutes ago, Sumits81 said:

Just to clarify- I can see FSUIPC under the addons menu but clicking on it does not bring up the FSUIPC configuration menu. Please see logs from FSUIPC.log:

The log is fine and shows FSUIPC is working okay. Sorry, I've never heard of a bug where SimConnect doesn't pass on the menu selection. It isn't a function of FSUIPC, and most definitely not calling simconnect end when you close the system cannot in any way affect anything before you close the session.

I can only think that the window is coming up behind. try using Windowed mode. If that works then it's a video driver problem.

What else have you changed? Something, evidently.

Pete

 

  • Upvote 1

Share this post


Link to post
Share on other sites

Just to clarify something about the P3D startup crash which is the main thing which folks are concerned with.

Some folks are saying it was all okay in version 4.959 and want to go back o that. but if you refer to this thread

http://forum.simflight.com/topic/82599-crash-loading-p3dvhttpforumsimflightcomtopic82599-crash-loading-p3dv34-reporte-fsuipc4dll34-reporte-fsuipc4dll/

you'll see, especially if you skip the first few messages which were different, that it was 4.959 which had the strt-up problems with P3D. It's a long thread with a long list of test releases going from 4.959a to 4.959m. The "m" version seemed to fix it for folks then, and it wasn't long ago. A couple of fixes to prevent LINDA crashing (due to a bug in LINDA now fixed i understand, to version 4.959p, it was relabelled 4.960 and released.

The change between 4.960 and 4.961 was a minor one, to put the OOMcheck into its own thread to prevent a small stutter every 10 seconds when Windows was asked to tot up the memory blocks. It was also announced to support P3D3.4.22 which was released the same day, though in fact 4.960 already was 3.4.22 ready.

So, i cannot revert back to 4.959 level as it will re-introduce the problems which have been fixed with a lot of blood sweat and toil. Well, maybe not blood.

The only conclusion we can reach is that there's more than one cause for the P3D startup problems. I am pretty sure it only occurs if the preceding otherwise good session crashed on exit, or even hung as some have reported,  Identifying what might cause that is the focus of my work on this. it isn't easy because it isn't crashing or hanging withing FSUIPC. As the log shows, FSUIPC is long finished and gone -- unloaded even. So if FSUIPC is causing it, it must be something it did whllst it was still there, even though nothing went wrong during that time.

With the original problems it seemed mostly relating to the way Lua plug-ins were terminating or being killed, so most attention was focussed on that area and I now believe that's a good as it's going to get.

So it's somewhere else.  Since I can't reproduce the problem, and nor can Thomas, I'd like volunteer user testers please, to try experiments and gather information on the resluts. Those willing and able to help and who can definitely reproduce the problem (crash or hand on exit, mainly. There's no way for us, outside L-M, to debug the crash on start). please drop me an email: petedowson@btconnect.com.

I'll post this as new new pinned thread too.

Pete

 

 

  • Upvote 1

Share this post


Link to post
Share on other sites

Thanks Pete. I've been looking around for a pattern of problems and it appears that FSDT also released their new addonmanagerx around the same time as the new FSUIPC. I've also noticed a lot of folks in their forum complaining of similar (if not exactly as mine) issues. In my opinion, I believe there appears to be some clash with FSDT's new files (or the way they write to the xml files) that causes FSUIPC to develop issues with loading in-sim.

I am hoping they rollback their update or provide a new one to eliminate the problem entirely.

I do appreciate you taking the time to look into this. Thank you.

Sumit

Share this post


Link to post
Share on other sites

Hmm. You say it might be FSDT others say it's PMDG 747, I expect others will say they have neither. The only common factor is P3D 3.4 -- and, mostly, Win 10, though that's only from what i've seen reported. Oh, and FSUIPC.

Pete

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • 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.