Fsuipc Error after exit from P3Dv4.5

[Mirtec1971]

Hi,

I have a small problem after installing a new software OpusFsi V6 that use a dll file OpusPDk45.dll for monitoring all functions during the flight.

When I close P3D a recieve an error link to unloading Fsuipc.dll ( link file )

I ask to Opus Support and they inform me :

Of course our PDK DLL has no connection or interface with FSUIPC or any other 'internal' launched P3D DLL.

It simply provides standard PDK functionality for our 'external' P3DSERVER and P3DCLIENT programs.

As for our P3DSERVER and P3DCLIENT software I will try and ensure I make no requests to FSUIPC immediately after receiving the sim's Close notification. I'm pretty sure that's what happens now.

My software's (P3DSERVER and P3DCLIENT program's) connection is NOT directly with the launched P3D FSUIPC DLL. I interface with an external FSUIPC DLL which connects and communicates with its own internal 'in sim' DLL.

There's nothing I can do in our PDK DLL as it has nothing to do with any other launched DLL. It interfaces with the sim using the standard LM PDK interface.

 

1. P3Dv4.5 hotfix2

2. FSUIPC ( last version )

3. IF I REMOVE THE OPUSPDK45.DLL FROM DLL.XML NO MORe ERROR WHEN EXIT FROM P3D.

 

Could you help me ?

Thanks in advance

Federico

dll.xml FSUIPC5.log Fsuipcerror.txt

[Pete Dowson]

42 minutes ago, Mirtec1971 said:

When I close P3D a recieve an error link to unloading Fsuipc.dll ( link file )

"FSUIPC.dll_unloaded" actually means FSUIPC isn't there, it's been closed along with the rest of P3D.  So it cannot actually cause a crash.  FSUIPC sometimes does get the "blame" for closing down crashes because it is usually the last to still be there -- some of its threads run around tidying things up for the external FSUIPC interface and any WideClients which may have connected.

I don't know how such an error arises -- normally the way to nail it is to follow a process of elimination to see which component is responsible, but you already have that identified -- the OpusPDK_v45.DLL module.

You could try a different loading order in the DLL.XML. In otherwords, move this section

<Launch.Addon>
    <Name>FSUIPC 5</Name>
    <Disabled>False</Disabled>
    <Path>D:\Prepar3D v4\Modules\FSUIPC5.dll</Path>
</Launch.Addon>
  
before the OpusPDK_v45.DLL entry.

I see that the FSUIPC log isn't complete -- FSUIPC hasn't even received notification that P3D is closing. If that is where P3D crashed then FSUIPC wasn't "unloaded" and you hadn't requested P3D close down. So, are you sure that's the right log?

Within the log I see another problem. Starting from about 58 minutes into the session one of your USB devices started playing up:

***** HID USB device reconnected: re-initialising FSUIPC connections
  3501333 HID: Vendor=045E, Product=0745 (Version 6.99)
  3501349 Manufacturer= 
  3501349 Product= Microsoft® 2.4GHz Transceiver v7.0
  3501364 Serial Number= 

this repeated every second, and in fact the Log finishes at the end of one such episode.

Perhaps this has something to do with it? Do you have other PCs wirelessly connected to the session? WideFS clients perhaps?  I see you have WideFS registered. Perhaps the WideServer.log is relevant? The "unloaded" error might just be messages arriving for FSUIPC after it has closed down -- whilst FSUIPC's WideServer does try to close everything tidily, some autonomous parts of the TCP/IP linking softare, in Windows and in the Mobo drivers, are in the process of sending something when FSUIPC is forced to close along with all other parts of P3D -- it imposes a time limit.

So, another avenue to investigate is to set all WideClients to close themselves down, along with programs they started, when signalled by the Server that the session is ending.

Is Opus using the network links too?

Pete

 

[Mirtec1971]

Hi Pete,

I tried to move the order of loading in dll.xml but nothing always the same error...

I disabled the WideServers ( is not necessary and i don't why was enabled ) but always same error.

I know that if i remove dll by Opus the error disapper ..

I spoke to Stephen ( Opus) and for him it's very strange because OpusPDK45.dll not use Fsuipc for working and trying with his computer have no problem ( crash on exit )

He told me that will try to ask you a support for investigate better.

Thanks in advance ....

Today I will send you a new log and ini file .... could be helpfull

Federico

 

 

[Pete Dowson]

1 hour ago, Mirtec1971 said:

I spoke to Stephen ( Opus) and for him it's very strange because OpusPDK45.dll not use Fsuipc for working and trying with his computer have no problem ( crash on exit )

He told me that will try to ask you a support for investigate better.

Why doesn't he "investigate better"? It evidently is a problem peculiar to your system and their DLL after all. Tell him to investigate better!

Really I think you need to identify the problems you evidently have with your devices. I already pointed out that you have a USB device coninually reconnecting. You have many USB devices connected and the driver for any on of them could be responsible. Start off by disconnecting everything. Test, then add one thing at a time, re-testing each time.

Pete

 

[Mirtec1971]

Hi Pete,

There is something that I cannot understand ....

I spoke to the Opus Support and i recieve an answer that explain me that Opus Software ( OpusPDK45.dll) don't use fsuipc for link or comunicate with the P3D software and it cannot generate the error link to fsuipc.

I spoke to you and you gave me some suggestions for solve the problem link to my multiple devices connected or moving some lines in the dll.xml

So the problem is still present and only deleting the command line for OpusPDK45.dll disappear.

My devices configuration is the same since a couple of years , without any problems with all other software.

And the only error that i have is linked  to fsuipc ....

So for OPUS  the problem is link to Fsuipc routine or other  and for FSUIPC is link to opus.dll or other problem in my configuration.

 I understand that is a strange problem and not easy to find the soultion but It's the first time that i ask a support after many years ... and  I was hoping to have a little more collaboration and not the usual barrel discharge

Thanks anyway

Federico

 

[Pete Dowson]

14 hours ago, Mirtec1971 said:

And the only error that i have is linked  to fsuipc ....

No, it is more closely linked to that Opus DLL.  FSUIPC is not even running or loaded when the error occurs. Something is causing some sort of corruption, or leaving a driver in some odd state. And this is happening since you introduced Opus.

15 hours ago, Mirtec1971 said:

I spoke to you and you gave me some suggestions for solve the problem link to my multiple devices connected or moving some lines in the dll.xml

The latter made no difference, but the logging from FSUIPC indicated definite problems with devices. So have you yet done as I suggested, and tried disconnecting everyting, testing, and gradually adding things back. You need to find a way of narrowing it down, and the only clue at present that something bad is going on are the misbehaving USB devices.

15 hours ago, Mirtec1971 said:

I was hoping to have a little more collaboration and not the usual barrel discharge

Collaboration means more than one party being involved. I cannot wave a magic want and fix an obscure problem on your system. You have to do something as well. I can suggest ways of trying to determine the cause. If you ignore those i cannot help further, can I? 

Pete