Noel Posted March 12, 2016 Share Posted March 12, 2016 Looks like some areas might but I'm not certain. Seems like mesh is really weak throughout FSX/P3D world. I learned about FreeMeshX but not sure it's really much better over default P3D V3 mesh--just from looking at its specs not from trying it. And do FTX regions utilize higher resolution mesh? I would happily pay $$ for a high resolution mesh it seems like it would add a lot provided the runway area terrain elevation problems aren't there. Link to comment Share on other sites More sharing options...
Alex Goff Posted March 12, 2016 Share Posted March 12, 2016 All of the regions except for Ireland and Australia have custom mesh included. The NA regions are 10m mesh in the US, and I believe 20m in Canada. New Zealand is 10m as well, same with all Europe except (again) Ireland. Link to comment Share on other sites More sharing options...
Holger Sandmann Posted March 12, 2016 Share Posted March 12, 2016 Hi Noel, to add to what Alex has stated the terrain mesh files made for the regions are always made from the best available (and affordable) source data and often blend different sources together for better local accuracy. For example, the NA regions are based on the USGS 10m data. However, since these are quite ancient (1940s-60s) and thus miss a surprising number of human-made surface changes for roads and railroads (i.e., cuts and fills) we blend in modern 3-m LIDAR data or similar sources to minimize unsightly "rollercoaster" highways across hilly terrain. Also keep in mind that the elevations and local "sculpting" of airports and lakes/rivers within an FTX Region are fit to our terrain mesh data meaning that using other mesh files may cause local terrain steps or other blending issues. Cheers, Holger Link to comment Share on other sites More sharing options...
pmb Posted March 14, 2016 Share Posted March 14, 2016 On 12.3.2016 at 5:41 PM, Holger Sandmann said: Also keep in mind that the elevations and local "sculpting" of airports and lakes/rivers within an FTX Region are fit to our terrain mesh data meaning that using other mesh files may cause local terrain steps or other blending issues. Cheers, Holger Which might pose a potential issue after we've got the unified lclookup without region switching. Outside of fat Regions (in OpenLC land) you will nee a 3rd party mesh (say one of the Pilot's flavors) - which however might interfere when you enter a Region being optimized for Holger mesh. Thus you would have to again "switch" mesh in the scenery library from, say, Holger mesh Australia to Pilot's at the borderline. Is this a pseudo problem or a real one? Thanks and kind regards, Michael Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.