END OF AN ERA, FRACTALFORUMS.COM IS CONTINUED ON FRACTALFORUMS.ORG

So i downloaded last fragmentarium and played with TexParameters. They do worse. All height-mapped area has artifacts... GL_LINEAR_MIPMAP_LINEAR, GL_LINEAR_MIPMAP_NEAREST...GL_NEAREST_MIPMAP_NEAREST... - nothind helps. Any ideas?

for the heightmap texture I think "no mipmaps" is correct because the texture represents an object of fixed geometry, unless you are accessing the mipmap layers directly for something

the aliasing artifact I see is on the columns under the "height" pixels, someone correct me if I'm wrong on this please, this part of the image/object is generated by the heightmap frag code and would not have anything to do with how the texture is wrapped, clamped or mipmapped, but has everything to do with how the facet is calculated between height pixels. In the case of using a mipmapped texture, when reading pixels to use as a heightmap you would still see these artifacts between pixels of varying height, you just wouldn't see single pixel columns unless the texture is accesed @ 1/1 scale

the mipmap settings do exactly what they are supposed to do regarding texture rendering, left = no mipmaps, right = mipmaps

Crist, I think we pointed out the problem earlier. Height-maps rendered within DE function will not be clean because "de = p.z + something" is not a true DE, but a rough approximation. The more height you add, the more artifacts you'll see. You'd need to go for bruteforce or other raymatching instead of DE.

perhaps this issue would best be served by introducing a geometry shader instead of piling more (unnecessary) work on the fragment shader

heightmaps usage <a href="https://www.youtube.com/v/v2b4yQ61lKI&rel=1&fs=1&hd=1" target="_blank">https://www.youtube.com/v/v2b4yQ61lKI&rel=1&fs=1&hd=1</a>

Sounds like a way to go. I don't see a point doing 'normal' terrain in fragmentarium.