Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Rewrite most of setHeights | Dan Goodliffe | 2024-03-08 |
| | | | | | Accounts for sensible corners and fixes quite a few bugs and edge cases... introduces a few more, is still a bit glitchy in places | ||
* | Bail out early if the input does not define an area | Dan Goodliffe | 2024-03-08 |
| | |||
* | Remove the nosplit list | Dan Goodliffe | 2024-02-24 |
| | | | | Not required now we don't randomly wonder into the new edges range | ||
* | 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 calculation of texture coords of terrain | Dan Goodliffe | 2024-02-22 |
| | | | | | | | | While we still use this... | ||
| * | 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 |
| | | |||
| * | 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. | ||
* | Remove the generic cache completely | Dan Goodliffe | 2024-01-26 |
| | |||
* | Remove the static texture cache | Dan Goodliffe | 2024-01-25 |
| | | | | | Static variables persist too long, destruction is unmanaged and occurs after the gl context is gone. | ||
* | Bind the network profile in as uniforms | Dan Goodliffe | 2024-01-22 |
| | | | | Makes the network shaders generic to network type | ||
* | Remove the old custom mesh per network link rendering | Dan Goodliffe | 2024-01-21 |
| | |||
* | Pass curve link radius, no recalculate, its constant | Dan Goodliffe | 2024-01-20 |
| | |||
* | Implement basic network curve part shader | Dan Goodliffe | 2024-01-20 |
| | |||
* | Update network with vertex array | Dan Goodliffe | 2024-01-20 |
| | |||
* | Render rail network using new shaders | Dan Goodliffe | 2024-01-20 |
| | | | | Non-functional, totally unimplemented at this stage | ||
* | Copy render vital link data to vertex buffer | Dan Goodliffe | 2024-01-20 |
| | |||
* | We only need 3x3 matrix for model rotation spec | Dan Goodliffe | 2024-01-13 |
| | |||
* | Only create VAOs for the light type(s) in use | Dan Goodliffe | 2024-01-13 |
| | |||
* | Merge common parts of light type vertices | Dan Goodliffe | 2024-01-13 |
| | |||
* | Minor tidy up | Dan Goodliffe | 2024-01-13 |
| | |||
* | Add model support for point lights | Dan Goodliffe | 2024-01-12 |
| | | | | Still invokes non-instanced point light shader | ||
* | Initial commit with working light instancing | Dan Goodliffe | 2024-01-10 |
| | |||
* | Add spot light definition, loader, and rendering | Dan Goodliffe | 2024-01-10 |
| | | | | Rendering is untested, data is passed to whatever GL program is currently active. | ||
* | Add the Illuminator (type) and Light (instance) classes | Dan Goodliffe | 2024-01-09 |
| | |||
* | Remove PositionxD from Network | Dan Goodliffe | 2024-01-07 |
| | |||
* | Global positions in network data | Dan Goodliffe | 2024-01-07 |
| | |||
* | Remove Position3D from RailVehicle | Dan Goodliffe | 2024-01-07 |
| | |||
* | Template Ray on position type | Dan Goodliffe | 2024-01-07 |
| | |||
* | Unified crossProduct | Dan Goodliffe | 2024-01-07 |
| | |||
* | Helper to create a cubiod from dimensions | Dan Goodliffe | 2024-01-06 |
| | |||
* | Simplified RailVehicle::intersectRay | Dan Goodliffe | 2024-01-06 |
| | |||
* | Remove more use of legacy types and unnecessary pointers from selectable ↵ | Dan Goodliffe | 2024-01-01 |
| | | | | interface | ||
* | Remove more use of legacy types | Dan Goodliffe | 2024-01-01 |
| | |||
* | Remove misleading power operator^ on vec2/3 | Dan Goodliffe | 2023-12-29 |
| | |||
* | Remove weird operator! on vec2/3 | Dan Goodliffe | 2023-12-29 |
| | |||
* | Use new calc types in geoData | Dan Goodliffe | 2023-12-17 |
| | |||
* | Render correct VAO for rail vehicle shadows | Dan Goodliffe | 2023-12-03 |
| | |||
* | 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 |
| | |||
* | Fix terrain texture tiling | Dan Goodliffe | 2023-11-26 |
| | |||
* | 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 | ||
| * | Remove getTransform | Dan Goodliffe | 2023-11-25 |
| | | |||
| * | 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. |