Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Create terrain vertices per surface type | Dan Goodliffe | 2024-04-12 |
| | |||
* | Introduce a basic terrain surface type asset | Dan Goodliffe | 2024-04-10 |
| | |||
* | Add GeoData face property for surface type | Dan Goodliffe | 2024-04-08 |
| | | | | Arbitrary int type for now. | ||
* | Update normals only as required | Dan Goodliffe | 2024-04-04 |
| | |||
* | Add lots of simple triangle property helpers | Dan Goodliffe | 2024-04-01 |
| | |||
* | Replace face 4-way split | Dan Goodliffe | 2024-04-01 |
| | | | | Fixes integer rounding issue and returns the new face handles | ||
* | Factor out some helper lambdas into members | Dan Goodliffe | 2024-03-31 |
| | |||
* | Psycho-rebased branch deform-terrain on top of main | Dan Goodliffe | 2024-02-24 |
|\ | |||
| * | First cut of terrain deformation | Dan Goodliffe | 2024-02-22 |
| | | | | | | | | | | | | | | | | | | | | This "works" for some definition of works... But it's flawed in many ways, not least the following: * It's glitchy for no obvious reason * It's unreliable; fails if you tweak the parameters * The sides of the modified area are triangulated in the dumbest possible fashion, which results in ill-formed polygons * Probably other things, but... It works, remember... | ||
| * | Fix getting cartesian coords from triangle baripos | Dan Goodliffe | 2024-02-14 |
| | | |||
| * | Include face handle in intersectRay result | Dan Goodliffe | 2024-02-13 |
| | | |||
| * | Add helpers for testing for triangle overlap/containedness | 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 |
| | |||
* | 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. | ||
| * | 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. | ||
| * | WIP typedefing all the things - headers | Dan Goodliffe | 2023-11-07 |
| | | |||
| * | 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 |
| | | |||
* | | Add methods to walk the boundary of the terrain mesh | Dan Goodliffe | 2023-11-05 |
| | | |||
* | | Simplify some logic with the triangle construct | Dan Goodliffe | 2023-11-04 |
| | | |||
* | | Rename TerrainMesh to GeoData to drop inplace | Dan Goodliffe | 2023-11-04 |
|/ | |||
* | Remove useless GeoData default constructor | Dan Goodliffe | 2022-11-14 |
| | |||
* | 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 |
| | |||
* | 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 |