+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: Some semi-random thoughts on terrain generation (/thread-409.html)
RE: Some semi-random thoughts on terrain generation - xoft - 06-23-2016
Don't replace, add it to the end. I'm still unsure whether to include it directly in the page, or rather as a link to your web.
RE: Some semi-random thoughts on terrain generation - NiLSPACE - 06-24-2016
And the PR is merged
I do want to note that I added a few extra features to the visualizer on my site, but I don't think we should put it on the documentation page.
RE: Some semi-random thoughts on terrain generation - sphinxc0re - 06-25-2016
Still, noone will see this because it's not linked anywhere. We have to change this
RE: Some semi-random thoughts on terrain generation - NiLSPACE - 07-11-2016
I've managed to improve the rendering speed dramatically: http://javascript.nilspace.nl/Cuberite/GrownVisualizer/index.html
@sphinxc0re Perhaps we need to setup a page with all the technical documentation we currently have? Similar to the Lua api.
RE: Some semi-random thoughts on terrain generation - xoft - 07-11-2016
http://cuberite.xoft.cz/docs/ is a mirror of the documentation in Git. Although it seems rather dated, I guess the auto-update script is failing recently.
RE: Some semi-random thoughts on terrain generation - NiLSPACE - 07-11-2016
Oh, I didn't know it was auto-updating. Perhaps we should link it on cuberite.org?
RE: Some semi-random thoughts on terrain generation - NiLSPACE - 07-11-2016
I've changed the visualizer again (It's just too much fun to mess around with
). When the size of the array is smaller than the canvas it uses the old rendering method. Otherwise it uses the newer version. That way you can still see the squares in the beginning, but get a performance boost later on as the array gets too big. Another way to look at it is that at first you see the progress the generator makes and after that you see a nice clean result.
RE: Some semi-random thoughts on terrain generation - NiLSPACE - 11-28-2016
@xoft , you might enjoy this subreddit: https://www.reddit.com/r/proceduralgeneration/
RE: Some semi-random thoughts on terrain generation - xoft - 12-17-2016
I think I have now sorted my thoughts enough to attempt the woodland mansions and ocean monuments.
It will require a new kind of generator. Somewhat similar to PieceStructures, but different in its processing of connectors. It needs to check all currently used pieces that ALL their placed connectors have a valid counter-connector to them. This will provide the guarantee that the structures don't have any holes in them and that their outer walls are complete and no internal parts touch each other and create unwanted corridors.
For ocean monuments, we'll need an additional vertical connector behavior. Current vertical connectors cannot be used for even-sized connections, they needn't fit after rotating the piece. We need a vertical connector type that changes when rotating the piece around the Y axis. That will be my first task on this, it will be shared with PieceStructures generator and will allow the TreePath prefabs we have in the Gallery.
RE: Some semi-random thoughts on terrain generation - NiLSPACE - 01-13-2017
I found this on the proceduralgeneration reddit. I thought it was pretty interesting as it's a really different approach compared to what we have.