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 shuts down

Featured Replies

Hi

I keep getting a shutdown of RC4, with the message....."The exception,Unknown software exception,occurred in the application 0x770d26fc. and I have to close RC4.

Any idea what would cause this? It has been fine till now.

Thanks.

WIN 7,FSX.

Dennis

Dennis Elliott
 

All airports? All flightplans?

 

Is this new behavior?

 

In the error window click details and see what module failures are reported if any.

  • Author

It seems to be one flight plan in particular,EDDV (Aerosoft,Hannover)

to EDDM. Happened 3 times in a row. I will try it again tomorrow and try to get more info if it happens again.( I just checked the event log and it says,,Faulting module ntdll.dll, version 6.1.7600.16645)

I flew another flight just after this just to check,and all was just fine,so not so bad after all.

Thanks.

Dennis

Dennis Elliott
 

ntdll.dll shows up on many error reports (very common) and is not unique to an application.

 

It could be a scenery or ai error based on time, date, weather. It could be caused by RC not trapping an error with FS and something returned to it via FSUIPC caused the crash. RC4 will hang if FS aborts or is shut down before RC.

  • Author

OK

Could be this airport. I can not seem to change the ATIS freq (in f4.csv)to 135.57 for some reason,it seems to prefer 118.00. Fist time I could not change one.

Thank you Ron.

All the best.

Dennis.

Dennis Elliott
 

You might have a corrupted f4.csv that is causing the rc crash. It is very fussy on formatting those lines. One clue is that the airport you edited in f4.csv does not accept a change.

 

If you wish to use frequencies extracted from your scenery there is a recent manual optional new procedure to do that and it must be carefully done to avoid corrupting rcv4's critical data files then requiring a reinstallation. First order of business is to make sure your makerwys.exe is current and then run the rc scenery rebuild, then close rc. Now make safe copies of rcv3.dat and keyboard.dat in your rcv4 folder to another safe folder outside of rc.

 

Now do not run rc again until the following steps are complete as at this point it will crash RC and possibly wipe out rcv3.dat. In your rcv4\data folder rename f4.csv to f4.hld. in your FS folder is an f4.csv file created by makerwys.exe. It is frequencies extracted from your FS default and add-on airports. The designers determine the frequencies. They can be changed in the scenery by a suitable utility such as ADE9x or perhaps AFX. Copy f4.csv in your fs folder to your rcv4\data folder as f4.csv. You should now be OK to go. Load your plan into RC and check out the frequencies.

 

FWIW, we had a similar problem when the extracted f4 was added to makerwys. It turned out that some airport names had commas in them which shoved the fields over. Pete Dowson fixed that in his code and all was well.

 

The reason that you make safe copies of rcv3.dat and keyboard.dat is that an error in the data files can wipe those out. Having safe copies enabled restoration without an RC reinstall.

 

Once your f4.csv is OK make a safe copy of that in that backup folder.

 

This is an optional "unofficial" procedure, BTW, and jdtllc, myself, and Pete Dowson can not take responsibility for any ill effects. It was worked on by Pete and myself.

  • Author

Thanks Ron.

I did what you said,and after doing all that I checked the new f4.csv file and the ATIS freq for EDDV is 136,575 as it should be,but when I load that flight,it still says 118.00. I can change it manually right there,but every time I come back to that flight it is back to 118.00

It is a mystery!

Thanks.

Dennis

Dennis Elliott
 

If you edit in the controller panel those changes are not kept between RC sessions as you probably know. Also place a check mark next to a blank or 0 entry to be able to add your frequency for this session only.

 

Which frequency is coming up 118.75 that you wish to change.

 

There is a fix in the f4.csv from makerwys.exe. Here is the correct field list:

ICAO Code, name, Wx/ATIS, CD, Ground, Tower, UNICOM, (unknown), Approach, Departure

 

unknown might be CTAF, not used by rc4. Ground and departure were reversed.

 

I only have the FS9 default EDDV and the line is:

EDDV,Hannover,132.12,0,121.95,120.17,0,0,0,0

 

The current Hannover information shows EDDV uses 136.575 for ATIS. GND is 121.95 and TWR is 120.175 as in that line. There is no radar in the extracted data. Currently there is only a listing for Bremen local radar to be used.

 

The Center frequency to start is pulled from an FIR data file (region) of the assigned center calculated from airport or route coordinates as required. That is a different .csv file.

  • Author

I can change any or all the other frequencies except ATIS. I just changed ground to 122.60 and that is what I get when I start RC4. then back to 122.80 and that is now back. so for some reason it has a problem only with ATIS.

It would be interesting to hear from another user with Aerosoft German Airports 2 to see what is happening with their version of EDDV.

Dennis

Dennis Elliott
 

Why don't you paste in the f4.csv line for EDDV in a reply here. I wonder if RC does not like a frequency in that range. Just for a test try replacing 136.575 carefully preserving format and spacing with 132.12 and see if it accepts that. I notice in f4.csv extracted from FS9 that only two decimal places are used so you can also try 136.57.

 

Edit:

I put in 136.575 in f4 and on the controller page it returned 118.00. I then tried 136.57, same result. I put back 132.12 and that was OK. It seems to be a frequency range problem.

 

I tried two other airports with 136.xx ATIS (EGAC and EGLC) and it has the same problem. This is an RC bug as it should be OK to go to 136.975, the top of the VHF communications range.

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.