RC has never done this before and all of a sudden it is fairly consistent. I get instructed to taxi into position and hold. Once I do, the cleared for TO call never arrives. I've been taking off without clearance, and the "Cleared for TO" call will come about 2-3 seconds before I rotate. I have run makerwys recently, so all of the .csv files are up to date. I have recently upgraded to 5.1, so it may be related to that. Does anyone have any idea about where RC is getting the position it thinks I should be in when holding for TO is?

Two locations I've recently had this issue at are T2G KMCO RW36R and FB KDEN RW08

If the problems are still you switched to 5.1 then that is the factor. Have you rebuilt the scenery database? v5.1 could be different to v5. Run MakeRwy again just to be safe.

Check the Deviations in General. They should be 15, 300 and 10.

@MDFlier, did my suggestion help?

@Ray Proudfoot I did rebuild the database but it did not fix the issue.

I started troubleshooting a different problem at KMCO and found out why RC4 was behaving incorrectly there. I was using the inibuilds exclude file for KMCO to block out the default scenery that was bleeding through and it is what was causing the RC4 problem on my system at Orlando.

What put me hot on the trail to fixing it there was that after I landed at KMCO and tried to use the airport map in the NGXu to taxi to gate 43. When I got close to where the map said gate 43 was I noticed that the terminal building had gate numbers 17 through 28 on it. Those gates are in airside 1. Gate 43 is in airside 3. My suspicion was (is) that whoever made the inibuilds exclude AFCAD ended up using the default KMCO scenery AFCAD as the base of the exclude instead of the original Taxi2Gate AFCAD file.

I spent a rainy day last week learning to use ADE and buiding a new KMCO AFCAD that excludes all of the default scenery bits that were bleeding through (taxi signs, towers, buildings, etc.), and adds the missing windsocks and runway lighting, and also adds a new vehicle parking with vehicle links in each of the 4 terminals that allows a fuel truck to spawn nearby so I don't have to wait 30 minutes for the fuel truck to arrive. I've only had 1 flight out of KMCO since I built it, and RC4 did correctly recognize that I was in position and holding.

I guess I'll just meed to wait until it happens again at a different location to take it on a case by case basis. I'm pretty sure that it also happened at KMSP, which is a Flightbeam airport. I suspect that I will find a different issue there as I seriously doubt that FB jacked up an AFCAD that bad.

That's some detective work! Well done for finding the problem and fixing it. AFCADs can be the bain of our lives!

1 hour ago, Ray Proudfoot said:

That's some detective work! Well done for finding the problem and fixing it. AFCADs can be the bain of our lives!

Thank you, but my adventure is not over. I'm a bit perplexed.

I ran Lorby and exported the scenery.cfg and then ran makerwys from a command line. It found 55391 runways.

I restored the original scenery.cfg and exited Lorby. I then ran makerwys again, and it found 54119 runways. It also appears to have run it's own tool "LorbySceneryExport.exe" that is in my root P3D folder along with makerwys.exe. Both have the same create date and time, so it looks like Pete packaged it together with makerwys (I have version 4.91).  When I run makerwys without running Lorby first, I see a "MakeRwys_Scenery.cfg" file appear in my root P3D folder just before it builds the runway information. I think that the 54119 runways it finds is the actual correct number of runways. I think the 55391 runways that it finds when I run Lorby first include some duplicates because the add-ons are getting appended to the scenery.cfg file twice. Once when I do it, and a 2nd time when it makerys runs the LorbySceneryExport.

So... I'm going to run makerwys standalone and call that good.

But... Me being the "inquiring mind", I decided to "start over" and delete all of the csv files that makeryws creates in the P3D root folder, as well as the a4.csv and r4.csv, files from RC4x\data. My logic is that when I started RC it would see the missing a4.csv and r4.csv and would initiate the makerwys process (with auto-Lorby) and would then rebuild the csv files from the resulting makerwys files. That should work great, right? Nope. Makerwys only found 52954 runways. Even worse, the runways.txt file shows this:

Airport KLAS :N36:04:48.1799  W115:09:08.1000  2180.99ft
          Country Name="United States"
          State Name="Nevada"
          City Name="Las Vegas"
          Airport Name="McCarran Intl"
          in file: Scenery\0202\scenery\APX17190.bgl

but NOT this, (which shows up when I run makerwys standalone):

