Hi, I tinkered with ADE a long time ago, but very basic. In the screen shot of KIFP, you can see how the river is messed up looking like a wall. Would this be fixable with ADE? If so, could someone point me in the right direction to try? Also I have P3D V4, I think it ADE works with it now. Thanks for any help.
-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
P3D v4 Terrain help
- Thread starter bobdee
- Start date
Hi Arno, so the elevation can be changed with ADE ? Someone did a nice job editing this airport a long time ago, & that elevation got messed up some how. The apron you speak of doesn't even exist anymore, so some work is needed. First the river bank needs fixing. Thanks,
- Messages
- 34,335
- Country
You should be able to do it in ADE. You can make flattens and other terrain vectors with it as well. A river is a terrain vector as well. But since the elevation is messed up, I would first check the flatten before touching the river.
Hi Bob:
If you tell us which add-on scenery (or sceneries) you have downloaded and installed for the KIFP area (and/or whether you have OrbX FTX Global / Vector etc. installed), we can advise you better.
FYI: Nearly all add-on scenery created for FSX will work properly in P3Dv4, but one may need to adjust the KIFP add-on scenery Area layer position in the Scenery Library GUI to configure all add-on BGLs in any KIFP scenery add-ons, so that they can be rendered properly in FS / P3D at run time.
NOTE: The FSX default scenery does not show the anomalies seen in your screenshot above:
You can verify this yourself if you download / install the Prepar3D v4 SDK:
http://www.prepar3d.com/support/sdk/
...then "Run as Administrator" P3Dv4 SDK TMFViewer
BTW: P3Dv4 SDK default install file / folder path is:
C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.28.21686\World\Terrain\tmfviewer.exe
...then load (P3Dv4 equivalent of):
[FSX / P3D install path]\Scenery\0202\scenery\dem0202.bgl
...and:
[FSX / P3D install path]\Scenery\0202\scenery\cvx1719.bgl
I suggest:
1.) Load the above default files into P3Dv4 SDK TMFViewer
2.) TMFViewer > Jump > Lat Long... set coordinates at: LAT: 35.160811, LON: -114.561724
3.) TMFViewer > View > LOD Grid: 12 (terrain grid 'quad' size)
4.) TMFViewer > View > QMID Grid: 11 (terrain grid 'quad' size)
'Jump' to the local coordinates, 'Zoom' in/out with +/- keys, then move the mouse cursor over areas in question; note elevation "Value" in Meters MSL on the bottom status bar.
I believe you will see that the default terrain mesh shows none of the above reported anomalies.
IMHO, this raises questions as to whether you have an issue with a custom terrain mesh and/or a custom CVX vector BGL from (1) or more KIFP add-on airport scenery package(s).
Additionally, one might wonder whether any of the KIFP add-on airport scenery package(s) you are using may have been compiled for use in FS9 ?
Hope this helps with troubleshooting your run time rendering anomalies at KIFP.
GaryGB
If you tell us which add-on scenery (or sceneries) you have downloaded and installed for the KIFP area (and/or whether you have OrbX FTX Global / Vector etc. installed), we can advise you better.
FYI: Nearly all add-on scenery created for FSX will work properly in P3Dv4, but one may need to adjust the KIFP add-on scenery Area layer position in the Scenery Library GUI to configure all add-on BGLs in any KIFP scenery add-ons, so that they can be rendered properly in FS / P3D at run time.
NOTE: The FSX default scenery does not show the anomalies seen in your screenshot above:
You can verify this yourself if you download / install the Prepar3D v4 SDK:
http://www.prepar3d.com/support/sdk/
...then "Run as Administrator" P3Dv4 SDK TMFViewer
BTW: P3Dv4 SDK default install file / folder path is:
C:\Program Files\Lockheed Martin\Prepar3D v4 SDK 4.0.28.21686\World\Terrain\tmfviewer.exe
...then load (P3Dv4 equivalent of):
[FSX / P3D install path]\Scenery\0202\scenery\dem0202.bgl
...and:
[FSX / P3D install path]\Scenery\0202\scenery\cvx1719.bgl
I suggest:
1.) Load the above default files into P3Dv4 SDK TMFViewer
2.) TMFViewer > Jump > Lat Long... set coordinates at: LAT: 35.160811, LON: -114.561724
3.) TMFViewer > View > LOD Grid: 12 (terrain grid 'quad' size)
4.) TMFViewer > View > QMID Grid: 11 (terrain grid 'quad' size)
'Jump' to the local coordinates, 'Zoom' in/out with +/- keys, then move the mouse cursor over areas in question; note elevation "Value" in Meters MSL on the bottom status bar.
I believe you will see that the default terrain mesh shows none of the above reported anomalies.
IMHO, this raises questions as to whether you have an issue with a custom terrain mesh and/or a custom CVX vector BGL from (1) or more KIFP add-on airport scenery package(s).
Additionally, one might wonder whether any of the KIFP add-on airport scenery package(s) you are using may have been compiled for use in FS9 ?
Hope this helps with troubleshooting your run time rendering anomalies at KIFP.
GaryGB
Last edited:
Hi Bob:
The "kifp_v2.zip" add-on scenery package you refer to is at flightsim.com:
"FSX - FSX Scenery FSX Scenery--Laughlin/Bullhead International Airport
[ Download | View ]
Name: kifp_v2.zip
Size: 8,983,092 Date: 01-02-2016 Downloads: 465
FSX Scenery--Laughlin/Bullhead International Airport. Bullhead City Airport (KIFP), Bullhead, Arizona (AZ), USA. This is the second release. Re-designed AFCAD, scenery models for Laughlin, Nevada (NV) by Joseph Jasper. By Scott Peterson. (Previous version had 1238 downloads)."
https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=188542
If "kifp_v2.zip" is installed / loaded in FSX on my computer, I do not see the anomaly your screenshots show.
FYI: If this file is de-compiled with Patrick Germains CVXExtractor:
[KIFPv2 install path]\kifp_v2\scenery\KIFP_ADEX_SWP_CVX.bgl
...one will see that there are several CVX vector objects that do not have an assigned Altitude in Meters.
Of particular note is the Hydro, Shoreline, and Road Polygon vertices (in *.BLN extract format):
Whereas FS2002 and FS2004 accepted "-9999" as an Altitude attribute value with legacy format LWM vector objects to allow such objects to be 'terrain-mesh-clinging', FSX / P3D now requires a discrete Altitude value in Meters and/or a Slope value for Hydro Polygon vertices (aka "Waterpolys").
https://msdn.microsoft.com/en-us/library/cc707102.aspx#TheShp2VecTool
https://msdn.microsoft.com/en-us/library/cc707110.aspx
AFAIK, there is no accommodation in the default FSX or P3Dv4 Terrain.Cfg which would allow CVX vector Hydro polys compiled without assigned Altitudes for each polygon vertex, to display as 'terrain-mesh-clinging' ...that would prevent such Hydro polygons from cutting through the ground down to 0 meters AMSL, and yet the Colorado River displays normally on my FSX installation.
I do, however, have the Richard Ludowise / Luis Feliz-Tirado "Modified Terrain.Cfg" installed.
I guess we'll have to check and see if the GUIDs for the above CVX vector objects in question might actually be FS2Kx legacy objects enabled by the "Modified Terrain.Cfg" that somehow are still being rendered 'normally' on top of the terrain inside FSX.
GaryGB
The "kifp_v2.zip" add-on scenery package you refer to is at flightsim.com:
"FSX - FSX Scenery FSX Scenery--Laughlin/Bullhead International Airport
[ Download | View ]
Name: kifp_v2.zip
Size: 8,983,092 Date: 01-02-2016 Downloads: 465
https://www.flightsim.com/vbfs/fslib.php?do=copyright&fid=188542
If "kifp_v2.zip" is installed / loaded in FSX on my computer, I do not see the anomaly your screenshots show.
FYI: If this file is de-compiled with Patrick Germains CVXExtractor:
[KIFPv2 install path]\kifp_v2\scenery\KIFP_ADEX_SWP_CVX.bgl
...one will see that there are several CVX vector objects that do not have an assigned Altitude in Meters.
Of particular note is the Hydro, Shoreline, and Road Polygon vertices (in *.BLN extract format):
Code:
10,1,HydroPolygons_0_0
-114.573347568512,35.1949167251587,0
-114.572739601135,35.1938760280609,0
-114.572203159332,35.193538069725,0
-114.571781158447,35.1963812112808,0
-114.573719501495,35.1978188753128,0
-114.574077129364,35.1969820261002,0
-114.574048519135,35.196408033371,0
-114.573934078217,35.1959842443466,0
-114.573683738708,35.1955282688141,0
-114.573347568512,35.1949167251587,0
2,1,Shorelines_0_0
-114.572517871857,35.1999378204346,-9999
-114.57261800766,35.1988863945007,-9999
108,1,Shorelines_1_0
-114.573726654053,35.1978188753128,-9999
-114.573805332184,35.1976579427719,-9999
-114.574077129364,35.1969981193542,-9999
-114.574084281921,35.1967942714691,-9999
-114.574062824249,35.1965153217316,-9999
-114.574048519135,35.1963543891907,-9999
-114.573969841003,35.196048617363,-9999
-114.573905467987,35.1959091424942,-9999
-114.573712348938,35.1955550909042,-9999
-114.573268890381,35.1947396993637,-9999
-114.573140144348,35.1945465803146,-9999
-114.573032855988,35.1943373680115,-9999
-114.572746753693,35.1938599348068,-9999
-114.572725296021,35.1938438415527,-9999
-114.572668075562,35.1938223838806,-9999
-114.57261800766,35.1937687397003,-9999
-114.572582244873,35.1936185359955,-9999
-114.572582244873,35.1935434341431,-9999
-114.572696685791,35.1934361457825,-9999
-114.572789669037,35.1933610439301,-9999
-114.572861194611,35.193178653717,-9999
-114.572811126709,35.1929157972336,-9999
-114.572367668152,35.1917034387589,-9999
-114.572203159332,35.1911133527756,-9999
-114.572167396545,35.1909148693085,-9999
-114.57234621048,35.1907110214233,-9999
-114.572331905365,35.1905769109726,-9999
-114.572303295135,35.19047498703,-9999
-114.572224617004,35.1901906728745,-9999
-114.572081565857,35.1900082826614,-9999
-114.571459293365,35.1894021034241,-9999
-114.5712018013,35.1891070604324,-9999
-114.571151733398,35.1883721351624,-9999
-114.571044445038,35.1881575584412,-9999
-114.570908546448,35.1875782012939,-9999
-114.570829868317,35.1872938871384,-9999
-114.570672512054,35.1866555213928,-9999
-114.57062959671,35.1864624023438,-9999
-114.570529460907,35.1859796047211,-9999
-114.570500850677,35.1858186721802,-9999
-114.570550918579,35.1854807138443,-9999
-114.570457935333,35.185250043869,-9999
-114.570379257202,35.1850247383118,-9999
-114.570379257202,35.1849603652954,-9999
-114.570407867432,35.1847726106644,-9999
-114.570508003235,35.1846867799759,-9999
-114.570465087891,35.184354186058,-9999
-114.570479393005,35.1842415332794,-9999
-114.570472240448,35.1837748289108,-9999
-114.570651054382,35.1819777488709,-9999
-114.570651054382,35.1816344261169,-9999
-114.570622444153,35.1814466714859,-9999
-114.570515155792,35.1810014247894,-9999
-114.570508003235,35.1808351278305,-9999
-114.570515155792,35.1807332038879,-9999
-114.570572376251,35.1786518096924,-9999
-114.570622444153,35.1771712303162,-9999
-114.570651054382,35.1759535074234,-9999
-114.570615291595,35.1755028963089,-9999
-114.570608139038,35.1752293109894,-9999
-114.570543766022,35.1746338605881,-9999
-114.570558071136,35.1745426654816,-9999
-114.570500850677,35.1734107732773,-9999
-114.570500850677,35.1730781793594,-9999
-114.57052230835,35.1730298995972,-9999
-114.570515155792,35.1727026700974,-9999
-114.570529460907,35.1723915338516,-9999
-114.570515155792,35.1720321178436,-9999
-114.570529460907,35.1718980073929,-9999
-114.570550918579,35.1718765497208,-9999
-114.570550918579,35.1718175411224,-9999
-114.570529460907,35.1717799901962,-9999
-114.570486545563,35.1712864637375,-9999
-114.570443630219,35.1706910133362,-9999
-114.57049369812,35.169752240181,-9999
-114.570550918579,35.1692533493042,-9999
-114.570593833923,35.1686954498291,-9999
-114.570622444153,35.1683360338211,-9999
-114.570643901825,35.1679444313049,-9999
-114.570593833923,35.1677888631821,-9999
-114.57049369812,35.1676332950592,-9999
-114.570472240448,35.1674723625183,-9999
-114.570508003235,35.1672202348709,-9999
-114.570608139038,35.1669895648956,-9999
-114.570686817169,35.166694521904,-9999
-114.570744037628,35.1665282249451,-9999
-114.5707654953,35.1663833856583,-9999
-114.570837020874,35.1655358076096,-9999
-114.570894241333,35.1649993658066,-9999
-114.57090139389,35.1648169755936,-9999
-114.570894241333,35.1645219326019,-9999
-114.571108818054,35.1629555225372,-9999
-114.571173191071,35.1621401309967,-9999
-114.571208953857,35.1619899272919,-9999
-114.571208953857,35.1618450880051,-9999
-114.571187496185,35.1617324352264,-9999
-114.571123123169,35.1611799001694,-9999
-114.571151733398,35.1608687639236,-9999
-114.571216106415,35.1605844497681,-9999
-114.571373462677,35.1604235172272,-9999
-114.571373462677,35.1603215932846,-9999
-114.571352005005,35.1601392030716,-9999
-114.571259021759,35.1595169305801,-9999
-114.571294784546,35.1593238115311,-9999
-114.571387767792,35.1592111587524,-9999
-114.571509361267,35.158599615097,-9999
-114.571580886841,35.1583850383759,-9999
-114.57177400589,35.1576554775238,-9999
4,1,Shorelines_2_0
-114.57177400589,35.1576554775238,-9999
-114.571866989136,35.1569902896881,-9999
-114.571895599365,35.1567435264587,-9999
-114.57190990448,35.15625,-9999
3,1,Shorelines_3_0
-114.57190990448,35.15625,-9999
-114.57190990448,35.1562339067459,-9999
-114.57190990448,35.1562339067459,-9999
4,1,Roads_0_0
-114.557590484619,35.1704925298691,-9999
-114.55780506134,35.1701599359512,-9999
-114.557719230652,35.1682716608047,-9999
-114.55766916275,35.1673918962479,-9999
16,1,Roads_1_0
-114.557704925537,35.1683467626572,-9999
-114.557118415833,35.1679122447968,-9999
-114.556889533997,35.1677942276001,-9999
-114.556438922882,35.1676601171494,-9999
-114.555451869965,35.1673758029938,-9999
-114.555294513702,35.1673328876495,-9999
-114.554615020752,35.1671558618546,-9999
-114.554393291473,35.16705930233,-9999
-114.554028511047,35.1668018102646,-9999
-114.553742408752,35.166517496109,-9999
-114.553513526917,35.1662868261337,-9999
-114.553241729736,35.165981054306,-9999
-114.55276966095,35.1657289266586,-9999
-114.552583694458,35.1656430959702,-9999
-114.552240371704,35.1656377315521,-9999
-114.55176115036,35.1656645536423,-9999
8,1,Roads_2_0
-114.552204608917,35.1656430959702,-9999
-114.552040100098,35.1637548208237,-9999
-114.552068710327,35.1632452011108,-9999
-114.552433490753,35.1626229286194,-9999
-114.552891254425,35.1621133089066,-9999
-114.55347776413,35.1614159345627,-9999
-114.553663730621,35.1609706878662,-9999
-114.553542137146,35.15625,-9999
8,1,Roads_3_0
-114.57245349884,35.1686149835587,-9999
-114.58075761795,35.1684272289276,-9999
-114.582731723785,35.1683950424194,-9999
-114.583268165588,35.1686149835587,-9999
-114.583582878113,35.168851017952,-9999
-114.583611488342,35.1691514253616,-9999
-114.583625793457,35.1715868711472,-9999
-114.583625793457,35.1715868711472,-9999
2,1,Roads_4_0
-114.580671787262,35.1610028743744,-9999
-114.580771923065,35.1716351509094,-9999
4,1,Roads_5_0
-114.575092792511,35.1610833406448,-9999
-114.581873416901,35.1609545946121,-9999
-114.583475589752,35.1604825258255,-9999
-114.589269161224,35.15625,-9999
8,1,Roads_6_0
-114.574835300446,35.15625,-9999
-114.575071334839,35.1604557037354,-9999
-114.575092792511,35.1611852645874,-9999
-114.574434757233,35.1630520820618,-9999
-114.573090076447,35.1656967401505,-9999
-114.572668075562,35.1670056581497,-9999
-114.572567939758,35.1679980754852,-9999
-114.571537971497,35.1721662282944,-9999
4,1,Roads_7_0
-114.574778079987,35.1622098684311,-9999
-114.574835300446,35.1622045040131,-9999
-114.57515001297,35.1622045040131,-9999
-114.575278759003,35.1624298095703,-9999
2,1,Roads_8_0
-114.575271606445,35.1619952917099,-9999
-114.57515001297,35.1622098684311,-9999
3,1,Roads_9_0
-114.557676315308,35.1673918962479,-9999
-114.557676315308,35.1671397686005,-9999
-114.55756187439,35.1671397686005,-9999
2,1,Roads_10_0
-114.573690891266,35.1645487546921,-9999
-114.580700397491,35.164532661438,-9999
4,1,Roads_11_0
-114.573419094086,35.1676976680756,-9999
-114.572632312775,35.1675528287888,-9999
-114.572632312775,35.1675528287888,-9999
-114.572632312775,35.1675474643707,-9999
4,1,Roads_12_0
-114.573419094086,35.1676976680756,-9999
-114.573783874512,35.1678961515427,-9999
-114.574613571167,35.1681268215179,-9999
-114.574613571167,35.1681268215179,-9999
3,1,Roads_13_0
-114.574449062347,35.1685559749603,-9999
-114.574613571167,35.1681268215179,-9999
-114.57599401474,35.1645594835281,-9999
3,1,Roads_14_0
-114.576745033264,35.1645648479462,-9999
-114.575200080872,35.1685452461243,-9999
-114.575200080872,35.1685452461243,-9999
3,1,Roads_15_0
-114.575879573822,35.1685291528702,-9999
-114.576852321625,35.1660400629044,-9999
-114.575643539429,35.1655036211014,-9999
4,1,Roads_16_0
-114.577081203461,35.1645702123642,-9999
-114.577031135559,35.1649296283722,-9999
-114.578289985657,35.1649349927902,-9999
-114.578318595886,35.1645487546921,-9999
7,1,Roads_17_0
-114.578282833099,35.1649403572083,-9999
-114.577803611755,35.1660025119781,-9999
-114.577689170837,35.1662439107895,-9999
-114.57738161087,35.1670807600021,-9999
-114.577567577362,35.1677352190018,-9999
-114.577960968018,35.1681858301163,-9999
-114.577960968018,35.1684755086899,-9999
2,1,Roads_18_0
-114.576816558838,35.1661258935928,-9999
-114.577610492706,35.1663619279861,-9999
2,1,Roads_19_0
-114.576480388641,35.1669842004776,-9999
-114.577367305756,35.1670914888382,-9999
5,1,Roads_20_0
-114.574656486511,35.1645541191101,-9999
-114.574656486511,35.1666355133057,-9999
-114.574635028839,35.167064666748,-9999
-114.574384689331,35.1680356264114,-9999
-114.574384689331,35.1680356264114,-9999
2,1,Roads_21_0
-114.575636386871,35.1654928922653,-9999
-114.574670791626,35.1651656627655,-9999
3,1,Roads_22_0
-114.572675228119,35.167064666748,-9999
-114.573040008545,35.1671290397644,-9999
-114.573040008545,35.1671290397644,-9999
3,1,Roads_23_0
-114.553542137146,35.15625,-9999
-114.553499221802,35.1544904708862,-9999
-114.553492069244,35.1544636487961,-9999
2,1,Roads_24_0
-114.589269161224,35.15625,-9999
-114.589283466339,35.1562392711639,-9999
2,1,Roads_25_0
-114.574828147888,35.1562124490738,-9999
-114.574835300446,35.15625,-9999
2,1,Roads_26_0
-114.554064273834,35.1561534404755,-9999
-114.553549289703,35.1561534404755,-9999Whereas FS2002 and FS2004 accepted "-9999" as an Altitude attribute value with legacy format LWM vector objects to allow such objects to be 'terrain-mesh-clinging', FSX / P3D now requires a discrete Altitude value in Meters and/or a Slope value for Hydro Polygon vertices (aka "Waterpolys").
https://msdn.microsoft.com/en-us/library/cc707102.aspx#TheShp2VecTool
https://msdn.microsoft.com/en-us/library/cc707110.aspx
AFAIK, there is no accommodation in the default FSX or P3Dv4 Terrain.Cfg which would allow CVX vector Hydro polys compiled without assigned Altitudes for each polygon vertex, to display as 'terrain-mesh-clinging' ...that would prevent such Hydro polygons from cutting through the ground down to 0 meters AMSL, and yet the Colorado River displays normally on my FSX installation.
I do, however, have the Richard Ludowise / Luis Feliz-Tirado "Modified Terrain.Cfg" installed.
I guess we'll have to check and see if the GUIDs for the above CVX vector objects in question might actually be FS2Kx legacy objects enabled by the "Modified Terrain.Cfg" that somehow are still being rendered 'normally' on top of the terrain inside FSX.
GaryGB
Attachments
Last edited:
Hi Bob:
We should also consider the possibility that any Airport Background / Boundary CVX vector flatten polygons which extend over to the area near the edge of the river may not have the proper assigned Altitude(s).
As Arno has alluded to above, it is possible that you may be able to change the elevation of 1 or more flattens extending between the airport and the river to make the area look somewhat normal.
Since we do not have the "KIFP_ADEX_SWP.ADE[2,3 or 4] project file available to examine the Altitude and GUID attributes assigned to the CVX vector parts of this airport project ouput by ADE and compiled via FSX SDK SHP2VEC into KIFP_ADEX_SWP_CVX.bgl, the latter information above can instead only be seen in SBuilderX via some special procedures.
If you are intent on fixing this for yourself (for your own personal use only), further instructions can be provided at your request within this thread ...regarding how to implement such a fix using SBuilderX.
Otherwise you may have to rebuild portions of the CVX vector parts of this airport project in ADE.
That might prove to be an interesting project using the new P3Dv4-compatible version of ADE.
GaryGB
We should also consider the possibility that any Airport Background / Boundary CVX vector flatten polygons which extend over to the area near the edge of the river may not have the proper assigned Altitude(s).
As Arno has alluded to above, it is possible that you may be able to change the elevation of 1 or more flattens extending between the airport and the river to make the area look somewhat normal.
Since we do not have the "KIFP_ADEX_SWP.ADE[2,3 or 4] project file available to examine the Altitude and GUID attributes assigned to the CVX vector parts of this airport project ouput by ADE and compiled via FSX SDK SHP2VEC into KIFP_ADEX_SWP_CVX.bgl, the latter information above can instead only be seen in SBuilderX via some special procedures.
If you are intent on fixing this for yourself (for your own personal use only), further instructions can be provided at your request within this thread ...regarding how to implement such a fix using SBuilderX.
Otherwise you may have to rebuild portions of the CVX vector parts of this airport project in ADE.
That might prove to be an interesting project using the new P3Dv4-compatible version of ADE.
GaryGB
Attachments
Last edited:
Gary, I very much appreciate your efforts to help me with this problem. I had no idea it was going to be that involved. This is way over my head, that said I think I'll just give up on it. I like to tinker a bit with program, but not to that extent. Sorry for wasting your time, & again thank you.
No problem. Bob.
When I reply to posts I typically try to provide info that may be of interest to others involved with more complex aspects of FS development who may read a thread ...as well as to the original person with an inquiry.
But since I do not (yet) have P3Dv4 to test this add-on scenery, we are both potentially at a loss to determine whether there is something different in the way that source data for such a CVX vector BGL may be rendered different in P3Dv4 versus FSX, or whether you may have some interfering files active elsewhere in the P3D Scenery Library stack of layers.
I provided the info for where the add-on can be freely downloaded; perhaps someone (even Arno or rhumbaflappy ?) might download and install that add-on to assist with adding to the FS Developer knowledge base regarding any possible new quirks in how this type of source data in a CVX vector BGL may be rendered different in P3Dv4 versus FSX.
Feel free to take your time with learning whatever FS development complexities you are inclined to, and have fun with flight simulation !
GaryGB
When I reply to posts I typically try to provide info that may be of interest to others involved with more complex aspects of FS development who may read a thread ...as well as to the original person with an inquiry.
But since I do not (yet) have P3Dv4 to test this add-on scenery, we are both potentially at a loss to determine whether there is something different in the way that source data for such a CVX vector BGL may be rendered different in P3Dv4 versus FSX, or whether you may have some interfering files active elsewhere in the P3D Scenery Library stack of layers.
I provided the info for where the add-on can be freely downloaded; perhaps someone (even Arno or rhumbaflappy ?) might download and install that add-on to assist with adding to the FS Developer knowledge base regarding any possible new quirks in how this type of source data in a CVX vector BGL may be rendered different in P3Dv4 versus FSX.
Feel free to take your time with learning whatever FS development complexities you are inclined to, and have fun with flight simulation !
GaryGB
Hi Gary, is their any way you, or anyone with enough expertise to make kifp_v2 compatible with P3D V4? Don't know if you need permissions or not from the original maker. I actually contacted him, & found out he is still with FSX & no plans to get P3D, so no help there.
Bob,
Bob,
Hi Bob:
Because I don't have P3Dv4 to personally test how the kifp_v2 scenery package (cited in our latter posts to this thread above) actually renders in P3Dv4 at run time, I may not be able to assist 'adequately'.
I did not, however, see any terrain anomalies on a cursory inspection of kifp_v2 in FSX SP2 / Acceleration.
It is indeed possible that someone else who does already have P3Dv4 would be able to offer feedback on how the kifp_v2 scenery package renders in P3Dv4 at run time on their own computer.
Bearing in mind that nearly all default scenery provided with a purchase of LM's P3Dv4 is derived from FSX SP2 (aka "ESP"), nearly all FSX compatible "terrain"-type scenery including terrain mesh and CVX vector BGLs "should" work OK, as they are essentially FSX scenery.
But that is not a guarantee that there is 'no' difference in how that scenery package will work in LM's P3Dv4.
So an initial recommendation would be to make certain that you have all add-on scenery other than the kifp_v2 scenery package disabled in the P3Dv4 scenery library GUI stack of layers during testing.
Also, if either you- or automatic installers for 3rd party add-on scenery packages- have added BGLs and mapped textures to any P3Dv4 equivalent of the FSX "Addon Scenery\Scenery" and "Addon Scenery\Texture" sub-folders (which, by default would be located in a lower position within the Scenery Library GUI 'stack of Area layers), they should be:
1.) Moved into new \Scenery and \Texture sub-folders nested under a 'top-folder' ...with its own new Area layer located at- or near- the top of the Scenery Library GUI 'stack of Area layers'
2.) Set as 'disabled' or 'not active' within the Scenery Library GUI 'stack of Area layers' when testing kifp_v2 in P3Dv4.
Since I do not see any anomaly in FSX, I am more inclined to suspect 1 or more terrain-type mesh or CVX vector BGL(s) that are either located at an improper location within the Scenery Library GUI 'stack of Area layers', or which may conflict with other 3rd party terrain-type mesh or CVX vector BGL(s) that have not yet been successfully 'de-activated' within the Scenery Library GUI 'stack of Area layers'.
PS: One of the procedural goals for use of add-ons in P3Dv3 and P3Dv4 was to keep all add-ons OUTSIDE the Prepar3d sub-folder chain.
AFAIK, very few add-on installers use the recommended procedure; you may wish to review these threads on the topic:
https://www.avsim.com/forums/topic/...-add-sceneryaddons-into-p3d-v4-the-right-way/
https://www.avsim.com/forums/topic/512368-prepar3d-v4-addon-organizer-094-released/
http://lorby-si.weebly.com/downloads.html
Hope this helps a bit more !
GaryGB
Because I don't have P3Dv4 to personally test how the kifp_v2 scenery package (cited in our latter posts to this thread above) actually renders in P3Dv4 at run time, I may not be able to assist 'adequately'.
I did not, however, see any terrain anomalies on a cursory inspection of kifp_v2 in FSX SP2 / Acceleration.
It is indeed possible that someone else who does already have P3Dv4 would be able to offer feedback on how the kifp_v2 scenery package renders in P3Dv4 at run time on their own computer.
Bearing in mind that nearly all default scenery provided with a purchase of LM's P3Dv4 is derived from FSX SP2 (aka "ESP"), nearly all FSX compatible "terrain"-type scenery including terrain mesh and CVX vector BGLs "should" work OK, as they are essentially FSX scenery.
But that is not a guarantee that there is 'no' difference in how that scenery package will work in LM's P3Dv4.
So an initial recommendation would be to make certain that you have all add-on scenery other than the kifp_v2 scenery package disabled in the P3Dv4 scenery library GUI stack of layers during testing.
Also, if either you- or automatic installers for 3rd party add-on scenery packages- have added BGLs and mapped textures to any P3Dv4 equivalent of the FSX "Addon Scenery\Scenery" and "Addon Scenery\Texture" sub-folders (which, by default would be located in a lower position within the Scenery Library GUI 'stack of Area layers), they should be:
1.) Moved into new \Scenery and \Texture sub-folders nested under a 'top-folder' ...with its own new Area layer located at- or near- the top of the Scenery Library GUI 'stack of Area layers'
2.) Set as 'disabled' or 'not active' within the Scenery Library GUI 'stack of Area layers' when testing kifp_v2 in P3Dv4.
Since I do not see any anomaly in FSX, I am more inclined to suspect 1 or more terrain-type mesh or CVX vector BGL(s) that are either located at an improper location within the Scenery Library GUI 'stack of Area layers', or which may conflict with other 3rd party terrain-type mesh or CVX vector BGL(s) that have not yet been successfully 'de-activated' within the Scenery Library GUI 'stack of Area layers'.
PS: One of the procedural goals for use of add-ons in P3Dv3 and P3Dv4 was to keep all add-ons OUTSIDE the Prepar3d sub-folder chain.
AFAIK, very few add-on installers use the recommended procedure; you may wish to review these threads on the topic:
https://www.avsim.com/forums/topic/...-add-sceneryaddons-into-p3d-v4-the-right-way/
https://www.avsim.com/forums/topic/512368-prepar3d-v4-addon-organizer-094-released/
http://lorby-si.weebly.com/downloads.html
Hope this helps a bit more !
GaryGB
Last edited:
Hi Bob:
It is reasonably likely, based on your above linked screen captures of the terrain anomaly between the airport and the river, that there is- at the least- an assigned elevation issue with a flatten (whether "flat" or "sloped") or other type of terrain polygon CVX vector BGL ...as Arno suggested.
Also, there appears to be a display of "Land popping up through a Water body drawn over sloped terrain" in the river shoreline area nearest to the airport.
Additionally, your first screen capture shows a terrain polygon in the area of the RWY-16 PAPI lights that is not displayed at the same level as the airport (...likely due to not having correctly assigned Altitude values in the vertices of the polygon source data to match the KIFP Airport Reference Point aka "ARP").
This 'may' be due to a difference in how P3Dv4 deals with assigned altitudes (or lack thereof) in a CVX vector BGL used for that flatten area compared to how FSX deals with such compiled Altitude attributes; but that would require confirmation by someone who actually has P3Dv4.
Also, I use a "Modified Terrain.Cfg" file which purposely eliminates the above "Land popping up through a Water body drawn over sloped terrain" which you likely are seeing since you do not have the same "Modified Terrain.Cfg" installed.
In theory, if one manually edited assigned altitudes in de-compiled CVX vector BGL(s) for that flatten area, then re-compiled the BGL(s), you should be able to force a "normal" terrain (and water) display in that area.
That process is what I alluded to above with use of Patrick Germains CVXExtractor and SBuilderX.
Alternatively, you could "Exclude and Replace" any / all of the CVX vector BGL(s) used for that flatten area associated with the terrain anomaly between the airport and the river ...using ADE.
If you would like to learn how to do this for yourself as a 'worked example' for the benefit of your own further enjoyment at this airport, and to help others here at FS Developer forum to learn how to fix malfunctioning display of FSX add-on scenery loaded into P3Dv4, perhaps we could proceed further with a guided, step-by step process in this thread.
Feel free to let me know whether you would like to proceed further with the described learning process.
PS: Do you have a history of a personal connection with this airport in real life ?
GaryGB
It is reasonably likely, based on your above linked screen captures of the terrain anomaly between the airport and the river, that there is- at the least- an assigned elevation issue with a flatten (whether "flat" or "sloped") or other type of terrain polygon CVX vector BGL ...as Arno suggested.
Also, there appears to be a display of "Land popping up through a Water body drawn over sloped terrain" in the river shoreline area nearest to the airport.
Additionally, your first screen capture shows a terrain polygon in the area of the RWY-16 PAPI lights that is not displayed at the same level as the airport (...likely due to not having correctly assigned Altitude values in the vertices of the polygon source data to match the KIFP Airport Reference Point aka "ARP").
This 'may' be due to a difference in how P3Dv4 deals with assigned altitudes (or lack thereof) in a CVX vector BGL used for that flatten area compared to how FSX deals with such compiled Altitude attributes; but that would require confirmation by someone who actually has P3Dv4.
Also, I use a "Modified Terrain.Cfg" file which purposely eliminates the above "Land popping up through a Water body drawn over sloped terrain" which you likely are seeing since you do not have the same "Modified Terrain.Cfg" installed.
In theory, if one manually edited assigned altitudes in de-compiled CVX vector BGL(s) for that flatten area, then re-compiled the BGL(s), you should be able to force a "normal" terrain (and water) display in that area.
That process is what I alluded to above with use of Patrick Germains CVXExtractor and SBuilderX.
Alternatively, you could "Exclude and Replace" any / all of the CVX vector BGL(s) used for that flatten area associated with the terrain anomaly between the airport and the river ...using ADE.
If you would like to learn how to do this for yourself as a 'worked example' for the benefit of your own further enjoyment at this airport, and to help others here at FS Developer forum to learn how to fix malfunctioning display of FSX add-on scenery loaded into P3Dv4, perhaps we could proceed further with a guided, step-by step process in this thread.
Feel free to let me know whether you would like to proceed further with the described learning process.
PS: Do you have a history of a personal connection with this airport in real life ?
GaryGB
Last edited:
That's a really a kind offer Gary, but I'm really not that interested in scenery design. Forty + years ago I would have been very interested. I just don't have the temperament anymore.
My first screen shot was a mistake, it was his version one, & was improved in two. I took a complete screen shot, & you can see, it's missing taxi ways .etc also. I could actually fix those basic problems myself, but the river kind of turns me off.
I still love to fly, especially with P3D V4 as it's the best FS available IMO. & been playing some form of MSFS since before it had it's own sound. Now I'm really hooked on VR, it feels like your really in the cockpit.
Yes, I do have history with this airport, I lived in Bullhead City for ten years.
Bob,
My first screen shot was a mistake, it was his version one, & was improved in two. I took a complete screen shot, & you can see, it's missing taxi ways .etc also. I could actually fix those basic problems myself, but the river kind of turns me off.
I still love to fly, especially with P3D V4 as it's the best FS available IMO. & been playing some form of MSFS since before it had it's own sound. Now I'm really hooked on VR, it feels like your really in the cockpit.
Yes, I do have history with this airport, I lived in Bullhead City for ten years.
Bob,
Attachments
Hi Bob:
I'm intrigued by the unusually gradual slope that is evident from the edge of the airport to the edge of the river, and it compels another question.
Do you have your P3Dv4 Terrain Mesh Complexity slider set to 100 % and your Terrain Mesh Resolution slider set to at least 10 Meters or smaller (ex: 5 Meters ...or even 1 Meter ), and your Texture Resolution slider at 7 cm ?
I am wondering if you may have the sliders reduced in favor of P3D run time performance.
PS: The slope extending to the river from the airport is less likely to be a complex thing to fix once we know what the cause is for that issue.
GaryGB
I'm intrigued by the unusually gradual slope that is evident from the edge of the airport to the edge of the river, and it compels another question.
Do you have your P3Dv4 Terrain Mesh Complexity slider set to 100 % and your Terrain Mesh Resolution slider set to at least 10 Meters or smaller (ex: 5 Meters ...or even 1 Meter ), and your Texture Resolution slider at 7 cm ?
I am wondering if you may have the sliders reduced in favor of P3D run time performance.
PS: The slope extending to the river from the airport is less likely to be a complex thing to fix once we know what the cause is for that issue.
GaryGB
Last edited:
Hi Bob:
I'll take a more detailed look at the KIFP_v2 CVX vector BGLs de-compiled to ESRI SHP files and appended to SBuilderX, to see if I can better understand what is going on with the river and adjacent East shoreline ...relative to the sloped terrain between that East shoreline and the airport.
[EDITED]
Looking at your first (very fuzzy and small !
) screen capture in the OP above at extreme zoom raises another question crucial to better understanding what you reported above.
Is both the East and West shoreline as well as the river water polygon raised significantly above the street level and base of the buildings ...which are located on both sides of the river ?
PS: Try this...
1.) Load a flight in P3Dv4 at KIFP RWY-34
2.) Slew the aircraft Eastward onto the river surface, and leave the aircraft at that location
3.) Start ADE in P3Dv4 mode
a.) ADE Menu > File > Open Airport From BGL
(1) Browse / Select KIFP: [kifp_v2 install path]\scenery\KIFP_ADEX_SWP.bgl
b.) Click [Connect] button in upper Right area of ADE work-space
c.) Read 'ground' Altitude in Meters (under user aircraft) from third parameter field in Red at upper Left of screen
d.) Please post that water body Altitude readout in a reply to this thread.
Also, please attach in that same reply to this thread, some larger, sharper screen captures taken from ground level looking at the river edge from both the East and West sides of the river.
[END_EDIT]
GaryGB
I'll take a more detailed look at the KIFP_v2 CVX vector BGLs de-compiled to ESRI SHP files and appended to SBuilderX, to see if I can better understand what is going on with the river and adjacent East shoreline ...relative to the sloped terrain between that East shoreline and the airport.
[EDITED]
Looking at your first (very fuzzy and small !
) screen capture in the OP above at extreme zoom raises another question crucial to better understanding what you reported above.Is both the East and West shoreline as well as the river water polygon raised significantly above the street level and base of the buildings ...which are located on both sides of the river ?
PS: Try this...
1.) Load a flight in P3Dv4 at KIFP RWY-34
2.) Slew the aircraft Eastward onto the river surface, and leave the aircraft at that location
3.) Start ADE in P3Dv4 mode
a.) ADE Menu > File > Open Airport From BGL
(1) Browse / Select KIFP: [kifp_v2 install path]\scenery\KIFP_ADEX_SWP.bgl
b.) Click [Connect] button in upper Right area of ADE work-space
c.) Read 'ground' Altitude in Meters (under user aircraft) from third parameter field in Red at upper Left of screen
d.) Please post that water body Altitude readout in a reply to this thread.
Also, please attach in that same reply to this thread, some larger, sharper screen captures taken from ground level looking at the river edge from both the East and West sides of the river.
[END_EDIT]
GaryGB
Last edited: