Jump to content
The simFlight Network Forums

FSUIPC, Radar Contact, FDC Live Cockpit Problems


 Share

Recommended Posts

Hi,

I have a problem that might be related to FSUIPC, but I am not completely sure.

I installed FDC Live Cockpit V3.90 lately.

Installation went fine so far. FDC tried to install an old version of FSUIPC, but discovered the newer one (4.5.3.0) on my PC, so it didn't.

The next thing I get during installation (FSUIPC4 Installer for FSX) is a warning window saying: Problem! My signature check fails on the installed FSUIPC4.DLL. Please check that I am not listed as an untrusted publisher in Internet Explorer. Then I have to reconfirm my registration numbers and FDC is properly installed.

Now, FDC Live cockpit runs without problems but one: The checklists take ages to load, and during the checklists the menu entry in FSX disappears until the answer is spoken (takes up to 30 seconds instead of instant reply).

I managed to get this problem away (but don't know how, really, I allowed FDC to communicate through the firewall, then it was gone). But today I installed radar contact. It also tried to install a version of FSUIPC, discovered the newer one and then didn't install FSUIPC. This time, I didn't have the warning box.

But now Radar Contact and checklists in FDC are slow again. Radar Contact takes as long to react as the checklists from FDC do. Firewall settings do not help now.

OS is Vista 64, soundcard an internal Realtek HD audio. 8GB RAM.

Both FSUIPC and WideFS are latest versions, as are Radar Contact and FDC. I am totally at a loss here, what do you suggest that I do?

Thanks for your help in advance,

Bernhard

Link to comment
Share on other sites

The next thing I get during installation (FSUIPC4 Installer for FSX) is a warning window saying: Problem! My signature check fails on the installed FSUIPC4.DLL. Please check that I am not listed as an untrusted publisher in Internet Explorer. Then I have to reconfirm my registration numbers and FDC is properly installed.

Sorry, I think you missed a bit there. Was SimFlight listed as an untrusted publisher? How did you get past the error? Can you show me the Install log for FSUIPC4, please -- it will be in the FSX Modules folder.

Now, FDC Live cockpit runs without problems but one: The checklists take ages to load, and during the checklists the menu entry in FSX disappears until the answer is spoken (takes up to 30 seconds instead of instant reply).

I managed to get this problem away (but don't know how, really, I allowed FDC to communicate through the firewall, then it was gone). But today I installed radar contact. It also tried to install a version of FSUIPC, discovered the newer one and then didn't install FSUIPC. This time, I didn't have the warning box.

What firewall is this? Are you using WideFS and running these programs on a separate PC to FSX?

Both FSUIPC and WideFS are latest versions, as are Radar Contact and FDC. I am totally at a loss here, what do you suggest that I do?

So I guess you are using WideFS? You really need to state such things, and where the RC and FDC programs are running.

If so, have you checked the WideClient, WideServer and FSUIPC4 log files to see if any problems are being reported?

Regards

Pete

Link to comment
Share on other sites

Sorry, I try to be more specific.

I am running all programs on the same computer.

Here's th FSUIPC log from the last session (minus my email address and name)

********* FSUIPC4, Version 4.53 by Pete Dowson *********

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

User Name="xxxxxxxxxxxxxxxx"

User Addr="xxxxxxxxxxxxxxxxxx"

FSUIPC4 Key is provided

WideFS7 Key is provided

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

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

62 System time = 19/10/2009 15:49:49

62 FLT UNC path = "C:\Users\Home\Documents\Flight Simulator X-Dateien\"

62 FS UNC path = "E:\FSX\"

515 LogOptions=00000000 00000001

515 SimConnect_Open succeeded: waiting to check version okay

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

9953 Initialising SimConnect data requests now

9953 FSUIPC Menu entry added

10015 C:\Users\Home\Documents\Flight Simulator X-Dateien\start.FLT

10015 E:\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR

28689 C:\Users\Home\Documents\Flight Simulator X-Dateien\LINZ_WIEN_IFR.PLN

48142 E:\FSX\SimObjects\Airplanes\C208B\Cessna208B.AIR

99014 Weather Mode now = Global

158606 Aircraft="Cessna Grand Caravan"

158606 System time = 19/10/2009 15:52:28, Simulator time = 15:49:59 (14:49Z)

167576 Advanced Weather Interface Enabled

174830 FSUIPC Display Title set = "Radar Contact"

284281 Sim stopped: average frame rate for last 118 secs = 24.6 fps

403715 Sim stopped: average frame rate for last 98 secs = 24.6 fps

406570 C:\Users\Home\Documents\Flight Simulator X-Dateien\LINZ_WIEN_IFR.PLN

406570 Weather Mode now = Custom

406570 C:\Users\Home\AppData\Roaming\Microsoft\FSX\Vorheriger Flug.FLT

443074 System time = 19/10/2009 15:57:12, Simulator time = 15:53:35 (14:53Z)

443074 *** FSUIPC log file being closed

Average frame rate for running time of 217 secs = 24.6 fps

Memory managed: 487 Allocs, 487 Freed

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

Radar Contact was again verxy slow during this session.

Here's the Wideserver.log:

********* WideServer.DLL Log [version 7.53] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 19/10/09, Time 15:52:36.006: Server name is HOME-PC

15756 Initialising TCP/IP server

15756 Initialising IPX/SPX server

15756 IPX/SPX socket() failed [Error=10044] Socket type not supported

15756 Failed to start IPX/SPX Server

15756 Initialising UDP/IP server

16115 Broadcasting service every 1000 mSecs

275591 Closing down now ...

Memory managed: Offset records: 487 alloc, 486 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

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

Firewall is the one in Vista - turning it off completely doesn't make a difference.

What I notice is that both FDC or Radar Contact are listed as non responding in the taskmanager when I wait for the sound output.

And no, I didn't miss a bit from the warning message - that was exactly what was written in the alert box. I really wondered why it was popping up and why it refered to IE - it wasn't even in use then...

Link to comment
Share on other sites

Here's the installer log from the FSUIPC installation through FDC:

Installer for FSUIPC4.DLL version 4.40

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

SetupPath="E:\FSX"

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

... Okay, Probe Manifest matches installed SimConnect 60905 (Original)

Found later build SimConnect 61242 (SP1 May07)

Found later build SimConnect 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

E:\FSX\Modules\FSUIPC4.DLL

... Version 4.530 found.

Installed version is later: it is not overwritten.

Looking for the current user's Application Data path:

... found as "C:\Users\Home\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\Home\Anwendungsdaten\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\AppData\Roaming"

Found FSX.CFG in "C:\Users\Home\AppData\Roaming\Microsoft\FSX\FSX.CFG"!

Now checking DLL.XML ...

... There is a previous DLL.XML, checking for FSUIPC4 section.

... FSUIPC4 section already exists but will be replaced.

... FSUIPC4 section of DLL.XML written okay

Now checking for a SimConnect.XML file ...

... There is a SimConnect.XML, checking for "local" section.

... "local" section already exists, file not modified.

Looking in "C:\Users\Home\Contacts\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Cookies\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Desktop\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Downloads\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Druckumgebung\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Eigene Dateien\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Favorites\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Links\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Lokale Einstellungen\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Music\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Netzwerkumgebung\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Pictures\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Recent\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Saved Games\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Searches\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\SendTo\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Startmenü\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Videos\Roaming"

No FSX.CFG there

Looking in "C:\Users\Home\Vorlagen\Roaming"

No FSX.CFG there

Now installing additional files into the Modules folder:

Installed "FSUIPC4 User Guide.pdf" okay

Installed "FSUIPC4 for Advanced Users.pdf" okay

Installed "FSUIPC4 History.pdf" okay

Installed "List of FSX controls.pdf" okay

Installed "GlobalSign Root.exe" okay

Installed "FSUIPC Lua Library.pdf" okay

Installed "FSUIPC Lua Plug-Ins.pdf" okay

Installed "Lua License.pdf" okay

Installed "Example LUA plugins.zip" okay

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! My signature check fails on the installed FSUIPC4.DLL. (Error ref FFFFFFFA)

Deleted GlobalSign Root fix programno longer relevant

All installer tasks completed okay!

Registration check for FSUIPC4 and WideFS was successful! (result code 00)

*************** End of Install Log ***************

Here's the error report taken out of the log again:

FSUIPC4.DLL signature failed: trying GlobalSign Root fix ...

Problem! My signature check fails on the installed FSUIPC4.DLL. (Error ref FFFFFFFA)

Deleted GlobalSign Root fix programno longer relevant

Link to comment
Share on other sites

I am running all programs on the same computer.

Hmmm. Yet you have wideFS running? why not move them onto a separate PC? FSX isn't very good at releasing any of the processors, unless you manage force it to (e.g. by severely restricting frame rates or reducing settings).

Here's th FSUIPC log from the last session (minus my email address and name)

Well, it doesn't show a code signature pproblem. How did you reolve that? What does the last FSUIPC Install log show?

There's nothing wrong in the FSUIPC4.LOG. I don't really think its a problem with FSUIPC specifically, perhaps more just a resource sharing problem -- maybe too many demanding programs?

Here's the Wideserver.log:

That's not relevant as it isn't being used.

Firewall is the one in Vista - turning it off completely doesn't make a difference.

There's no firewall relevance to any of this. With the SP2/Acceleration version of SimConnect only pipes are used by FSUIPC, not TCP/IP.

What I notice is that both FDC or Radar Contact are listed as non responding in the taskmanager when I wait for the sound output.

Windows always thinks things are non-responding if they aren't processing messages. It sounds like there's a problem with your sound drivers -- they should not be holding up the processing of messages in either program.

And no, I didn't miss a bit from the warning message

Sorry, when I said you'd missed a bit I meant you'd left out part of the story you were relating! HOW did you fix the code signature problem? Where is the Install log I asked you to show me?

- that was exactly what was written in the alert box.

Yes, I know, but that's not the point. You carried on and managed to run FSUIPC4 in FSX, which isn't possible if the code signature fails. I wanted to know the part of your story you missed out.

I really wondered why it was popping up and why it refered to IE - it wasn't even in use then...

IE manages authorisations for software publishers. It is is charge of all of the code and webpage signing certificates. That is why you are referred to it to sort such problems out.

Regards

Pete

Link to comment
Share on other sites

Ok, it seems I have resolved the issue by allowing a response interval of 1 second instead of 0.25 seconds.

I installed FDC on a second computer via WideFS, and with my profile for FDC it displayed the same error - so I was able to rule out the soundcard or the driver. As I noticed it ran fine with the default response time, I applied this time to my setup and - voila.

Thanks for assisting me.

Link to comment
Share on other sites

Ok, it seems I have resolved the issue by allowing a response interval of 1 second instead of 0.25 seconds.

Where was that parameter?

I installed FDC on a second computer via WideFS, and with my profile for FDC it displayed the same error - so I was able to rule out the soundcard or the driver. As I noticed it ran fine with the default response time, I applied this time to my setup and - voila.

So it was down to something internal in FDC?

Sorry for the questions, but it helps me to know on case others ask.

It also seems odd that it changed by itself?

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 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.