tangent/OrangeDream
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

started working on temperature range corrections

Browse Source
This commit is contained in:
tangent
2026-08-19 13:53:38 -06:00
parent c9a49eba48
commit 44e67966f0
4 changed files with 41 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ReadMe.md
+10 -5
View File
@@ -8,14 +8,19 @@ Using the heightmap generator from here: https://github.com/TangentFoxy/heightma
- [ ] Remove heightmap library
- [ ] Update ReadMe
- [ ] ReadMe should also point out where the simplex implementation comes from
- [ ] Update the `simplex` library to the latest version with FBM
- [ ] Round the new map generator to a planet shape
- [x] Update the `simplex` library to the latest version with FBM
- [x] Round the new map generator to a planet shape
- [ ] Move `tile_size` out of the map generator (this is a render feature, not a map feature)
- [ ] Turn the new map gen into a wrapper kind of like my heightmap wrapper? (This is sorta already done in a sloppy way.)
- [x] Turn the new map gen into a wrapper kind of like my heightmap wrapper? (This is sorta already done in a sloppy way.)
- [ ] Rebuild the multi-noise map system.
- [ ] Renormalize to Earth extremes. :D (This will probably give bad initial results and need extensive changes.)
- [ ] Use a spreadsheet to map -0.9 to 0.9 to find a mapping function to modify initial values to realistic height ranges!
- [ ] Rename `humidity` to `rainfall`.
- [x] Use a spreadsheet to map -0.9 to 0.9 to find a mapping function to modify initial values to realistic height ranges!
(This was done with -1 to 1)
- [x] Rename `humidity` to `rainfall`.
- [ ] make documentation of how this is all working so I can remember when I forget to work on it for a while
### Long-Term
- [ ] Do all terrain generation within a radius check so unnecessary work isn't done and discarded.
- [ ] Terrain generation steps should happen within a single loop wherever possible?
(Tasks/Issues are stored in the ReadMe instead of using a webUI issue tracker due to how using such a tracker negatively influences portability of the project.)