FSUIPC5.log File Missing "Reading Options from"

[Glenn Weston]

Hello Pete,

I Finally made the move to P3D V4.1 and purchased FSUIPC5.

All went fairly well, and thankyou for your continued support.

I just have noticed a small issue that is not a show stopper but it is something I refer to with one of my Lua Scripts to get the Modules folder location of the currently running FSUIPC.

In Version 4 of FSUIPC the FSUIPC4.log contained the lines:

********* FSUIPC4, Version 4.947c by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.ini"
Running inside Prepar3D v2 on Windows 7
Module base=649C0000

In Version5 of FSUIPC the FSUIPC5.log file looks like this:

********* FSUIPC5, Version 5.122 (17th November 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FEDB840000

As you can see the "Reading options" line is missing in the Version 5 Log file.

I just wanted to point it out to you and hopefully ask for you too put it back in the log file on the next iteration of FSUIPC5.

Thanks Pete

 

Regards Glenn.

 

[Thomas Richter]

Hi,

why trying to read the FSUIPC location from the logfile that is located in that folder? Also the FS location is given some lines later in the logfile, just add \Modules.

Quote

FSUIPC5 Key is provided
WideFS7 Key is provided
       78 System time = 02/01/2018 00:30:55
       78 FLT UNC path = "C:\Users\TSR\Documents\Prepar3D v4 Files\"
       78 ------ Module Version Check ------
       78        acontain.dll: 4.1.7.22841
       78             api.dll: 4.1.7.22841
       78        controls.dll: 4.1.7.22841
       78      fs-traffic.dll: 4.1.7.22841
       78             G3D.dll: 4.1.7.22841
       93        language.dll: 4.1.7.22841
       93            sim1.dll: 4.1.7.22841
       93        visualfx.dll: 4.1.7.22841
       93         weather.dll: 4.1.7.22841
       93          window.dll: 4.1.7.22841
       93 ----------------------------------
      172 FS UNC path = "F:\FS\Prepar3D v4\"
      312 ---------------------- Joystick Device Scan -----------------------

The usual way is to check Offset 0x3E00

Quote

3E00, 256, Path of the Flight Simulator installation, . . .

Thomas

[Pete Dowson]

12 hours ago, Glenn Weston said:

As you can see the "Reading options" line is missing in the Version 5 Log file.

I just wanted to point it out to you and hopefully ask for you too put it back in the log file on the next iteration of FSUIPC5.

I'll take a look. The original reason it was added was because FSUIPC3 and 4 allowed different configurations, which involved renaming the FS EXE and the KEY file, which made FSUIPC read a similarly differently named INI file and FS to use a similarly renamed CFG file.

Such an elaboration was not only not needed once Profiles were introduced, but was also rather incompatible with the way things were going with all the ancillary files and other addons needing to retain normal naming.

However, if the message still has a use I'll certainly add it back.

Pete

 

[Glenn Weston]

Thankyou for the consideration Pete.

I could certainly also go about it differently looking at Thomas' suggestions.

I would just have modify my scripts to do that, so if it is a major issue I can always modify my side.

Cheers Glenn.

[Pete Dowson]

2 hours ago, Glenn Weston said:

I would just have modify my scripts to do that, so if it is a major issue I can always modify my side.

Ah, I'd missed that point that you were reading parts of the Log file to get information! That is never a good idea at all. The log file is, well, a log, to enable problems to be diagnosed and fixed. It is always liable to change. Much better to use the provisions made for you to get the exact information you want, reliably!

Meanwhile, I checked into what happened to that message, and it was an error that it 'disappeared'. The order of some initialisation code was changed resulting in the message being output before the log was actually created! It will be fixed in the next version, but i'd still prefer you to use the proper provisions for such things.

Is there anything else you get from the Log file? If it is something you found no other source for, I would rather look at adding it someplace legitimate.

Pete

 

[Glenn Weston]

No that is the only thing that I read from the log file.

It was just a quick and dirty way for me to find the full path to the modules folder.

Regards Glenn.