Control just too impatient!

[Ray Proudfoot]

In principle I agree totally with your assertion that control is too impatient. In fact many aspects bug me to death and I've been moaning about it for years. The best one is when you are handed over to approach and there is no time to request the "Full ILS" before you are given vectors. All it would take is a two or three-second pause, for one to hit the relevant keys to request an ILS. But no... there is simply no time to do it. I have suggest just putting pauses between all comms., but it seems a no go. JD suggest there is no problem - presumably as there are not many peeps complaining: clearly those after a realistic experience, don't actually appreciate what constitutes "reality".

Gabe, I have raised this issue with JD too and remain hopeful he will change the code so it's possible to choose the IAP option before making contact with APP. It's my number 1 irritation.

[virtualstuff]

In principle I agree totally with your assertion that control is too impatient. In fact many aspects bug me to death and I've been moaning about it for years. The best one is when you are handed over to approach and there is no time to request the "Full ILS" before you are given vectors. All it would take is a two or three-second pause, for one to hit the relevant keys to request an ILS. But no... there is simply no time to do it. I have suggest just putting pauses between all comms., but it seems a no go. JD suggest there is no problem - presumably as there are not many peeps complaining: clearly those after a realistic experience, don't actually appreciate what constitutes "reality". Oh the irony ! I know STARS should be included in the next release (?)... but as a decent workaround in the meantime, why not just a time gap, allowing one to request an ILS, before you're given vectors. This could have been coded in from the start... and certainly added later... but no. Sad really as it totally shatters any sense of reality on approach.

Well your not alone and that's the most frustrating part of this program :( not realistic at all...

[Ops Normal]

+1 In my little corner of the world part of your enroute clearance from centre is the type of approach to expect at your destination airport. This helps in planning and doing the approach brief. When you are finally handed to approach you can then ask for a full approach or vectors to another runway depending on weather or traffic. I hope this slight mod could find its way into RC5.

[Loren Larsa]

That the controller is too impatient... Oh well, shooting the FSDO guy was probably the best thing I ever did, no more complaints!All it took was give the FSDO guy a blank wav file, or a few gunshots to make your point.

[jd]

the controllers aren't impatient. you need to be running at 1x. you need to be starting whatever the controller tells you to do, before you acknowledge what he told you to do. also make sure the "display text" option is NOT checked in the rc options. also, please don't be messing with windows processor affinity, or execution priority. let windows do it's job - it really is better at it than you are. jd

[Ray Proudfoot]

the controllers aren't impatient. you need to be running at 1x. you need to be starting whatever the controller tells you to do, before you acknowledge what he told you to do. also make sure the "display text" option is NOT checked in the rc options. also, please don't be messing with windows processor affinity, or execution priority. let windows do it's job - it really is better at it than you are. jd

Sorry JD but in relation to requesting an IAP when contacting APP you cannot select that menu option until after APP has given you approach vectors. You have to ack that (even though you will ignore it) and then request an IAP. Time acceleration is not a factor as I always fly at x1. The IAP option needs to be available around 45 miles out so the request can be granted without having to go through the above procedure. Pete D and myself flew 8 legs last weekend and wanted to fly the published APP. We never once managed to request IAP without first having to ack APP instructions.

[jd]

1) that is not correct. you have 90 seconds between first contact with approach, and the first vector 2) iap can't be 45 miles out, approach doesn't own that airspace. jd

[Ray Proudfoot]

1) that is not correct. you have 90 seconds between first contact with approach, and the first vector

That is not my experience with either manual or co-pilot comms. The first instruction from APP to flying a heading and descend comes almost immediately after making contact.It is certainly nowhere near 90secs. It is very frustrating trying to navigate through the APP menu to request an IAP when RC is issuing my aircraft with an instruction and then communicating with other Ai.

2) iap can't be 45 miles out, approach doesn't own that airspace.

I'm not asking to contact APP 45 miles out. Only to make the program aware that when I do make contact at 40m I want to fly a STAR and not be vectored. Could this not be an option for those who wish permanently to fly their own approach?

[jd]

1) :-) it's been a while, but i'm pretty sure it's coded to wait 90 seconds. maybe it's 90 seconds from the time the app controller starts talking to you. i'll look back at the code. but i remember 90 seconds was in there for just this reason 2) i suppose if there are checkpoints inside 40 miles, there could be an assumption such as you suggest. jd

[Ray Proudfoot]

Would you like a log for the first point? Regarding the second it might be that the final waypoint in the plan supplied to RC is outside 40 miles but the user wishes to fly a STAR selected in the CDU. Bear in mind this is a user-selected option so it would only be selected if a STAR was to be flown. Otherwise the default option of doing nothing would give you radar vectors for an approach and landing.

[Dave Morgan]

Hi. Would it be easier (!) to move the request for a STAR from the second contact with Approach to the first? It's been a while since I flew anything other than Flight Unlimited but from memory when Centre tells you to contact Approach you can only say 'Hi, I'm me, in my plane and here.' until Approach has given you vectors, whereupon if you're quick you can refuse and ask to follow a STAR. A second option in that first contact (along with the existing 'Hello...') would be more useful, something like 'Hi, I'm me, in my plane, here and I'd like to fly a STAR.' I guess in that case that JD would have less to recreate and more to shuffle around in any upgrade. Cheers,D

[jordanal]

1) :-) it's been a while, but i'm pretty sure it's coded to wait 90 seconds. maybe it's 90 seconds from the time the app controller starts talking to you. i'll look back at the code. but i remember 90 seconds was in there for just this reason jd

In all my years of using RC, I've never had more than a few seconds before Approach gives me inital approach vectors. At least one wav loop must play before I get the 'ILS' option in the menu. Now, Otto almost always has comms at this point but that should not matter and if it does, it needs fixed. I almost always go ahead a start the vector descent to the initial approach altitude but at the same time, ignore the lateral instruction while go through the 'Request ILS' menu. No where have I ever seen anything close to 90 seconds to get ILS. The 'Request ILS' menu item should be reprogrammed to be available right after I or Otto leave the Freq to get weather before the 40nm mark.