Airport KLAS :N36:04:49.2814  W115:09:08.3994  2180.99ft
          Country Name="United States"
          State Name="Nevada"
          City Name="Las Vegas"
          Airport Name="McCarran Intl"
          in file: E:\P3D5\Addon Scenery\FlyTampa\LasVegas\scenery\ade_klas_xwind.bgl

So... When RC4 runs makerwys, the Lorby exporter does not seem to run first and the add-ons are not found. Just for grins, I renamed makerwys.exe to makerwys.exe.bak and then deleted a4.csv and r4.csv and started RC4 again. I was hoping to find that RC4 was launching a different makerwys from another location. Nope. Got an error. I put makerwys.exe back and started RC4. It ran the process but did not add my add-on airports.

Still testing, but now I have no idea how to get the "correct" data into RC4. If I run makerwys standalone, it builds all of the csv files and puts them in the P3D root folder. How to I get these into the RC4 scenery DB?

Apparently, the runway start locations in the default KMCO are close enough to the T2G add-on runway locations for RC to work. Go figure,

Edited November 14, 20205 yr by MDFlier

I hate replying to myself, but here goes. lol.

I "split the difference". I deleted the RC4\Data\a4.csv and r4.csv files. I then ran Lorby and exported the scenery.cfg file. Then, I started RC4 and it said that it was going to rebuild the database. I let it run as usual, and it ran makerwys, It found 54119 runways (which I believe is correct) and then it replaced a4.csv and r4.csv and went to the normal RC home screen. I exited RC4 and then restored the scenery.cfg and exited Lorby. I think I'm good now as I see all of my add-on airports in the runways.txt file and that same data set is what RC4 used to build the other files.

The part that is confusing me is that when I run makerwys.exe in Powershell, I get a different result than when RC launches makerwys.exe. I have no idea why that would happen. Maybe Pete checked to see how it was launched and made the decision as to whether or not it needed to run the Lorby exporter. 

I think I'm good now. I'll let you know if it didn't correct the issue at my other airports. I'm 99% sure that it has. When I moved RC4 to 5.1, I think I remembering it rebuilding the DB. Not sure. I was moving everything over and it's all a blurr now.

Thanks for your help, Ray. Much appreciated, my friend.

@MDFlier, wow, that’s a lot to digest. One tip. You don’t need to use Lorby’s export facility for scenery.cfg. Providing you have Addon Organiser installed when you run MakeRwys.exe it will automatically scan all your scenery both in scenery.cfg and the add-on entries in Addon Organiser.

I’ve never launched MakeRwys in powershell. Just run it with admin privileges.

Powershell doesn't impact how applications run. It's is just a more powerful console shell than cmd.exe. Programs launched by it operate exactly the same.

I just departed LatinVFR BWI and RC recognized that I was holding in position on 33L. That's a good start.

Edited November 14, 20205 yr by MDFlier

3 hours ago, Ray Proudfoot said:

I’ve never launched MakeRwys in powershell. Just run it with admin privileges.

Well... That was my problem. Set the Lorby exporter and makerwys to run as admin, deleted a4.csv, fired up RC4, hit the button, and walla! She worky fine now.

But there’s no need to run the exporter. It’s handled internally by MakeRwys and Addon Organiser. Don’t ask me how. I used to do it your way but it just isn’t necessary now. Hasn’t been for a long time.

Ray,

        I went looking for more info on makerwys and I ended up downloading version 5.02 from Pete Daswon's web site.

Then, I did the unthinkable. I read the readme file. On page 2 it has a big note in bold red that says:

"NOTE that you should run MakeRunways “as administrator”. This is especially true on Win10. The best way is to mark it needing admin privileges in its (or its shortcut) “Properties – Compatibility” settings (right click on the EXE or the shortcut)."

That was my problem. I did NOT have makerwys set to run as administrator, so Windows prevented it from launching Lorby. This caused it to leave all of my addons out of the data files. When  I taxied into position I was at the location of the addon scenery's runway not at the location of the default airport's runway so RC didn't think I was at the right spot. That's why it never cleared me for TO. I was not sitting where it thought the runway was. 

After setting makerwys to run as admin, it works just like yours. Makerwys automatically runs Lorby and all of my addons are in the data files.

I've since flown out of BWI, MIA, and BOS. RC cleared me for TO as soon as I was in position. Problem solved.  

Edited November 15, 20205 yr by MDFlier

Told ya! 😉 Who’s Pete Daswon? 😁