MakeRunways and FB SEQM

[pracines]

I was wondering if anybody else has had no success getting MakeRunways to output R4.csv info for SEQM.

Radar Contact still has no info on SEQM - I tried (trying anything I can think of) with and without the Lorby AO export tool. 

It must be something simple I'm missing, but rebuilding a RC4.3 database is as simple as it gets.

I'm using MakeRunways version 4.8.7.1 and even when run from the P3D directory directly it does not pick up that SEQM is there, however, SEQU is still there in the R4.csv

I have a post in the Flightbeam forum to see if anybody there has insight into something with the scenery itself.

I'm at a loss.

 

[downsc]

I'm following your post in the FB forum because I had same problem.  However, I think the solution is to make sure you run MakeRunways with admin privileges.  I notice that it was not making the interim file MakeRwys_Scenery.cfg until I made that change.  SEQM now appears in Runways.txt.

[Pete Dowson]

9 minutes ago, downsc said:

I'm following your post in the FB forum because I had same problem.  However, I think the solution is to make sure you run MakeRunways with admin privileges.  I notice that it was not making the interim file MakeRwys_Scenery.cfg until I made that change.  SEQM now appears in Runways.txt.

Do you have your Sim installed in your Program Files folder? Because if so that's protected from writing. I wouldn't have thought you'd get any files written by MakeRunways withoutadmin privileges.

Otherwise i can only think it's the Lorby-Si program used to make that CFG file which needs this level on your systems. I'm not sure why.

Pete

 

[pracines]

1 hour ago, downsc said:

SEQM now appears in Runways.txt.

Yes I get SEQM in runways.txt but I need it in the csv files.

I have all my programs set to run as administrator - that's like breathing to me 😃.

1 hour ago, Pete Dowson said:

Do you have your Sim installed in your Program Files folder? Because if so that's protected from writing. I wouldn't have thought you'd get any files written by MakeRunways withoutadmin privileges.

Otherwise i can only think it's the Lorby-Si program used to make that CFG file which needs this level on your systems. I'm not sure why.

Pete

 

I have P3D installed in C:\Prepar3D v4 

Initially I figured it was a simple fix on Flightbeam's end, because I have been using MakeRunways and Radar Contact for what seems to be about 15 years w/o any problems. Been through the Orbx global/vector phase,  Ray Smith afcad phase, payware and freeware, FSAerodata,  all w/o a single issue. SEQM is the only roadblock.  

I will look further into Lorby and see if I can figure this out.

I'm almost due for a total system refresh, so not too big a deal - I will just use default ATC to get to SEQM until then.

------------------

Thanks for the ideas gentlemen.

 

 

 

[Pete Dowson]

8 hours ago, pracines said:

Yes I get SEQM in runways.txt but I need it in the csv files.

If the runways for SEQM are not appearing in the resulting database files then  the scenery files are in error somewhere. Do the runways appear in the drop-down position list for "go to airport" in the Sim? If they do, please show me the relevant section of Runways.txt (which is only a log of what the program finds, not a database).

8 hours ago, pracines said:

I will look further into Lorby and see if I can figure this out

No need. If the airport itself is appearing in the MakeRunways log file, then it is being included in the scan list. It must be something wrong or very non-standard in the AFD BGL for the aiport.

Pete

 

[pracines]

2 hours ago, Pete Dowson said:

If the runways for SEQM are not appearing in the resulting database files then  the scenery files are in error somewhere. Do the runways appear in the drop-down position list for "go to airport" in the Sim? If they do, please show me the relevant section of Runways.txt (which is only a log of what the program finds, not a database).

Yes, the P3Dv4 airport selection does show the SEQM airport, the runways, that helipad, gates, and GA parking on the dropdown selection list. The airspace and runway is indicated on the map as well. There is a pretty huge section for SEQM and related to that, the closure of SEQU following (just incase its something to do with that), so I will attach that section in a zip file. 

SEQM runwaysTXT.zip

[Pete Dowson]

2 hours ago, pracines said:

There is a pretty huge section for SEQM and related to that, the closure of SEQU following (just incase its something to do with that), so I will attach that section in a zip file. 

SEQM runwaysTXT.zip

Why is that an "rtf" file. A simple text file would be far easier for me to deal with. Trying ot open is brings up Microsoft Word which then says it can't open it. Perhaps you could send again, as a Zipped TXT file lease. 

