Having a problem running the Align AIRAC with scenery and get the message "f5.csv is missing..."

 

I've searched the forums and found similar issues but with FSX not P3D V2.5 12946 (or folks that have both FSX and P3D V2).  What I've done to validate (running networked configuration):

 

1.  Paths are all correctly mapped

2.  MakeRwys.exe is the latest v4.6.7.9 from Pete D.

3.  The f5.csv file is being generated in the root of P3D (in my case V:\Lockheed Martin\Prepar3D v2) 

4.  Client computer is able to access the F5.csv via Explorer and open it in Notepad

5.  Tried Run As Administrator

 

Also tried "Rebuild Scenery DB" but that came back with error saying "MakeRwys.exe not found in " ... the clue here is that it appears PATC is using a null/blank for the Path (guess it's using the FSX path definition rather than the P3D path definition and I don't have FSX installed)??  Since I don't have FSX installed (and it's path is null) and only P3D, I have no Path entry for FSX root defined.  

 

I copied Prepar3d.exe and renamed it to FSX.exe ... this allowed me to enter a Path under FSX in PATC and allowed me to do the Align AIRAC with Scenery.  Note: I'm running NavDataPro  1507 Rev 1

 

Thinking all is good ... I imported a Flight plan generated by FSC9.6 using FSInn and my Gate/Parking drop down is empty, nothing I can select ... not good.  So I enter the ICAO manually in PATC ... ENGM still has no Gate/Parking information ... if I try to save I get some error about Selected Index = -1 (which means nothing selected) so I'm certain that's related to the Gate/Parking drop down.

 

So I check FSC9.6 and it has all the correct Gate/Parking info for ENGM (which it gets from the Scenerycfg.cfs (copy it makes)).  Next I check Runways.txt and all the correct information is there for ENGM.  Checked F5.csv and it has the frequency info for ENGM.

 

So that's where I'm at trying to get PATC v1.4.4.2 to work.  I guess what I need to be able to do is recover the original data?  Or will it just be easier to uninstall and re-install?  But I "assume" not being able to Align AIRAC with scenery is going to be a show stopper?

 

On the plus side it does connect to my my P3D v2.5 PC and I get all the correct ATC menus, prompts etc. etc. 

 

Any suggestions?

 

Cheers, Rob.

 

EDIT: I have posted this over at PATC support forum also but requires moderator review.

Hi Rob, looking over some old posts, I noticed that others have had this problem. The way they got around it was to use the MakeRwys.exe that is in your root folder and not click on the Rebuild Scenery Database in ProATC. Some have reported a smaller file size from the ProATC version. I personally always use the version in my root folder and then just use Start Alignment in ProATC.

 

Having a problem running the Align AIRAC with scenery and get the message "f5.csv is missing..."

 

I've searched the forums and found similar issues but with FSX not P3D V2.5 12946 (or folks that have both FSX and P3D V2).  What I've done to validate (running networked configuration):

 

1.  Paths are all correctly mapped

2.  MakeRwys.exe is the latest v4.6.7.9 from Pete D.

3.  The f5.csv file is being generated in the root of P3D (in my case V:\Lockheed Martin\Prepar3D v2) 

4.  Client computer is able to access the F5.csv via Explorer and open it in Notepad

5.  Tried Run As Administrator

 

Also tried "Rebuild Scenery DB" but that came back with error saying "MakeRwys.exe not found in " ... the clue here is that it appears PATC is using a null/blank for the Path (guess it's using the FSX path definition rather than the P3D path definition and I don't have FSX installed)??  Since I don't have FSX installed (and it's path is null) and only P3D, I have no Path entry for FSX root defined.  

 

The problem is that MakeRunways won't work when run from a program on a Networked PC as it would be reading the FS installation details from the registry on the Client, and anyway it wouldn't be able to access the SCENERY.CFG in the ProgramData folders on the FS PC.

 

The facility in ProATCX is designed to operate correctly when ProATCX is on the same PC as FS/P3D. Do as SierraHotel suggests -- run MakeRunways from the P3D base folder yourself then just use the "Align" option, bypassing the way ProATCX tries to run MakeRunways itself.

 

Even if MakeRunways could figure it all out and manage to somehow read the FS PCs registry and the correct SCENERY.CFG file across the network, because the EXE would be running in the client PC not in the FS PC every single BGL file it would need to scan would be getting read across the network then the resulting files written back across. It would take a long long time!

 

