Technology (Read Only) > Mapping

How to make: Successful/Interesting map

<< < (4/4)

Tezuni:
This is very helpful for me, thanks.

memo3300:

--- Quote ---If, you don't optimize your map and it has fps problems, nobody will play your map and complains that its laggy and it will get removed from the server.
WARNING! If you are making map for Zombie Survival the fps will drop by half or more. So be prepared.
--- End quote ---


How can you optimize it? adding no draw texture to the textures that people will never see? and is there another way to optimize it?

Tezuni:

--- Quote from: memo3300 on December 15, 2011, 05:59:23 AM ---
How can you optimize it? adding no draw texture to the textures that people will never see? and is there another way to optimize it?

--- End quote ---
All I can think of in addition to nodraw is placing a water_lod_control entity somewhere in your map to reduce water quality over distance.
Contrary to what some people say, grouping doesn't optimize your map.  It's purely for ease of selection in hammer editor.

jimonions:
  A lot of simple things can mess your map up. Such is the source engine. improper cubemaps is one of these simple problems that pretty much destroy the map if they aren't properly utilized, and I don't want to go into too much detail about that.

  Optimizing is basically making players have better framerates during gameplay. Everyone knows that yea?
Ways of doing this in the source engine are as you said adding nodraw textures to certain surfaces to speed up both compiling and rendering ingame. Others include visleafs and level of detail.
  Visleafs are implemented in many other games but source is very lacking in how well its simulated and such. Often the compiler will make mistakes and mess up these visleafs so creating references in hammer can solve these problems. A variety of entities and tool materials are used.
  Another way for optimizing are lod's.
Often very complex models with a high number of polys can cause performance problems. Take for example perhaps a model of a train in a field.The modeler isable to create different versions of the model to produce lower "resolutions" of it. Basically lowering the amount of polys used. This reduces the load ingame and despite being far away the model can still look fairly realistic but can appear very detailed when the player moves right up next to it. These different distances in which the model may "switch" between lods can be defined through the entity in hammer or just the base source code. This tactic is used for pretty much every game coming out.
  These different ways summarize the more major parts of optimization omitting texture resolution lods and other video card settings.

Navigation

[0] Message Index

[*] Previous page