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.

Strange problem with RC.

Featured Replies

When itry to connect to RC after starting my flight, the plane moves to the runway area then rises into the air "too low flaps, too low flaps" and crashes into the ground. I have tried rebuilding the scenery data base, but no luck. Any idea what could be going on here?

Thanks.

I assume you are not using an rcd flight but just loading a parked flight into fs and the matching pln file int RC. Be sure your .pln departure airport is the same as your parked flight loaded into RC. (That has happened.)

 

If you are a dual FS version user your have two folder installations of RC for each FS version. Be sure you load the correct path for each build for the RC installation (FSX or FS9) you use. FSX and FS9 data is different.

 

Be sure you have the latest versions of FSUIPC and Makerwys from:

http://forum.simflight.com/topic/66136-useful-additional-programs/

http://forum.simflight.com/topic/66139-updated-modules/

and rebuild RC's scenery database again if you update makerwys. Be sure you rebuild the database from within RC and if on an RC client pc to an FS host pc via WideFS you run makerwys.exe first in your FS folder.

 

In your rcv4\data folder right click on r4.csv and check that the date-time modified tamp is correct for your scenery rebuild session.

 

Test RC with only RC and FS running and no other add-ons. In FS be sure the move aircraft on loading a plan option is off.

 

Usually this type of problem occurs with an RC data vs. departure destination coordinates different in the .pln.

 

Search this forum for known previous cases.

  • Commercial Member

rc will move your plane to the departure airport, if you aren't there. load the flight plan into fs first, so the plane is where it is supposed to be. then rc won't need to move it.

 

jd

  • 2 weeks later...
  • Author

After much tinkering i think i have found the culprit..London Heathrow (EGLL). Many scenery changes for EGLL make sugnificant changes to the airport and it becomes much larger. wheras, other airports have the "shell" and the deatail is changed. I haven't tried payware for EGLL but did try several scenery changes including UK scenery freeware, same result, RC won't work., the plame slams into the ground. Did rebuild scenery database, updated make runways ....Same result. All other airports are fine after a scenery change.

 

Thanks.

Did you find any solution to this? I too have the same error!

And indeed it appears to be related to addon scenery in the london area. It doesn't work for me at either Gatwick or Heathrow, where I'm using UK2000 Extreme at both... I think something is broken in RC4 with these airports.

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author

Gatwick will work if i don't have Heathrow installed. If i do install Heathrow, both Gatwick and Heathrow cause RC to slam the plane into the ground.

See if either one modifies AP default airport profiles. If a developer changes these than multiple airports in that default airport area are affected.

 

Check the RC\data a4.csv file (use a text editor and don't save anything) and get the coordinates for each. Then reply here with those two lines from a4 and then paste in the coordinates from the flight plan files.

 

It is necessary to check coordinate sync.

 

Be sure you are running from here:

http://forum.simflight.com/topic/66136-useful-additional-programs/

makerwys.exe version 4,615 and rebuild the scenery database after installing.

 

The fact that EGLL also affects Gatwick is suspicious.

 

Does Gatwick run OK if EGLL is not activated? Is Gatwick also a UK2000 scenery?

Hi Guys,

 

All of UK2000 sceneries work well with RC.You must make sure that you do not have a conflict with any other versions of the scenery and also keep them near the top in your scenery listings

 

I have flown from both Gatwick ,Heathrow and Liverpool in the past ten days using the I Fly 737ng and not had any problems.

 

It would appear to be somthing to do with your set up.

Norman Bowman

Here is how to check the scenery priority recorded during the scenery rebuild:

 

In your FS folder open runways.txt in word or wordpad, not notepad, since it is a huge file. First search for "Airport EGKK". First you will find a default section with a path to an AP filer. Search again and for any afcad type or add-on scenery you will find a deletions section with a path to the add-on folder. Search again and you eventually should find a section with runways, etc listed. Keep searching for sections "Airport EGKK" until no more occurrences are found. The last deletion section and the last runway section should point to your UK2000 EGKK scenery folder path.

 

Do the same for EGLL.

 

If you still have trouble you might try reversing in the fs scenery lib the priority positions of EGLL and EGKK to see if that has an effect in case a certain installation order is required.

I currently have UK2000 EGLL and EGKK at the top of my priority list, so should i move them down some?

James W

 

Banner_FS2Crew_Supporter.jpg

Just swap their positions at the top to see if that makes any difference. EGKK should be at the top with EGLL following to prevent any EGLL excludes from affecting EGKK. Have you checked out the product forums?

 

http://www.uk2000scenery.org/forum/

 

In the makerwys log "runways.txt" the EGKK section with the runways listing should be the last entry with no EGLL section deletions following. Refer to previous replies if you are having problems on interpreting runways.txt.

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.