Terrain Loading Help

(Noobanator) #1

I’m having problems loading a large map file. I created it with EasyGen. It is a basic terrain which I then plan to edit. It is approx. 4MBs, but whenever I load it Radiant crashes. I have loaded much larger files (10MBs+) without any problems.

I have compressed it, through lowering of triangles, to 1.5MBs and it loads. Only problem is now you can’t even figure out where the islands because they are connected in several spots.

Is there are problem with the EasyGen files that limits the size? I’m just using the default metashader file and aphlamap could that be the problem?

Thanks for any help

(Noobanator) #2

BUMP

I take it there isn’t many people that use EasyGen to create terrain. What do you use?

(Ifurita) #3

I use Easygen. How many triangles are you trying to import?

(Noobanator) #4

How many triangles are you trying to import?

I started out trying to get about 60,000 to import. I’m down to only about 30,000 needed for islands. The rest was mainly for underwater terrain.

(Ifurita) #5

Posted from another thread

The limit is 32768 brushes. However there are also limits on the number of unique planes in the map, so what error you run into first depends on the complexity of your brushes.

Sounds like you’re already past the limit

(Noobanator) #6

Thanks for the info. I was over the limit by less than 200.

(]UBC[ McNite) #7

I did use EasyGen to great success in my map The River II. Its a very cool tool imo.
Which size is your heightmap in pixels? If you look at The River II, its 77x89 pixels with each pixel 128 units in radiant and its considered a pretty large map.

When u think of isles… u have to be very careful about VIS and do a good planning on how to effectively block VIS or your framerates will suffer seriously.
If you already have 30.000 triangles only for the terrain this means u got already 30.000 tris only for the terrain. That s by far too much if you dont get a VERY good VIS-blocking working. Having 8-15.000 tris being calculated by the engine is a good value and gives you about 125 FPS.

What I also experienced is that fog will NOT help you with improving your framerates but lower them considerably (I got 2 threads on that problem in this forum and the Q3map2 forum). So you need a good VIS planning right from the start when going to do such a large map.