johnvv, what is its performance? Does it use some caching and utilizes multiple CPU cores?

Why do my maps look like something from Minecraft? Original map was 8192 x 4096 dimensions, resized it in Photoshop to 16384 x 8192 with an un-sharpen mask and Gaussian blur filter applied. Then resized it again (without the sharpen option checked marked as on) in IrfanView-64 to 32768 x 16384 before saving RAW file (for the Surface Texture CubeMap folders)

Wilbur was used to calculate height map from the 32768 x 16384 sized PNG. I did increase the contrast to the greyscale a whole lot, so I could see it, again before saving in RAW format with IrfanView-64 (for the Bump Texture CubeMap folders)

Why do my maps look like something from Minecraft?

Probably because your map is an 8-bit image, which means there are a maximum of 256 different height values it can specify (256 shades of gray, including black and white). Height maps should to be 16-bit images, which can specify 65,536 different height values, to avoid that "stair step" effect.

If your image isn't 8-bit, it could be that the height data in it originates with an 8-bit image.

If your image isn't 8-bit, it could be that the height data in it originates with an 8-bit image.

Like this? Not much better. Gaussian, Smart, Radial, Blur, & Blur More... all leave Etch-a-Sketch patterns. Using WIlbur "A terrain manipulation thingy" software program, any suggestions on how best to attenuate the settings to calculate better elevation bump maps, from original 8-bit Scurface Textures, based on color variations alone or artist renderings of visible light views of terrain seen from space?

Or should I do the up-scaling from 8bit to something higher using the original Surface Texture and all the other smoothing out before importing to Wilbur? Or will I always notice some pattern like these?

If the bump map is 8-bit at any point in the process, you're probably going to run into this issue. It's possible that there could be some good way of converting the 8-bit values into 16-bit and then interpolating in a smooth way, but I couldn't say how.