Jump to content
The simFlight Network Forums

Can anyone tell what the two lines 46488 mean?

Recommended Posts

Sorry about asking, and yes I like to look at my log.  I highlighted them in black.

Thank you.


Can anyone tell me why I'm getting these error messages in the FSUIPC log?
I have no idea what they mean.

********* FSUIPC4, Version 4.955 (1st June 2016) by Pete Dowson *********
Prepar3D.exe version =
Reading options from "G:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=5D880000
User Name="xxxxxx"
User Addr="xxxxxx"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
16 System time = 12/07/2016 13:07:44
16 FLT path = "C:\Users\Jetline\Documents\Prepar3D v3 Files\"
16 ------ Module Version Check ------
16 acontain.dll:
16 api.dll:
16 controls.dll:
16 fs-traffic.dll:
16 G3D.dll:
16 language.dll:
16 sim1.dll:
16 visualfx.dll:
16 weather.dll:
16 window.dll:
16 ----------------------------------
16 Trying G:\P3D\Modules\SimConnectP3D3.dll
16 Found it: trying to connect
16 FS path = "G:\P3D\"
125 ---------------------- Joystick Device Scan -----------------------
125 Product= Saitek Pro Flight Rudder Pedals
125 Manufacturer= Saitek
125 Vendor=06A3, Product=0763 (Version 1.1)
140 Serial Number= 
140 Product= Pro Flight TPM System
140 Manufacturer= Mad Catz
140 Vendor=06A3, Product=0B4D (Version 1.98)
140 Serial Number= G0007131
140 Product= Saitek Pro Flight Yoke
140 Manufacturer= Saitek
140 Vendor=06A3, Product=0BAC (Version 3.4)
140 Serial Number= 
140 Product= Saitek Pro Flight Quadrant
140 Manufacturer= Saitek
140 Vendor=06A3, Product=0C2D (Version 2.0)
156 Serial Number= 
156 -------------------------------------------------------------------
156 LogOptions=00000000 00000011
156 -------------------------------------------------------------------
156 ------ Setting the hooks and direct calls into the simulator ------
156 --- CONTROLS timer memory location obtained ok
156 --- SIM1 Frictions access gained
156 --- FS Controls Table located ok
156 --- Installed Mouse Macro hooks ok.
156 --- Wind smoothing fix is installed
156 --- All links okay (except older global weather setting method)
156 -------------------------------------------------------------------
156 SimConnect_Open succeeded: waiting to check version okay
156 Trying to use SimConnect Prepar3D
4727 Running in "Lockheed Martin� Prepar3D� v3", Version: (SimConnect:
4727 Initialising SimConnect data requests now
4727 FSUIPC Menu entry added
4743 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
4743 C:\Users\Jetline\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
4743 G:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
4899 Memory in use: 857Mb, Avail=3239Mb
19391 G:\P3D\SimObjects\Airplanes\Carenado Aero_Commander_500S\500S.air
44632 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
45490 System time = 12/07/2016 13:08:29, Simulator time = 13:07:49 (18:07Z)
45490 Aircraft="Carenado 500S Aero Commander N786E"
46488 Starting everything now ...
46488 Note: "G:\P3D\Modules\PFCFSX.DLL", Error 126 (The specified module could not be found. )
46488 Note: "G:\P3D\Modules\EPICINFO5.DLL", Error 126 (The specified module could not be found. )

46504 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
46535 Run: "C:/Program Files (x86)/NaturalPoint/TrackIR5/TrackIR5.exe"
46551 ASN active function link set
46551 Ready for ASN WX radar
46598 Deactivated for PID=3448, "TrackIR5.exe"
46598 Lost focus to PID=3448, "TrackIR5.exe"
47830 Advanced Weather Interface Enabled
62744 Deactivated: culprit unknown
62744 Focus lost: culprit unknown
65193 Memory in use: 2093Mb, Avail=2003Mb
80980 Weather Mode now = Theme
125487 Memory in use: 2094Mb, Avail=2002Mb
185688 Memory in use: 2178Mb, Avail=1918Mb
245936 Memory in use: 2206Mb, Avail=1890Mb
279944 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
279944 Sim stopped: average frame rate for last 235 secs = 59.4 fps
279944 Max AI traffic was 68 aircraft
312517 === NOTE: not calling SimConnect_Close ...
313515 System time = 12/07/2016 13:12:57, Simulator time = 13:11:43 (18:11Z)
313515 *** FSUIPC log file being closed
Minimum frame rate was 45.7 fps, Maximum was 64.8 fps
Minimum available memory recorded was 1887Mb
Average frame rate for running time of 235 secs = 59.4 fps
Maximum AI traffic for session was 68 aircraft
Memory managed: 106 Allocs, 106 Freed
********* FSUIPC Log file closed ***********

Link to comment
Share on other sites

As Mario says, the meaning is there in the message, where it says the DLLs which it would load if they were there are not there (that's why they are "not found", as it says), so they won't be loaded! :-)

You have "EXTRAS" logging enabled in the Logging tab, so you get extra information logged telling you things you may or may not wish to know -- and in this case, they are not in ant sort of mysterious code form, but in English and surely self-explanatory?



Link to comment
Share on other sites

Thanks Pete, for you they may be self explanatory but I'm a pilot not a programmer.  I like to look at these things every once in a while and when I see error I wonder if there's a problem.

I have no idea what these dll files are, what they do, or even what a dll is.

I did a search on my PC and found none of them.  Why did they suddenly show up?


Link to comment
Share on other sites

2 hours ago, PHII33 said:

Why did they suddenly show up?

Oh, I thought I told you that? .... It is because you enabled Extras logging. That adds quite a lot more information to the log, and data such as why a couple of extra optional hardware drivers (other programs of mine) did not load would be useful to someone who needs to use them because of the specific hardware they are using with FS. 

PFCFSX is my driver for the serial port PFC devices, made by PFC in Sacramento, and the EpicLink one is for EPIC based devices including those made by FlightLink. EPIC is, or was maybe, an interface card system for inputs and outputs, much like you might have a driver for Saitek and GoFlight devices.

And you surely don't need to be a programmer to understand words like "could not be found"? And as for not knowing what a "DLL" is: well, FSUIPC is one of those but you appear to be using it. So you don't need to know to use them, obviously!

If you don't understand logging, why are you looking at the file? It is mainly produced to help me help folks with problems. What problems exactly do you have with FSUIPC? Why not post about those instead?



Link to comment
Share on other sites

Hi Pete, not one problem with FSUIPC.  Sorry mate, just a very curious type.  I'm trying to learn but it's a slog.

I really appreciate you explaining what those devices are, that helps a lot.

Like I said, just curious.


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.