Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
1 Is almost finished, another one is currently in work and the third TTT-Map is still in planning.
Here is why I believe this map is better performance wise.
1. Unlike NPC-Metro / Town, this Map uses prop_static's and only a few prop_dynamics. Prop_static are the cheapest way (Performance wise) to add a 3d Model to a Map. On NPC-Town I ONLY used prop_dynamic & prop_physics, which dulls the Performance.
2. Open Areas are a nightmare to Optimize, if you can do it at all. On NPC-Prison this isn't much of a problem, since the outside is kept small and without many props.
3. I actually got better at using Areaportals. Thanks to a Map-maker buddy, I now know the jank of the Sourceengine. Areaportals determin what should be rendered and what shouldn't. These are the "Optimization-Essential".
4. I believe the lighting on NPC-Metro is an Issue. Every single lightbulb has a point_spotlight entity, creating a fancy lighting effect. But I overused it here.
5. Mapsize... NPC-Metro is huge compared to this Map.