Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello everybody,

 

First, sorry for my english but i hope i can tell you my problem.

In last Time, after i have a 16 Hours flight with my FSX, i have a FSUIPC4.log textfile there is 24GB. After newstart from FSX, there is 3KB and allready is fine but after runnig a Longhaul flight it is a big Problem. 

 

I dont see any option to turn off this problem in FSUIPC. Anybody can help me?

 

Greez

 

Tobi

Posted
12 minutes ago, AAsergeantKK said:

In last Time, after i have a 16 Hours flight with my FSX, i have a FSUIPC4.log textfile there is 24GB. After newstart from FSX, there is 3KB and allready is fine but after runnig a Longhaul flight it is a big Problem. 

Without logging options set the Log is very small indeed.

Can you paste a bit of this log here, please, so I can see what sort of stuff is being logged?

I have one other report, and I am fairly sure it is due to one add-on which is interfacing to FSUIPC and enabling logging of things like the interface (IPC) reads and writes, which ofr a busy add-on using FSUIPC can amount to very many lines indeed.

Please also list all the add-ons you are running, including those on any WideFS client PC, as I might then be able to spot one in common with the other report.

Pete

 

Posted (edited)

Hello Pete,

 

here is a Entry after FSX is Running 5 Minutes. 

All Addons run before verry fine and from one day to the next i have this problem.

Addon there are Running:

PFPX

FS real Time

CAAS (VA Tracker)

EFASS

ASN

Ivao Ivap

 

EDIT:

Forgot the Entry hehe

 

      327 System time = 18/05/2016 19:37:29
      327 FLT path = "C:\Users\AB\Documents\Flight Simulator X-Dateien\"
      327 ------ Module Version Check ------
      327        acontain.dll: 10.0.61637.0
      327             api.dll: 10.0.61637.0
      327        controls.dll: 10.0.61637.0
      327      fs-traffic.dll: 10.0.61637.0
      327             G3D.dll: 10.0.61637.0
      327        language.dll: 10.0.61637.0
      327            sim1.dll: 10.0.61637.0
      327        visualfx.dll: 10.0.61637.0
      327         weather.dll: 10.0.61637.0
      327          window.dll: 10.0.61637.0
      327 ----------------------------------
      374 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      374 FS path = "E:\FSX\"
      530 ---------------------- Joystick Device Scan -----------------------
      530 Product= Saitek X52 Flight Control System
      530    Manufacturer= Saitek
      530    Vendor=06A3, Product=075C (Version 1.16)
      546    Serial Number= 
      546 Product= Saitek Pro Flight Rudder Pedals
      546    Manufacturer= Saitek
      546    Vendor=06A3, Product=0763 (Version 1.0)
      546    Serial Number= 
      546 -------------------------------------------------------------------
      561 Run: "C:\Program Files (x86)\HiFi\ASNext_FSX\ASNext.exe"
      655 Run: "C:\Program Files (x86)\FS Real Time\FSRealTime.exe"
      702 Run: "C:\Users\AB\Documents\FS Products\CAAS\kACARS - ColoniaAir.exe"
      795 Run: "C:\Programs\EFASS - Electronic Flight Assistant\EFASS.exe"
     1263 LogOptions=00000000 00000009
     1263 -------------------------------------------------------------------
     1263 ------ Setting the hooks and direct calls into the simulator ------
     1263 --- CONTROLS timer memory location obtained ok
     1263 --- SIM1 Frictions access gained
     1263 ASN active function link set
     1263 --- FS Controls Table located ok
     1263 --- Installed Mouse Macro hooks ok.
     1263 Wind smoothing may be by ASN, not FSUIPC, if it is running
     1263 Will switch smoothing action when ASN starts/stops
     1263 --- G3D.DLL fix attempt installed ok
     1263 --- All links checked okay
     1263 -------------------------------------------------------------------
     1279 SimConnect_Open succeeded: waiting to check version okay
     1279 Trying to use SimConnect Acc/SP2 Oct07
     1279 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     1279 Initialising SimConnect data requests now
     1279 FSUIPC Menu entry added
     1326 E:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     1326 E:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
   281285 System time = 18/05/2016 19:42:10, Simulator time = 03:37:24 (02:37Z)
   281285 Aircraft="Aircreation582SL red"
   283110 Weather Mode now = Theme
   283266 Starting everything now ...
   283266 LUA.0: beginning "E:\FSX\Modules\ipcReady.lua"
   283329 Ready for ASN WX radar
   283391 AES Link established
   315137 Sim stopped: average frame rate for last 34 secs = 16.0 fps
   315137              Max AI traffic was 0 aircraft
   316994 Advanced Weather Interface Enabled
   391625 Sim stopped: average frame rate for last 76 secs = 29.8 fps
   391625              Max AI traffic was 0 aircraft
   401968 LogOptions changed, now 00000000 00000001
   442855 System time = 18/05/2016 19:44:51, Simulator time = 03:38:52 (02:38Z)
   442855 *** FSUIPC log file being closed
Minimum frame rate was 11.2 fps, Maximum was 30.0 fps
Minimum available memory recorded was 2301Mb
Average frame rate for running time of 123 secs = 25.9 fps
G3D fix: Passes 20253, Null pointers 0, Bad pointers 0, Separate instances 0
Maximum AI traffic for session was 0 aircraft
Memory managed: 49 Allocs, 49 Freed
********* FSUIPC Log file closed ***********

Edited by AAsergeantKK
Posted
17 minutes ago, AAsergeantKK said:

here is a Entry after FSX is Running 5 Minutes. 

That only contains normal entries.  And for some reason you've dleeted the top few lines which are most important, as they tell me about versions!

Anyway, there is nothing there which will ever possibly amount to 24Gb, no matter how long you run it! I need to see some of the extra logging which may be occurring. Please don't delete the top few lines next time!

Quote

Addon there are Running:

PFPX

FS real Time

CAAS (VA Tracker)

EFASS

ASN

Ivao Ivap

Of those only CAAS and EFASS might be doing it. Can you try without them and let me know? And what about

kACARS - ColoniaAir.exe

which you seem to be starting in FSUIPC4INI?

Pete

Posted

Hey,

okey i will run the FSX for longer Time tomorrow. 

KaCars is the CAAS (the VA tracker from Colonia Air)

Only i wonder how is the problem now after i run the system 1 year without problems.

Posted
1 minute ago, AAsergeantKK said:

KaCars is the CAAS (the VA tracker from Colonia Air)

Does that use FSUIPC?

Quote

Only i wonder how is the problem now after i run the system 1 year without problems.

What have you changed recently?

Pete

 

Posted
Quote

No, for Sure...

So, a one-year old version of FSUIPC? I can't tell the version number you are using because you deleted the first few lines. Current version is 4.953.

Quote

at this time how i have this problem, the fsx dont shutting down correctly. i almost must shutdown about taskmanager

So, with nothing whatsoever changing, you have all these sudden problems?

Only hardware faults or file corruption can do that sort of thing. Unchanged software doesn't change the way it behaves on its own.

Pete

 

Posted

Do you have any hardware drivers which may use FSUIPC? I've just been reliably informed, for example, that the Flight Deck Solutions drivers write to offset 3400 in FSUIPC, which is the array of bits enabling assorted logging options.

Maybe other software writes there too, probably by mistake.

Pete

 

Posted

Please update to FSUIPC version 4.954, now available in the Download Links sub-forum. This blocks program changes to the logging, by default. (Install 4.053 first if not already done).

Pete

 

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.