I recieve this message when starting RC4.3 for FSX. Have never seen it before and don't have it in RC4.3 for FS9. Both on the same computer.

Be sure you are running rc4 build 3845 as shown on the splash screen. If you are running RC and FS on different pcs over WideFS please note that and check the special instructions for scenery rebuilds in this case.

 

A frequent reason is FS is not running with a flight loaded when you press the RC start button although that may read time out.

 

The next reason could be a flight plan format problem or scenery coordination problem..

 

Since you have both FS9 and FSX installed you should have two folders installed, rcv4 and rcv4x. You should have a shortcut for each clearly labeled for each and if on VISTA or FSX they should have a property set to run as admin, a program level access as opposed to user account access so RC can access your FS folders and FS itself.

 

Be sure you have the latest makerwys installed in both the FSX and FS9 versions:

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

 

Be sure you have the latest fsuipc full and interim updates installed:

http://forum.simflig...pdated-modules/ and check the release notes. 3.999i for fs9 and 4.827 are today's latest. Be sure the correct fsuipc4.dll is in your fsx\modules folder.

 

Before installing fsuipc full .exe installer versions it is expedient to check your FSX and FS9 registry paths with this free flight1 utility registry checker repair utility (right click on it and run as admin):

 

http://www.flight1.c...sp?page=library

 

If you updated makerwys be sure to rebuild again the scenery from within RC.

 

Now that preliminaries are taken care of be sure after adding scenery you put the correct FS version path in for the version of RC4 you started for the rcv4 or rcv4x folders. If a mistake is made and you use the FS9 path for the FSX version you'll get the incorrect scenery data when rebuilding the database for each version. Be sure your paths for the correct FS version for each version of rcv4 you are starting are correct for that FS version.

 

In looking at your flight plan file with wordpad or notepad make a note of your airport coordinates. Now browse to your rcv4x\data folder. right click on a4,csv (you may want to make a safe copy first) and select to open it with notepad or wordpad. Sear for the ICAO code of the airport you are trying and get the coordinates. They should be close to your plan coordinates. You may need to converted decimal portions of coordinates to minutes and seconds by multiplying the decimal readings by 60 as needed. You can also check in your rcv4x\data folder the modified attributes of date and time by right clicking on it to insure it agrees with the time you ran the scenery update for FSX within rcv4x.

 

You should do your tests with a default aircraft at default scenery with nothing else running for starters.

 

These tests are comparing scenery data and what is in your flight plan to make sure coordinates are correct within the allowed range.

 

If nothing helps then follow the pinned topic on sending a log in. In your case start FS and load a flight with a parked aircraft with avionics on. The load up RC and click the debug button. Load you flight plan starting at the same airport. Set your options in RC and start it. If you get the IPC error if RC has not closed if necessary do an alt-tab to it and quit it. Exit FSX. go to your rcv4x folder and rename the rcv4.log to a unique name such as rcv4-date.log so it will not be overwritten. Zip up that log file and send it to [email protected] subject ipc error and describe the error code and what was happening when it occurred. (Your flight plan and fsuipc and rc versions will be included in the log for jd to look at.) Usually the log file pinpoints the problem.

 

Please reply how things work out in this thread and if fixed what corrected the problem.

Be sure you have the latest fsuipc full and interim updates installed:

http://forum.simflig...pdated-modules/ and check the release notes. 3.999i for fs9 and 4.827 are today's latest. Be sure the correct fsuipc4.dll is in your fsx\modules folder.

 

Please reply how things work out in this thread and if fixed what corrected the problem.

 

Thank you for that link. That solved the problem. No I didn't have an old version of FSUIPC. To my surprise I discovered that I hadn't installed FSUIPC at all.