The geometry on my map isn't perfect. I have walls that I have to move with a 1px grid. What is the effect of this on optimizing?
Geometry not grid perfect
- Thread starter Koei
- Start date
It will probably send your map to the grave, I suggest you set aside a whole day and work your way though your map putting all your brushes to the biggest grid size you can get away with, if it is a really small brush in all three dimentions then you probably want to func_detail it.
You always want to have the grid in 16 32 or 8 if you can, untill of course you need to put detailed brushes in that are smaller. Again, you should always be very carefull how you place brushes, make sure they line up to each other and the grid when you place them so that you don't have to worry about it later
You always want to have the grid in 16 32 or 8 if you can, untill of course you need to put detailed brushes in that are smaller. Again, you should always be very carefull how you place brushes, make sure they line up to each other and the grid when you place them so that you don't have to worry about it later
I was afraid of that 
. Gonna have to do some serious fixing (luckily still in early stage). And what about sizing of walls? 510px wall (for example) is bad right?
. Gonna have to do some serious fixing (luckily still in early stage). And what about sizing of walls? 510px wall (for example) is bad right?
I had the same problem when I first started. I find that as the map progresses, I invariably move to a smaller grid. Starting small makes it nigh impossible to make the nice detail geometry later on. Do all your walls size 32, and go from there.
And what about wall lengths, heights? What sizes should I use? 1024, 512, 256, 64, 8? Because of texture scaling (from 1024x1024)? Multiples of 8? 16? 32?
no multiples of 8, powers of 2 (can be added together i guess)
2 4 8 16 32 64 128 256 512 1024....
Walls should generally be 16 units thick unless you have a reason for making them otherwise. Height depends on the room but generally 128 - 512 (using multiples of 64 usually) The compile tools just find it easier to cut up your map if everything is nice sizes and aligned to the right grid size.
2 4 8 16 32 64 128 256 512 1024....
Walls should generally be 16 units thick unless you have a reason for making them otherwise. Height depends on the room but generally 128 - 512 (using multiples of 64 usually) The compile tools just find it easier to cut up your map if everything is nice sizes and aligned to the right grid size.
Sweet, thanks. Now there is nothing to stop me from winning that GPU . Actually, those are all multiples of 8.....128*8=1024 .
. Actually, those are all multiples of 8.....128*8=1024 .Could you please clarify and/or expand on this? Do you mean a bigger grid as in what you change with the [ and ] keys?
And what would be the disadvantages of using a "smaller" grid?
Apparently using a smaller grid (eg 1, 2, 4) makes the compiling process harder and may or may not result in leaks. (correct me if I'm wrong)
Plus if you have things on a larger grid, you won't have to zoom in as much in Hammer...
edit: oh! And yes, you get smaller/bigger grid with [ & ].
Plus if you have things on a larger grid, you won't have to zoom in as much in Hammer...
edit: oh! And yes, you get smaller/bigger grid with [ & ].
Apparently using a smaller grid (eg 1, 2, 4) makes the compiling process harder and may or may not result in leaks. (correct me if I'm wrong)
Plus if you have things on a larger grid, you won't have to zoom in as much in Hammer...
edit: oh! And yes, you get smaller/bigger grid with [ & ].
Is it only the compiling process that suffers, by which I would assume you mean it takes longer?
I would also think this would only cause leaks because if you're zoomed far out with a larger grid, you wouldn't notice a leak. Is this correct?
- Feb 26, 2008
- 1,626
- 1,325
Simply using a smaller grid does not cause longer compile times. To the compiler a line is a line, it doesn't care how wide. However a symptom of using smaller grids is MORE LIKELY to cause YOU to make errors. So, you can safely make a map with 1 unit grids, but it's much easier to make mistakes and therefore cause the compiler to go nuts.
Okay, but texture scaling still suffers from weird wall sizes i guess.
Like how should I handle this? Which is preferred? And what if it was a floor at the bottom of a level, if it was 1block thick?
edit: or I could just put the walls on the floor >_<.
But I really prefer the 2nd picture, that way I can make the floor exactly 1024x1024 and the walls 1024x512 (wxh). But I'm worried about problems with compiling or lighting because the wall and floor would only hit on 1 point instead of a full edge.
edit: or I could just put the walls on the floor >_<.
But I really prefer the 2nd picture, that way I can make the floor exactly 1024x1024 and the walls 1024x512 (wxh). But I'm worried about problems with compiling or lighting because the wall and floor would only hit on 1 point instead of a full edge.
Last edited:
Paria
L5: Dapper Member
- Dec 12, 2007
- 202
- 31
your second example is just fine, it they touch, the map wont leak dosent matter that they dont cover the corners at all. I actually prefer using the 2nd example.
And unless your floor has a specific requirement to be 1 unit think just make it the same size as the walls, 16 units is a decent starting size for walls /floors / roofs,
And unless your floor has a specific requirement to be 1 unit think just make it the same size as the walls, 16 units is a decent starting size for walls /floors / roofs,
The second picture is how I do my rooms, whenever possible. I also make everything 32 thick at the start, and adjust as needed.