RAD Compiler Last edited 16 years ago2008-06-11 08:13:23 UTC

You are viewing an older revision of this wiki page. The current revision may be more detailed and up-to-date. Click here to see the current revision of this page.

This article was converted from a previous version of TWHL and may need to be reviewed

  1. The formatting may be incorrect due to differences in the WikiCode processing engine, it needs to be revised and reformatted
  2. Some information may be out of date
  3. After the article is re-formatted and updated, remove this notice and the Review Required category.
  4. Some older articles are no longer useful, or they duplicate information from other pages. In this case, delete the page after merging any relevant information into other pages. Contact an admin to delete a page.
This is the final of the four compiling programs. It takes data from the VIS program and assigns a light value for each texture so that the game engine doesn't have to trace the values during game play. RAD requires lots of RAM and time. The bigger the map and the more lights, the more time RAD will need to compile.

I compiled a map on a PII 400 with 128Mb RAM and then the same map on a P4 1.6GHz with 256Mb RAM. The difference in the time the RAD compiling took was about one fifth that of the older machine.

More info from DOE, Snowdog:
RAD: The RAD tool, or Radiosity tool, is responsible for generating and applying all lighting effects in a level. Everything from entity lights and the "sky" down to the lowly texture light has to be handled by this tool. A .bsp that has not had RAD run on it will appear pitch black in game or full-bright depending on video-mode and console-settings. This tool is normally the one responsible for slowing down compiles most of the time as it has to process huge amounts of data in the completion of its task.

Comments

You must log in to post a comment. You can login or register a new account.