Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

RTError 76 Fsuipc

Featured Replies

Recently in my overseas  flights , suddenly RC stops and received the following warning:

 

Radar Contact

fsuipc rev4 code

 

How shall I solve this problem.

THX

Ahmet Sanal

 

"Time you enjoyed wasting, was not wasted"

Are you doing long flights (oceanic crossings or such)? Or are you doing just normal length flights overseas. We need clarification.

 

Error 76 means "path not found" to a file. Do you have any peripherals with a sleep mode enabled such as an external or internal disk drive that may not be accessed during long flight legs? Any network connection involved?

 

If you run just RC and FS, nothing else, no real world updated weather periodically, does this happen?

 

Be sure your fsuipc is current getting full and interim versions from:

http://forum.simflight.com/topic/66139-updated-modules/

 

Also be sure makerwys is current from:

http://forum.simflight.com/topic/66139-updated-modules/

and then execute the RC scenery rebuild.

 

There could be external interference from an add-on application for either FS or security.

 

Please enter your software and hardware information in your user profile on AVSIM so those can be examined. Look at mine using the links under the tree frog avatar as an example.


Error 76 is "path not found" to a requested file. Be sure your flt.wx path is correct.

 

We need to clarify "overseas". Are you referring to long lengthy legs such as oceanic crossings? Are you referring to just any flights occuring in non-FAA territories?

 

Check to see if any of your disk drives have a sleep mode enabled where they shut down if not accessed for a while. Check your power management settings.

 

Be sure your fsuipc is current:

 

http://forum.simflight.com/topic/66139-updated-modules/

 

Be sure your makerwys.exe is current:

 

http://forum.simflight.com/topic/66136-useful-additional-programs/

 

and run the RC scenery rebuild.

 

Does this happen with just RC and FS running with no other add-ons? Do not enable real world weather updates for this test.

 

Please fill out your hardware and software AVSIM profiles. Look at the links under my avatar as an example.

 

Are you running RC and FS on the same PC?

 

Also read the error 75 topic and be sure RC and FS are excluded from any blockage by your security applications.

 

Have you set a shortcut to RC with properties set for run as admin? Win 7 or later requires two of these settings. If so, right click on the shortcut and click on properties. In this first window enable run as admin. Now click on advanced. Set run as admin here as well. OK this window, click Apply in the first window to save both changes, and then OK to close the properties window.

  • Author

Are you doing long flights (oceanic crossings or such)? Or are you doing just normal length flights overseas. We need clarification.

Oceanic crossings

 

Error 76 means "path not found" to a file. Do you have any peripherals with a sleep mode enabled such as an external or internal disk drive that may not be accessed during long flight legs? Any network connection involved?

No 

 

If you run just RC and FS, nothing else, no real world updated weather periodically, does this happen?

 I didnt run RC without any addons. I will test it

 

Be sure your fsuipc is current getting full and interim versions from:

http://forum.simflig...pdated-modules/

 Fsuipc4929

 

Also be sure makerwys is current from:

http://forum.simflig...pdated-modules/

and then execute the RC scenery rebuild.

Downloaded again

  

There could be external interference from an add-on application for either FS or security.

NO.Never happened before

 

Please enter your software and hardware information in your user profile on AVSIM so those can be examined. Look at mine using the links under the tree frog avatar as an example.

Done

Error 76 is "path not found" to a requested file. Be sure your flt.wx path is correct.

 Done

 

We need to clarify "overseas". Are you referring to long lengthy legs such as oceanic crossings? Are you referring to just any flights occuring in non-FAA territories?

 oceanic crossings

 

Check to see if any of your disk drives have a sleep mode enabled where they shut down if not accessed for a while. Check your power management settings.

Be sure your fsuipc is current:

 

http://forum.simflig...pdated-modules/

Done

 

Be sure your makerwys.exe is current:

Done

http://forum.simflig...ional-programs/

and run the RC scenery rebuild.

Done

 

Does this happen with just RC and FS running with no other add-ons? Do not enable real world weather updates for this test.

 OK

 

Please fill out your hardware and software AVSIM profiles. Look at the links under my avatar as an example.

 Done

 

Are you running RC and FS on the same PC?

 Yes

 

Also read the error 75 topic and be sure RC and FS are excluded from any blockage by your security applications.

 NO blockage for RC

 

Have you set a shortcut to RC with properties set for run as admin? Win 7 or later requires two of these settings. If so, right click on the shortcut and click on properties. In this first window enable run as admin. Now click on advanced. Set run as admin here as well. OK this window, click Apply in the first window to save both changes, and then OK to close the properties window

Done

 

 

Ron,

Thanks for your help.I will make a test flight and will inform

Ahmet Sanal

 

"Time you enjoyed wasting, was not wasted"

