RCV4 / FSUIPC error message

[elsmoko]

Please see screen cap of the error at the link below.  I have not seen this before over my many years of

RCV4 usage.  I've seen it twice in past three days and afterwards RCV4 stops responding.  Has anyone else 

experienced this who can explain what it means or how to avoid the problem ?  I use RCV4 via WideFS

with FSX and Win 7-64.  It happened while flying the QW B788.

https://www.dropbox.com/s/734wrox8wiyj2ld/RCV4 Error.jpg?dl=0

Thank you,

Ken Boardman

[Pete Dowson]

1 hour ago, elsmoko said:

Please see screen cap of the error at the link below.  I have not seen this before over my many years of

RCV4 usage

Please tell me what it says, not post dropbox links.

If it is RCV4 which is failing I can't really do much about it. You might see if the old RCV4 support group is still operating, or ask Ray about it over on AVSIM. He still uses RCV4.

Pete

 

[elsmoko]

Hi Pete,

  The error states >>

"fsuipc, wait. can't get D008 to change from 32677733 always 32677733"

Has only happened two times and I was flying the QW B788 both times so

perhaps the plane has something to do with it.  Ray told me to contact you ~:)

Best regards,

Ken

[Pete Dowson]

7 hours ago, elsmoko said:

The error states >>

"fsuipc, wait. can't get D008 to change from 32677733 always 32677733"

That offset is a timestamp telling it when trying to read some details of AI traffic -- either which runway is in use by AI, or what the details were of other AI (tail number or flight according to your settings). The timeout could occur because either no AI traffic in range has been assigned a runway, or the AI one being requested has been deleted -- either because it went out of range or because a Traffic Limiter or other program deleted it.

With a highly loaded system it could also be caused by FSUIPC not being able to get the AI traffic data for a certain time. You can adjust that in the FSUIPC INI file. Check the FSUIPC log to see if it says it had to restart traffic scanning. That means SimConnect is being overloaded.

Really this should never cause a program to crash or hang, and certainly not produce an error message box. But I do seem to remember, a long long time ago, one version of RCV4 did have such a problem. Maybe there's a history somewhere of RCV4 support requests and exchanges you can check?

Didn't Ray point you to a source for old RCV4 problems? There used to be quite a big forum with Ray a main participant.

[LATER]

Found it! It is still there, on AVSIM. Didn't you look?

https://www.avsim.com/forums/forum/135-radar-contact-support-forum/

and searching there for D008 I immediately found three relevant threads! Take a look at those please.

Pete

 

 

 

[Pete Dowson]

Further to my message above, I have seen that the QW787 models place an enormous load on Simconnect. For some reason they fire hundreds of events every minute. Logging the Events in FSUIPC reveals them. It's worse than the PMDG ones which do similar things.

If Simconnect is stalling (see the FSUIPC4.LOG) you can make FSUIPC wait longer by changing 

SimConnectStallTime

in the [General] section of FSUIPC4.INI. see the Advanced User's Guide, page 12, for details.

You could also try adding UseAIClient=No or UseAIClient=Yes to the same section 9or change it if it is there).

As I final resort you could just stop FSUIPC supplying AI data to RCV4 by changing (or adding) this:

ProvideAIdata=No

Pete

[elsmoko]

    Many thanks for all of the insight and suggestions Pete.  The QW plane is quite the (FSX) VAS hog

so it doesn't surprise me that it is suspect regarding other issues.  I do like to fly the plane though. 

    I will certainly give your suggestions a try.

Best regards,

Ken