Hi all. I just received my RC CD and today flew a trial run from my hometown of KSTL to PHNL. RC worked quite well, but I found that as the flight progressed, the frame rates decreased, even in areas with virtually no clouds. Normally my frame rates are around 29 fps, but with RC running, they averaged around 12 fps, and for extended periods they dropped to 4 fps.On another issue, almost immediately after contacting approach, and without a vector being issued (only a 7000 ft altitude clearance was received), Otto Pilot turned the plane around 180 degrees and began flying back where we came from. No further clearance was received and I finally had to end the adventure. At this point, frame rates were terrible and the RC scroll bar and pilot's menu essentially stopped working.Has anyone heard of these problems?Thanks for any input.

Hi Steve,i think i have an answer for your second issue,looks like you didn't cross your first waypoint within 2 NM. RC wants you to cross the first wp within 2 NM and else waypoints within 10 NM.If you don't hear a 'ding' while crossing a wayponit RC waits until you reached it properly. You can access the scroll bar and ask for direct wayponit so you don't have to fly back. While crossing a wp the number in the scroll bar should count up and show you the heading, distance and frequency to the new wp.Hope you understand ? Sorry for my bad english.Carsten

I've been using rc for several years and have never run into the frame rate problem you describe. I would try a few different flights (different airports, different weather) and see if the problem persists. It could have been a coincidence, or it could be related to some particular scenery or weather. Weird.Sidney Schwartz [KPDX]

I've experienced those frame rate problems you describe on flights from EDDK to KPHL. I tried changing all the other variables, such as weather, airplane, display options, but only ending the RC adventure improved performance.Never had such problems with FS2000, and never have problems with RC on shorter flights. Since a search of this forum didn't produce many other accounts of this problem (and I know that other users of RC use it successfully for long flights) I attributed the problem to my setup or something else strange about how adventures work.I'll bet with RC 3.0, since it is not adventure-based, this won't be a factor.

Steve,On the first issue: I can't say since I never saw this, but there's a small possibility that becaue FS turns off ATC when adventures are running, that the AI aircraft left stranded wherever they were can cause a frame hit. Try turning off AI before running the adventure (or after you notice the frame drop) and see if that helps.Second issue: Are you sure you are being turned 180 degrees immediately after contactiong Approach, or after being turned to final? If it's the latter, then it's probable that you are flying a back-course approach to a runway. Which runway are you given at Honolulu? If it IS when you first contact Approach, then that's another issue. Can you check:1) that Jamie or you got weather before your CR2) what runway is active (from the ATIS)3) what your altitude is with the crossing restriction (should be 10000)4) what your final waypoint is5) if you are turning after contacting APC or given final, where Otto will turn on APR modeWith these answers we can probably help.

>On the first issue: I can't say since I never saw this, but there's >a small possibility that becaue FS turns off ATC when adventures are >running, that the AI aircraft left stranded wherever they were can >cause a frame hit. Try turning off AI before running the adventure>(or after you notice the frame drop) and see if that helps.That is exactly what the problem is. But it's easy to fix while you are still flying - just go into options and set AI Traffic to '0'.All the traffic will be deleted and the framerate will go back to whatever is normal for you.-hoo

Sorry for the delay in responding, and thank you for your input. You are correct that the frame rate hit was caused by AI traffic congestion.It also appears that the strange vectoring may have resulted from an old flight plan still residing in FS Flight Planner. Once I cleared the old plan, everything seems to work OK.

it's good to know that it wasn't rc :-)i didn't realize that the ai planes, would cause such a frame hit, even if they aren't in the picture. i guess it makes sense

JD,Since there's no ATC, but the AI is still "on", what appears to happen is that the AI reaches the end of it's command code, gets nothing else, and goes into an infinite loop from start to finish - something like: "did that..." "did That..." "did that..." "Hello?? Anyone there? Hello?" ... "did that..." "did That..." "did that..." "Hello?? Anyone there? Hello?"Y'know - real MS I. :-lol

Hey Gang!Long time no post! But I still read!I have repeatedly experienced the first issue. I have noticed that it occurrs on long flights. Usually, things start out allright and as time progresses, the FPS goes down the drain to 3-4 FPS. I've also done these flights with FSMeteo working together with RC and FS2002. I usually get things back to normal by changing the time of day from day to night or vice versa; this process loads everything back and the program somehow refreshes without having to terminate the flight.On the second issue, the 2nm rule is probably the culprit. RC is very adamant about you intercepting the waypoint within 2 nm's or you will be taken back.Just my 2 cents.Sincerely,Dennis D. Mullert

2 miles for departure procedure waypoints10 miles for enroute waypoints

Hi Dennis,>I usually get >things back to normal by changing the time of day from day >to night or vice versa; this process loads everything back >and the program somehow refreshes without having to >terminate the flight. I believe that any time you force a reload of the scenery (change time, change location, etc.), the ai traffic is reset. That's probably why this is working for you.Sidney Schwartz [KPDX]