Just had a thought. In your modules folder examine fsuipc.log since the error is fsuipc's. Maybe it might state something pointing to what failed. Do this after you get the error and before the next run. fsuipc can be set for a more detailed log.

 

Now, this is for FSX, correct, not P3D2. At the moment that is incompatible with RC only in some instances (saving in flight and loading a saved flight). However, that error occurs immediately. P3D2 does not use .flt files when it saves. It uses .fxml for that. See other threads here regarding this.

  • Author

Ron,

 

I am with FSX. I made a test flight from KEWR to KORD, RC  performed without incident. Tomorrow I will fly KEWR-PHNL this is a long flight . I there is something in this flight it will show up. THen I will check up fsuipc.log and will inform you.

 

Regards

Ahmet Sanal

 

"Time you enjoyed wasting, was not wasted"

Have a good time in Honolulu.

 

Here's real flight of about 5 hours from KSAN-PHNL

 

KSAN PEBLE4 SXC VTU RZS AUDIA 3400N 13000W CUNDU BILLO R464 BITTA MAGGI3 PHNL

 

which as an FSX plan I created with FSBuild is:

 

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

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KSAN to PHNL</Title>
        <FPType>IFR</FPType>
        <RouteType>HighAlt</RouteType>
        <CruisingAlt>36000</CruisingAlt>
        <DepartureID>KSAN</DepartureID>
        <DepartureLLA>N32° 44' 00.00" , W117° 11' 22.00",</DepartureLLA>
        <DestinationID>PHNL</DestinationID>
        <DestinationLLA>N21° 19' 07.00" , W157° 55' 20.00",</DestinationLLA>
        <Descr>KSAN, PHNL</Descr>
        <DeparturePosition>27</DeparturePosition>
        <DepartureName>SAN_DIEGO_INTL</DepartureName>
        <DestinationName>HONOLULU_INTL</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>60905</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KSAN">
             <ATCWaypointType>Airport</ATCWaypointType>
             <WorldPosition>N32° 44' 00.00",W117° 11' 22.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>KSAN</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MELDY">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 05' 21.00",W117° 41' 37.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MELDY</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PEBLE">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 10' 55.00",W117° 50' 10.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>PEBLE</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SXC">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N33° 22' 30.00",W118° 25' 11.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>SXC</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="VTU">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N34° 06' 53.00",W119° 02' 56.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>VTU</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="RZS">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N34° 30' 34.00",W119° 46' 15.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>RZS</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="AUDIA">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 14' 56.00",W123° 05' 24.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>AUDIA</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="3400N13000W">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N34° 00' 00.00",W130° 00' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>3400N13000W</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CUNDU">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N33° 16' 50.00",W133° 37' 22.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>CUNDU</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BILLO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N31° 10' 41.00",W141° 17' 23.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BILLO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BEKME">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N27° 53' 31.00",W147° 58' 11.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BEKME</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BOARD">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N24° 17' 44.00",W154° 15' 00.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BOARD</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BITTA">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N23° 31' 40.00",W155° 28' 43.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BITTA</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MK150">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N23° 14' 07.00",W155° 41' 21.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MK150</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MK100">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N22° 32' 16.00",W156° 11' 13.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MK100</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="SOMOH">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N22° 19' 17.00",W156° 20' 33.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>SOMOH</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="MAGGI">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N21° 50' 25.00",W156° 57' 56.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>MAGGI</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="BAMBO">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N21° 24' 59.00",W157° 30' 36.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>BAMBO</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="GRITL">
             <ATCWaypointType>Intersection</ATCWaypointType>
             <WorldPosition>N21° 19' 39.00",W157° 37' 24.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>GRITL</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="CKH">
             <ATCWaypointType>VOR</ATCWaypointType>
             <WorldPosition>N21° 15' 54.00",W157° 42' 10.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>CKH</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PHNL">
             <ATCWaypointType>Airport</ATCWaypointType>
             <WorldPosition>N21° 19' 07.00",W157° 55' 20.00",</WorldPosition>
             <ICAO>
                 <ICAOIdent>PHNL</ICAOIdent>
             </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>
 

------------------------------

 

Interesting  the fsbuild duration was the same as the actual flight duration noted on the source route from flightaware.com.

 

At least this should be a little shorter test time for you. See how this works.

  • Author

Thanks. That will be my flight plan.

Ahmet Sanal

 

"Time you enjoyed wasting, was not wasted"

  • Author

MY schedule changed I made flight from Newark to Osaka .It was a 14 hours flight, with PMDG 747X. RC passed the test. Worked WELL.

During  Zero visisbilty landing, I was keep hearing OOM beeps. I didnt get OOM, but it was so close , 290MB left .

 

AS all ways thanks for your great support.

Ahmet Sanal

 

"Time you enjoyed wasting, was not wasted"

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.