Jump to content

FSUIPC4.104 logging on its own...


Recommended Posts

Hi pete.

I just happened to notice yesterday that my FSUIPC4.log file was on

the large size and opened it up to find that it is logging events, even

though I do not have logging enabled.

I searched through the INI file and couldfind nothing in there that

was related to turning logging on and in the drop-down menu in FSX

logging is not enables. I did enabled it and then disabled it to see

if the "toggle" would cure the problem but it did not.

Here's the first few entries when I started flight:

********* FSUIPC4, Version 4.104 by Pete Dowson *********

User Name="............."

User Addr="...................."

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX (SimConnect SP1 May07)

Module base=61000000

DebugStatus=15

78 System time = 12:55:18

78 FLT UNC path = "\\BOHEMIA\Cerna Hora\Documents and Settings\GB\My Documents\Flight Simulator X Files\"

78 FS UNC path = "K:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

2515 LogOptions=00000001

2515 SimConnect_Open succeeded: waiting to check version okay

13625 Running in "Microsoft Flight Simulator X", Version: 10.0.61355.0 (SimConnect: 10.0.61242.0)

33047 SimStart Event: Initialising SimConnect data requests

33047 FSUIPC Menu entry added

34437 C:\Documents and Settings\GB\Application Data\Microsoft\FSX\Previous flight.FLT

34437 C:\Documents and Settings\GB\My Documents\Flight Simulator X Files\IFR Greater Rochester Intl to Buffalo Niagara Intl.PLN

34437 K:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\beech_baron_58\Beech_Baron_58.AIR

34437 C:\Documents and Settings\GB\My Documents\Flight Simulator X Files\IFR Greater Rochester Intl to Buffalo Niagara Intl.PLN

35219 SimRead: 0BB6="AILERON POSITION"

FLT64: 0

35219 System time = 12:55:53, FSX time = 13:55:32 (11:55Z)

35422 Aircraft="Beech Baron 58 w G1000"

130047 SimRead: 0BB6="AILERON POSITION"

FLT64: -0.0148315429688

130797 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0713500976563

----------------------------

Here's the first few entries after I enabled logging, selected "New Log"

and then disabled logging:

********* FSUIPC4, Version 4.104 by Pete Dowson *********

User Name="............."

User Addr="...................."

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

[Continuation log requested by user]

Running inside FSX (SimConnect SP1 May07)

Module base=61000000

1338578 System time = 13:17:37, FSX time = 13:55:53 (11:55Z)

1338781 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.025146484375

1338922 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0228881835938

1339265 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0198974609375

1339406 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0264892578125

1339562 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0248413085938

1339703 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.020263671875

1339890 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0310668945313

I'm running FSX SP1. I've not had an occasion to look at the log file

for some time so I can't say when this problem started.

Paul

Link to comment
Share on other sites

I searched through the INI file and couldfind nothing in there that

was related to turning logging on and in the drop-down menu in FSX

logging is not enables.

Let me see the INI file -- looks like a Monitor entry is there, or possibly a LogExtras.

Here's the first few entries after I enabled logging, selected "New Log" and then disabled logging:

There's no such thing as "disabling logging". FSUIPC always creates a log. It will log certain things always. However, certainly these:

1338781 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.025146484375

1338922 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0228881835938

1339265 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0198974609375

1339406 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0264892578125

1339562 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0248413085938

1339703 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.020263671875

1339890 SimRead: 0BB6="AILERON POSITION"

FLT64: 0.0310668945313

should only appear if there's a LogsimC or Monitor entry for 0BB6, or a specific LogExtras value set, introduced (temporarily, for 4.104 only, to debug one user's specific problem which turned out not to be a problem anyway).

I need to see the INI.

Regards

Pete

Link to comment
Share on other sites

Okay, never mind about the INI file -- I've reproduced the case where it is logging the Aileron changes notified from SimConnect. I'll fix it in ther next increment (4.105, or maybe 4.11), within the next few days. Thanks for letting me know.

Regards

Pete

Link to comment
Share on other sites

Okay, never mind about the INI file -- I've reproduced the case where it is logging the Aileron changes notified from SimConnect. I'll fix it in ther next increment (4.105, or maybe 4.11), within the next few days. Thanks for letting me know.

Regards

Pete

Thanks Pete. What I meant by turning off logging was the logging

of events feature where the types of events to be inclucded in the

log can be selected via the menu. ( The one that you caution about

using too much as the log file grows rapidly) :)

Paul

Link to comment
Share on other sites

What I meant by turning off logging was the logging

of events feature where the types of events to be inclucded in the

log can be selected via the menu. ( The one that you caution about

using too much as the log file grows rapidly) :)

Oh, yes. Okay. Anyway, the problem is fixed in 4.11. Thanks for reporting it in time! ;-)

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
 Share

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