Frictional Game Wiki

<h2>2. Creating Models</h2> <div class="level2"> </div> <h3>2.1 Geometry</h3> <div class="level3"> <p> IMPORTANT NOTE:<br/> When you want an object to have physics simulated it is very important that it is placed with its mass center as the center of the scene (not the map, the scene in the maya, 3ds, etc file). When you have several objects, when creating joint’s for example, it is important that the pivot of each object is at their mass center (Note that simply changing the pivot point may not be the best option since that changes the transformation, the best thing is to go into vertex mode and move the entire object until the center is where you want it to be). This may also be used to your advantage when creating bodies that would be hard to tip or have the mass center offset for some other reason. </p> <p> You should always try to center the object to the editor’s scene center! </p> <p> <b><em>As of July 2006</em></b> the engine automatically calculates the body center if it's a single mesh model. However, it is still recommended that you do the above as a proper work method for the engine.<br/> <br/> </p> <p> All geometry <b>must</b> be triangles. This can be made sure by either triangulating or choosing an “export as triangles” option in the exporter. </p> <p> Currently all types of meshes are supported except for shadow casting meshes where triangles that share the same 3 vertices (or 3 vertices with the exact same coordinates) are forbidden. This means that double sided polygons are not handled on shadow casters for the time being. (For those interested this is due to a limitation in the edge detection algorithm, used when creating shadows, but may be fixed if it is really needed.) Shadow casters does <b>not</b> handle edges with more than 2 triangles as well. </p> <p> Also note that closed meshes with normals facing away from its center (i.e. a closed room) cannot cast shadows since the shadow will be omnidirectional and will fill the entire screen. This will most likely only apply to scene geometry and the ways to fix it are the following:<br/> </p> <ul> <li class="level1"> Set the geometry as non shadow casting (see <a href="/doku.php?id=hpl1:documentation:content.creation.document.chap3" class="wikilink1" title="hpl1:documentation:content.creation.document.chap3">chapter 3.5</a>).</li> </ul> <ul> <li class="level1"> Create a hole in the geometry (for door, window, etc.).</li> </ul> <ul> <li class="level1"> Detach some polygons so that the closed geometry is split up into several unclosed geometries.</li> </ul> <pre class="code">\\ \\ ==== 2.2 Animations ==== </pre><p> </p> <p> IMPORTANT NOTE 1: <br/> Animated objects do not have any physical simulation. Bodies may collide with them but they will not push other bodies around in a convincing matter and bodies might also get stuck. So use animation with colliders carefully. </p> <p> IMPORTANT NOTE 2: <br/> When creating the skeleton for an object then the joints can NOT be rotated. You may only use translations for the initial placement. Rotation may be used in animations as normal though. </p> <p> At the moment the engine can <b>not</b> handle animations with scale! <br/> Currently both skeletal (using skinned bones) and object (just key framing objects) are supported. Objects may not be attached to bones and the two they may not be mixed. </p> <p> To create models with several animations you need to use entity files (covered in <a href="/doku.php?id=hpl1:documentation:content.creation.document#entityfiles" class="wikilink2" title="hpl1:documentation:content.creation.document" rel="nofollow">chapter 6</a>). These allow the user to add more files with animation. When doing this there are two types of files: </p> <p> When using skeletal animations make sure that the skeleton root is at the root of the scene. If not, the engine will not find it. </p> <p> <b>Main file:</b> This is the file that defines the geometry, material, skinning and so on of the model. This also contains colliders. If the animation is not skeletal then there must be an animation in this file for the engine to determine the data needs. The animation data in the main file is NOT added though! </p> <p> <b>Animation files:</b> These files should contain exactly the same data as the main file except for colliders. </p> <p> At the moment the engine cannot load animation data alone since it depends on whether the model is skinned or not and the placement of nodes. So the extra animation files must also contain all other data as the main file. However the animation files should not contain physics data like colliders. These should only be in the main file. </p> <p> If you want to add colliders to the animation you can do either group them with the object they should move relative to or not group them at all. If not grouped they will be placed relative to the center of the entity (this mean the center of all objects apart of the animation). It is possible to combine these two types. </p> <p> If you have 2 boxes spinning around each other and want to add colliders to them you simply create two collider objects and place them correctly. Them you select collider 1 and box 1, press group, select collider 2 and box 2 and after that you press group again. Now the colliders will be attached to the boxes. </p> <p> Since animated objects do not interact physically with other bodies then sometimes you might want to encapsulate the entire animation inside an animation. To do this just create the collider and do not group it with anything (it MUST lie in the scene root, so that it has no parent node). </p> <p> When you want to change material or perhaps even alter the look of an object this only has to be done in the Main File, as long as the placement (transform) is the same. </p> <p> <u>Maya specific:</u> If an animation doesn’t show up correctly try sampling it. In Collada options mark Sample and set the sampling function to the sampling rate, which is the time for each frame you sample. If you want to sample 5 times a second write "0.2" (1/5), for a sample rate 30 times a sec write ".033333" (1/30) and so on. </p> <pre class="code">\\ \\ ==== 2.3 UV-Mapping ==== </pre><p> </p> <p> Since the HPL-Engine uses per pixel lighting and normalmapping extra care has to be used when creating mapping the uv for a model. The best advice is to have as few pieces as possible and to put the seams in hidden or flat surfaces. It is also good if the seems are close to each other on the texture map and if the angle between the edges making the seam is a small as possible. </p> <pre class="code">\\ \\ ==== 2.4 Colliders ==== </pre><p> </p> <p> Colliders are used by the physics system to calculate collisions. Models that don’t have any colliders cannot collide with anything. Unlike static map meshes (see <a href="/doku.php?id=hpl1:documentation:content.creation.document#creatingmaps" class="wikilink2" title="hpl1:documentation:content.creation.document" rel="nofollow">chapter 3</a>) you don’t have to add a “nocollide”-parameter to show that the model doesn’t have any collision, models never have any collision unless it has one or more colliders. </p> <p> Colliders are made with normal geometry that is named in a special way. The naming has the following syntax: <br/> <b>_collider_[shape type]_[name]</b> </p> <p> The first variable “shape type” is the type of shape and “name” can be anything you like. The following shapes are available: </p> <span class='np_break'> </span> <div class="table"><table class="inline"> <tr class="row0"> <td class="leftalign"><b>sphere</b> </td><td class="col1">A normal sphere, <em>nonuniform spheres are not allowed</em></td> </tr> <tr class="row1"> <td class="leftalign"><b>box</b> </td><td class="col1">A 6 sided box</td> </tr> <tr class="row2"> <td class="col0"><b>cylinder</b></td><td class="col1">A cylinder where height is the Y axis</td> </tr> <tr class="row3"> <td class="col0"><b>capsule</b> </td><td class="col1">A cylinder but with rounded caps</td> </tr> </table> <span class='np_break'> </span> </div> <p> An example of a name is <b>“_collider_box_pCube1”</b>, this defines a box collider. </p> <p> When creating a shape only rotate, scale and translate should be used (as well as setting the size in Input). If you alter the vertices by hand make sure this pivot is at the mass center, however this untested and might not work very well. </p> <p> The way in which colliders are added to the scene varies depending on the context. Below is a list of the different types used: </p> <p> <b>Normal Model</b><br/> A normal model is a model without joints or skeleton. In this case the colliders are simply added to the scene and they all will become a single body. The centre of mass will be the centre of the scene. The body will be named [entity name] + “_” + [name of model file]. </p> <p> <b>Joint Model</b><br/> This is a model where one or more joints has been added. This most likely means that the model will consist of several physical bodies This means that it must be shown which body belongs to which body. This is done by grouping the mesh and the bodies in a group. Note that there can only be one mesh per group, if more is wanted these must be children of the first mesh. The centre of mass for each body will be the centre of it’s mesh. The bodies will be named [entity name] + “_” + [name of mesh]. </p> <p> <b>Skeletal Model</b><br/> If a model contains a skeleton the colliders must be attached to the bones. The bone that a collider belongs to must be its parent, several colliders can share the same bone parent. The centre of mass for each body will be the combined center of all colliders. The bodies will be named [entity name] + “_” + [name of bone parent]. </p> <p> <b>Animated Objects (non skeletal)</b><br/> The same rules as Joint Model applies. <br/> <br/> TIPS: If you need to have several meshes connected to the same collider. For example, a door with a glass window. This is done by placing one of the meshes as children the to the other. The "top mesh" can have as many children as you like. </p> </div> <h3>2.5 Joints</h3> <div class="level3"> </div> <h4>2.5.1 General</h4> <div class="level4"> <p> Joints are used to constrain the movement between to bodies. They are a very powerful tool and can be used to do a lot of stuff such as lamps that can sway back and forth, drawers that can be interacted with and even a car with wheels and suspenders. </p> <p> All joints are made up from an anchor (also called pivot point) and an axis (also called pin direction), these have different meanings for the different joint types and describe the constraint. All bodies also have some limits to limit the constraint. If all of these values are set to 0 the limit is disabled. It can also be set if the two bodies on the joint will collide or not. <br/> </p> </div> <h4>2.5.2 Joint types</h4> <div class="level4"> <p> <u><b>Ball and socket joint</b></u><br/> <b>Name in engine:</b> ball<br/> <b>Limits:</b><br/> Max twist angle, this is the maximum angle that bodies can twist relative to each other. Has a value from 0 – 180. Max cone angle, this is the maximum angle between Body1 and the axis. Has value from 0 – 180. </p> <p> <a href="/lib/exe/detail.php?id=hpl1%3Adocumentation%3Acontent.creation.document.chap2&media=document:ball-and-socket.jpg" class="media wikilink2" title="document:ball-and-socket.jpg"><img src="/lib/exe/fetch.php?media=document:ball-and-socket.jpg" class="media" title=":document:ball-and-socket.jpg" alt=":document:ball-and-socket.jpg" /></a><br/> <em>This joint is used to model things like rope segments and arm joints</em> <br/> <br/> </p> <p> <u><b>Hinge joint</b></u><br/> <b>Name in engine:</b> hinge<br/> <b>Limits:</b><br/> Maximum and minimum angle between the bodies relative to the start position. Max angle is in the positive direction and min in the negative. To get the positive direction place your thumb on your right hand in the direction of the axis. Now bend your fingers towards your palm, the direction in which you fingers are pointing is the direction of the positive angle. In mathematics this is called the right hand rule. Valid values are 0 – 179. </p> <p> <a href="/lib/exe/detail.php?id=hpl1%3Adocumentation%3Acontent.creation.document.chap2&media=document:hinge.jpg" class="media wikilink2" title="document:hinge.jpg"><img src="/lib/exe/fetch.php?media=document:hinge.jpg" class="media" title=":document:hinge.jpg" alt=":document:hinge.jpg" /></a><br/> <em>This joint is used to model things like doors and wheels (picture turning the axis 90 degrees to the left, the bodies will now spin around each other).</em> <br/> <br/> </p> <p> <u><b>Slider joint</b></u> <b>Name in engine:</b> slider<br/> <b>Limits:</b><br/> Maximum and minimum distance. Picture the anchor as attached to Body1. When the anchor is moved in the distance of the axis the distance gets larger and when it moves in the other way it gets negative (and smaller). At the start position the distance is 0. </p> <p> <a href="/lib/exe/detail.php?id=hpl1%3Adocumentation%3Acontent.creation.document.chap2&media=document:slider.jpg" class="media wikilink2" title="document:slider.jpg"><img src="/lib/exe/fetch.php?media=document:slider.jpg" class="media" title=":document:slider.jpg" alt=":document:slider.jpg" /></a><br/> <em>This joint is used to model things like drawers and pumps.</em> </p> <p> Note that the slider cannot spin around the axis! <br/> <br/> </p> <p> <u><b>Screw joint</b></u><br/> <b>Name in engine:</b> screw<br/> <b>Limits:</b> Same as slider.<br/> </p> <p> This is joint works exactly as the slider but it can spin around the axis. <br/> </p> </div> <h4>2.5.3 Modeling</h4> <div class="level4"> <p> To create a joint (or joints) what you have to do is first to model all the geometry needed to make up the bodies. Each body can only be one object! After that you have to create colliders for the objects, this is done as described as in 2.4. An addition is that you have to set which collider belongs to which body. To do this you have to group the bodies and colliders. The group name doesn’t matter; the important thing is that all colliders and bodies belongs to a group! </p> <p> Note: In the game world, the bodies will be named [Entity_name] +”_”+[Object Shape name], note that it is the editor’s <b>SHAPE</b> name that is used! </p> <p> When modeling the different meshes that make up the bodies you cannot use scale directly on the object. You have to go into vertex mode and scale the vertices instead so that the transform is intact with scale (1, 1, 1)! </p> <p> To create the joint first make a cylinder to represent the joint. A height of 1 and a radius of 0.1 should be fine, it does not really matter as the object is only used for placing the joint. Use a size and ratio you think is easy to work with. The rotation set the direction of the pin and the pivot of the cylinder is the anchor. <br/> </p> </div> <h4>2.5.4 Naming</h4> <div class="level4"> <p> The joints have to be named in a specific way: </p> <p> <b>_joint_[Type]_[Body1]_[Body2]_[Var1]_[Var2]_ …(properties)… _[Name]</b> </p> <ul> <li class="level1"> <b>Type:</b> This is the engine name of the joint (ball, screw, slider or hinge).</li> </ul> <ul> <li class="level1"> <b>Body1:</b> The name of the first body. Use the name of the object.</li> </ul> <ul> <li class="level1"> <b>Body2:</b> The name of the second body. If the joint is connected to the world use “null” (without “”) here.</li> </ul> <ul> <li class="level1"> <b>Var1:</b> Joint dependant.</li> </ul> <ul> <li class="level1"> <b>Var2:</b> Joint dependant.</li> </ul> <ul> <li class="level1"> <b>Name:</b> The joint will be named [Entity_name] +”_”+[Name] in the game.</li> </ul> <p> <br/> Properties are created just as explained in <a href="/doku.php?id=hpl1:documentation:content.creation.document#nameparameters" class="wikilink2" title="hpl1:documentation:content.creation.document" rel="nofollow">chapter 3.5</a>. The following parameters exist: </p> <ul> <li class="level1"> <b>nocollide</b> This means that the bodies in the joint will not collide.</li> </ul> <p> <br/> </p> <p> As stated Var1 and Var2 where joint specific. Here are the details: </p> <p> <b>Hinge:</b><br/> Var1: Min angle 0-179.<br/> Var2: Max angle 0-179<br/> </p> <p> <b>Ball:</b><br/> Var1: Max cone angle 0 – 179,<br/> Var2: Max twist angle 0 – 179.<br/> </p> <p> <b>Slider and Screw:</b><br/> Var1: The maximum length the child will move in the opposite direction of the axis. 0 – inf in cm!<br/> Var2: The maximum length the child will move in the direction of the axis. 0 – inf in cm!<br/> <br/> </p> <p> Some examples:<br/> <b>_joint_hinge_pCube1_pCube2_30_10_nocollide_hinge1</b><br/> This is a hinge joint that is connected to the objects pCube1 and pCube2. The hinge has a minimum angle of 30 and a maximum of 10. The objects pCube1 and pCube2 will not collide. The joint is named hinge1.<br/> <br/> <b>_joint_slider_pCube1_null_slider2</b><br/> This is a slider joint that is connected to the object pCube1 and the world and the joint is named slider2.<br/> <br/> <b>_joint_ball_pCube1_ pCube2_ball2</b><br/> This is a ball joint without any limits. It is connected to pCube1 and pCube2 and the objects collider with each other and the joint is called ball2. <br/> <br/> </p> </div> <h3>2.6 Lights</h3> <div class="level3"> <p> Lights are created exactly as stated in <a href="/doku.php?id=hpl1:documentation:content.creation.document.chap3#lights" class="wikilink1" title="hpl1:documentation:content.creation.document.chap3">chapter 3.3</a> with the exception that the dynamic prefix is <b>not</b> allowed. </p> <p> A light must be attached to a group for it to be animated. The light itself cannot be animated. </p> <p> If the model has joints or is animated the light must be child to one of the geometries. If not the light should be placed directly under the root (with no parent) node. </p> <p> The light will be named <b>[entity name]_[lightname]</b> in game. <br/> <br/> </p> </div> <h3>2.7 Billboards, sound entities, references and particle systems</h3> <div class="level3"> <p> Created as stated in <a href="/doku.php?id=hpl1:documentation:content.creation.document#creatingmaps" class="wikilink2" title="hpl1:documentation:content.creation.document" rel="nofollow">chapter 3</a>. </p> <p> The object (billboard, reference, sound or particle system) must be attached to a group for it to be animated. The object itself cannot be animated. </p> <p> If the model has joints or is animated the object must be child to one of the geometries. If not the object should be placed directly under the root (with no parent) node. This does not apply to references though, which may always be placed in the root. </p> <p> The light will be named <b>[entity name]_[objectname]</b> in game. <br/> <br/> </p> </div> <h3>2.8 Optimizations</h3> <div class="level3"> <ul> <li class="level1"> When ever you can a model should be <b>one</b> object and <b>one</b> texture! Rendering is more limited by the number of object and texture changes in a scene than the poly count!</li> </ul> <p> <br/> <br/> </p> </div> <h3>2.9 Issues</h3> <div class="level3"> <ul> <li class="level1"> Two faces in the same object may <b>not</b> share the same vertices, even if the order is inverted! This means that double sided polygons are not supported!</li> </ul> <ul> <li class="level1"> An edge may only have <b>one</b> or <b>two</b> faces! If this is not followed shadows will be messed up.</li> </ul> <ul> <li class="level1"> When creating animated or joint-containing models you <b>must not</b> use the pivot point when exporting. If you have made a pivot point make sure that you clear it so that the model only has <b>one</b> scale, translation and rotation transform in the exported file.</li> </ul> <p> <br/> <b>Maya Specific:</b> Do not use the center pivot command when creating these models! Note that normal models not containing animation or joints may use the pivot point! <br/> <br/> <br/> </p> </div>