PeteP

You don't really give much information to go on but one place to check would be your rcv30winwood directory. You should have a series of directories numbered from 2 consecutively upwards to somewhere between 10 and 13 depending on extra sets downloaded. If you only have a few of these directories or there is a gap in the numbering, this might explain why RC is only selecting a few controllers.Pete

Mike,This has been covered here on a number of previous occasions but I'll run through it again.RC3 keeps its controller files in the rcv30winwood directory in a series of directories numbered (named) from 2 sequentially upwards - the upper figure depends on how many extra sets have been downloaded but is usually around 12 or 13. The directories 0 and 1, incidentally, contain the co-pilot and pilot respectively.To remove Francesco's set, you can either rename directory 5 to something outside the 2 - 12 number sequence or, if you're sure you won't use it again, just delete the whole directory. You'll then need to reinstate the numeric sequence - RC3 stops looking for controllers when it finds a gap in the directory numbering. Probably the easiest way would be to take your highest-numbered controller directory (12) and rename it as 5.The good news is that RC4 automates this process for you, allowing you to select or deselect pilots and controllers by a simple mouse click.Pete

You're welcome - let me know if it cures the problem.There are many better flight planners available than the built-in FS9 one and each has its strengths and weaknesses - and its fan club! However, for a complete novice, I'd recommend Ernie Alston's FSBuild2. It's payware, but worth every penny.Pete

Good grief, whatever did you use to produce the YSSY-YSCB plan? Whatever it was, it's produced a corrupt flight plan - all those YMs should not be there and I'd guess your having the same problem with the plans that contain lots of EGs and EIs. It's no wonder RC was having problems sorting it out.So that you can check that it's your flight planner that's causing the problem, I've recreated (as near as I can) your flight plan in the proper format. I removed YGLB form the route as this is an airport (Goulburn) which is not suitable as an navaid in an IFR plan and you've already got the Goulburn NDB (GLB) which is on the airport so only one is necessary anyway. Also, you had both the Canberra VOR (CB) and the Canberra NDB(CB) in the plan so I left one out for ease of planning. I think you'll find this cures your departure problem.Pete

Yes, you can use RC with the LDS 767 without problem. You'll need duplicate flight plans, though - one in *.rte format for the FMC and the other in *.pln format for RC3.If by "will the co-pilot work", you mean will it control the autopilot, the answer is "no" but all other co-pilot functions will work normally.Pete

You're very welcome.PP

>what would be the difference in procedure?

Those of you who enjoy flying real-world routes might like to know that I've just uploaded 130 B767 flight plans in *.rte format which are usable in both the LDS and the PIC FMCs. These are real plans that have all been flown during the past 4 weeks and they should be available soon from both Avsim and Flightsim as ldsfplv1.zip.The plans cover a wide selection of flights from a 37 minute positioning flight to 10 hour plus "long-haulers" from Europe to the US and Caribbean. If you really have some time to spare there's also a 13 hour 24 minute plan from Heathrow to Singapore to try! Especially for RC3 users, the zip file also contains an identical set of plans in *.pln format for use with Radar Contact.Pete

Those of you who enjoy flying real-world routes might like to know that I've just uploaded 130 B767 flight plans in *.rte format which are usable in both the LDS and the PIC FMCs. These are real plans that have all been flown during the past 4 weeks and they should be available soon from both Avsim and Flightsim as ldsfplv1.zip.The plans cover a wide selection of flights from a 37 minute positioning flight to 10 hour plus "long-haulers" from Europe to the US and Caribbean. If you really have some time to spare there's also a 13 hour 24 minute plan from Heathrow to Singapore to try! Also in the zip file is an identical set of plans in *.pln format for use with the FS2002/03 GPS and programs such as Radar Contact.Pete

Try www.ais.org.uk/Pete

>>How is the lat/long of centerpoint calculated <

