-R_speeds (part 1)- What are they? & How can I see them?
- Short introduction
- What are they?
- How can I see them?

R_speeds (part 1), short introduction

This tutorial will explain what R_speeds are and will form the base for part 2. This base helps to understand why certain methods work and will give you a more tangible view on (difficult) terms like w_polys.

- R_speeds, What are they?

R_speeds stands for 'render speeds'. So R_speeds has something to do with the speed some things are rendered. You'll probably understand that if things are renderd faster the game will pass off more smoothly. And that is exactly what R_speeds do. They give you information on how fast everything in your map is being rendered.

R_speeds consists of four different values that represent the play-ability of your map. This values are the polygons (w_polys/e_polys), the fps (frames per second) and the ms (ping in miliseconds). So:

• w_polys
• e_plolys
• fps
• ms

fps, the amount of frames that is being rendered per second.

ms, the time in miliseconds that your computer needs to render a single frame on your screen.

fps and ms represent how smooth the game is running. So it's good when your fps are high (40-60) and your ms is low (0-5). Because then a lot of frames are being rendered in very short time.

w_polys and e_polys are both polygons, a polygon is a surface (the surface of a wall for example) W_polys come in all kind of shapes like triangles, squares, rectangles etc. E_polys are always triangles. Polygons influence the fps and ms. The more polygons that have to be rendered, the worse your fps and ms will be, and so the play-ability of your map.

every rectangle above, within the white lines, is a single w_poly.

the e_polys of a desert eagle, the polygons of a model are always triangles.

The amount of polygons that HL has to render is determing the speed of the game play. In easy words: does HL see many polygons? then your map will lag. Does HL only see few? then you map wil pass of smooth an fast. So we want as few polygons in our map as possible. Especially the w_polys can cause bad fps and ms, e_polys cause lag but not as much as w_polys.

Summary What are R_speeds:

• R_speeds are four different values that indicate the play-ability of your map.
• fps and ms represent the play-ability of your map.
• the Polygons (w_polys/e_polys) have influence on the fps and ms and because of that also on the play-ability of your map.
  

- R_speeds, How can I see them?

Now you have an idea of what Polygons and R_speeds are, you probably want to see them. This is possible ingame.
When you open your map with CS open the console (~) and typ 'r_speeds 1'. Now the above mentioned values will stream through the console. These values are: w_polys, e_polys, fps and ms. To stop this type 'r_speeds 0'.

the console after the command'r_speeds 1'

You should know the meaning of this values. Try to keep the w_polys under 800 and the e_polys under 5000. Also try to predict where combat will take place, there you should pay special attention to keeping the w_polys low. If you don't have much w_polys somewhere in your map you can have some more e_polys there and vice versa. It's all about the balance.

Now we want to see the actual polygons. Normally this can't be done in CS, because the following option has been disabled in multiplayer games. We will have to disable CS from being a multiplayer game. Just follow the instructions:

• open CS, and open the console '~'
• typ : 'developer 0'
• typ : 'deathmatch 0'
• typ : 'map mapname', so for example. 'map cs_italy'
• Now the map is loaded and you can walk around.
• Now typ 'gl_wireframe 1' or 'gl_wireframe 2' a clarification stands below.

Every surface within the white lines is 1 w_poly. 'gl_wireframe 1' shows all the polygons that can be seen by you as player. 'gl_wireframe 2' shows beside that also all the polygons that HL has to render. So also polygons that you cannot see at all but where HL 'thinks' of you can. Typ 'gl_wireframe 0' to stop it.

gl_wireframe 1, the polygons that you as player can see.

gl_wireframe 2, from the same position. The polygons of which HL 'thinks' that you can see them.

Summary R_speeds How can I see them?:

• console command to see the r_speeds = r_speeds 1 (r_speeds 0 to stop)
• console command to see the w_polys that can be seen by you as player = gl_wireframe 1 (gl_wireframe 0 to stop)
• console command to see w_polys that HL renders = gl_wireframe 2 (gl_wireframe 0 to stop)

R_speeds (deel 1) - R_speeds (deel 2)