Post by mal on Dec 31, 2020 10:57:56 GMT -5
OCC R&H 1st hole. Fairway sloping has striations where elevation data has been interpolated. Green has obvious muting to natural slope and break lines. If you know what to look for you can identify these same issues throughout the whole course. I had no idea that you used DEM files when I first played these courses, I just knew that something was "off." If you need to sculpt anything on a lidar/dem based course, your alignment to OSM is off, which I'm guessing you probably didn't have correct projection data coordinates and matching all this up had to take some considerable effort. The game actually "sculpts" surfaces automatically within the bunker spline which can cause anomalies with green-side and sheer face surfaces. Honestly, the fidelity within the game engine is sorely lacking in many situations...
Chadtools already tosses out a huge chuck of data from normal lidar files since the default resolution it processes the terrain is 2 square meters, but Chad did some pretty solid work with the smoothing algorithms, and we end up with green surfaces that are about 90% accurate. However, when elevation changes by a few feet on/near green surfaces you get some odd behavior due to how the game renders these surfaces. The putting surface breaklines become more dramatic than they would be IRL, but this usually works out fine in the game with how the putting physics are modeled.
In your case, you have done the opposite. You have taken data that has already had the source lidar averaged from 1M sq to 5M sq, and then asked chadtools to process this at 2M sq. While you do end up with an approximation of the terrain, it is almost as if the course has been processed through a gaussian blur filter. Again, for TGC2019 and when using a simulator, this may be acceptable, but on PGA2k21 with the increased fidelity and resolution of terrain rendering, and along with the differences in physics modeling, it becomes very noticeable.
What resolution is your yardage book?
In ArcGIS you can convert to slope data from those DEM files and create topo imagery to use for manually fine tuning the surfaces. Sadly, there is no substitute for the raw point cloud data.
There is always this: wingtra.com/mapping-drone-wingtraone/mapping-cameras/qx1-ppk-bundle/
Chadtools already tosses out a huge chuck of data from normal lidar files since the default resolution it processes the terrain is 2 square meters, but Chad did some pretty solid work with the smoothing algorithms, and we end up with green surfaces that are about 90% accurate. However, when elevation changes by a few feet on/near green surfaces you get some odd behavior due to how the game renders these surfaces. The putting surface breaklines become more dramatic than they would be IRL, but this usually works out fine in the game with how the putting physics are modeled.
In your case, you have done the opposite. You have taken data that has already had the source lidar averaged from 1M sq to 5M sq, and then asked chadtools to process this at 2M sq. While you do end up with an approximation of the terrain, it is almost as if the course has been processed through a gaussian blur filter. Again, for TGC2019 and when using a simulator, this may be acceptable, but on PGA2k21 with the increased fidelity and resolution of terrain rendering, and along with the differences in physics modeling, it becomes very noticeable.
What resolution is your yardage book?
In ArcGIS you can convert to slope data from those DEM files and create topo imagery to use for manually fine tuning the surfaces. Sadly, there is no substitute for the raw point cloud data.
There is always this: wingtra.com/mapping-drone-wingtraone/mapping-cameras/qx1-ppk-bundle/