Is the SEQM data in a separate BGL, like "SEQM.BGL"? Perhaps to save time you could include that -- it will be identified in the Runways.txt section you upload.

Additionally can you confirm the exact version nmuber of the MakeRunways you are using please?

Pete

 

[pracines]

39 minutes ago, Pete Dowson said:

Why is that an "rtf" file. A simple text file would be far easier for me to deal with. Trying ot open is brings up Microsoft Word which then says it can't open it. Perhaps you could send again, as a Zipped TXT file lease. 

Is the SEQM data in a separate BGL, like "SEQM.BGL"? Perhaps to save time you could include that -- it will be identified in the Runways.txt section you upload.

Additionally can you confirm the exact version nmuber of the MakeRunways you are using please?

Pete

 

Apologies, the sheer size of the runways.txt kept me from opening it as a simple txt (notepad) file (taking forever to load) so I went RTF fast. I did not realize it would be difficult to open for you, sorry. 

Here it is in a simple txt - no need to even zip up.

version 4.8.7.1 - reverified, redownloaded, and reinstalled twice last week, trying to cover all the basics.  

seqm runways.txt

[Pete Dowson]

46 minutes ago, pracines said:

Here it is in a simple txt - no need to even zip up.

Oky. that definitely has the runways and the log entries there do indicate that they've gone to the data files.

Are they missing in all the files, XML, R5, R4?

I think I need the resposible BGL so i can take a look and run the test here,.
C:\Prepar3D v4\Flightbeam\Flightbeam - SEQM\scenery\SEQM_ADEP4_DS_04_W_STATICS.bgl 

Pete

 

[pracines]

47 minutes ago, Pete Dowson said:

Oky. that definitely has the runways and the log entries there do indicate that they've gone to the data files.

Are they missing in all the files, XML, R5, R4?

I think I need the resposible BGL so i can take a look and run the test here,.
C:\Prepar3D v4\Flightbeam\Flightbeam - SEQM\scenery\SEQM_ADEP4_DS_04_W_STATICS.bgl 

Pete

 

R5 and XML both have SEQM - R4.CSV is the one that does not have SEQM. If it possibly matters, in my quest I also discovered that F4 F5 G5 Helipads T5.CSV all contain SEQM.

I personally have no problem sending the BGL, but I've never had to send a BGL file in my experience, particularly from a licensed piece of software, and am unsure of the legal ramifications (if any). Please advise if I should ask permission from Flightbeam. Just covering all the bases.

**** Hold on - I found a piece of info that likely makes this more a Radar Contact v4.3 issue than a MakeRunways issue. In double checking all the CSV files in my P3DV4 directory the R4.CSV there, it does have SEQM, and yet the same date R4.CSV in the RCv4/data directory does not have the SEQM entry. Must have to do with the rebuild database batch program in RC4.3. I would never have guessed that would make a difference especially with a single airport.

I suppose it just a matter of copying the good one from P3D over to the Radar Contact/data directory.

But if we should still alert Flightbeam about this for some reason that they can/should correct, I will communicate with them unless you think its best to contact them yourself about it, based on how complicated it may be. 

  

 

[downsc]

18 hours ago, Pete Dowson said:

Do you have your Sim installed in your Program Files folder? Because if so that's protected from writing. I wouldn't have thought you'd get any files written by MakeRunways withoutadmin privileges.

Otherwise i can only think it's the Lorby-Si program used to make that CFG file which needs this level on your systems. I'm not sure why.

Pete

 

Pete, my P3D is installed on my d: drive and yet I still need to mark the run as admin setting to generate the Makerunways_senery.cfg interim data file by the Lorby module.

[Pete Dowson]

5 minutes ago, pracines said:

R5 and XML both have SEQM - R4.CSV is the one that does not have SEQM. If it possibly matters, in my quest I also discovered that F4 F5 G5 Helipads T5.CSV all contain SEQM.

Hmm. that's odd. they are both produced at the same time in the same bit of code. The R5 one just contains an extra field or two (?).

6 minutes ago, pracines said:

I personally have no problem sending the BGL, but I've never had to send a BGL file in my experience, particularly from a licensed piece of software, and am unsure of the legal ramifications (if any).

Well it isn't the scenery, just the definition of these things we are talking about.  But there's no point is sending it in any case if you have R5 with the details included.

