Hi all,

 

Running RC4 over WideFS in FS9. 3.9.9.9 FSUIPC Registered.

 

I begin my flight, all as expected on ground, I get weather, runway and cleared alt/FL - then clear to taxi and takeoff fine. Then the problems start. I'm ascending to my required altitude, get my handoff and my response is that I am at my cleared xxxxft/alt, even though I am on the climb to it. RC doesn't give me any alt warnings missed , and I continue to get commands to my filed altitude, which I get to. Any speed restriction busts do get ATC's attentions.

 

Flight to filed FL goes fine, happily cruise then I get my descent command. Regardless of whether it's FL level, or ALT commanded, I meet this (checking my alt and QNH as necessary, using "B" to make certain. Where appropriate, alt does change on gauge). Then, after some time, I'll get told that I've not met my required altitude, I"m given a new heading, which I change over to... then....nothing. I'll continue for 40/50/60 miles, no ATC contact occurs after this command.

Now, I've busted my alt enough times before to know that I should be getting ATC requests after that :) - although not every time. JD critiques me good on my flight performance more often than not, he he.

 

One one flight, I've requested after this to deviate to the waypoint prior to my heading change, and I get the direct to checkpoint acknowledgement fine, but ATC won't direct or acknowledge me on after this. Only thing I can do is cancel IFR in RC to get any kind of response from ATC.

 

Another flight, I've diverted back to my original plan, and lined up for my runway, with landing. RC will continue with chatter to other a/c, but mine is just ignored: no request to contact tower or approach.

 

Occasionally, the FP will work without error.

 

The same plans can be filed under FSX, and they seem to be OK (JS41/737X).

 

I am using the Quality Wings Avro 70/85/100 in FS9, and I've not attempted to replicate with other aircraft, payware or default.

 

PlanG and FSC (also under WideFS) will both show the same telemetry as the plane does.

 

I'll use FSCommander or FSBuild for my flightplan, which exports and imports to Radar Contact just fine (ie no errors)

 

Looks to be regardless of FP - have been able to replicate in the US and Europe.

 

Attached is an example FP that's caught me out. This latest FP gave me something new - I was commanded down to 15 000ALT and told that was my final (sorry, can't remember the exact wording).

 

I know that the first thing you're going to ask to see is the log file - this is the kicker - of the 10 or so flights I've been able to replicate this on, if I use debug mode, so far, RC has worked as expected. So no log file thus far with this behaviour :(

 

Does anyone have any ideas off the top of their head that might at least help me know where to start?

 

Thanks in advance, Leo

I meet this (checking my alt and QNH as necessary, using "B" to make certain. Where appropriate, alt does change on gauge). Then, after some time, I'll get told that I've not met my required altitude, I"m given a new heading, which I change over to... then....nothing. I'll continue for 40/50/60 miles, no ATC contact occurs after this command.

 

Hello

Do not use the "B" key to reset the altimiter, See this post for info:

http://forum.avsim.net/topic/360518-incorrect-altitude/page__hl__transition#entry2234869

Hi Leo,

 

Sorry to hear that you are having problems.

 

If you are flying in Europe never ever use the B key.European countries have various transition levels and the B key is hard coded to the American transition level.

 

This may lie at the root of your problems.The quoted example points to the fact that you missed your approach fix crossing altitude,again it could revolve around the B key use.Try using the manual approach to changing your barometer settings.

 

I would also re-read the tutorial flights as we can all forget things from time to time.

In addition do not fly under accelerated time modes and in cruise maybe 2x might be OK depending on your system. I'd also look for any network communication timing issues between your host and client PCs.

 

Today's FSUIPC is 3.999s and for FSX remains at 4.84 from:

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

Some timing issues were address in later FSUIPC versions.

 

RC may wait forever until you get down to the required crossing altitude (again the 'B' key thing). Another cause for RC waiting is a missed ack before you cross a waypoint in which case you will not get credit.

 

If you request to skip a waypoint is is direct from your present position to that next waypoint. Check against heading in the RC status area. If you get too close to a required waypoint when requesting the waypoint skip you may not get credit for it as you cross hanging things up. I don't understand your comment on RC not directing after acking an approved waypoint skip. You just change your heading as needed. You don't want to do this close to the approach phase which starts at 40 nm out.

 

If you are referring to a nav equipment guided STAR remember that the STAR waypoints up to 35 nm out from destination must be in the plan sent to RC. In the typical case of using an FMC where STARs are runway dependent just send the STAR waypoints (based on arrival direction) common to all runways. After getting acking the first vector request an IAP to the approach assigned runway and RC will not monitor you just letting you follow FMC guidance all the way in. The suggested altitude is your merge altitude for the intercept to final.

 

I wrote the tip sheet based on FSBuild 2.3 and has revisions for FSBuild 2.4 which includes procedures on syncing ATC and the FMC type guidance:

 

 

 

Another tip for RC4 is on an altitude or heading change to execute it before acking the command unless you are very close to a required waypoint. Wait for the climb or descent to start. This is a work around for an impatient controller.

 

You should also investigate in the manual the use of NOTAMs. In certain phases of your flight they offer a bit of looseness in ATC guidance regarding headings and altitudes (but not the hard crossing restriction).

 

BTW: The voice for the critique is not jd but Doug Thompson, the other partner in jdtllc. At the time he was an active center controller in the US and retired just a few years ago.

if you make a log, i can see what is going on. instructions pinned to the top of the forum

 

make sure you click debug, before loading the .pln

 

jd