Sign in to follow this  
~Helgon

Common way to save terrain data

Recommended Posts

Hi,

 

i would like to know what the common way is to save the map data.

 

Heightmaps or a file consisting of vertices and indices? My plan is to change the terrain afterwards in an editor so i would choose the second option. But are there any advantages in heightmaps I don't see?

 

Or is it normally done totally different?

 

Regards

Share this post


Link to post
Share on other sites
Well, heightmap takes a lot less space, so you should use that unless you need the freedom from separate vertices.<br /><br />HOWEVER, if by editing you mean actually moving the vertices around to lets say create a cave, that is of course impossible to achieve using only a heightmap.<br /><br />With a heightmap you could edit it in an image editor, that might be useful.

Share this post


Link to post
Share on other sites

I would use heightmaps. You can edit them with an image editor, or easily in your own editor by manipulating the image data directly. I would suggest you to use 16bit image data because you will have smoother surfaces. You can also generate lightmaps with these heightmap. You dont have to load the whole image at once, you could split it into chunks and then load them individually.

 

Share this post


Link to post
Share on other sites

As always, it depends...

 

As mentioned before caves and cliffs are easier with an actual mesh. However there are some hybrid method to do them with heightmaps.

I would also imagine that it will be easier to deform terrain that is based on a heightmap (e.g. for artillery craters).

 

However I find heightmaps often suffer from the fixed mesh resolution. E.g. on steep mountain surfaces, if you where using a mesh, you could just add more vertices.

 

One more thing, if you are building a shooter or another game where the player gets a close view of your terrain, I would use meshes. They can look much better and much less generic. E.g. if the artist is working on it in a skulpting application.

But if you wish to procedurally generate your terrain or just need much of it and don't have time I would recommend height maps.

 

There is always a third way to do it. For exaple you could use tileable meshes like they can look much better than just height maps but aren't as much work as individual meshes.

For more information on that take a look at Warcraft 3 or Starcraft 2, they used meshes for the cliffs and ramps and also support heightmaps (at least that is what I think they are using) for the rest of the terrain.

 

Good luck,

Christoph

Share this post


Link to post
Share on other sites

Thanks for all the hints. To be honest i even didn't thought about the problem of caves (when using heightmaps). 

 

 

 

However I find heightmaps often suffer from the fixed mesh resolution

 

That should be no problem with tessellation

 

 

I think that i go for a hybrid solution. Be able to import heightmaps, then construct the terrain out of it as a deformed grid and then save the data in my own format.

 

 

Thanks for the suggestions

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this