Commit message (Collapse) | Author | Age | ||
---|---|---|---|---|
... | ||||
| * | Include face handle in intersectRay result | Dan Goodliffe | 2024-02-13 | |
| | | ||||
| * | Add helpers for testing for triangle overlap/containedness | Dan Goodliffe | 2024-02-12 | |
| | | ||||
| * | Create flat GeoData as 10m squares instead of one big square | Dan Goodliffe | 2024-02-12 | |
| | | ||||
* | | Simplify vector addition/subtraction with differnt types | Dan Goodliffe | 2024-02-24 | |
|/ | | | | | Automatically applies correct rounding with float to int operations, adjusts test expectations accordingly. | |||
* | Template Ray on position type | Dan Goodliffe | 2024-01-07 | |
| | ||||
* | Unified crossProduct | Dan Goodliffe | 2024-01-07 | |
| | ||||
* | Use new calc types in geoData | Dan Goodliffe | 2023-12-17 | |
| | ||||
* | Handle the case where the ray never enters the map | Dan Goodliffe | 2023-12-02 | |
| | ||||
* | Extend ray for intersect walk to cover the extents of the map | Dan Goodliffe | 2023-12-02 | |
| | ||||
* | Replace positionAt with pure integer version | Dan Goodliffe | 2023-12-02 | |
| | ||||
* | Calculate vertex normals only | Dan Goodliffe | 2023-11-26 | |
| | | | | | | Doesn't require half edge normals or face normals, which uses Newell's method, which results in integer overflow... Not to mention we don't need all the other normals. | |||
* | Merge branch 'ints' into terrain | Dan Goodliffe | 2023-11-26 | |
|\ | | | | | | | | | | | Conflicts fix, compiles, some test failures remain. Trees not added, possibility of OM invalid handle assertion failures, normals broken due to integer overflow in Newell's method. | |||
| * | Model positions as integers | Dan Goodliffe | 2023-11-25 | |
| | | | | | | | | | | Introduces test failure in arcs due to rounding, but I don't want to create a complicated fix as link positions are still floats and hopefully that'll go away... somehow | |||
| * | Switch to millimeters for spatial units | Dan Goodliffe | 2023-11-15 | |
| | | | | | | | | | | | | Mostly a case of changing far too many magic numbers, something else to fix I guess. I probably missed something. Also there's some hackery when loading 3D models, which are still assumed to be in metres. | |||
| * | Reformat with new clang-format | Dan Goodliffe | 2023-11-07 | |
| | | ||||
* | | Fix todo for handling a terrain walk from outside the mesh | Dan Goodliffe | 2023-11-05 | |
| | | ||||
* | | Fix calculating extents | Dan Goodliffe | 2023-11-05 | |
| | | ||||
* | | Fix and split linesCross | Dan Goodliffe | 2023-11-05 | |
| | | | | | | | | | | Previous tested they crossed in a specific direction, which is wrong but useful. Adds linesCrossLtR for this use case. | |||
* | | Add methods to walk the boundary of the terrain mesh | Dan Goodliffe | 2023-11-05 | |
| | | ||||
* | | Refactor to further simplify line/point operations | Dan Goodliffe | 2023-11-04 | |
| | | | | | | | | Adds another perf test | |||
* | | Simplify some logic with the triangle construct | Dan Goodliffe | 2023-11-04 | |
| | | ||||
* | | Rename TerrainMesh to GeoData to drop inplace | Dan Goodliffe | 2023-11-04 | |
|/ | ||||
* | Drop .hpp for header only things | Dan Goodliffe | 2023-04-29 | |
| | | | | Half of them acquired a .cpp part anyway | |||
* | Fix up all the static analyzer warnings | Dan Goodliffe | 2023-01-08 | |
| | ||||
* | Rename rdiv to ratio and add a vec2 override | Dan Goodliffe | 2022-11-18 | |
| | ||||
* | Progressive constructors for RayTracer | Dan Goodliffe | 2022-01-13 | |
| | ||||
* | Fix up includes | Dan Goodliffe | 2022-01-13 | |
| | ||||
* | Ray Trace cursor clicks to terrain surface | Dan Goodliffe | 2022-01-10 | |
| | ||||
* | Tweak ray tracer calls to account for scale | Dan Goodliffe | 2022-01-08 | |
| | ||||
* | Initial commit GeoData ray tracer | Dan Goodliffe | 2022-01-07 | |
| | ||||
* | GeoData::quad works in world coordinates | Dan Goodliffe | 2022-01-06 | |
| | ||||
* | Extracting finding a surround geo quad into separate function | Dan Goodliffe | 2022-01-04 | |
| | ||||
* | Support for querying terrain height in GeoData | Dan Goodliffe | 2022-01-03 | |
| | ||||
* | Separate geographic data (GeoData) from its visual representation(s) (Terrain) | Dan Goodliffe | 2022-01-02 | |