Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello,

I registered and installed FSUIPC 4.70b a couple weeks ago. At that time, I set some initial FSUIPC settings through the Add Ons menu in FSX. However, since that time, I have installed the Level-D 767, REX, and Ultimate Traffic 2. I have been working on getting FSX "tweaked" per some suggestions over at AVSIM. I was going to try and limit the maximum visibilty with FSUIPC, but when I went to do this today, FSUIPC had "disappeared" from the Add Ons menu. The Ultimate Traffic 2 menu is there. Here are my pertinent system specs:

Intel i7 2600K OC'ed to 4.6GHz

4x2 GB Corsair Vengeance 1600 RAM

128 Crucial C300 SSD (for OS and FSX)

500GB Seagate Barracuda for other programs/backup

EVGA GTX560 1024 DDR5 (with latest drivers as of 6/7/11)

Windows 7 Pro x64

I'm kind of at a loss. I've been a FSimmer since FS98 and spent most of my time with FS9 and have never seen a version of FS that is so finicky. Anyway, I've searched this forum and seen that you most definitely will want my FSUIPC.log file; I have added the text of the FSUIPC4.log to this post, the forum is not letting me add it as an attachment. The strange thing about the log file is it lists the current system time/date as 22/06/2011 14:42:06 even though the last time I started the sim was about 30 minutes ago (02/07/2011 16:12) The following files are present in my Modules folder:

FSUIPC Documents <DIR>

FSUIPC4 Install.log

FSUIPC4.dll

FSUIPC4.cfg

FSUIPC4.key

FSUIPC4.log

LVLD.dll

LVLD.DLL_for_SimConnect_1.zip

Let me know what you think. Thanks!

Adam

********* FSUIPC4, Version 4.70b by Pete Dowson *********

Reading options from "C:\FSX\Modules\FSUIPC4.ini"

Trying to connect to SimConnect Acc/SP2 Oct07 ...

User Name="Adam xxxxxx (privacy)...the actual file has my correct full name"

User Addr="I REMOVED THIS LINE for privacy, but the actual file has my correct email addy"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

