Hello,

I m using my B777 with autocruise and maximum timecompression of x8. However, doing this and flying at x8, radard contact often does not recognize that I reached a waypoint and already heading to the next one. In consequence, it is telling me to turn 180 degrees to get back to this waypoint. The only way to solve that is to ask for a "direct to" the next waypoint to get rid of these messages.

As this is quite annoying, I would like to ask whether there are other users that have the same issues and maybe found a workaround?

 

Since Pro ATC X is also on the market, does someone have experience whether this issue exists with that software as well or is it worth trying Pro ATC X if there is no workaround with radar contact?

 

Thank you for any advise.

 

Kind regards, 

Tilo

Sorry, if you see this topic three times but there have been an error message, that the site is not available. so I tried it three times  :huh:

 

Sorry about that...

 

Tilo

It works the same in PATCX as well. You will have to put up with it. It is no great deal, only takes a couple of seconds to ask for Direct.

One advantage with PATCX, it does not nag. RC gets a bit bolshy when you depart from the norm.

 

Remember, the T7 was released long after Radar Contact finished development. The chances of any update to consider the T7 is very remote.

I would love an automatic reduction to 1x around every waypoint myself. Guess, PMDG have their hands full with more important T7 issues ...

 

You can request a DIRECT before activating the time acceleration and, after receiving the clearance, execute that DIRECT in your FMC. That way RC won't nag until the DIRECT WP is reached.

 

If you're pondering a 2nd ATC purchase: I use RC and VoxATC alternatively. Vox only cares about the first WP in your flightplan; after that one you can fly any route you want. You can also shut down Vox in flight and re-start it before you reach your TOD: That way you'll be back under full ATC control for your descent/approach/landing. Vox can assign SIDs and STARs according to your flightplan, that's what makes it fun to be under Vox control with an FMC-equipped aircraft.

Thank you both for your advice. I will check out VOX ATC to see how it works.

 

Tilo

Just an idea. When using rc4 could you not just request for permission to divert left and right of course due to wx before warping to 8x which should then avoid the controller telling you you are of course.

Hmm, I am afraid this will not work. As far as I know, it is possible to increase the deviation tolerance but when RC thinks I did not pass the waypoint at all, it will start complaining.

[TYPICAL KYLE OPINION]

I look at this like trying to have your cake and eat it, too.

 

Either use time compression as is and deal with whatever extra procedures are required to make it all work together, or don't use it.  It was added into the simulation so that people could fly longer routes in the sim without being forced to sit there the whole time, or just get it done faster in general.

 

It wasn't created so that it would work seamlessly with every other add on out there.  That would be the aim, but trying to tune it to every single program out there would be work prohibitive.  1X around waypoints?  Good luck on airways with close intersections.  As someone else mentioned, try a workaround to get the other program to cooperate with the feature.

 

I'll add this to the entire list of things I dislike intensely about RC.  Controllers aren't there to force you to hit every waypoint.  If you miss one, they might ask you to report your assumed position and advise you that they see you as X nm left or right of track, but they'll just either vector you back toward the track/radial or give you direct to the next waypoint.  To me, more of the issue is an issue with RC and its tolerances, versus an issue with the 777.

 

My opinion, though, is that you can't expect everything to behave seamlessly when you're using shortcuts like time compression.  Things are programmed for normal time.  If you use compressed time and the program isn't designed to handle that, you're going to get odd results.  Deal with it, or don't use it.

[/TYPICAL KYLE OPINION]

Users like me, that uses the RC4, i think we must deal with it, since we can't expect any future update to this software. Also if RC skips a waypoint, you can request to go to a specific waypoint, and follow the route from there