oskrypuch

I have set all the settings to nautical/imperial, but still get a curious blend of the two on the Approach tab. For example, the ILS 08R into KGRR, for the Cat 1 DA/vis it shows (navigraph 1905): 1000 / 550 m The DA is actually 1000ft, that's OK. The required visibility is 1/2SM. For the visibility it shows 550m, not quite 1/2SM, but in any case it is confusing to have a mix of the two units. Am I missing a setting somewhere, or is this bug? * Orest

Here are the two entries from scenery_add-ons.xml ... <AddOn.SceneryComponent> <Path>C:\Z_P3D_v4\FlyTampa\Toronto\scenery_LC</Path> <SceneryCRC>-707770097</SceneryCRC> </AddOn.SceneryComponent> <AddOn.SceneryComponent> <Path>C:\Z_P3D_v4\FlyTampa\Toronto\scenery</Path> <SceneryCRC>1938342259</SceneryCRC> </AddOn.SceneryComponent> The log file does appear to correctly add \scenery to the LC path, and that is where the BGL is. But, the logfile shows that Aivlasoft does NOT find the main scenery in the \Toronto\scenery path. That is where it is, and it does display in the sim. Any chance you allow only one path per addon, and the second entry is ignored? * Orest

Thanks. Very helpful! * Orest

Is there a way of carrying over all the file paths and other settings, for the display unit in particular, when moving to a new update? Even on minor updates (eg. .14 -> .15) an uninstall is forced, and a number of the settings go back to defaults. It is tedious to get them all set back up. * Orest

There are two sets of scenery components, in two different layers for FT CYYZ listed in the P3D Scenery Library. There is their custom landclass in: ..\FlyTampa\Toronto\scenery_LC (layer 12) (curiously the BGL is actually in the ..\FlyTampa\Toronto\scenery_LC\scenery directory) And then the rest of the scenery in: ..\FlyTampa\Toronto\scenery (layer 11) * Orest

The latest update (.15) still does not show the Fly Tampa CYYZ airport scenery, instead you see the default CYYZ. The update does seem to address the other addon sceneries that I have. The CYYZ airport data is found, according to the scan log file. (see attached) Has this been reported? Solution? * Orest DataProviderLogfile.txt

Well, even if you solely provide the aircraft VATSIM ID in the tag, for example UAL001, it would be handy. You could have a setting to turn it ON/OFF. Something to chew on. * Orest

Of course you have the aircraft labels shown while enroute, of other aircraft within range, with ID, alt, speed etc. But, I would like to see the aircraft ID of the other planes, on the ground, as well. Sometimes you are looking around to find where a buddy is, or who is taxiing, and there are no labels. Perhaps I'm missed a setting, if not, can this be added to the wishlist? * Orest

Noticed that, have Rev3 downloaded, haven't tried it yet. I also noticed odd 360 circles depicted on the PFD, at the FAF. I expect that is a related issue. * Orest

Thanks! Will grab Rev2. * Orest

I don't use routefinder. Anything else of note in 1.3.5? * Orest

I enjoy VATSIM, and been flying it for a long time. PE is definitely different. Guaranteed ATC (although in a smaller area) is a big plus for. The ATC on PE is at a little higher level, than the already quite good VATSIM ATC. The focus is somewhat different as well. To me, PE is well worth the monthly fee. And yes, the EFB works just fine with PE, traffic shows up when online as well. There is not a way to preview traffic, when still offline, like there is for VATSIM and IVAO, but that is not a biggie. * Orest

Be sure that you are manipulating the correct file. Vista/Win7 has a maze of duplicate user and application directories. Checking the date/time of access for the file may help confirm that you have the "active" settings file. * Orest

http://www.navigraph.com Payware, but dead cheap. * Orest

Not just for EFB's purposes, but really all your other add-ons ... Do you have an old computer somewhere? Even a slow one, networked to your current one can handle all your add-ons for you with aplomb. Not only gives you easy display/access, but smooths the primary computer's job right out. You need paid-up FSUIPC and WideFS, but FSUIPC is such a valuable utility you should have it running in any case. * Orest

Looking at KRNM, there are three approaches, one straight-in to runway RNav 9, and the other two circle-to-land: Rnav B and VOR/DME A. Only the RNav 9 is shown as available. Appears to be a bug related to the insistence of a runway association for an approach. * Orest

Thanks GG. * Orest

Trying to enter the following (valid) route, just doesn't work ... KWJF PMD V197 PDZ KRIV It keeps hanging on interpreting PDZ as an airport somewhere. When I try to correct that in the Destination change area, I then can't put PDZ (the VOR) into the plan. * Orest