I have bee a RC4 user for years and years... never had too many problems with it. But with a new computer and FSX coming along, I have been using FSX more and more, and therefore RC4 for FSX. So, now I see my issues compounded and need to finally look up and ask.Now,... I have 3 issues.... just throwing it out there while I'm at work.1. Time Lag,... I'll look more into this tonight after work. Yes, I do have ASE, and yes it is updated to the latest build - This is especially bad when on the ground in pre-flight mode. There's a lot of lag between commands and actions. For instance, I am usually having to wait for T/O Clearance on the runway for a couple minutes.2. Why does it descend me 40 miles before my preferred TOD? - You'd think that there would be an easy configuration in RC4 to say be at this waypoint at this altitude? NO, it is not too busy around the airspace, and YES this happens every flight! It is very annoying particularly because it increases my overall flight times by reducing my altitude way too early and therefore my speed too.3. Whats with the 20 miles finals? So I come in at a waypoint 10 miles south of the field and am asked to turn 90 left/right and fly for 20 miles before doing a 180 and lining up with the runway... you ask for a short runway, visual, or IAP and they all of a sudden release you from any vectoring?Anyone listening and have comments? ANy of this going to be improved in RC5?thanks,Justin

See my comments below within your quote in italics:

I have bee a RC4 user for years and years... never had too many problems with it. But with a new computer and FSX coming along, I have been using FSX more and more, and therefore RC4 for FSX. So, now I see my issues compounded and need to finally look up and ask.Now,... I have 3 issues.... just throwing it out there while I'm at work.1. Time Lag,... I'll look more into this tonight after work. Yes, I do have ASE, and yes it is updated to the latest build - This is especially bad when on the ground in pre-flight mode. There's a lot of lag between commands and actions. For instance, I am usually having to wait for T/O Clearance on the runway for a couple minutes. In general as far as RC computer performance be sure Display Text and Prerecorded Chatter is off. Try running RC without ASE to see if you have an improvement. While ASE directly uses Sim Connect RC also uses Sim Connect via FSUIC4. There is in FSX and ASE high traffic inter process messaging within the Windows processes that can slow things down.2. Why does it descend me 40 miles before my preferred TOD? - You'd think that there would be an easy configuration in RC4 to say be at this waypoint at this altitude? NO, it is not too busy around the airspace, and YES this happens every flight! It is very annoying particularly because it increases my overall flight times by reducing my altitude way too early and therefore my speed too.RC has a fixed estimate of vertical descent ratio to get you down to a crossing restriction altitude just inside 40 nm out from destination. Continous descent to destination is not approved in many locations and is still experimental here in the U.S. as advised by our real world ATC personnel in a few locations. Many ATC managers are against its use because it make ATC traffic separation more difficult in terminal areas. They prefer a strata separation in most cases. A STAR implementation with altitude restrictions is being looked at which will be user configurable if desired. Your TOD using I believe the 3:1 descent ratio to meet those restrictions including the standard 40 nm altitude restriction now present.3. Whats with the 20 miles finals? So I come in at a waypoint 10 miles south of the field and am asked to turn 90 left/right and fly for 20 miles before doing a 180 and lining up with the runway... you ask for a short runway, visual, or IAP and they all of a sudden release you from any vectoring? Depending on your approach angle entry into RC will assign one of three methods as described in the manual. At many airports in poor visibility and high traffic times ATC will extend final to space out aircraft. If you look at many high density traffic airport approaches they can mimic VFR rectangular traffic legs but are extended much further out. The base leg of an IFR entry is at first 90 degrees to the runway then 45 degrees or less to intercept the localizer. In VFR visual approach conditions they can depart from the legs of a standard pattern entry 'cutting corners' and descending in the pattern for a shorter final by going to base earlier. Once you are granted an IAP or visual approach you do your own navigation.RC will come alive again when it is time for you to contact tower. I can't recall if shorter downwind request was in 4.3 but if so RC should quickly turn you to an intercept vector at an advised altitude to enter final. If you get the IAP the altitude advised is your intercept altitude for the glideslope or extended centerline.Anyone listening and have comments? ANy of this going to be improved in RC5?Yes, there are significant improvements requiring a large code rewrite for RC. There are some real world private and commercial pilots in the beta test team and quite a few real world ATC current and retired controllers within and outside of FAA jurisdictions that comprise a dedicated real world advisory committee. The approach phase is not fully coded yet and its desiign is not yet feature frozen.thanks,Justin

