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.

FDC 3 with Radar Contact 4

Featured Replies

Hi. Wondering if anyone can help. When I use FDC version 3 with RadarContact 3 there where no problems. With the new version of Radar Contact, Version 4, FDC locks up FS9 when I start my take off roll after the co-pilot says "airspeed active". I'm not using any of thecustom checklists just the standard flightdeck calls.It was suggested to move the FDC folder to a different folder. So Imoved the FDC folder to another harddrive with the same result.This message has also been posted on the FDC forumAny help on this would be great. Thank You.Stephen

First ... Thanks for RC4 ... AWESOME ... I have the same issue as Stephen ... I always fly with ASV, RC, FDC and FS Flight Keeper ... FDC seems to be causing the issue outlined above ... HELP!!!The usual start order is ASV, RCx, FDC, usually FSNav for moving map, then FSlight Keeper. I recall a similar issue when RC3 was published ... and the fix was to start it before FDC .. then there was a fix.Hopefully between you all and Dave March ... you can come up with a quick fix!!!And did I say thanks for all of your hard work!!!!Best wishes for very happy holidays!!!Regards,Paul BenoitKSAN

  • Commercial Member

does the work around not work with v4, or with the patched version of fdc?dave is getting a copy of rcv4, maybe he can figure out what is going on with fdcjd

Hi,I just tried (running RC and FDC on the same nachine) and got exactly the same problem. Forcing FDC to close 'unfroze' FS and RC continues okay.I'll try running RC on widefs next and see what happens.All the best,John

For what it's worth the problem does not seem to occur with FDC running on the main machine and RC running on a second machine via widefs.All the best,John

Hi Folks,Good news is I think I've been able to cure this problem. As you say if you kill FDC then FS and RC continue as normal. Equally if you kill RC4 then FDC and FS continue okay. Had me scratching my thinning hair till the early hours I can tell you.Problem was caused, I believe, by flooding FSUIPC with READs during the actual takeoff phase. At that point in time all FDC is interested in is the increasing speed of the aircraft in order to call out the various speeds plus V1, VR, etc. I guess RC is only interested in monitoring the aircraft to detect when it leaves Terra Firma plus checking for user input to abort the flight, etc. Basically FS simply ground to a halt!!!I've now reduced the number of calls I'm making dramatically! Doesn't appear to have caused any undue problems so I think we're on the right track. I'll hopefully get the update out very soon as I'm just tidying up some other enhancements which were due to be released this weekend anyway.My thanks to the RC team for providing a copy of RC4 for me to track this one down.CheersDave MarchEmail:[email protected] Website:http://www.oncourse-software.co.uk

  • Commercial Member

thanks dave. i'll see if i can find where i'm flooding fsuipc with calls and cut them down. is it after clearance for takeoff? or before?jd

Hi JD,Wasn't suggesting for a minute that RC was flooding FSUIPC with calls but FDC most certainly was. It occurs right after you're cleared for takeoff and start the roll... FDC goes into takeoff mode and simply sits in a loop reading the IAS and making various calls. Without a pause in the loop I was hitting some 2500 calls a second !!!! Ridiculous high !!! Just one that slipped through the net. ;-)I 'guess' RC would be in a similar loop watching to see when the aircraft actually takes off and also monitoring any user input in case of an abort. But I didn't get into checking any IPC logs.CheersDave MarchEmail:[email protected] Website:http://www.oncourse-software.co.uk

  • Commercial Member

i do watch for "on the ground" or not, so i can remove the abort takeoff option off the menu. that's a bout itjd

I'll let you developers dig it out but Pete added some kind of arbitration via an FSUIPC.ini setting that mainly applied to some gauges hogging processes. Perhaps something in there might help. As I recall it was post 3.48 so I'd check the history notes.

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.