Jump to content

What is - most likely - included in FV 1.12


pellelil

Recommended Posts

In this topic I plan to describe the features that are most likely coming in version 1.12. Some of the items are fully implemented, some will be work in progress. Everything is subject to change, and I can't offer a deadline. Feel free to comment, ask questions and suggest other features.  

 

The main theme for version 1.12 is to add the "remaining" features for each user to tailor the Flightplan data so these match his/her scenery and preferences. There are no 2 installations of P3D that are identical, so the datafiles and flightplans I bundle with the program are constructed to match a default (plain vanilla) P3D installation without any 3rd party scenery installed. So when you look at an airport in FV it will match the default P3D airport when it comes to: ICAO-code, runways, gates, frequencies and so on. However most users will be running with a few or many 3rd party airports installed. For instance I personally run with quite a few 3rd party airports (and a few ORBX regions), and on top of this I subscribe to FsAeroData (https://www.fsaerodata.com/), which is updated each 28 days, following the 28-day AIRAC cycles. Installing a 3rd airport will in most cases just update runways, gates and frequencies for that single airport, but the FsAeroData updates a lot of outdated data, so you will also notice that many wrong/outdated ICAO codes are updated as well (e.g. the ICAO code of Johannesburg, South Africa, is changed from "FAJS" into "FAOR"). So in order to have the information in FV match the installed/active scenery you have to run MakeRunways as instructed in the manual or described in this video:

 

 

It's not new that you can use MakeRunways to update the info in FV to match your scenery. This feature have been in the software since its first (beta) release. But as a new feature in version 1.12 you can now in the settings form specify the path where you have the files that MakeRunways is generating. Its still a manual process to run MakeRunways - after you have installed-/updated scenery - but if you specify this path in the settings from, you don't need to copy the 3 files into your UserData folder anymore. If a valid path is specified in settings, and this path contains the 3 files (f5.csv, g5.csv and runways.xml) these will be loaded at startup; otherwise the files in the UserData folder will be used as a fall-back option.

 

In version 1.11 I added a new form to edit the airport-redirections, where you in the past had to manually edit the "UserAirportRedirect.xml" file in the UserData-folder using a text-editor. The "redirections" in this file are used to automatic "redirect" (change) from one airport to another, when flightplans are imported. E.g. there are many flighplans that use the ICAO code "LYPR" for "Pristina International Airport". The "problem" is hovewer there are no airport in P3D with the ICAO code "LYPR", but there is one with the ICAO code "BKPR" at the same location also with the name "Pristina". The version of the redirection-file that I bundle with the installer is build with the default P3D scenery in mind, and as such - among other redirection - it contains a redirection from "LYPR" to "BKPR". But this file is just as "personal" as those files extracted by MakeRunways, so each user should define his/her own redirections to match his/her installed scenery (at least when it comes to changed/added/deleted ICAO-codes). E.g. as mentioned previously, since I run with FsAeroData I want to have a redirection from "FAJS" to "FAOR" in my personal version of the redirection-file.

At the bottom of the "Edit Redirect" form I have in version 1.12 added a new button ("Generate redirection report") which lets you generate a report of pseudo-airports and active redirections. The purpose of this report is to give you all the data you need in order to determine how YOU want to setup YOUR personal redirections to match YOUR installed scenery. The manual updated for version 1.12, and the "whats new" video I will record for version 1.12 will contain a lot more description of how to use the report to setup your personal redirections. Anyway here is an example from a report, generated on my own computer based on my installed scenery:

 

FAJS*, S26°08'01.298" E028°14'32.341", Johannesburg Intl, Johannesburg, South Africa, NON FS-Airport: with: GPS, TZ, Country, Name/City
--------------------------------------------------------------------------------------------------------------------------------------------
0,0 NM, FAOR, S26°08'01.262" E028°14'32.308", Johannesburg Intl, Johannesburg, South Africa, FS-Airport (4 runways, 81 gates, 9 frequencies)
7,1 NM, FABB, S26°14'17.001" E028°18'21.002", Benoni, Brakpan, South Africa, FS-Airport (2 runways, 2 frequencies)
8,1 NM, FAGM, S26°14'30.001" E028°09'06.001", Rand, Johannesburg, South Africa, FS-Airport (4 runways, 9 gates, 3 frequencies)
10,4 NM, FAGC, S25°59'13.437" E028°08'25.969", Grand Central, South Africa, FS-Airport (2 runways, 3 gates, 2 frequencies)
11,0 NM, FASI, S26°15'00.000" E028°24'00.000", Springs, South Africa, FS-Airport (4 runways)
18,4 NM, FAWK, S25°49'39.676" E028°13'15.211", Waterkloof AB, Waterkloof, South Africa, FS-Airport (4 runways, 6 frequencies)
19,8 NM, FASK, S25°48'41.997" E028°09'48.002", Swartkop AB, Swartkop, South Africa, FS-Airport (4 runways, 3 frequencies)
19,9 NM, FAKT, S25°51'38.973" E028°27'05.799", Kitty Hawk Aero Estate, Boschkop, South Africa, FS-Airport (2 runways, 2 gates, 2 frequencies)
--------------------------------------------------------------------------------------------------------------------------------------------
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air Austral - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air China - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air France - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air Mauritius - Su18
FAJS*, S26°08'01.200" E028°14'32.400", 0,0 NM, Air Namibia - Wi18-19
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Air Seychelles - Wi18-19
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Alitalia - Wi18-19
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Astral Aviation - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Bid Air Cargo - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, British Airways - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Cargolux - Su15
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Cargolux Italia - Su15
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Cathay Pacific - Wi18-19
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Delta Air Lines - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Egypt Air - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, El Al Israel Airlines - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Emirates - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Ethiopian Airlines - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Ethiopian Airlines Cargo - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Etihad Airways - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Etihad Cargo - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Fly Safair - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Iberia - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Kenya Airways - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, KLM - Wi18-19
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Kulula - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, LATAM Airlines Brasil - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Lufthansa - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Lufthansa Cargo - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Malawian Airlines - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Mango - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Martinair - Wi18-19
FAJS*, S26°07'56.400" E028°14'30.600", 0,1 NM, Qantas - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Qatar Airways - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Qatar Airways Cargo - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, SA Airlink - Wi17-18
FAJS*, S26°08'01.301" E028°14'32.339", 0,0 NM, Saudia - Su15
FAJS*, S26°08'01.301" E028°14'32.339", 0,0 NM, Saudia Cargo - Su15
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Singapore Airlines - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Singapore Airlines Cargo - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, South African Airways - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, South African Airways Cargo - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, South African Express - Wi17-18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Swiss - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, TAAG Linhas Aereasde Angola - Wi18-19
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Turkish Airlines - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Turkish Airlines Cargo - Su18
FAJS*, S26°08'01.200" E028°14'31.799", 0,0 NM, Virgin Atlantic - Su18

 

The top-line for each (pseudo/redirected-airport) represent the airport that is currently used in FV. In this case the pseudo airport "FAJS" is in use. On your system (perhaps not using a 3rd party version of Johannesburg, nor FsAerodata) "FAJS" will NOT be a pseudo airport as the Johannesburg in the default P3D is indeed using the ICAO code "FAJS". But on my system (thanks to FsAerodata) "FAJS" IS a pseduo airport. Below the top-line you see that there are not less than 8 nearby (within 20 Nm) airports. The nearby airports are sorted by distance to the airport in the top-line. The very first of the nearby airports is "FAOR" and you can see its name is indeed "Johannesburg Intl". The ICAO code is not suffixed with an asterisk, and the last part of the line says "FS-Airport (4 runways, 81 gates, 9 frequencies)" to tell us that this is indeed an FS-Airport, and the data extracted tells us that MakeRunways was able to extract data regarding: 4 runways, 81 gates, and 9 frequencies. So based on this I would add a redirection from "FAJS" to "FAOR". The last many lines after the nearby airports tells us all the installed flightplans that are currently referencing the "FAJS" pseudo-airports.

 

Lets look at another example from the same generate report on my system:

 

BKPR, N42°34'21.997" E021°02'08.998", Pristina, Serbia and Montenegro, FS-Airport (2 runways, 6 gates, 7 frequencies)
--------------------------------------------------------------------------------------------------------------------------------------------
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Adria Airways - Wi18-19
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, AtlasGlobal - Su17
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Austrian Airlines - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Danish Air Transport - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, easyJet - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, easyJet Switzerland - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Edelweiss Air - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Eurowings - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Germania Flug AG - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Germanwings - Su17
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Norwegian - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Sun Express - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Sun Express Deutschland - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Sundair - Wi18-19
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Swiss - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Trade Air - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, TUI fly Belgium - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Turkish Airlines - Su18
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Wizz Air - Wi18-19
BKPR<-LYPR**(AUTO), N42°34'21.600" E021°02'08.999", 0,0 NM, Wizz Air UK - Wi18-19

 

In this case we are not informed about any nearby airports, but in stead we can see that the airport in use in FV is "BKPR" which is not a pseudo airport (there is no asterisk after "BKPR" and it tells us that this is a FS-Airport: "FS-Airport (2 runways, 6 gates, 7 frequencies)". For each flightplan (below) we can see that they were all referencing the "LYPR" airport, however this was (based on the active redirections) reverted to the "BKPR" airport in stead ("BKPR<-LYPR**"). The direction of the arrow tells us that "LYPR" was redirected to "BKPR". The 1st asterisk after "LYPR" tells us that "LYPR" is a pseudo airport, and the 2nd asterisk tells us that there is (thanks to this redirection) no flightplan using "LYPR" (they have all been redirected to use "BKPR" in stead.

 

Once you have setup your preferred redirections its time to process/change all installed flightplans so they comply with your chosen redirections. Changing all installed flightplans to match your preferred redirections is a 4 step process:

 

 

  • Run MakeRunways (as instructed) to update the flight-sim data about each airport to match your installed scenery.
  • Generate and extract the redirection report.
  • Edit the airport-redirections based on the info in the redirection report.
  • Use the new "Re-process airport redirects" menu-item to go through all flightplans, and update them to match our preferred airport-redirects.

 

The behind-the-screen implementation of the "Re-process airport redirects" menu-item is still work in progress. This part is a bit "long haired" and requires a lot of testing to get it right, so more on this feature at a later time. Beside the main-theme of version 1.12 being re-processing all installed flightplans to match your scenery/preferred redirections, a handful of other small changes have been added as well:

 

  • Abillity to automatic check for available program-updates at startup (can be disabled in the settings-form).
  • The Generic Randomizer form can now be used to pick a random flight.
  • In the "Search legs" form, you can now enter multiple ICAO-codes (separated by comma).
  • The data-files I supply with the installer have been updated with information about a handful of military aircraft. As of now the following list of aircraft have been added: A6/AE6, A10, C5, C17, E2, E3, EF2000, F14, F15, F16, F18, F22, F35, F111, F117, JAS39, KC10, KC135, MiG 21/23/25/27/29/31, Mirage III/5/2000, Rafale, SU 17/20/22/24/25/27/30/32/34, V22.
  • I assume most of us don't need these military aircraft, so a (default) setting have been added to the settings-form to exclude these military aircraft from being listed, unless specific requested.

 

Link to comment
Share on other sites

I've made good progress over the weekend, and I must say I am happy with the implementation of the ”Flightplan reprocess” feature. I still need to do a little more tweaking and test, but its almost there. As posted previously the purpose of these new feature is to go through all flightplans and make them fit with YOUR (personal) installed scenery. The job is started with you opening the new “Re-process Flightplans” form where you set your criteria:]

 

Please login to display this image.

 

In the left side of the form you first select which of the active flightplans to re-process (by default they are all selected). In the right side of the form you have 3 combo-boxes that lets you choose how you want the selected flightplans to be re-processed. I will not go into details with these 3 combo-boxes, but they will be described in the manual and in the “whats new in version 1.12” video that I am going to record.

 

The screen-shot above was taken while the process was running. Before it was started the "Cancel" button was replace by a “Process” button. The "Cancel" button lets you abort the operation, but the flightplans already processed will have been saved with (perhaps) updated content. When the process has finished the user will be presented with a report telling the user what was changed in the process:

 

Please login to display this image.

 

This report is grouped by flightplan (sorted), and for each flightplan you can see what was changed. I case of flightplans where nothing was changed, they will not be part of the report. In this screen-shot you see the reported changes for “Wizz Air” and “Wizz Air UK” along with the “result” of the report telling you how many aircraft that were redetected (in this case none – hence not written to the report), how many airports that were reverted, how many airports that vere redirected and how many flightplans that were updated (re-saved). It also tells you how long time the process took. When I started to work on this feature I was afraid it would take a lot longer to re-process 540 flightplans (considering all the work done in the background), so I am very pleased with the performance I was able to squeeze out of it (re-processing 540 flightplans in about 4 seconds).

Link to comment
Share on other sites

Just a quick update: Version 1.12 will be able to user FS Global Real Weather (FSGRW) as a weather provider. But it will only support METAR as FSGRW does not put any TAF data in the files it generates:

 

Please login to display this image.

Link to comment
Share on other sites

As you can see in the screen-shot below a "Transfer to SimBrief" button have been added to the "Legs info" form:

 

Please login to display this image.

 

Clicking this button will transfer the primary flight-data to SimBrief to kick-start your "paper-work", and you only have to enter the remaining "blanks" (e.g. you have to set/choose Alternate, Pax/Cargo and so on). The data transferred to SimBrien is: airline, flight-number, departure-/arrival airport, depart-time, aircraft-type, registration, flight-time and taxi-in/out times. Naturally you are free to change everything within SimBrief:

 

Please login to display this image.

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

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. Privacy Policy & Terms of Use