Hi I running RCv4 on windows 7 64 and when trying to fly IFR form an uncontorled airport Im unable to get weather or clearance from Flight service. After starting FSX and loading the flight plan into FSX and RC and starting RC the box appears with 2 for FSS WX and 4 for Clearance by FSS, but when eiether option is slected I get a standby message very birefly and then it returns to 2 for FSS wx and 4 for FSS Clr but I am never able to make contact with FSS, also the option for getting clearance in the air is never available.

I have Win XP SP3 32 bit. I loaded a flight and a flight plan from a non-controlled no coms airport and got the same menus you describe. As soon as you make a selection the menu returns but the process continues. The telephone dial tone then dialing was heard OK in both selections. For weather I either got an auto response or a standby and then delivery. I then selected the CD by FSS option and got the FSS person answering. The pilot voice then identified the flight data, a standby was issued, and after about thirty seconds the clearance was delivered. The menu was then changed to ack and contact with a response NA (not applicable) or ack in which case the pilot read back the clearance and FSS gave readback correct.

 

Now there are some pauses while the audio data was assembled for playback.

 

Starting on page 61 of the RC43 manual is the sequence of departing from an uncontrolled field and activating your plan in the air. Note the reference to void time.

 

I used a flight plan from the default KROS to KGRB for testing (FS9).

 

In the RC controller tab for your departure airport there should be all zeros and no x's the the departure airport frequency list. Some will have the departure frequency of a nearby airport otherwise you will contact center first to activate your plan in the air otherwise you activate with the nearby departure airport (within 40 nm of your actual departure airport). If you wish to force a frequency to become available then click the box next to it.

 

Is everything working with controlled airports OK?

 

I'm not sure of the degree RC monitors your altitude on departing uncontrolled airports but it expects at least 1,000 AGL for VHF comms to become available.

 

RC4 has no filing from the air as I recall, just activating a plan already filed.

 

If you still have a problem, turn on debug before loading your plan. Then proceed with the steps and take-off until you have had the errors occur. At that time alt-tab to RC and press the quit button so RC will save the log. (If you just quit FS RC will hang and not save the log correctly.) Then go into your RC folder and rename the log so it does not get overwritten and send it in per the pinned topic.

 

Be sure your fsuipc is up to date and especially the scenery rebuild makerwys.exe from the links posted at the forum top. We want to make sure your scenery data is correct as well as FSUIPC so RC can correctly relate your aircraft position and altitude to your installed scenery.

 

RC is at version 4.3845.

Hey Ron,

 

Thanks for the Reply, I downloaded and ran the latest version of Make runways Version 4.612, my version of RC is 4.3.3845, and I have the latest version of fsuipc 4.853 witch is a registred version. I re read the manual starting on Pg 61 and then tryed a flight plan from KWRL to KBIL. after getting everthing set up I tryed to contact FSS for WX and waited over a minuite and still no reply, then I tryed to contact FSS for Clearance and also no response after a minuite or more of wating. So with conditions being VFR I took off hoping to be able to activate my flight plan in the air that also was a no go. Other than that everthing else seems to work ok controled airports and such. I have a log and will be sending it in.

 

Thanks Ryan

I created a plan in FSBuild from KWRL to KBIL. There were no navaids found enroute by FDB's auto routing so it was direct for the 113 nm distance. I used a freeware Piper Archer I had using FS9. I had the altitude at 12,000 feet (yes, I know it is beyond the ceiling of the Archer) but this was a quick ground test for comms.

 

Everything transitioned as it should as I stayed parked at a GA ramp. The FSS weather volume was low. As soon as the weather was complete (it just ends with no goodbye required) I selected the FSS CD which was more normal. There were some standbys for each function. After all of the acking was done after CD the TAXI runway selection menu came up which emulates announcing on Unicom/Multicom which runway you will be taxiing to. Avionics were on for this test even though comms are not used.

 

Maybe the log will yield something.

 

One thing you can look for is hard disk activity during the weather and CD processes to indicate that the wavs are being fetched. After they are fetched it takes a while for them to be assembled and buffered in ram for delivery. This includes CD readback for the pilot.