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.

RC4.2 Intermittent Crash

Featured Replies

Hi,I'm running rc4.2 with fs9 on W2K. I installed Ultimate Traffic a month or so ago and have been getting intermittent rc crashes during flights which I didn't have before - rc has been usually very reliable. Usually 10 or so minutes into the flight but the timing isn't consistent. On several crashes I got a Run-time Error 5 - RadarContact_fsuipc.rcV4code message. Sometimes there is no error message - rc simply disappears. I had fsuipc 3.709 (I think) and changed to 3.71 and have only had the crashes with no error message but I haven't been running long with this fsuipc version.Seems to happen with any plane I use and I think both center and approach controllers. Can't say if traffic density settings have an effect yet.I ran a log with a resumed flight and last few lines are - >>>>>>>>>>>>>>ERROR> 5 RadarContact RadarContact.rcv4module.chatterSaveWaveI can off course send the full log or another if it helps.Any thoughts?I have W2K, 1GB RAM and a GF-7600GS card, processor is a bit slow at Athlon 2100+, rc and fs9 running on same machine.IanPS on a different note I was looking at VATSIM the other day and noting the lack of ATC coverage was wondering if anyone had thought of setting up an equivalent multi-flyer system but with worldwide ATC coverage provided by something like RC - pilots would then get to fly with other "real" traffic but with a realistic and widely available ATC system? I toyed with VATSIM for a while but most of the aiports and areas I was interesting in simply weren't covered most of the time if at all. Don't know what fsx is capable of here. (Sorry - this should probably be another thread)

I use UT 2 and have no problem. I used it under W98 and XP.Here are some things to look into in general:UT adds a number of AFCADS starting with F1 something. Make sure that if you have any other added AFCADS that you prefer, move the conflicting file out of the add-on scener/scenery folder where I think they are located. Use AFCAD to insure only one AFCAD layer exists beyond the default/stock layer.UT also adds in your modules folder a TCAS dll that might be interfering. This is used with the Palm Spotter and TCAS gauge furnished with it. As I recall there was a patch for this on the Flight1 support forum. Try removing that module running without the Palm Spotter and F1 TCAS gauge. I am not at my FS location now so I can not look into this. It may be causing conflicts with other modules including FSUIPCBe sure you have reinstalled FSUIPC 3.71 or better. Do note officially that it only supports Win XP.Be sure after adding UT you have run the RC scenery database rebuild utility so the new UT-AFCADS are are included. You do this after FS has started and reindexed your scenery, then close it, open RC, and run the utility.UT adds a lot of traffic. You seem to have enough ram but at airports with a lot of AI showing that exerts a performance penalty.

  • Commercial Member

the error indicates that one of the wavs in the chatter directories (84-98) is not in the proper format. with a little more of the log, i could tell you which directory, possibly what wav.did you add/download a new set of wavs?jd

Thanks Ron,I'll look into all your points.JDThanks, I'll email the full log to you. I haven't added any voices recently but did when they first became available. One or two gave me problems with delays as they spoke but I de-selected those.Ian

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.