Please send me the entries from the R5 file. Actually, probably better sending me both the R4 and R5 files complete please. Zipped they'll be quite small.

9 minutes ago, pracines said:

**** Hold on - I found a piece of info that likely makes this more a Radar Contact v4.3 issue than a MakeRunways issue. In double checking all the CSV files in my P3DV4 directory the R4.CSV there, it does have SEQM, and yet the same date R4.CSV in the RCv4/data directory does not have the SEQM entry. Must have to do with the rebuild database batch program in RC4.3. I would never have guessed that would make a difference especially with a single airport.

Aha! So probably you haven't copied over the files RC needs since installing that airport.

I didn't know RC automatically copied the files it needed. When I used RC I always had to do that manually.

11 minutes ago, pracines said:

But if we should still alert Flightbeam about this for some reason that they can/should correct

I'm not sure where you think FlightBeam have any responsibility to either MakeRunways or RC (the latter isn't even supported any more).

10 minutes ago, downsc said:

Pete, my P3D is installed on my d: drive and yet I still need to mark the run as admin setting to generate the Makerunways_senery.cfg interim data file by the Lorby module.

That's odd.

Pete

 

[pracines]

34 minutes ago, Pete Dowson said:

I'm not sure where you think FlightBeam have any responsibility to either MakeRunways or RC (the latter isn't even supported any more).

Well not "responsibility", but it is the only scenery package that has not automatically copied over to RC43/data in my 15 years of Radar Contact. When you mentioned a BGL may be responsible (I think unconventional is possibly a better word) , I thought that it may be something Flightbeam would like to know.

The only file I have had to copy over (instead of manually editing each flight in the RC UI)  is the F4.csv as FSAerodata has been updating the frequencies as needed with each new AIRAC.

----------------------

Ok, so I just ran MakeRunways from P3D directly (to P3D) and also from the RC3.4 rebuild DB method (to RC4/data).

Now wouldn't you know it, SEQM is not even in the R5.csv anymore. I know for sure it was there - I'm using the find feature. I have no other programs running at all.

Here is the STATISTICS bgl

 

SEQM_ADEP4_DS_04_W_STATICS.bgl

[Pete Dowson]

20 minutes ago, pracines said:

Well not "responsibility", but it is the only scenery package that has not automatically copied over to RC43/data in my 15 years of Radar Contact.

Hmm. Very strange. I never had any option to automatially do this, and I used RC since it started (as an adventure language program) with FS98 all the way through to a few years back when  I upgraded to ProATC/X and now to Pilot2ATC (as i like the voice interaction, better than menus).

23 minutes ago, pracines said:

When you mentioned a BGL may be responsible (I think unconventional is possibly a better word) , I thought that it may be something Flightbeam would like to know.

Yes, but based on your later posting it seems to be nothing to do with the BGL itself, but only to do with the non-copying of a file to RC.

Before I even think about testing with a BGL I think you need to sort out what files you are using, when they were generated and which ones are actually applicable the the FB scenery and which not. Your finding now with R5 makes no sense. compare dates of generation to start with , and realte the files to the correct Runways.txt.

Pete

 

 

[pracines]

 

29 minutes ago, Pete Dowson said:

Before I even think about testing with a BGL I think you need to sort out what files you are using, when they were generated and which ones are actually applicable the the FB scenery and which not. Your finding now with R5 makes no sense. compare dates of generation to start with , and realte the files to the correct Runways.txt.

This seems to be a case where I failed to use the Lorby export tool prior to running MakeRunways. I must have been too excited to get flying to SEQM that I missed a step I never missed before, I don't think so, but its possible.

RC4.3 now sees SEQM normally.

However, a freeware product called Destination Finder 2.0 that uses MakeRunways and its own database maker (FSXDATA.CSV)  still does not see SEQM. But I'm not so concerned over that, as LNM does the job, plus you have given way too much time on this.

I may have to move to newer ATC / utilities  as the P3D world changes. 

Thank you  Pete.

[Pete Dowson]

2 hours ago, pracines said:

This seems to be a case where I failed to use the Lorby export tool prior to running MakeRunways. I must have been too excited to get flying to SEQM that I missed a step I never missed before, I don't think so, but its possible.

The latest version of MakeRunways uses the tool in;uded in its download. The use of the separate AddOnOrganise program is not longer automatic.

Pete