See my comments below within your quote in italics:

Thanks for the response, greatly appreciated...I guess I'll try and select IAP always fort an approach then. It would be nice if it was part of the options before cranking up RC4. In big airports it can be quite a pain to select the correct approach, there are so many menu selections. Though with the lag issue, which I'll have to experiment with, it becomes a pain in between all of the other orders given by ATC during that phase of flight. I understand the descent rate aspect... though it seems kind of arbitrary to be at 11,000 or 12,000 feet 40 nm before the airport.... it makes for a really long approach phase. Understandable with non-controlled airports but not with standard STARs.Looking forward to future improvements and developments.Thanks again,~Justin

I have bee a RC4 user for years and years... never had too many problems with it. But with a new computer and FSX coming along, I have been using FSX more and more, and therefore RC4 for FSX. So, now I see my issues compounded and need to finally look up and ask.Now,... I have 3 issues.... just throwing it out there while I'm at work.1. Time Lag,... I'll look more into this tonight after work. Yes, I do have ASE, and yes it is updated to the latest build - This is especially bad when on the ground in pre-flight mode. There's a lot of lag between commands and actions. For instance, I am usually having to wait for T/O Clearance on the runway for a couple minutes.2. Why does it descend me 40 miles before my preferred TOD? - You'd think that there would be an easy configuration in RC4 to say be at this waypoint at this altitude? NO, it is not too busy around the airspace, and YES this happens every flight! It is very annoying particularly because it increases my overall flight times by reducing my altitude way too early and therefore my speed too.3. Whats with the 20 miles finals? So I come in at a waypoint 10 miles south of the field and am asked to turn 90 left/right and fly for 20 miles before doing a 180 and lining up with the runway... you ask for a short runway, visual, or IAP and they all of a sudden release you from any vectoring?Anyone listening and have comments? ANy of this going to be improved in RC5?thanks,Justin

1) if this is reproducible, then make a log, make sure you click debug before loading the flight plan. i can tell you why there was a delay.it could be a number of things. it could be a departing a/c isn't far enough away. it could be i'm looking at all the arrivals, and determining if i can squeeze you on the runway. it could be you aren't quite close enough to an imaginary point, on the taxiway. that can usually be fixed by clicking the rebuild rc scenery database (make sure you have the latest makerwys.exe downloaded, installed first). if the lag is between the time you line up, and the time you are cleared for takeoff, that could also be caused by slightly out of date runway info, which rebuilding the rc scenery database will help with. it could be an a/c is crossing the runway at the far end of the runway. any number of things.2) the calculations to determine when to start your descent, has to work with every a/c. it has to be generalized, and it is just math in the end. you can always request the descent be at pilot's discretion. that will allow you to descend when you are ready. but, you have to have the comms. pilot autoreply has to be off. and you need to be sure that you make the crossing restriction.3) i don't see how you can be at a point 10 miles south of the airport. you would already have been switched to approach way before then. the vectors would have started way before the 10 mile point. maybe you can send me a screen shot of the gps display, for this approach that you are talking about. i might be able to explain better what happened. also include a little narrative if possible, of what approach told you to do, and when - to match what the gps shows.jd

There was just another post here where the latest full FSX release of FSUIPC4 speeds up responses with ASE present. FSUIPC 4.70 is at the main link:http://www.schiratti.com/dowson.html