Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Major bug in RC3

Featured Replies

On my way from KIAH to CYYZ - passing over Evansville in Indiana some 488 miles from Toronto, RC3 decides to forget about the flightplan and tells me the distance to Toronto and an angry man tells me not to exceed 250 kts. - and i can choose visual landing etc.. No way i'm going to fly with 250 kts. - with 290 there's still almost one hour left and i'm in FL350 - not very logic.What's going on? I don't assume i can do anything about that...??So - a ruined flight..

  • Commercial Member

i'd have to see the flight plan. where was the last checkpoint in your flight plan?why don't you copy/paste your .pln file here, and let me look at it.

[flightplan]title=KIAH to CYYZdescription=KIAH, CYYZtype=IFRroutetype=1cruising_altitude=35000departure_id=KIAH, N29* 58.83', W95* 20.38', +000095.14departure_position=S PARKING 3destination_id=CYYZ, N43* 40.63', W79* 37.83', +000567.59departure_name=G Bush Intercontinental/Houstdestination_name=Toronto/Pearson Intlwaypoint.0=KIAH, A, N29* 58.83', W95* 20.38', +000095.14,waypoint.1=DAS, V, N30* 11.38', W94* 38.70', +000000.00,waypoint.2=LFK, V, N31* 9.74', W94* 43.02', +000000.00,waypoint.3=EMG, V, N32* 24.09', W93* 35.71', +000000.00,waypoint.4=WOOTN, I, N33* 30.66', W92* 54.95', +000000.00,waypoint.5=MATIE, I, N34* 5.70', W92* 33.04', +000000.00,waypoint.6=LIT, V, N34* 40.66', W92* 10.83', +000000.00,waypoint.7=DEVEN, I, N36* 49.72', W89* 19.46', +000000.00,waypoint.8=PXV, V, N37* 55.70', W87* 45.74', +000000.00,waypoint.9=IMPEL, I, N38* 21.57', W87* 4.98', +000000.00,waypoint.10=JUDDI, I, N38* 45.56', W86* 26.41', +000000.00,waypoint.11=KURTZ, I, N38* 58.33', W86* 5.56', +000000.00,waypoint.12=BIGXX, I, N39* 19.86', W85* 29.85', +000000.00,waypoint.13=FYLLS, I, N39* 54.41', W84* 37.83', +000000.00,waypoint.14=ROD, V, N40* 17.27', W84* 2.59', +000000.00,waypoint.15=DJB, V, N41* 21.48', W82* 9.72', +000000.00,waypoint.16=KEEHO, I, N41* 55.06', W81* 49.86', +000000.00,waypoint.17=BROKK, I, N42* 19.89', W81* 34.92', +000000.00,waypoint.18=YXU, V, N43* 2.28', W81* 8.92', +000000.00,waypoint.19=YYZ, V, N43* 39.48', W79* 37.90', +000000.00,waypoint.20=CYYZ, A, N43* 40.63', W79* 37.83', +000567.59,It started with waypoint 8 PXW. When he started with his 250 kts. i had just passed that waypoint. On the ADVdisp window it said CYYZ 488 miles and i was told not to exceed 250 kts. A bit premature i would say?? :-)Had to cancle the flightplan and land in Cleveland. Parked at the gate an AI plane drove through my B747.. What a day.. ;-)

  • Commercial Member

if you want to try to duplicate this, fly it again, save me a dat as you cross DEVENthen continue your flight. see if it happens again

Will do that, though it won't be today. When he started with his 250 kts, i had just passed PXW, so are you sure it's DEVEN? If it had gone wrong there i would have heard him complaining for some 20 min. - and i didn't.. :-)I'll do the flight in a day or two and then let you know... I think Microsofts ATC have done something similar once, but never with RC 2.2. OK - once i had made a flightplan which took me just west of KSFO down towards Salinas and back - then it send me directly to KSFO, but i was of course very close to the airport. Here i was 488 miles away, so...

  • Commercial Member

most times i need the state of rc/fs prior to the nasty event. saving after the event doesn't really help me debug it. i have to fly into it :-)

Yes - i can see that JD. I just was so confused when it happened that i didn't think of that. Of course i didn't have the option to call up and ask for permission to land elsewhere, but perhaps i should choose an airport in the area as the secondary airport, just in case - if it's an option. Since he kept talking about "not exceeding 250 kts", i assume he expected me to be at FL100 - but i was at FL350, so i would probably have to land manually anyway? ;-)It's probably not that "major" anyway - my mood was just very low.. hehe

  • Commercial Member

i'm just curious what happened.you should have declared an emergency, and had fun with that section of the code ;-)looking forward to seeing this myself and seeing what happened.

Hi JdMade the flight today again and everything went smoothly. Beats me what happened. But it was so obvious that the program assumed i was about to land in CYYZ. It had left the course heading straight toward CYYZ with the infamous message that i should not exceed 250 kts. And it wasn't me - i was sitting in my sofa when it started... :-) (There should be an option to say "shut up" to the controller in such a situation - or at least to Ruthanne, who like Jamie keeps saying "Roger OK" in an eternity!! :-lol To the best of my knowledge, i didn't have the emergency option when this happened. Only thing was that i e.g. could choose a visual approach or go on to one of my alternative airports. But at least i can cancel the program now and then land manual, though it's not the best alternative.. ;-)Or maybe someone don't want me to land in CYYZ? I had to abort the landing today, as it was a pea soup in the Toronto area and head on to Montreal instead which was my alternative airport... Hope this was a one-time event.

  • Commercial Member

keep scrolling through the menus. emergency is always available on departure, center and approach

Must admit i'm still a newbie, JD, but thank's for pointing it out for me. I'll go for that solution, should it ever happen again.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.