Jump to content
The simFlight Network Forums

pracines

Members
  • Content Count

    77
  • Joined

  • Last visited

  • Days Won

    7

pracines last won the day on April 24 2017

pracines had the most liked content!

Community Reputation

1 Neutral

About pracines

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    usa

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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 😃. 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.
  7. 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 so
  8. It was me then...I thought the initial sentence was a "history lesson" and the second sentence was a "new possibility" with the M4.csv file. So I thought the info was being pinched from M4🤡😄
  9. Yes I did mean the /+T parameter. I figured it was me. I don't own EFB, I use Navigraph Ultimate, and I only own RC4. After all the trial and error trying to get /+T to function, I was surly stumped. Thanks for looking into this. HiFi, PMDG, and the P3D SDK (World\Traffic) all use Airports.dat someway, could they be used in some way? *** never mind on the last question**** I checked them - no TA TL info
  10. I'm using MakeRwys version 4.8.6.1 and following the directions exactly, the m4.CSV file remains unchanged. I have tried the CMD as admin console window method and creating the shortcut method running as admin (check box and right clicking). I tried both methods without running as admin. I tried exporting the library via the Lorby-SI and tried it w/o exporting the library. The original m4.CSV is copied from RC4x/Data to P3Dv4 root and after running MakeRwys it remains dated 1/6/2006, yet all the other CSV files in the P3Dv4 root show modified today 9/1/2018. Are we positive th
  11. Hi Simon, Are you in touch with the Traffic Global development team? On the surface it does not appear to be much different from Traffic 360 except for updated schedules and A/C types. https://www.justflight.com/product/traffic-global
  12. Great news indeed Simon, thanks for sticking with it!
  13. after .bgl you can just add .orig So just make the file name TrafficAircraft.bgl.orig This way if you need the original file restored just edit out .orig and FSX will read the file again.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.