Wow, now there's novel! These sort of posts are usually from Americans complaining about too many British controllers in RC - nice to see one the other way around for a change. :-) Unfortunately, although there are several Brit controller voice sets, there's not much you can do about getting British pilot/co-pilot voices in RC3. Scott Campbell has released (http://fsflightdeck.com/rcv3) a few extra voice sets for this purpose but they're virtually all American (amusingly described as having no accent!:-)) and not a single true Brit among them. RC4 has an option to select which of the available voice sets you want to use as pilot/co-pilot but the only real solution for RC3 is to record your own set. The co-pilot is voice set 0 and the pilot is voice set 1 in your Winwood directory.Pete

No, you haven't mis-configured anything and yes, it's perfectly normal in RC3. The controller and pilot voices are (mostly) recorded by the RC beta team members and since it's an international team and you're just as likely to find an American controlling at EGCC as you are a Brit at KMHT.RC v4 makes it easy for you to be as xenophobic as you want by providing a simple interface to allow you to chose which controller and pilot voices you want to use. It's also possible to do this in RC3 but you have to do it manually. The controller voices are kept in the "winwood" directory in folders numbered from '2' sequentially upward - the upper limit depends on how many extra voice sets you've downloaded but it's probably around 12 or 13. Listen to a *.wav file from each of these folders and rename the folder(s) that contain the voice(s) you don't want to use. You may need to renumber (rename) some of the remaining controller folders so that the numbers run sequentially from 2 upward - if I remember correctly, RC3 stops looking for more controller folders when it finds a gap in the number sequence.The basic procedure is the same for removing pilot voices.Pete

>loaded the .pln in rc? post your .pln file hereHe already has, jd - see message #7. I suspect that the departure runway problem he had was with the PMDG FMC and not RC - I had the same problem with the FMC when I flew the plan.PP

No, I flew it with the "Fair Weather" theme. I wanted to depart from 4 but that didn't seem to be in the FMC so I had to use 13. Let us know what happens when you re-fly the plan.Pete

Hi Andy, I flew your plan using RC and the PMDG 737NG without being able to recreate your problem. The FMC's tracks agreed with RC's to within 1 degree throughout the flight so I'm afraid I can't help on this one. Maybe jd has some more ideas.Pete

Errrr... ask me what? :-hmmm Pete

Errrr... ask me what? :-hmmm Pete

You're probably thinking of the PSS problem which was dropping the first waypoint. Doesn't seem to apply here - looks fine in the PMDG FMC. I'll fly it later this evening - I'm too busy watching England beat South Africa at the moment!!!PP

Oh, well that puts paid to my theory then. Other than double-checking that the *.pln version for RC and the *.rte version for PMDG of your flight plan are not different in any way, I can't think of anything else that might cause this. If you want to post the route you used here I'll try flying it for you and see if I get the same problem.Pete

You're not by any chance flying a direct track between those airports without a waypoint in between or with more than about 250 nms between what waypoints you do have are you, Andy? RC3 is not especially good at the Great Circle tracks required over that sort of distance so that might be your problem.Pete

Done.PP

>i only see qantas and qanta jetconnect in the official>document. do you mean jetconnect?jd,Jetstar is there - it's entry number 3205 on the "By Operator" tab.PP

Don't worry, Janosch, I think jd has been working so hard sorting out various ai problems with V4 that he's forgotten what we've actually done with speed limits in Europe (and other non-US areas) in V4! I think he's getting confused with the 250kt relief that's available to "heavies" operating in the US which is on a menu item.We actually sorted out the non-US departure speed restriction for V4 several months ago and it applies to all aircraft and not just to heavies. The procedure is very straightforward and no menus are involved. For a flight outside US/Canadian airspace (the option is greyed-out within North America) simply activate the "Speed Restriction, No" check box and when you contact "Departure", you'll hear the phrase, "No ATC speed restriction". You can then accelerate to any speed you feel is appropriate regardless of your altitude/FL.And as for the comment that, "no mention of a high speed approach has ever been mentioned", well, as I said, he's been working very hard lately... ;) ;) ;) Pete

Luigi,Although the option to use different Transition Altitudes is availabel in RC3, the program handles them incorrectly on 2 counts - 1, it requires the T A to be input in flight level format and 2, it calculates an incorrect Transition Level from this input.There is, however, a simple workaround. Take the published TA, add 1000 then convert to flight level format before input. For example:Published Transition Altitude = 5000ftAdd 1000 = 6000Convert to flight level format = 60What you're actually doing is calculating your own Transition Level and so, in the above example, by inputting 60 on the Controller Info page, RC will use altitudes up to and including 5000ft and flight levels above that. This workaround wouldn't be any use in the real world with a QNH below 1013.2 but it works just fine in Flight Sim/RC.Andy,Well done for spotting the input format error in RC but to get it to handle a TA of 11000ft correctly, you need to input '120'. This will give you altitudes up to and including 11000ft and flight levels above that.Pete