what is r_speeds? Created 20 years ago2004-05-06 16:42:53 UTC by MCYORIAN

?? what is the difinition for:

1- r_speeds

2-NPC

3-some body knows what the meaning of "H.E.V." ?

sorry but i dont speak much english! and btw im noob

NOBODY YELL AT THIS GUY! OK, I also fell vixtim of asking what r_speeds are at one point in time. You better hope Kol never comes back because he will hunt you down man. For future reference, look for the question your asking in the forums before you ask it. But here is what r_speeds are:
R_speeds are how much of the level Half Life can handle at a time. IF you have a small encolsed area or a big area surrounded by walls so tha you cannot see the whole thing, the r_speeds will be low, thus producing a very smooth, non-lagging map. IF you have a huge block of a map where ou can see the whole thig then the r_speeds can rack up and the map will lag. If you dont know what I mean then build a huge hollow block map with no walls and play it. It will lag.

NPC = Non-Player Character. AI enemies, friendlies.

HEV = Hazardous Environment Suit. The protective orange thing that Gordon Freeman wears.

some some tutorial search on the internet and here for r_speeds. lots of myths are about it

And you didnt even get yelled at, lucky you.

What can also effect r_speeds is the amount of intersecting world brushes in a map. Every time 1 world brush touches another, the engine breaks this up into separate blocks making more complex data for your computer to display.

I think r_speeds is a combination of w_polys (world polygons or brushes) and e_polys(entity polygons or number of entities) that the player can see at any given point in time. To see what your r_speeds are in a map, type r_speeds 1 in your console once you've got the map loaded. You can run around your map and check the figures. (This should give you a fps value as well, very handy)

Theres a great tutorial here.

r_speeds is just the command. The r_ prefix denotes "render". Wpoly is usually termed "r_speeds" and should be kept under 800 where possible, the maximum without hardware acceleration.

It surely isn't bad when they exceed 1000. Today's computers can handle higher amounts of polygons than 5 years ago. Some singleplayer mods nowadays go for a 1200-1500 limit. They don't aim for software mode users.
Software mode can only render 800 polygons, any more will disappear. But Direct3D and OpenGL mode don't have this limit.

Multiplayer maps should think some more about polygon use, 800 is a good limit for these.

Also note that the framerate can drastically decrease when the player can see too far (about 3000 units or so, don't know exactly). This is especially true on older computers, newer ones shouldn't have problems with it.

I dont get the whole R_speeds thing at all, how can i ruduce them on a map already made with a poly count of around 1500 to 2000 with out making any dramatic changes to the structure of the level.

Did you read the tut? Theres one here on TWHL as well as on Verc

yes but i dont want to change my textures to scale 10, it will make the level look crap! How did the original half-life team to it?

By making small, simple maps.

Id just say-

r_speeds: number of polygons visible to the engine (not just to yourself, it can 'see' beyond some walls) in the direction you are looking in. Type 'gl_wireframe 2' in the console to see what the engine is currently rendering.
The general rule of thumb is that higher r_speeds = lower performance, where its best to aim for a high of around 800 wpolies (world polygons, everything you created in hammer), which almost any machine these days can handle without performance drop. Epolies you can usually ignore as they dont lag the engine as much (they refer to the models the engine is rendering)