Radar Contact got around this problem by first asking if it was a WideFS PC, and if you answered Yes it would simply instruct you to run MakeRunways yourself. Before proceeding to extract the files it needed.

 

Regards

Pete

I had the same error without using on a network, and it was due to the fact I forgot to check P3D in the Pro ATC setup menu. Options/In-flight/  menu at the top of the page. 

Thanks for all the excellent suggestions folks, much appreciated.  The problem appears to be two fold.

 

I did indeed NOT have the correct version selected on the Options | In-Flight dialog, corrected that here:

 

 

That did resolve my ability to run Align AIRAC with scenery.  However, that didn't solve the parking spot issue with ENGM.  As you can see here there are no parking spots for ENGM:

 

 

However, issue seems to be specific to ENGM  (Aerosoft's Oslo).  Other airports are working just fine (ENTC, etc.).  I'm not sure but it looks like Aerosoft have two scenery library entries for ENGM, one is a flattening entry (NOT to be selected) and the other is the Airport.  This is the ONLY airport I have with these two scenery entries so perhaps this is causing some issues with MakeRwys?  The parking spots do show up in P3D.

 

Does anyone have Aerosoft's Oslo installed and using PACT .... if so, are you seeing all the correct parking spaces in PACT?

 

Cheers, Rob.

Just a quick question. Is this the new ENGM from Aerosoft?

 

In FSX and with the original Aerosoft's ENGM, I have no problems with ProATC. I wonder if it's P3D coversion or the new ENGM that is causing the problems.

Sent you a PM Rob.

 

 

Is this the new ENGM from Aerosoft?

 

I'm running Aerosoft's Oslo 2.0 - v1.04a (solved the flicker issues in P3D) ... there is a v1.06 that I'm downloading now.

 

Cheers, Rob.

I suppose PATC gets its gate data from the G5.CSV file produced by MakeRunways. If so, here that file contains these gates:

 

ENGM,,15,60.194677,11.093306,20.0,16.4,8,NAX,CNO
ENGM,,13,60.194785,11.092564,20.0,16.4,8,CNO,SASX
ENGM,,14,60.195793,11.092633,20.0,197.2,8,NAX,CNO
ENGM,,16,60.195683,11.093394,20.0,197.2,8,CNO,NAX
ENGM,,18,60.195591,11.094021,20.0,197.2,8,NAX,CNO
ENGM,,20,60.195465,11.094895,20.0,197.2,8
ENGM,,22,60.195360,11.095616,20.0,197.2,8,NAX,CNO
ENGM,,24,60.195251,11.096371,20.0,197.2,8,CNO,NAX
ENGM,,26,60.195127,11.097222,20.0,197.2,8,NAX,CNO
ENGM,,38,60.194401,11.102230,25.0,197.2,9,CNO,SASX,FIN,AFR,KLM,ELL,TAP,CSA,DLH,SWR
ENGM,,40,60.194299,11.102935,25.0,197.2,9,TAP,DLH,BLF
ENGM,,42,60.194188,11.103694,25.0,197.2,9,SAS,NAX,KLM,ELL,RZO,BTI,PGT
ENGM,,44,60.194079,11.104454,25.0,197.2,9,BTI,NVR,SAS,SXS,BLX,PRI,VKG,TVS
ENGM,,46,60.193960,11.105279,25.0,197.2,9,ICE,AWE,USA,JKK,SXS
ENGM,,48,60.193826,11.106207,25.0,197.2,9,AWE,ICE
ENGM,,50,60.193612,11.107448,36.0,253.1,10,VKG,COA,AWE,THA,PIA,VKG
ENGM,,51,60.192774,11.107804,36.0,342.6,10,BAW,AFL,SAS,VKG,BLX
ENGM,,53,60.193094,11.108039,36.0,285.5,10,AFL,SAS,VKG,BLX,BAW
ENGM,,49,60.192825,11.106466,32.0,339.3,10,SAS,VKG,BLX,BAW,AFL
ENGM,,47,60.192873,11.105464,24.0,16.4,8,BLX,CAI,KKK,ECA,JTG,KBR,LBT
ENGM,,45,60.192980,11.104744,24.0,16.4,8,SAS,JKK,DLH,NAX,SWR
ENGM,,43,60.193095,11.103945,24.0,16.4,8
ENGM,,41,60.193200,11.103242,24.0,16.4,8,TAP,DAT,BLF,DLH
ENGM,,39,60.193325,11.102436,24.0,16.4,8,CNO,BER,AFR,FIN,KLM
ENGM,,7,60.195034,11.090182,14.0,61.6,8,WIF,DNU,DTR,NFA,SUS
ENGM,,3,60.195431,11.090337,14.0,61.6,8,WIF,DNU,DTR,NFA,GAO,SUS
ENGM,,2,60.195885,11.090580,14.0,166.0,8,WIF,DNU,DTR,NFA,GAO,SUS
ENGM,,9,60.195110,11.091068,15.7,16.6,8,WIF,DNU,DTR,NFA,SUS
ENGM,,11,60.194898,11.091838,20.0,16.4,8
ENGM,,10,60.195985,11.091187,15.7,197.2,8,WIF,DNU,DTR,NFA,SUS
ENGM,,12,60.195898,11.091899,15.7,197.2,8,WIF,DNU,DTR,NFA,SUS
ENGM,,178,60.193428,11.091961,20.0,196.2,9,NAX,CNO
ENGM,,177,60.193538,11.091196,20.0,196.5,9,CNO,NAX
ENGM,,176,60.193648,11.090439,20.0,196.5,9,NAX,CNO
ENGM,,175,60.193757,11.089685,20.0,196.5,9,CNO,NAX
ENGM,,174,60.193858,11.088985,20.0,196.5,9,NAX,CNO
ENGM,,173,60.193968,11.088221,20.0,196.5,9,CNO,NAX
ENGM,,172,60.194078,11.087458,18.0,196.5,9,NAX,CNO
ENGM,,171,60.194210,11.086555,18.0,196.5,9,CNO,NAX
ENGM,,88,60.197535,11.100134,20.0,103.9,9,TAP,DLH,BLF
ENGM,,84,60.196929,11.099769,20.0,104.8,9,CNO,NAX
ENGM,,80,60.196455,11.099491,20.0,105.0,9,CNO,NAX
ENGM,,92,60.198155,11.100217,25.0,104.4,9,ICE,AWE,USA,JKK,SXS
ENGM,,76,60.195972,11.099218,20.0,104.9,9,NAX,CNO
ENGM,,96,60.198831,11.101457,14.0,161.4,8,WIF,DNU,DTR,NFA,SUS
ENGM,,95,60.198675,11.102540,14.0,161.9,8,WIF,DNU,DTR,NFA,SUS
ENGM,,93,60.198516,11.103454,14.0,197.6,8,WIF,DNU,DTR,NFA,GAO,SUS
ENGM,,89,60.198155,11.102843,20.0,284.0,8,NAX,CNO
ENGM,,85,60.197600,11.102514,20.0,284.0,8,TAP,DAT,BLF,DLH
ENGM,,81,60.197131,11.102211,20.0,284.0,8,CNO,SASX,FIN,AFR,KLM,ELL,TAP,CSA,DLH,SWR
ENGM,,77,60.196654,11.101946,20.0,284.0,8,SAS,JKK,DLH,NAX,SWR
ENGM,,73,60.196179,11.101641,20.0,284.0,8,NAX,CNO
ENGM,,69,60.195697,11.101364,20.0,284.0,8,CNO,NAX
ENGM,,65,60.195161,11.101176,20.0,284.0,8,NAX,CNO
ENGM,Park,181,60.191785,11.103627,19.1,194.0,8,SUS,LOT,DUO,BLF,CRX,BRT,TYR,EZE,CLH,ADR,FIN,AFR,KLM
ENGM,Park,182,60.191670,11.104381,19.1,194.0,8,SUS,DAT,CIM,EZE
ENGM,Park,183,60.191557,11.105137,19.1,194.0,8,CIM,CLH,DAT,SUS,EZE
ENGM,Park,184,60.191442,11.105895,19.1,194.0,8,DAT,LOT,DUO,BLD,CRX,BRT,TYR,CLH,ADR,FIN,AFR,KLM
ENGM,Park,185,60.191311,11.106769,19.1,194.0,8,CNO,AEU,ELL,CSA,RZO
ENGM,Park,186,60.191088,11.107936,23.0,194.0,8,CIM,CLH,DAT,SUS,EZE
ENGM,Park,187,60.190931,11.108978,19.1,194.0,8,CNO,AEU,ELL,CSA,RZO
ENGM,Park,208,60.193529,11.086227,31.0,106.4,8,MNB,ICEC
ENGM,Park,207,60.193010,11.085916,31.0,107.6,8,UPS,MNB
ENGM,Park,206,60.192497,11.085606,31.0,106.5,8,TAY,ICEC
ENGM,Park,205,60.191984,11.085302,31.0,106.1,8,DHK,BCS
ENGM,Park,204,60.191311,11.085569,31.0,106.7,8,KALC
ENGM,Park,203,60.190931,11.085341,31.0,106.6,8,SWN,WLX
ENGM,Park,202,60.190560,11.085119,31.0,107.4,8,SWN,WLX
ENGM,Park,201,60.190193,11.084900,31.0,105.8,8,WLX,SWN,ATN
ENGM,,28,60.195096,11.097997,20.0,172.3,8,NAX,CNO
ENGM,,36,60.194557,11.101297,25.0,221.2,9,CNO,SASX,FIN,AFR,KLM,ELL,TAP,CSA,DLH,SWR
ENGM,,72,60.195514,11.098892,20.0,104.9,9,NAX,CNO
ENGM,Park,312,60.198458,11.077310,20.0,266.2,1,BIZ,MMD
ENGM,Park,313,60.198739,11.077297,20.0,266.2,1,BIZ
ENGM,Park,314,60.199019,11.077238,20.0,266.2,1,BIZ,MMD
ENGM,Park,316,60.199582,11.077163,20.0,266.2,1,BIZ,MMD
ENGM,Park,315,60.199301,11.077210,20.0,266.2,1,BIZ
ENGM,Park,317,60.199862,11.077122,20.0,266.2,1,BIZ,MMD
ENGM,Park,319,60.200422,11.077029,20.0,266.2,1,BIZ,MMD
ENGM,Park,318,60.200141,11.077059,20.0,266.2,1,BIZ,MMD
ENGM,Park,320,60.201604,11.076440,20.0,285.7,1,SWN
ENGM,Park,321,60.201982,11.076666,20.0,285.7,1,SWN
ENGM,Park,322,60.202348,11.076886,20.0,285.7,1,SWN,SAG
ENGM,Park,323,60.202720,11.077091,20.0,285.7,1,BIZ,SAG,SWN
ENGM,Park,324,60.203104,11.077295,20.0,285.7,1,BIZ,SAG,SWN
ENGM,Park,325,60.203472,11.077518,20.0,285.7,1,SWN,BIZ,SAG
ENGM,Park,326,60.203842,11.077745,20.0,285.7,1,SWN,BIZ,SAG
ENGM,Park,327,60.204213,11.077965,20.0,285.7,1,SWN,BIZ
ENGM,Park,328,60.204578,11.078214,20.0,285.7,1,SWN,BIZ,SAG
ENGM,Park,329,60.204960,11.078419,20.0,285.7,1,SWN,BIZ,SAG

I'm not sure what version of Aerosoft's ENGM I've got installed.  The airport details including gates are defined in the file ENGM_AFX.bgl.  It's definitely version 2.0 with most files dated Feb 2014.

 

Pete

Re the Oslo problem, the work around, should you need it, is to replace the Alpha_Flatten.bgl with Allpha_Flatten.off before you run Make Runways. Once Make Runways has completed rename Alpha_Flatten.off to Alpha_Flatten.bgl again.

Re the Oslo problem, the work around, should you need it, is to replace the Alpha_Flatten.bgl with Allpha_Flatten.off before you run Make Runways. Once Make Runways has completed rename Alpha_Flatten.off to Alpha_Flatten.bgl again.

Hello Mike,

 

The latest version contains the flatten fix previously posted on the Aerosoft forum. (1.06)

Hi Stephen,

 

Thanks again for the support.  My first problem was indeed not setting to the correct mode (Prepar3D).

 

The second issue was with Aerosoft's Oslo 2 (1.04) ... updating Oslo to 1.06 fixed the issue (see below).

 

Pete's MakeRwys is working very well, no issues there.

 

 

 

ProATC X is working VERY well in P3D V2.5.

 

Cheers, Rob.

Thanks for the info Stephen. And Rob, welcome to the club...;-)

I love using Pro ATC, most of the problems I run into are self created " Pilot error". Still learning....

I had the same error without using on a network, and it was due to the fact I forgot to check P3D in the Pro ATC setup menu. Options/In-flight/  menu at the top of the page. 

 

This simple solution just cured a major headache for me. Thanks!