Jump to content
The simFlight Network Forums

FSUIPC4 causes P3D to fail after multiple axes assigned


Recommended Posts

This took me ages to diagnose, but here goes.

If I assign only a couple of controller axes to be controlled by FSUIPC4, everything runs fine. It doesn't matter whether those axes belong to separate devices or the same one. All is good at this point.

Once I assign half a dozen or so, then I can no longer load P3D. The point at which I would normally expect it to open the Scenario Setup page it instead just goes to a blacked out desktop and nothing else. There's no actual CTD, rather the process just hangs as a background process occupying @250MB of RAM which I have to kill manually after Alt-Tabbing away from the black screen.

At this point, the only way I can load P3D again is to manually delete FSUIPC4 from \Modules. Deleting just the .ini file doesn't do it. Then when I install FUSIPC4 again, it all works fine until I once again configure too many axes, at which point I once again only get access to my sim again by deleting it.

 

Here's a paste of my log file (minus my personal details):

********* FSUIPC4, Version 4.959 (19th December 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
Prepar3D.exe version = 3.4.14.18870
Reading options from "D:\GAMES\Other Installed Games\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 8.0 or later
Module base=18170000
User Name= [REMOVED]
User Addr= [REMOVED]
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
      250 System time = 30/12/2016 16:42:39
      250 FLT path = "C:\Users\Luke\Documents\Prepar3D v3 Files\"
      250 ------ Module Version Check ------
      250        acontain.dll: 3.4.14.18870
      250             api.dll: 3.4.14.18870
      250        controls.dll: 3.4.14.18870
      250      fs-traffic.dll: 3.4.14.18870
      250             G3D.dll: 3.4.14.18870
      250        language.dll: 3.4.14.18870
      250            sim1.dll: 3.4.14.18870
      250        visualfx.dll: 3.4.14.18870
      250         weather.dll: 3.4.14.18870
      250          window.dll: 3.4.14.18870
      250 ----------------------------------
      250 Trying D:\GAMES\Other Installed Games\Prepar3D v3\Modules\SimConnectP3D3.dll
      250 Found it: trying to connect
      250 FS path = "D:\GAMES\Other Installed Games\Prepar3D v3\"
      407 ---------------------- Joystick Device Scan -----------------------
      407 Product= Saitek Pro Flight Combat Rudder Pedals
      407    Manufacturer= Saitek
      407    Vendor=06A3, Product=0764 (Version 2.1)
      407    Serial Number= Saitek
      407 Product= Throttle - HOTAS Warthog
      407    Manufacturer= Thrustmaster
      407    Vendor=044F, Product=0404 (Version 1.0)
      407    Serial Number= Thrustmaster
      407 Product= Joystick - HOTAS Warthog
      407    Manufacturer= Thustmaster
      407    Vendor=044F, Product=0402 (Version 1.0)
      407    Serial Number= Thustmaster
      407 Product= Pro Flight Cessna Trim Wheel
      407    Manufacturer= Saitek
      407    Vendor=06A3, Product=0BD4 (Version 1.7)
      407    Serial Number= RD000360
      407 -------------------------------------------------------------------
      422 LogOptions=00000000 00000001
      422 -------------------------------------------------------------------
      422 ------ Setting the hooks and direct calls into the simulator ------
      422 --- CONTROLS timer memory location obtained ok
      422 --- SIM1 Frictions access gained
      422 --- FS Controls Table located ok
      422 --- Installed Mouse Macro hooks ok.
      422 --- Wind smoothing fix is installed
      422 --- SimConnect intercept for texts and menus option is off
      422 --- All links okay (except older global weather setting method)
      422 -------------------------------------------------------------------
      422 SimConnect_Open succeeded: waiting to check version okay
      422 Trying to use SimConnect Prepar3D
      422 Opened separate AI Traffic client okay
     9110 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.14.18870 (SimConnect: 3.4.0.0)
     9110 Initialising SimConnect data requests now
     9110 FSUIPC Menu entry added
     9141 C:\Users\Luke\Documents\Prepar3D v3 Files\default scenario.fxml
     9141 D:\GAMES\Other Installed Games\Prepar3D v3\SimObjects\Airplanes\C172\Cessna172SP.air
   174594 User Aircraft ID 2 supplied, now being used
   175094 System time = 30/12/2016 16:45:34, Simulator time = 08:00:00 (15:00Z)
   175094 Aircraft="Cessna Skyhawk 172SP Paint1"
   181110 Starting everything now ...
   181110 LUA.0: beginning "D:\GAMES\Other Installed Games\Prepar3D v3\Modules\ipcReady.lua"
   181110 LUA.0: ended "D:\GAMES\Other Installed Games\Prepar3D v3\Modules\ipcReady.lua"
   181141 LUA.1:  *************************** STARTING LINDA **************************
   181141 LUA.1: LINDA:: [START] Loading System Configuration files
   181141 LUA.1: LINDA:: [START] WARNING - All LUA logging switched off !!!
   181141 LUA.1: LINDA:: [START] Go to Setup LINDA to switch on (if required)
   181157 LUA.1: LINDA:: *********************************************************************
   181157 ASN active function link set
   181157 Ready for ASN WX radar
   181172 LUA.1: LINDA:: [START] System Configuration files loaded
   186594 Weather Mode now = Theme
   191547 Advanced Weather Interface Enabled
   328094 === Calling SimConnect_Close ...
   328297 === SimConnect_Close done!
   329297 System time = 30/12/2016 16:48:08, Simulator time = 08:00:22 (15:00Z)
   329297 *** FSUIPC log file being closed
Minimum frame rate was 11.8 fps, Maximum was 30.0 fps
Minimum available memory recorded was 1601Mb
Average frame rate for running time of 41 secs = 24.7 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 78 Allocs, 74 Freed
********* FSUIPC Log file closed ***********

 

Link to comment
Share on other sites

Before I did anything with FSUIPC, I deselected "enable controller(s)" in P3D settings, and it remains so.

enable.jpg

 

I ran some tests with and without Linda.

 

1. Removed Linda. Fresh install of FSUIPC4. Started sim. Assigned multiple axes.

2. Restarted sim, started okay.

3. Re-added Linda. Restarted sim. Again, started okay. Assigned another axis.

4. Attempted to restart sim. Problem recurred. Unable to start the sim.

5. Removed Linda again. Attempted to restart sim. Problem recurred. Unable to start the sim.

6. Removed FSUIPC4 again. Sim started okay.

 

I'll have to quit and restart the sim multiple times without Linda to ensure that it does have some involvement in the problem. But once it starts, the only thing that fixes it is removing FSUIPC. The problem is very much tied to FSUIPC4.dll.

I can't run any more tests today, but I will run more tomorrow.

Link to comment
Share on other sites

On 12/30/2016 at 6:08 AM, paralipsis said:

Here's a paste of my log file (minus my personal details):

That log only shows a successful run with FSUIPC closing normally.

What do you mean by "too many axes"? 1, 2, 3 ... 64?

Are you sure it isn't just one specific controller who's driver is hanging? Try to isolate which action actually causes the problem.

And please, when supplying a Log file, show the one applicable to the problem being reported.

Pete

 

Link to comment
Share on other sites

On 1/6/2017 at 1:23 AM, Pete Dowson said:

That log only shows a successful run with FSUIPC closing normally.

What do you mean by "too many axes"? 1, 2, 3 ... 64?

Are you sure it isn't just one specific controller who's driver is hanging? Try to isolate which action actually causes the problem.

And please, when supplying a Log file, show the one applicable to the problem being reported.

Pete

 

It's very hard to pin down the exact number. At the moment I am trying to determine if keeping Linda off my P3D install prevents the issue from happening. I think it's working. The problem being that I can't nail down the exact trigger for the onset of the issue. Once it starts happening, it happens 100% unless I reinstall FSUIPC, but at least for now, I'm still stuck in a situation where I cannot reliably nail down what causes it to start, and thus I'm still just trying to work out if I am stable for now or not. In the next day or two I plan to backup FSUIPC with what settings I have managed to apply so far, and then reintroduce Linda back into my \Modules folder and see if that brings the problem back or not.

For now it seems like Linda may be the root cause of the problem, but the problem itself seems to get rooted in something FSUIPC writes to itself when I apply settings while Linda is running. But proving that is slow and uncertain.

 

Also, I can only attach the log file I have. If FSUIPC doesn't rewrite to the file once the problem starts happening, there's not much I can do at my end to fix that.

Edited by paralipsis
Link to comment
Share on other sites

5 hours ago, paralipsis said:

the problem itself seems to get rooted in something FSUIPC writes to itself

"Writes to itself". Sorry, what is that supposed to mean? How do you derive that?

5 hours ago, paralipsis said:

Also, I can only attach the log file I have. If FSUIPC doesn't rewrite to the file once the problem starts happening, there's not much I can do at my end to fix that.

If no log is being produced then FSUIPC isn't starting. This is therefore the same as that reported in other threads near here -- 

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

('t know how that title got screwed up) and

FSUIPC Causes P3D Failure

Some do talk about LINDA's involvement. Perhaps you should look at those too? They are being actively investigated.

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.