<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
<html>
<!-- Created by texi2html 1.76 -->
<!--
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
Karl Berry <karl@freefriends.org>
Olaf Bachmann <obachman@mathematik.uni-kl.de>
and many others.
Maintained by: Many creative people <dev@texi2html.cvshome.org>
Send bugs and suggestions to <users@texi2html.cvshome.org>
-->
<head>
<title>Crystal Space 1.2.1: 4.16.4.3 Hints</title>
<meta name="description" content="Crystal Space 1.2.1: 4.16.4.3 Hints">
<meta name="keywords" content="Crystal Space 1.2.1: 4.16.4.3 Hints">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.76">
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: serif; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: serif; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.sansserif {font-family:sans-serif; font-weight:normal;}
ul.toc {list-style: none}
-->
</style>
</head>
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
<a name="Map-File-Hints"></a>
<a name="0"></a>
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="Map-File-Syntax.html#0" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="Binary-XML.html#0" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="Using-Crystal-Space.html#0" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="Old-Map-File-Format.html#0" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="Working-with-Engine-Content.html#0" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="cs_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="cs_Index.html#0" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="cs_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<hr size="1">
<h4 class="subsubsection"> 4.16.4.3 Hints </h4>
<p><em>Written by Jorrit Tyberghein,
<a href="mailto:jorrit.tyberghein@gmail.com">jorrit.tyberghein@gmail.com</a>. Mathematical typesetting for
TeX performed by Eric Sunshine, <a href="mailto:sunshine@sunshineco.com">sunshine@sunshineco.com</a>.</em>
</p>
<p>This section contains extra discussions and hints regarding the map file and
the objects contained within it (this documentation is a little bit outdated
but still useful for the general idea. However it should be moved to the
thing mesh object description).
</p>
<p>First, a little explanation about <samp>‘LEN’</samp> and <samp>‘TEXLEN’</samp>. With these
you can specify the size of the texture on the polygon. For example, let's
say that you have a rectangular polygon which is 4 units wide and 6 units
tall. A texture with <samp>‘LEN’</samp> set to 2 will be tiled 2 times horizontally
and 3 times vertically. If this texture is 128x128 (for example) then the
final texture on the polygon will be 256x384.
</p>
<p>Using a <samp>‘TEXTURE’</samp> statement inside a <samp>‘POLYGON’</samp> or with a
<samp>‘PLANE’</samp> statement you can obtain even more control over how the texture
should be scaled across the polygon. This is most easily explained with an
example. Say that you have a polygon like this:
</p>
<table><tr><td> </td><td><pre class="example">VERTEX (0,2,3) VERTEX (2,2,3) VERTEX (2,0,3) VERTEX (0,0,3)
POLYGON 'poly' (VERTICES (0,1,2,3))
</pre></td></tr></table>
<p>Let's say that you want to align the texture so that its origin is at (2,2,3).
You can do this as follows:
</p>
<table><tr><td> </td><td><pre class="example">POLYGON 'poly' (
VERTICES (0,1,2,3)
TEXTURE (
ORIG (2,2,3)
FIRST (0,2,3)
SECOND (2,0,3)
FIRST_LEN (1)
SECOND_LEN (1)))
</pre></td></tr></table>
<p>With <samp>‘ORIG’</samp>, <samp>‘FIRST’</samp>, and <samp>‘SECOND’</samp> you specify how the u/v
coordinate system is located. The origin of u/v is at <samp>‘ORIG’</samp>; the u-axis
is at <samp>‘FIRST-ORIG’</samp>; and the v-axis is at <samp>‘SECOND-ORIG’</samp>.
<samp>‘FIRST_LEN’</samp> and <samp>‘SECOND_LEN’</samp> are similar to <samp>‘LEN’</samp> and
<samp>‘TEXLEN’</samp> except that you can control the u and v scaling separately here.
Note that <samp>‘ORIG’</samp>, <samp>‘FIRST’</samp>, and <samp>‘SECOND’</samp> need not coincide with
vertices of the polygon. They should just be on the same plane as the
polygon. That way you can also create slanted textures.
</p>
<p><samp>‘TEXLEN’</samp> in a <samp>‘THING’</samp> or <samp>‘SECTOR’</samp> is the default <samp>‘LEN’</samp> for
all polygons following the <samp>‘TEXLEN’</samp> declaration. <samp>‘TEXNR’</samp> in a
<samp>‘THING’</samp> or <samp>‘SECTOR’</samp> is the default <samp>‘TEXNR’</samp> for all following
polygons. <em>Note, however, that <samp>‘TEXNR’</samp> is considered obsolete and
its use is deprecated.</em>
</p>
<p>Use of planes is recommended. A <samp>‘PLANE’</samp> provides a way to assign a name
to a texture orientation. All polygons sharing the same <samp>‘PLANE’</samp> will
have textures that fit perfectly at the borders. Crystal Space will also be
able to do some optimizations on polygons that share the same plane (like
backface culling an entire set of polygons in one operation). Note that even
if a <samp>‘PLANE’</samp> is only used by one polygon it does not hurt. If you do not
specify the <samp>‘PLANE’</samp>, Crystal Space will create one anyway.
</p>
<p>Currently Crystal Space assumes that there is a sector called <samp>‘room’</samp>. It
will use that as a starting place, and will always start at location (0,0,0)
unless you use an <samp>‘ORIGIN’</samp> directive to instruct it otherwise.
</p>
<p>Note that Sectors must be convex (unless you add a <small>BSP</small> tree). Things
need not be convex.
</p>
<p>Vertices in a <samp>‘THING’</samp> are specified in local object space. You can
translate this object space to world space with the <samp>‘MOVE’</samp> directive.
</p>
<p>When a <samp>‘THING’</samp> or <samp>‘SPRITE’</samp> is defined in the <samp>‘WORLD’</samp> statement
and not in a <samp>‘SECTOR’</samp> or <samp>‘ROOM’</samp> then it defines a template. This
template can then be used inside a <samp>‘SECTOR’</samp> or <samp>‘ROOM’</samp> by providing
another <samp>‘THING’</samp> or <samp>‘SPRITE’</samp> statement and using the <samp>‘TEMPLATE’</samp>
statement there. It is also possible to define the <samp>‘THING’</samp> or
<samp>‘SPRITE’</samp> inside a <samp>‘SECTOR’</samp> or <samp>‘ROOM’</samp> directly, but using
templates is preferable.
</p>
<p>With <samp>‘WARP’</samp> you provide a matrix which will mirror or warp space. For
example, when you want to make a mirroring floor the warping matrix should
invert the Y-axis and leave the others intact. So the <samp>‘WARP’</samp> matrix
would be:
</p>
<table><tr><td> </td><td><pre class="example">/ 1 0 0 \
| 0 -1 0 |
\ 0 0 1 /
</pre></td></tr></table>
<p>The vector should be a vector on the plane of the mirror. It is used to
determine exactly where mirroring should start. For example, if the floor is
at height -1, then (0,-1,0) is a good spot.
</p>
<p><samp>‘MATRIX (.5)’</samp> is a shorthand for:
</p>
<table><tr><td> </td><td><pre class="example">/ .5 0 0 \
| 0 .5 0 |
\ 0 0 .5 /
</pre></td></tr></table>
<p>Portals are unidirectional. If you need a <samp>‘PORTAL’</samp> that works in two
directions (so that you can go back) then you'll also have to specify a
<samp>‘PORTAL’</samp> in the other sector pointing back.
</p>
<p>Note that even though a <samp>‘PORTAL’</samp> does not require a texture (unless it
has alpha transparency) you still need to specify one, since Crystal Space
currently assumes that every polygon has a texture.
</p>
<p>The <samp>‘ROOM’</samp> and <samp>‘SIXFACE’</samp> interfaces are good for human editors but
it not suited for computer generated output. Ignore <samp>‘ROOM’</samp> and
<samp>‘SIXFACE’</samp> if you want to write an editor or converter and concentrate on
<samp>‘SECTOR’</samp> and <samp>‘THING’</samp> instead.
</p>
<hr size="1">
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="Map-File-Syntax.html#0" title="Previous section in reading order"> < </a>]</td>
<td valign="middle" align="left">[<a href="Binary-XML.html#0" title="Next section in reading order"> > </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="Using-Crystal-Space.html#0" title="Beginning of this chapter or previous chapter"> << </a>]</td>
<td valign="middle" align="left">[<a href="Old-Map-File-Format.html#0" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="Working-with-Engine-Content.html#0" title="Next chapter"> >> </a>]</td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left"> </td>
<td valign="middle" align="left">[<a href="index.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="cs_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="cs_Index.html#0" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="cs_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<p>
<font size="-1">
This document was generated using <a href="http://texi2html.cvshome.org/"><em>texi2html 1.76</em></a>.
</font>
<br>
</p>
</body>
</html>
distrib
>
Mandriva
>
2010.0
>
i586
>
media
>
contrib-release
>
by-pkgid
>
bad97183153701b09df5fae1052b1c30
>
files
>
4219
