Results 1 to 10 of 96

Threaded View

  1. #11
    Join Date
    Apr 2003
    Some optimization tecniques that i found very usefull:

    Keep an eye out
    While designing your map keep an eye out for your rendering statistics. Make sure you keep it all acceptable or that with the optimization it will be acceptable. With acceptable i mean the framerate offcourse. It's very usefull to try to keep an eye out on how it runs and how it will run, a little difficult if you just started the map. But as you go along and add more and more detail you'll get a better idea on how it will eventualy be, so you can geuss more accuratly if it runs well.
    Use these console commands ingame to check "stat none", "stat render", "stat hardware", "stat all", "stat fps". Without quotes offcourse.
    I usely use the stat render command. Other usefull commands are "rmode 1" which put everything in wireframe mode, good for checking antiportals and visibility. Just walk around your map and look around to see what is rendered and what not. Go back to normal with "rmode 5".
    Some reads about console commands:

    In general about antiportals
    Make them as big as you can make them. As you may know only if a SM is completly behind a antiportal it is not rendered. So the bigger the anti portals the more change ithere is that it will not be rendered. Don't use to many of them in your map about 20 max will do.
    Some reads about anti portals:

    In general about zones
    if you are in one zone and can look into another that one is rendered too. Only the zones that you can't see will not be rendered. So make the zone portals as small as posible and make sure that the change is slim that you can look from one zone into another. So it's useless to zone a hallway in 10 zones if you can look down the whole hallway. They still all be rendered then. Also if your zoneportals are small there is less change that you can look into antoher zone or the one beyond that for that matter.
    Some reads about zoning:

    Distance fog
    Distand fog is a good way to cut off rendering after the maxdistand of the fog. It will look better too if you set the bClearToFogColor to true. Might not be pretty in your indoor map so i would avoid using it, but it's a powerfull tool nontheless.
    Some reads about distance fog:

    One very powerfull tool that is overlooked i think is the culldistance of SM's. In it's display properties look for this setting, you can put a valeu in it, for instance 8000. If you do that the static mesh is not rendered beyond 8000 units. So this one is extremely powerfull even in indoor maps, but also in outdoormaps in conjunction with distand fog. Just watch out that your scenery won't pop up in indoor maps or in outdoormaps without distandfog. So make the culldistance is far enough.

    Cull static meshes in zones
    There's also a way to make sure that SM's are not rendered if you are in a particular zone, but i never used that. So i don't know how you would set that up.

    Terrain specific teqniques
    You can pull out layers that are not really visibile anyway. The more layers on a terrain the more performance it will take. Expecialy if they are drawn upon each other. So in the terrain tool, goto the layers tab and press the grid icon ont the right side. Choose a layer, for instance layer 1. Now there will be a grid dispayed in your map for that particular layer. the grid only shows where that layer is painted, so know you can use the painting tool to remove that layer or make it show again. If you remove the layer the complexity of the terrain will be reduced and it will help the framerate. Only drawback is that your terrain might be looking a little bit dull if you pull out to much. But you can do this for every layer you have and it's a very usefull tool.

    Use the visibility tool, Extremely powerfull and usefull tool. Make terrain you don't see anyway invisibile. So if you have a mountain and the player cannot see or get to the other side of the mountain, make it invisible so the polys won't get rendered. Again, use this tool alot.

    When creating your heightmap, try not to go beyond the standard heightmap size of 256 * 256, it might be difficult to optimize otherwize. You can get away with higher resolutions but you'll make it yourself a whole lot harder. The amount of polys on your terrain is determent by the size of your heightmap.
    Some reads about terrain:

    That's most of what i know of at the moment about optimization, but if those are not enough you are propably doing something wrong in your map design.

    Last edited by Mr. SlackPants; 08-11-2003 at 07:07 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts