mirror of
https://github.com/UberGames/GtkRadiant.git
synced 2024-12-19 08:51:34 +00:00
50 lines
2.2 KiB
HTML
50 lines
2.2 KiB
HTML
|
<html>
|
|||
|
|
|
|||
|
|
<head>
|
|||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
|
|||
|
|
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
|
|||
|
|
<meta name="ProgId" content="FrontPage.Editor.Document">
|
|||
|
|
<title>Introduction</title>
|
|||
|
|
</head>
|
|||
|
|
|
|||
|
|
<body background="../pics/background.jpg" text="#FFFFFF" link="#FFFFFF" vlink="#FFFFFF" alink="#FFFFFF">
|
|||
|
|
|
|||
|
|
<b><font SIZE="5">
|
|||
|
|
<p align="center">Introduction</p>
|
|||
|
|
</font></b><font FACE="Times New Roman">
|
|||
|
|
<div align="right">
|
|||
|
|
<table border="1" cellpadding="10" width="100%" bgcolor="#000000" bordercolor="#808080" cellspacing="1">
|
|||
|
|
<tr>
|
|||
|
|
<td width="100%" bordercolor="#000000"><font FACE="Times New Roman">
|
|||
|
|
<p><font color="#FFFFFF"> <font size="3">Creating workable terrain style maps for the Q3A engine takes some
|
|||
|
|
reorganizing of thought, but in many ways is not substantially different from
|
|||
|
|
making a halls-and-rooms type of map. The designer still has to be concerned
|
|||
|
|
about how much can be seen at one time and give thought to map flow and play.
|
|||
|
|
The rules and restrictions that guide conventional map design are still there
|
|||
|
|
<EFBFBD> it just occurs on a much grander scale. You still have to think about poly
|
|||
|
|
counts, that hasn<73>t changed; but generally speaking, the polys that you will
|
|||
|
|
use to make your game terrain are VERY large and less are likely to be seen all
|
|||
|
|
at once during a game.</font></font></p>
|
|||
|
|
<p><font face="Times New Roman" size="3" color="#FFFFFF">
|
|||
|
|
The <20><i>terrain</i><EFBFBD> style maps in Quake III: Team Arena do not represent any
|
|||
|
|
changes to the Quake 3 Engine. The power to make them work has always been there,
|
|||
|
|
unrealized and untapped. What has changed is the way map files are created and
|
|||
|
|
processed. These construction techniques rely on changes in the <a href="http://www.qeradiant.com/" target="_blank"> Q3Radiant editor</a>
|
|||
|
|
and the q3map program that processes the map files into game files.</font></p>
|
|||
|
|
</font>
|
|||
|
|
<p align="center"><a href="table_of_contents.html">Back</a> - <a href="table_of_contents.html">Table
|
|||
|
|
of Contents</a> - <a href="key_changes.html"> Key Changes</a></p>
|
|||
|
|
|
|||
|
|
</td>
|
|||
|
|
</tr>
|
|||
|
|
</table>
|
|||
|
|
</div>
|
|||
|
|
</font>
|
|||
|
|
<p align="center"> </p>
|
|||
|
|
<p align="center"> </p>
|
|||
|
|
<p align="center">-3-</p>
|
|||
|
|
|
|||
|
|
</body>
|
|||
|
|
|
|||
|
|
</html>
|