Running inside FSX on Windows 7 (using SimConnect Acc/SP2 Oct07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=15

437 System time = 22/06/2011 14:42:06

437 FLT path = "C:\Users\Adam\Documents\Flight Simulator X Files\"

437 FS path = "C:\FSX\"

811 LogOptions=00000000 00000001

827 SimConnect_Open succeeded: waiting to check version okay

2465 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

2465 Initialising SimConnect data requests now

2465 FSUIPC Menu entry added

2480 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

2480 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

19126 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

57783 System time = 22/06/2011 14:43:03, Simulator time = 14:42:09 (21:42Z)

57783 Aircraft="Aircreation582SL red"

58188 Starting everything now ...

59280 Advanced Weather Interface Enabled

624768 Sim stopped: average frame rate for last 567 secs = 58.3 fps

698526 Sim stopped: average frame rate for last 72 secs = 55.3 fps

704204 System time = 22/06/2011 14:53:50, Simulator time = 14:47:55 (21:47Z)

704204 *** FSUIPC log file being closed

Average frame rate for running time of 639 secs = 58.0 fps

Memory managed: 285 Allocs, 285 Freed

********* FSUIPC Log file closed ***********

Posted

I registered and installed FSUIPC 4.70b a couple weeks ago. At that time, I set some initial FSUIPC settings through the Add Ons menu in FSX. However, since that time, I have installed the Level-D 767, REX, and Ultimate Traffic 2. I have been working on getting FSX "tweaked" per some suggestions over at AVSIM. I was going to try and limit the maximum visibilty with FSUIPC

You should really do that in your weather program.

but when I went to do this today, FSUIPC had "disappeared" from the Add Ons menu. The Ultimate Traffic 2 menu is there.

Seems that the DLL.XML file has been destroyed or corrupted by something you installed. Not UT2 which is loaded via the EXE.XML file.

I'm kind of at a loss. I've been a FSimmer since FS98 and spent most of my time with FS9 and have never seen a version of FS that is so finicky.

It is more complex, but i don't think "finicky". The problems tend to arise from bad installers which mess crucial files up.

Anyway, I've searched this forum and seen that you most definitely will want my FSUIPC.log file; I have added the text of the FSUIPC4.log to this post, the forum is not letting me add it as an attachment.

Pasting is the best way anyway.

The strange thing about the log file is it lists the current system time/date as 22/06/2011 14:42:06 even though the last time I started the sim was about 30 minutes ago (02/07/2011 16:12)

It certainly sounds like that was the last time FSUIPC4 was actually loaded and run, then, because it will create a new log file each time. Either that or the date and time of your PC are set incorrectly.

Of these:

FSUIPC Documents <DIR>

FSUIPC4 Install.log

FSUIPC4.dll

FSUIPC4.cfg

FSUIPC4.key

FSUIPC4.log

There's no such thing as "FSUIPC4.CFG". Don't you mean "FSUIPC4.INI"? That contains all your FSUIPC4 settings.

Anyway, the log file shows everything was okay. All that is hapening now is that FSUIPC4 (and probably that LVLD.DLL) aren't being loaded, because the DLL.XML file is either deleted or corrupted.

If you know where to find your FSX.CFG file, look in the same folder. You will see the EXE.XML file, which must be there as it loads UT2, and maybe a DLL.XML file. Rename or move the latter, so you don't lose it, and then re-run the FSUIPC4 Installer. It will make a new DLL.XML file. Run FSX and FSUIPC4 will run okay. But now any other DLL's you may have installed will not. So, paste the DLL.XML file you renamed or saved here so I can see what is wrong and help you fix it. Despite the filetype of XML it is an ordinary text file.

If you don't know where to look for these files, paste the FSUIPC4 Install log here and I will tell you, as it will be logged therein.

Regards

Pete

Posted (edited)

Pete,

Thanks a lot for the help! I really appreciate it. Yeah, that file is certainly FSUIPC4.ini...I'm new-ish to Windows 7 after my new build and have yet to have Windows display the full filename. I did not know that dll.xml could be removed and the FSUIPC installer would create a new one. I will try that out and let you know.

Thanks again, I'm very new to FSX after finally building a capable PC. After being a proficient FS9 user, it's funny feeling like such a newbie again! Strange as it sounds, it took me a bit to even find where the "Aircraft" folder is to manually edit callsigns in UT2. I do know where dll.xml is though so no worries there. I am comfortable working with .xml files from my days of adding waypoints to FS9 with the SDK.

Thanks,

Adam

Edited by adamant365
Posted (edited)

Pete,

Again, thanks for the help. I renamed my dll.xml file and reinstalled FSUIPC. That did the trick. I added back in the lines from the old dll.xml that contained the Level-D information and both the Level-D and FSUIPC menus show perfectly. Of course, since UT2 uses the exe.xml, it wasn't affected. It makes me wonder....I did install the FSX SDK since I have it from buying FSX Accel. Is it possible that caused the issues? I installed it before installing UT2 and can only think this might be the issue. Here is the complete text of my original (bad) dll.xml:

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>dll.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>Object Placement Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Traffic Toolbox</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Visual Effects Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>FSUIPC 4</Name>

<Disabled>False</Disabled>

<Path>Modules\FSUIPC4.dll</Path>

</Launch.Addon>

<Launch.Addon>

<Name>Level-D Simulations</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>Modules\LVLD.dll</Path>

</Launch.Addon>

<Launch.Addon>

</SimBase.Document>

4

Thanks,

Adam

EDIT: Just noticed the number "4" at the bottom of the original dll.xml. I wonder how that got there?? I can assure you that before I started probing into this issue today, I had never modified my dll.xml. I removed the 4, and decided to try using the old dll.xml and everything worked fine. I'm 100% certain this caused the entire .xml file to be invalid. I hadn't noticed yet because I haven't had a chance to fly the Level-D. Very strange....

Edited by adamant365
Posted

Just noticed the number "4" at the bottom of the original dll.xml. I wonder how that got there?? I can assure you that before I started probing into this issue today, I had never modified my dll.xml. I removed the 4, and decided to try using the old dll.xml and everything worked fine. I'm 100% certain this caused the entire .xml file to be invalid. I hadn't noticed yet because I haven't had a chance to fly the Level-D. Very strange....

Yes, indeed. I find XML quite annoying. It looks to be a very flexible form of data definition, but the slightest error in its syntax causes things to go wrong. Seems to defeat the object to me. And it is very cumbersome compared to the simple INI / CFG file format.

Glad you got it sorted so easily.

Regards

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.