| polygons [message #-988780] |
Sat, 21 December 2002 18:02  |
|
|
|
when you say "20k polys is a good size for a map" , thats not including base buildings is it?
|
|
|
|
|
|
| polygons [message #-988778] |
Sun, 22 December 2002 12:38  |
|
|
|
yeah 20k is okay for a map, but if you can make it have least polys as possable, so the map doesn't cause lag.
|
|
|
|
| polygons [message #-988777] |
Sun, 22 December 2002 16:08 |
|
|
quote:
Originally posted by Laser2150:
yeah 20k is okay for a map, but if you can make it have least polys as possable, so the map doesn't cause lag.
Well, about the polygon count, you really don't need to worry about the it because most graphic cards get over 30 million polygons per second. And you guys are worried about little amount.
|
|
|
|
|
|
| polygons [message #-988775] |
Mon, 23 December 2002 05:06 |
|
|
quote:
Well, about the polygon count, you really don't need to worry about the it because most graphic cards get over 30 million polygons per second. And you guys are worried about little amount.
You have to consider the low end graphics cards and computers. Renegade was designed to have minimum requirements of PII 400, with a 16MB graphics card (i think), making maps for high end graphics cards is not you best option.
20k polys is a good number for a map. Westwoods maximum was about 40,000 on city, and my latest map only has about 10k. But remember, there are other factors apart from polys you have to look out for.
|
|
|
|
Search
Help
Members
Register
Login
Home
