More easygen woes - Solved!


(Grand_Mister_P) #1

Right, so ive got a detailed pixel map that i can scale accordingly, but i want it to map to a terrain that will be 52167008 (xy)radiant measures big. Ive got a whole page of workings trying to find out how it does it, and have come across nothing easy and linear. The web seems to not let me in on this secret either (or i dont know exactly what to search for) so any guidance in this matter would be greatly appreciated!

Many thanks


(Mr_Tickles) #2

Ummm, I’m not exactly sure of what you are asking here, but i’ll have a shot.

When you create your terrain in Easygen, you need to have the divisions exactly one less then the number of pixels in your alphamap.

So, create your heightmap, import it to easygen, you don’t need to do anything here yet. Export the .map, load it in Radiant, check the size of it, if you need it bigger, alter the divisions in easygen, make them bigger. Make them smaller if you want the map in Radiant to be smaller. When you have got the size of your map as you want it, then scale your alphamap to be one pixel larger than the divisions you have decided to use in Easygen. Don’t forget that the x and y values are separate so you will need to scale your image according to those. Make sure it’s correct after you’ve stretched it I mean.

However, if your pixel map is your heightmap, simply get to Radiant with it then go back and alter the Div.Widt. in easygen till you get the size you want.

Have fun :slight_smile:


(Grand_Mister_P) #3

Right then i kind of see where your going. But then again i dont think im meant to go into alpha maps here.

I have an 8-bit greyscale bitmap (heightmap), currently i have a huge one thats really detailed and i scale it down accordingly as i recently found out that theres limit to how detailed it can get. these bitmaps cant get any bigger than 128128. So ive got it as a size 96129 (maybe that 129’s the problem? im not sure whether the extra pixel matters here…) and i size the easygen starting grid to the size i want (52167008) and put the right number of divisions in (95128) and then when i import the above bitmap it stretches the sides to much bigger values. So does the size of the bitmap (heightmap) im going to import reflect how big easygen makes the terrain? All im interested in atm is getting the terrain the right size and shape. Hope you can help!


(Mr_Tickles) #4

Sorry I haven’t replied for a while, other things needed doing…

Ummm, nope, I did manage to make a map with a 129*129 size heightmap.
Hoh-kay, well, i’m sure if you alter the grid’s size before you import it shouldn’t do much as the importing would make the grid to the size of the bitmap.

Ummm, not too sure what you are trying to explain as I can’t really see what the ‘sides’ are that you’re talking about.

The heightmap that you import will determine the size of your terrain that easygen exports. However, once you import the heightmap, you can then use the div widt to alter the spread of the mesh, or the Width box itself.


To do what you want to do (I think):

[ul]1. Ok, if you import your heightmap which is 96 * 129. Easygen will take the Divisions to be 95 * 128 right?

  1. Remember to uncheck the box which says “Lock terrain shape (don’t deform it)”. Maybe that was the problem with the sides stretching out?

  2. Then, you can go to the width box on the left and type in the width that you want your terrain to be. Under X put 5216 and under Y, 7008. Remember to press Apply though otherwise nothing will happen.[/ul]

But yes, don’t bother altering things before you import, do it after, like above.

Have fun :slight_smile:


(Grand_Mister_P) #5

Ahhh, bingo, twas that little tickbox! Thanks for sticking with that Mr Tickles, youre a star! Many, many thanks, hopefully now, i can finish the actual building of my map. Then its command map time!! Oh ho ho!

Thanks again


(Mr_Tickles) #6

No probs, have fun :wink: