Author Topic: Heightmap Gen  (Read 882 times)

Hey, could someone make a utility to convert two images - a heightmap and colormap - to a bls? Th e heightmap defines the height of the bottom of each cube in studs, while the colormap defines the color of each brick. The bricks would be represented by a pixel and a size parameter.

The bricks can be floating, that's fine. I can just place zones. It also doesn't need a GUI, command-line's pretty chill.

Sure. Should it be able to take an arbitrary brick or just use one specific brick?

EDIT: Herr, missed "...and a size parameter." Should it only accept square bricks, like a 2x2 or 3x3, or should it accept all bricks? Does it need to have bricks to make sure there are no world gaps, or should world gaps be allowed? If it accepts all bricks, how would rotation be defined?
« Last Edit: April 25, 2014, 07:26:46 PM by Xalos »

Sure. Should it be able to take an arbitrary brick or just use one specific brick?

EDIT: Herr, missed "...and a size parameter." Should it only accept square bricks, like a 2x2 or 3x3, or should it accept all bricks? Does it need to have bricks to make sure there are no world gaps, or should world gaps be allowed? If it accepts all bricks, how would rotation be defined?
I would go with only square. It's up to you whether you want to do just cubes, or bricks and plates as well.

World gaps would probably only be possible with an alpha channel. Seems like a waste of time,  though. I don't really see why someone would want a gaping hole in their map; but again, it's up to you.

In my opinion, the coder should always get the final word on this stuff; it's their work, after all.

World gaps would probably only be possible with an alpha channel. Seems like a waste of time,  though. I don't really see why someone would want a gaping hole in their map; but again, it's up to you.

If there's an extremely steep hill, it's possible for the bricks to not be tall enough to quite reach each other. This would be most easy to visualize with plates. A difference of just two plates over one brick distance leaves a very visible gap between both plates.

So the question is: should this automatically get filled in, or just left there?

If there's an extremely steep hill, it's possible for the bricks to not be tall enough to quite reach each other. This would be most easy to visualize with plates. A difference of just two plates over one brick distance leaves a very visible gap between both plates.

So the question is: should this automatically get filled in, or just left there?
Oh, I didn't think of that. Probably filled in. A maximum slope of 45° is rather limiting.

Bump for image:


Click image to download Test Heightmap.bls


Should I polish up the few things that need to be finished and release the executable and then it gets deleted by Badspot?

That looks pretty neat, actually

How many bricks is that?

256000, with 6144 having been truncated of the original 262144

Wow. It doesn't even look like it was made in blockland anymore.

It works at lower resolutions and with normal colors too, of course.

image snip

Very nice, but seems a bit spammy and would cause some users to lag.

Very nice, but seems a bit spammy and would cause some users to lag.
That's because I gave him a ridiculous heightmap, 512x512. If you did something more normal, like 64x64, you get only 4096. You can change what brick it uses, too.