Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by ChuckOman

  1. Bruce - I'm running 5.1HF1, and after I replaced the GPs at 0S9 provided by BuddhistManX, as Nick suggested, both my 0S9 Jeffco and 11S Seiku ground objects now seem fine - I'm not encountering the "if its on the other is off" problem you describe. Are you using 5.2? Chuck O
  2. Turns out KPO6 is the old ICAO for KIFP. So perhaps KPO6 crept in during the LM update to P3D5. My Orbx SCA KIFP scenery looks normal in P3D4.5. So this is somehow a P3D5 thing. I recall last summer Ed Correia noted that P3D5 airports with ICAO changes would need to be identified and eventually fixed ([useful tip] Known Issues with Prepar3D v5 - PREPAR3D® V5.x Support Forum - Orbx Community and Support Forums (orbxsystems.com). Perhaps this is one of them. Nick says he's seeing floating objects here. Anyone else also having issues with the P3D5 SCA Region at KIFP ?
  3. My P3D5 map view of the P3D5.1 base airport only shows KIFP at FE 699 ft, same as yours. But I did notice that when I originally selected the airport there was a second airport, KP06 that showed up a bit northwest - see screenshot. If I highlight KP06 it says "Bullhead City, Az". KP06 isn't in the airport index, only KIFP. I searched my P3D5 and Orbx Library for KP06 but there is no .bgl by that name.... Very strange. But I think you are onto something !
  4. Thanks Nick and Dean - Based on your comments, I turned .off all four Orbx SCA KIFP files - including the elevation adj - leaving only the P3D5.1 base 0202 airport, which apparently just has ramps and three parking spots. It looks different, but there are still elevation issues - the ramps and runways just don't match the underlying mesh. I am running Orbx Global Base and Vector 1.52. Is there anything in Base or Vector that might cause this ? Could it just be that LM changed the 0202 mesh ? BTW I'm not aware of any AI or navigation data installed in the sim. Chuck
  5. Thanks Dean. Wasn't certain which world scenery folder you were referring to. My system has an X:\Orbx Library\p3dv5\NA Southern California\Scenery\World\scenery and a file: ADE_FTX_SCA_KIFP_elevation_adjustment.bgl. Turning this .off made no difference. Or perhaps you are you recallling a different one ? Chuck
  6. I've searched my P3D5 root and my Orbx Library for duplicate KIFP files - none found. I hadn't realized that the elevation stubs weren't functional in P3D5 - and are simply legacies from P3D4. Any reason not to delete them? So my Orbx SCA KIFP is #114 in my library, and the LM KIFP base is lower down, #202. Presumably you have the same two files as I, and in the same relative order. Could it be that our Orbx SCA and LM base files are different ? Is there any other possible explanation ? Could LM have changed the elevation of the 0202 base? If you are also using P3D 5.1 "HF1"( we should be looking at the same scenery, shouldn't we? Chuck
  7. Hi Nick - Thanks for having a look. No, this one reminded me of the uncorrected AEC problems we used to see in P3D4, with ramps, taxiways and runways at one elevation and the taxiway signs, buildings, tower, etc at another. Looks like an elevation difference of a 80-100 feet..... See the two screen shots attached. I notice the P3D base file is APX17190 dated 2/6/2020. Most of the other files in the 0202 base folder have same date, soI assume are from P3D5.0 . A few others have dates in April 2020 and I'm guessing were part of the subsequent LM updates. The Orbx ADE_FTX_SCA_KIFP.bgl (and companion CVX and PLC .bgl files) have a 10/5/2015 creation date. Guessing these were part of the original Orbx SCA region release. My SCA elevation_adjustment.bgl stubs like ADE_FTX_SCA_KIFP_elevation_adjustment.bgl also have 2015 creation dates. I had assumed in the P3D5 compatible versions of Orbx SCA, the airport elevation stubs (there are about 40-50 of them) had been tweaked to match for P3D5, since there was no longer an AEC tool available. But apparently not. Is there any hope of a fix ? I usually fly in on Pilot Edge in SoCal, so SCA is an important scenery! Many thanks Chuck O
  8. Hi Nick - Need your advice on resolving an Orbx SCA KIFP elevation issue I've encountered under P3D5.1. Runways/ramps and some scenery float above the terrain. KIFP has an elevation adjustment; on my P3D5.1 system it's in X:\Orbx Library\p3dv5\NA Southern California\Scenery\World\scenery\ADE_FTX_SCA_KIFP_elevation_adjustment.bgl, among the Orbx NA Southern California Elevation Stubs down near the bottom (#305 or 309) of my scenery library priority, among all the other stubs for my Orbx scenery The P3D5.1 base for KIFP is in C:\Program Files\Lockheed Martin\Prepar3D v5\Scenery\0202\scenery\APX17190.bgl. It's #202 in my P3D5 scenery library, among all the other P3D5 base scenery The SCA KIFP SCA scenery is in X:\Orbx Library\p3dv5\NA Southern California\Orbx\FTX_NA\FTX_NA_SCA05_SCENERY\scenery\ADE_FTX_SCA_KIFP.bgl, and is #114 in my scenery library, alongside my dozen other Orbx regions. So all the parts for KIFP seem present. The Orbx stubs should be below all the P3D numbered base scenery in the library, right ? My other similarly ordered Orbx airports in the SCA region - like KEED, or KRAL or KSBD - that carry elevation stubs don't display any elevation issues. Couldn't find other reports about KIFP elevation on the forum. So I'm puzzled. What could it be about my KIFP files or installation that is isn't right ? Chuck O
  9. No, wasn't aware. I wonder how many others are. I can understand that due to .bgl changes and without a AEC tool in P3D5, conversion won't be easy.
  10. MilViz has released new version of KA350i for P3D4.5 and 5. https://milviz.com/flight/products/KA350/index.php How long till it will be avail for download on Central ? Chuck O
  11. Actually plateau appearance is result of FSX/P3D flat runway artifact. Chart shows R22/29 intersection as 4848' but the approach end of R4 is 4784' and R11 approach end is 4820'. Since this airport has an ILS on R11, best compromise could be to edit the .bgl to 4820'.
  12. P3D5 users using Vector will discover that FTX Global freeware KGJT Grand Junction Regional (ADE_FTX_FTXG_KGJT.BGL), appears on a plateau about 20 feet higher than surrounding P3D base scenery. BGL elevation 4858 ft is correct, as charted. Lacking the P3D4 AEC tool, will require elevation tweak to blend with surrounding elevations.
  13. These have been an issue for some people in some earlier FSX and P3D versions - see e.g. Holger's responses to posts in 2018 in FSX support forum but it seems there are more reports in P3D5 now. Lots of recent discussion on the LM forums e.g. https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=137646 Never noticed any towers in P3D4, but they've popped up in my newly installed P3D5HF2. Particularly visible at night. (I'm using P3D 5.0.32/3523, Orbx Base, Vector, and openLC NA in both P3D4 and P3D5. Don't see towers when flying in my Orbx western regions. I use Chaseplane, but see them even when CP isn't running, so it isn't a CP camera thing.) Since so many use Orbx products, it is hard to know whether this is an Orbx issue or strictly an LM P3D issue. Hope both Orbx and LM will elevate the priority and investigate Meanwhile, is deactivating hazards.bgl an acceptable workaround fix ? In his 2018 post (above) Holger cautioned that there was a downside to doing this. Does deactivating hazards.bgl create serious problems in P3D5 ? For those who have tried this, please share your experience. Chuck O
  14. Agree ! But does anyone know if you have both TE and the corresponding FTX region installed, do the small GA airports with their static aircraft and peopleflow that make FTX so fun for GA pilots still pop through ?
  15. Beautiful scenery Ed. But can TrueEarth Northern California coexist with Orbx's Northern California regional scenery ? If I have to deinstall my Northern California region, won't I lose all the small NCA airports with their wonderful details? Chuck
  16. Reporting that at KBZN Bozeman, the R30 entry sign at Taxiway A1 incorrectly reads "21-3", rather than"30-21".
  17. The latest Jepp IAP notes that the localizer is offset three degrees, and the glideslope is now 3.6 deg. In the interim till the scenery is updated, if you have ADE, open \Lockheed Martin\Prepar3D v4\Orbx\FTX_NA\FTX_AA_KSFF\Scenery\APX_KSFF.bgl, select the localizer object and open properties, add 3 degrees to the true heading, and change the glide slope to 3.6 degrees, recompile, and replace the existing file, backing up the original. Works ok.
  18. Nick - In addition to runway number update, the R22R localizer is misaligned in the scenery. The scenery .bgl has it aligned with the runway heading (218 deg), whereas in real world, it is offset (as noted on the IAP) 3 degrees left (to 221 deg), presumably for clearance from hilly terrain to the north. Anyone navigating to the correctly located AZTEM (IF/IAF), DIYSA or HANSN waypoints using current (e.g. Navigraph) databases will notice the significant misalignment. Hope you can put this on the fix list for the next KSFF update. Chuck O
  19. Thanks, Nick and Hanss. Will give it a try, but not migrate anything already installed. Do either of you know if SimStarterNG can handle the new library configurations ?
  20. Operating system: Win10 64 Simulator: P3D4.4 Screenshot: Issue: Hi Nick - I own dozens of Orbx global and NA sceneries for P3D4. But back in August after reading all the forum posts about problems with migration, AEC, MakeRunways, and - apparently - SimstarterNG compatibility, I've delayed updating from FTX Central 3 to Central 4, since my P3D4 scenery install is working well. But I don't want to remain an Orbx orphan. - Is it now safe for P3D4 users like me with prior Central 3 scenery installs to upgrade to Central 4, provided I don't migrate any prior sceneries ? (I assume no migration happens automatically). - Have the AEC and migration problems now been substantially resolved ? - If I remain with FTX Central, what will I miss, other than improved download features ? Will scenery and library updates still continue normally ? - If I purchase new Orbx products, will they appear in FTX Central 3 normally ? Would appreciate any advice. Many thanks. Chuck O
  21. Anyone who has installed FTX Global freeware airport KFLG should be aware: ILS R21 localizer was recently reoriented, and associated waypoints were changed. Real world final R21 LOC approach course is now 214 deg, not 211. Waypoint names have changed. Missed is now to OATES, not a hold over FLG. RNAV (GPS) final approach course is also now 214, and waypoints have changed. RNAV (GPS) R3 unchanged.
  22. Anyone else who has flown the KASE LINDZ8 DP noticed when intercepting the offset LDA IPKN (108.5) that the CDI needle sense is not a published ? When the loc comes in after takeoff, the needle should be deflected to the left. IPKN is charted as a back course offset LDA, with feather shading on the right flying outbound, indicating you should fly towards the needle. Not sure how to try to fix in ADE. Is it fixable ?
  23. For next FTX NA KSFF Felts Field update: parallel runways 3/21 were recently renumbered 4/22. R22R ILS heading is now 221, no longer 216.
  24. Running P3Dv3.4 with Orbx FTX Global, Vector, & OLC Norh America, and the regionals including Northern Rockies, installed via FTX Central Vector Configurator AEC was previously run and applied. Flew into 43D Odessa Municipal Airport - a small GA airport near the border of NRM and CRM. Wanted to flag that the taxiway textures aren't right. They flash on and then disappear. Repeatable on rerunning. Don't see 43D in either lists of AEC enabled or disabled. Guessing some inconsistency in elevation. Not a huge deal, but something to put on the list.
  • Create New...