Search the Community
Showing results for tags 'erode'.
Found 4 results
Hello all, I am on a MAC and was wanting to play around with heightfields but most of the nodes will not work on Mac. The ones I have found so far are the erode nodes and the Slump node. They immediately error including using a shelf tool that throws them down. Has anyone else encountered this error or have an idea what the issue could be? I have attached a screenshot of the error it is throwing up. The Specs on the Mac are below just in case it's helps. Not my personal box. haha iMac, late 2013, High Sierra OS Processor: 3.4 GHz intel Core i5 Memory: 32Gb 1600 MHz DDR3 Graphics: NVIDIA GeForce GTX 780M 4096 MB
Hey guys, so I'm building a procedural erode / rock tool. Here are my results so far, the tool generates an infinite number of variations on these. I intend to add more surface detail like cracks and more small geometry details, breaking up the edges more, tweaking the nodes and playing around with it. I'm very happy with the results so far. Also I'd like to know if people are interested in this, it feels nice working on this knowing that it will be useful for people. All the best, Wout
Hi - I'm struggling to find a tutorial that explains the workflow for exporting a large heightfield terrain as tiles. I'm unsure where I would use a tilesplit/splice node for example - before or after my erode node? If I have a large terrain with many voxels, the erode takes a lot of memory. Can I use a tile split node before the erode to make the computation less demanding per tile, and somehow iterate over the individual tiles, exporting each tile's maps along the way? If I try to compute the erode on a very large terrain all at once, my pc runs out of memory. I would really appreciate any tips, links or advice you might be able to offer on appropriate workflows for working with large terrains and exporting tiled maps. Thank you Bryan