I Purchased Radar Contact V4, FS build 2, and Active Sky Evolution (lastest build with SP2), I have FSUIPC V4 and FSX w/ SP2. I made my flight plan in FSbuild, opened ASE and launched FSX from ASE, using the windowed FSX I opened Radar Contact, loaded the Flt Pln without issue. When I attempted to start RCv4 I rec'd an IPC Error. I went through the Forum here and made sure I had all the correct versions of the programs, as a matter of fact that is what prompted me to by the latest version of ASE, so I would have the correct build. I tried several times to start RCv4 always getting the IPC Error. I found that if I made my Flt Plan, then opened FSX alone, did not start ASE, then running RCv4, it would start and I could fly the route using RCv4. Whenever I attempt to launch FSX with ASE, I receive that IPC Error. Finally I tried a different approach. I made my Flt Pln, opened FSX alone, started RCv4, loaded Flt Pln, started RCv4, then started ASE, I didn't have any IPC Error. I went into my FSX and ASE was active, RCv4 was active and everything seemed to operate correctly.Is there a conflict by starting FSX with ASE? I am also using Ultimate Traffic 2. My system is a Gigabyte MB, 8 Gb 1333MHz Ram, Intel Core I3 2.8 GHz CPU, running Win 7 64 bit, GeForce GTS 250 1Gb video.Any help you can provide will greatly be appreciated.Jim K, Greenville NC

First there have been some FSUIPC4 fixes regarding time-outs and FS access especially when using ASE in DWC mode which loads down the CPU. Here are the update links:-----------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflight.com/forum/142-download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.com/view.asp?page=library-----------------In addition while you do not appear to be making this error there must be a flight loaded in FS before using the Start button in RC.Read through the ASE Slows RC thread in this forum. In addition as part of that thread traffic created by UT2 may not be spawned at destination in time for RC4 to read it using its current code. Be sure UT2 is set to spawn AI at the maximum range (50 nm I think).

First there have been some FSUIPC4 fixes regarding time-outs and FS access especially when using ASE in DWC mode which loads down the CPU. Here are the update links:-----------------Get the base FSUIPC version from:http://www.schiratti.com/dowson.htmland then interim update from the modules link on this page:http://forum.simflig...download-links/FSUIPC now self installs initially based on your registry entry for your FS path. Check that with this free utility:FSX/FS9 Registry Repair Tool (36KB) from http://www.flight1.c...sp?page=library-----------------In addition while you do not appear to be making this error there must be a flight loaded in FS before using the Start button in RC.Read through the ASE Slows RC thread in this forum. In addition as part of that thread traffic created by UT2 may not be spawned at destination in time for RC4 to read it using its current code. Be sure UT2 is set to spawn AI at the maximum range (50 nm I think).

Ronzie, I've been going through many of the threads here, trying to get some idea on how everything goes together. I will try loading a flight in FS before starting rcv4, I wasn't doing that. I'm pretty sure I have have to latest FSUIPC, but i'll check that. While reading others problems I keep noticing a program that gets mentioned "MAKERWYS.EXE". I have no idea what this program is and where it resides, could this cause my problem?Thanks for the response and helpJim K, Greenville NC

Ronzie, I've been going through many of the threads here, trying to get some idea on how everything goes together. I will try loading a flight in FS before starting rcv4, I wasn't doing that. I'm pretty sure I have have to latest FSUIPC, but i'll check that. While reading others problems I keep noticing a program that gets mentioned "MAKERWYS.EXE". I have no idea what this program is and where it resides, could this cause my problem?Thanks for the response and helpJim K, Greenville NC

Recommended sequence:Start ASE and initialize Start FSBuild and create flightplan Load plan in ASERun RC and load plan, set options, etc. - Do not press 'Start' ButtonRun FS with default plane at starting airportLoad whatever plane you're flyingLoad flightplan and set weight and fuelNow press 'Start' in RC and go flyNote: if you are running in Win7, all these programs should be run 'as administrator'makerwys.exe resides in the main FS directory and should be run whenever you install an add-on that contains afcad data. It is used by RC to create the airport and runway data that RC uses - run it by pressing the 'rebuild scenery db' button.DJ

Just to clarify any time you add new airport scenery and/or afcad files (by convention the label may start with AFX, AF, etc., but is not necessary) run the scenery rebuild option from within RC and only RC running which will start makerwys and return to finish in RC all in one process to update RC's data files. The process is a bit different when RC does not reside on the FS pc. Some issues with certain scenery were resolved in version 4.41 dealing with layer information priorities. The scenery data RC gets is used to determine user and AI position with regard to various airport elements which is critical for RC to recognize the position state of aircraft (such as holding short near enough to a runway to obtain line-up and wait clearance).Note that some traffic application programs might install new afcad type files but if you have add-on scenery it is best to rename those traffic installed .bgls to .bgx so they don't conflict with add-on scenery.The latest version of makerwys is on that same download links page under Useful Additional Programs.