| ▲ | reactordev 3 days ago |
| I came here to say this. My masters was on procedural generation. Perlin, fBm, etc. The things these noise functions have that an LLM doesn’t is speed. 1-D perlin is just a dozen or so multiplications with a couple random coefficients. The GPU can do 4-D Perlin all day long every frame taking up a 4096x4096x32 texture volume. While I do like the erosion effects and all, having a few height texture brushes that have those features that you can multiply on the GPU is trivial. I still welcome these new approaches but like you said, it’s best for pre generation. |
|
| ▲ | yunnpp 3 days ago | parent | next [-] |
| My masters was also on procedural generation. Now I wonder how many of us are out there. At any rate, given that this paper divides the terrain in regions and apparently seeds each region deterministically, it looks like one could implement a look-ahead that spawns the generation on async compute in Vulkan and lets it cook as the camera flies about. |
| |
| ▲ | DonHopkins 3 days ago | parent | next [-] | | Now days there are a whole lot of people procedurally generating their masters degrees, but that's a different thing entirely. | | | |
| ▲ | daemonologist 3 days ago | parent | prev | next [-] | | I think it's catnip for programmers, myself included. (See also: boids, path traced renderers, fluid simulations, old fashioned "generative"/plotter art, etc. - stuff with cool visual output) | | |
| ▲ | tonyarkles 3 days ago | parent [-] | | Boids is so satisfying! | | |
| ▲ | VikingCoder 2 days ago | parent [-] | | Boids, Game of Life, Genetic Algorithms, Pixel Shaders... All so satisfying to play with. One of my favorites was when I was sure I was right about the Monty Hall problem, so I decided to write a simulator, and my fingers typed the code... and then my brain had to read it, and realize I was wrong. It was hilarious. I knew how to code the solution better than I could reason about it. I didn't even need to run the program. |
|
| |
| ▲ | reactordev 3 days ago | parent | prev [-] | | Which is what a sane terrain system would do. Just beyond the far plane you would load/gen the tile/chunk and as you got closer, increase the resolution/tessalation/etc. (or you start with high and each level away you skip vertices with a wider index march for a lower lod). In any case, like I said, I welcome any new advances in this area. Overhang being the biggest issue with procedural gen quad terrain. Voxel doesn’t have that issue but then suffers from lack of fine detail. |
|
|
| ▲ | anentropic 2 days ago | parent | prev [-] |
| I am curious - why would you want to keep generating the same perlin noise every frame? why not pre-generate the terrain? |
