Talk:Optimization (level design)

The page had no useful content, so I added some: an article I'd written originally for http://www.hl2world.com/wiki/index.php/Optimization but now choose to place at a more official wiki. It predates the wikification of Valve's SDK docs (eg, Optimizing and Checking Your Map) so it might be reasonable to do some merging. Maven 07:47, 13 Sep 2005 (PDT)

re: Program Optimisation For Mod DLL's

This article is for map optimisation. Isn't there a code equivalent where that can go? --TomEdwards 00:23, 24 May 2006 (PDT)

Whoa! compiling is not very nice.. The compiling eats here at the end 650mb of my memory and compiling takes forever.... And maybe move it to Pre-publication_evaluation --dutchmega 08:35, 24 May 2006 (PDT)

Well.. I can't even compile server with it... takes 1200mb of memory... lol! --dutchmega 08:42, 24 May 2006 (PDT)

Optimisation articles need work

Map optimisation is a mess on VDC. I've found these pages all talking about the same thing:

• Optimization (Geometry)
• BSP Map Optimization
• Controlling Geometry Visibility and Compile Times
• Optimizing and Checking Your Map
• Optimization (Non-Geometry)

There's at least some unique content on each page, but most still overlap dreadfully. They need to be condensed (optimised, you might say...) into a single location (though not necessarily article).

Here are my thought on a structure for this document, that would be found at this URL:

1. Visibility
   1. Visleaves
      1. Leaks
      2. glview/mat_leafvis/OB Hammer leaf view
      3. func_detail
      4. func_viscluster
   2. Hints
   3. Areaportals
   4. Occluders
2. Rendering
   1. Lightmap scale
   2. Dynamic light
   3. Fade distances
   4. Overdraw
   5. Models in water
3. Physics
   1. Start asleep and hammer_updateent
   2. Debris

Any further suggestions? --TomEdwards 00:29, 1 Sep 2008 (PDT)