Wolfire Games Wiki - User contributions [en]

File:Hammer1.jpg

2015-02-15T14:45:17Z

Poddus:

Dog Polearm

This two-handed war hammer is unwieldy, but can cause catastrophic damage to even the most heavily armored opponents. This is the first clan specific weapon Aubrey has made for the dogs. Even though it may not be the most practical weapon, it is very commonly used by commanders of one of the dog clans because it is important to their clan identity.

[[Category: Screen Shots]]
[[Category: Weapons]]
[[Category: Overgrowth]]

File:Hellbovine9lp.gif

2015-02-15T14:43:32Z

Poddus: removed Category: Jeff was Bored

[[Category: Wolfire Art]]

Lugaru Level 15

2015-02-15T14:43:03Z

Poddus: removed jeff was bored category

[[Image:hellbovine9lp.gif|left]]
Also known as the Secret Cow Level. In order to travel to this level, you must have Wirt's wooden leg and a Tome of Town Portal. Put them in your Horadric Cube and transmute to open a portal in the Rogue Encampment.

Once you arrive, prepare yourself for a bodacious Bunny vs. Bossie battle. Good luck, but don't worry too much: if you've managed to actually get to Level 15 in Lugaru, you're a mighty unusual individual, and a few thousand halberd-wielding bovines shouldn't faze you.
[[Category:Random]]

Portal:Overgrowth

2015-02-15T14:36:40Z

Poddus: /* Phoenix Engine Documentation */ added link to summary blog post and notice

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
''NOTE: A lot of (somewhat dated) information can be found via [http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview this blog post] by David. If you have some time, please merge that info into the wiki, and update/add as needed!
* [[Editor Interface]]
* [[Scripting]]
** [[Hotspots]]
* [[3D Objects]]
* [[Character Models]]
* [[Particle Effects]]
* [[Post Processing Effects]]
* [[Overgrowth Levels]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Custom Terrain]]

==Alpha Testing==
* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Getting Started

2015-02-15T14:28:43Z

Poddus: /* Preordering Overgrowth */ added link to guide for steam users

==Preordering Overgrowth==

By pre-ordering Overgrowth, you can do two things:

* Access the [http://forums.wolfire.com/viewforum.php?f=13 Secret Preorder Forums] (referred to as SPF)
* Check out the latest alphas

First of all, you need an account on the forum. If you don't have one already, [http://forums.wolfire.com/ucp.php?mode=register register there]. Then follow the link given in your pre-order email, and type your nickname to get access to the SPF.

In the SPF, you'll find a sticky named "Unofficial alpha XX, weekly build". You can check that post out to get the link to download the latest Overgrowth alpha.

The SPF is also a place where discuss discuss the alpha with others who have preordered the game, speculate about Overgrowth and ask questions to the Wolfire team. Participate and join us in the discussions!

Steam users can follow this guide to getting access to the Preorder Forums:
http://forums.wolfire.com/viewtopic.php?f=13&t=16422

==Downloading Overgrowth==

After preordering Overgrowth and linking a forum account, access to the [http://forums.wolfire.com/viewforum.php?f=13 Secret Preorder Forum] becomes available. Each week, the alpha build is posted as a stickied topic with a title of the form: "Unofficial Overgrowth a###, weekly build".

There are multiple download options available - a direct download, torrent download, and a "differences" download, which can be used to update a previously installed alpha.

Additionally, once at least one full alpha installation has been performed, the community-made [http://forums.wolfire.com/viewtopic.php?f=13&t=14201 SUMLauncher] may be used for updates (requires a Java Runtime Environment)

==Running Overgrowth==

Upon opening the game, you will be greeting with a menu screen. There is a side-scrolling list of levels from which to choose. Clicking on a thumbnail causes the level to load. If you need to change settings such as the games resolution or anti-aliasing, please refer to [[Configuring Overgrowth]].

For help controlling your character, see [[Control_Reference#Player_Controls|Player Controls]].

If you wish to try community-created content for the game, you can either get and install the files manually, or use [http://blog.wolfire.com/2013/04/Introducing-SUMLauncher-3 SUMLauncher]

==Reporting Bugs==

Overgrowth is currently in Alpha, and as such, features may be buggy, incomplete, non-functional, or otherwise broken. In order to help with development, you can report bugs to Wolfire via email at [mailto:bugs@wolfire.com bugs@wolfire.com]

Your email should contain the following:
* The Alpha Version in which the problem was encountered
* Your system setup (Hardware, OS, etc.)
* A Brief explanation of the problem
* Actions performed, step by step, which led up to encountering the problem
* Expected and Actual Results
* Attachments (screenshots, crash reports, etc.)

Refer to [http://university.utest.com/writing-quality-bug-reports-and-utest-etiquette/ this webpage] for tips on how to write a quality bug report.

[[Category:Overgrowth]]

Particle Effects

2015-02-13T22:03:43Z

Poddus:

There isn't much information released about Overgrowth's particle system. Running or jumping on the ground creates small dust clouds at the characters' feet, and particle streams were added in [http://blog.wolfire.com/2011/04/Overgrowth-a128-video-changelog A128] along with blood dripping. Particles are controlled through scripts, examples below.

==Simple Particle Example==
<pre>
MakeParticle("Data/Particles/impactfast.xml",pos,vec3(0.0f));
</pre>

==Particle Stream Example==

<pre>
float blood_force = sin(time*_spurt_frequency)*0.5f+0.5f;
uint32 id = MakeParticle("Data/Particles/blooddrop.xml",bleed_pos,(head_transform*vec3(0.0f,blood_amount*blood_force,0.0f)+this_mo.velocity));
if(last_blood_particle_id != 0){
ConnectParticles(last_blood_particle_id, id);
}
last_blood_particle_id = id;
</pre>

==File Structure==
There appear to be two different kinds of particles. Both are defined by an .xml file, however, one version is based on a video file, while the other is based on a static texture.

===OGV-Based===
One Particle Effect is based on .ogv files found under Data/Textures/anims/ (though they are not referenced as .ogv but as .xml files in the Particle XML)


<pre>
<?xml version="1.0" ?>
<particle>
<textures animation_effect = "Data/Textures/anims/bigexplosion.xml"
shader = "theorabluescreen"
soft_shader = "theorabluescreensoft"/>
<size val="40.0"/>
<color red = "1.0"
green = "1.0"
blue = "1.0"
alpha = "1.0"/>
<behavior inertia="1.0" gravity="0.0" wind="0.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<no_rotation />
</particle>
</pre>

'''<textures/>''' - This tag has 3 attributes.
* animation_effect - this is the only attribute specific to ogv-based particles and references the file path, starting from the Data folder, to a video file. ''NOTE: for some reason, as of a209, the files referenced are xml format, however all files under Data/Textures/anims/ are ogv format. Is the reference is a typo?''
* shader - the name (not including file extension, typically .frag) of the shader in folder Data/GLSL/
* soft_shader - ?? usually just the name of the shader with the word "soft" appended to the end.

'''<size/>''' - This tag uses the attribute "val" (floating point number) to specify the size of the particle. Can also be defined by "min" and "max" attributes, see Texture-Based Particle below ''NOTE: Units are unknown''

'''<color/>''' - This tag has a varying number of attributes, one for each channel (RGB + Alpha), while the Alpha Channel may be defined as a range, requiring two attributes, alpha_min and alpha_max ''Range? perhaps floating point values from 0.0 to 1.0''

'''<behavior/>''' - This tag has 5 attributes. All are likely floating point values from 0.0 to 1.0
* inertia - Rate at which the particle slows its initial speed
* gravity - Degree with which a downwards gravitational force acts upon the particle
* wind - Degree with which wind effects the particle vector
* size_decay_rate - Rate at which the size of the particle decreases ''NOTE: is this value range bounded by 0 & 1?''
* opacity_decay_rate - Rate at which the alpha channel values of the particle increase ''NOTE: is this value range bounded by 0 & 1?''

===Texture-Based===


<pre>
<?xml version="1.0" ?>
<particle>
<textures color_map = "Data/Textures/smoke.tga"
normal_map = "Data/Textures/smoke_normal.tga"
shader = "litsprite"
soft_shader = "litspritesoft"/>
<size min = "0.4" max = "0.7"/>
<color red = "0.5"
green = "0.5"
blue = "0.5"
alpha_min = "0.5" alpha_max = "1.0"/>
<behavior inertia="0.9" gravity="0.0" wind="1.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<quadratic_expansion speed="4.0"/>
<quadratic_dispersion persistence="1.0"/>
</particle>
</pre>

'''<textures/>''' - With texture-based particles, the "animation_effect" attribute has been replaced by two different ones
* color_map - Path to a file in .tga format. ''Note: Constraints? Do textures need to be square, does their size need to be a power of two?
* normal_map - Path to a file in .tga format.

= Relevant blog posts =

[http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview A summary] of most blog posts explaining Overgrowth's graphical features, focusing on more technical details. There are additional links below, some of which are not mentioned in the summary.

http://blog.wolfire.com/2008/12/object-lighting-part-1/
http://blog.wolfire.com/2010/02/Gamma-correct-lighting

http://blog.wolfire.com/2009/09/character-rim-lighting/
http://blog.wolfire.com/2009/10/character-normal-maps/
http://blog.wolfire.com/2009/09/soft-normal-maps-for-fur/

http://blog.wolfire.com/2009/09/trees-in-the-breeze/
http://blog.wolfire.com/2010/10/Imposters

http://blog.wolfire.com/2009/05/decals-editor-part-one/
http://blog.wolfire.com/2009/05/decals-editor-part-two/
http://blog.wolfire.com/2009/06/decals-editor-part-three/

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Portal:Overgrowth

2015-02-13T21:42:03Z

Poddus: /* Phoenix Engine Documentation */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
** [[Hotspots]]
* [[3D Objects]]
* [[Character Models]]
* [[Particle Effects]]
* [[Post Processing Effects]]
* [[Overgrowth Levels]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Custom Terrain]]

==Alpha Testing==
* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Hotspot Scripting

2015-02-13T21:41:10Z

Poddus: Created page with "In Overgrowth you can use hotspots to trigger certain events. For example give health, add velocity to character or change the level. <pre> //Variables can be created outside an..."

In Overgrowth you can use hotspots to trigger certain events. For example give health, add velocity to character or change the level.

<pre>
//Variables can be created outside any function, these will be available to all following functions.
float force;
int friendly;
void Init() {
//Inside the init function you can put something that only needs to happen once.
Print("Initializing hotspot\n");
}
//Inside the SetParameters function you can set declare variables that the user can change. By selecting the hotspot and press Ctrl + U the parameters will be available to the user.
void SetParameters() {
params.AddString("Upward force", "5.0");
//You can either assign the parameter to a variable straight away or fetch it when it is used.
force = params.GetFloat("Upward force");
//Sliders can be usefull for the user to quickly change parameters.
params.AddFloatSlider("Recovery Time", 1.0f, "min:0.0,max:50.0");
//You can add checkboxes for simple on/off functions.
params.AddIntCheckbox("Friendly", false);
friendly = (params.GetInt("Friendly") == 1);
}
//You can check for a character or an item to enter or exit the hotspot.
void HandleEvent(string event, MovementObject @mo){
//Here we check if a character enters the hotspot.
if(event == "enter"){
OnEnterChar(mo);
}
//The function "OnExitChar()" will be called if a character exits teh hotspot
else if(event == "exit"){
OnExitChar(mo);
}
}
//The same technique can be used for an item.
Note: There is a difference between an ItemObject and an Object. An ItemObject is affected by gravity, such as weapons and collectables.
An Object is static for example a hexcrete or joshua tree.
void HandleEventItem(string event, ItemObject @obj){
if(event == "enter"){
OnEnterItem(obj);
}
if(event == "exit"){
OnExitItem(obj);
}
}

void OnEnterItem(ItemObject @obj) {
if(obj.GetType() == _collectable){
Print("A " + obj.GetType() + " item has entered the hotspot\n")
}
//An item can just like a character have it's properties changed via a hotspot.
vec3 vel(0.0f,15.5f,0.0f);
obj.SetLinearVelocity(vel);
}

void OnExitItem(ItemObject @obj) {

}
void OnEnterChar(MovementObject @mo) {
//To check if the character is the user you can check if it is a controller MovementObject.
if(mo.controlled){
Print("A user has entered the hotspot\n")
//If you choose to retrieve the parameter as needed you can request by name.
mo.velocity.y = params.GetFloat("Upward force");
}
else{
Print("An NPC has entered the hotspot\n");
}
//You can create effects with MakeParticle.The first parameter is the particle file to load. The second parameter is the position in the world to spawn this particle. The last parameter is the direction the particle is moving. The higher the values the faster it will move.
MakeParticle("Data/Particles/fire.xml", mo.position,vec3(0.0f,15.0f,0.0f));

//Certain functions are only accessible if you go through the Execute() function. These can contain multiple functions and even parameters.
mo.Execute("SetOnGround(false);DropWeapon();recovery_time = "+params.GetFloat("Recovery time")+";");

//The level itself can also receive various function
level.SendMessage("loadlevel \"/Data/Levels/sea_cliffs.xml");

//To put some text on the screen in stead of the console you can use.
level.SendMessage("displaytext Test Message");
//And to clear it.
level.SendMessage("cleartext");

//You can also reset the level.
level.SendMessage("reset");

//If you want to put an image onto the screen
level.SendMessage("displayhud /Data/Textures/twisted_paths.png");
//And to remove this again use
level.SendMessage("clearhud");

//To play a sound you use the PlaySound function. The second parameter to specify the location is optional. Make sure the audio file mono or else the positional effect won't work.
PlaySound("Data/Sounds/fall_swoosh.wav", mo.position);

//To get a random value you can use RangedRandomFloat. This will be usefull for example with particle effects.
float direction = RangedRandomFloat(-100.0f,100.0f);

//To spawn objects you can use the CreateObject function. This can be an Object, ItemObject or Character.
int objectid = CreateObject("Data/Objects/rock.xml");
//The function return an id number which you can use to get the Object. Now the Object can be manipulated.
Object@ objectid = ReadObjectFromID(obj_id);
//If the object is character use the MovementObject type.
MovementObject@ character = ReadCharacterID(objectid);
//If the object is a plant use the EnvObject type.
EnvObject@ plant = ReadEnvObjectID(objectid);
//If the object is weapon or collectable use the ItemObject type.
ItemObject@ weapon = ReadItemID(objectid);

//The hotspot is also an object inside the game. You can also move and resize it.
Object@ this_hotspot = ReadObjectFromID(hotspot.GetID());
}
void OnExitChar(MovementObject @mo) {

}
//The Update() function will continue to execute as long as the hotspot is loaded. It does not need to be triggered.
void Update() {

}
</pre>

Editor Interface

2015-02-13T21:07:46Z

Poddus:

{{WQA in Progress}}

'''This page is in dire need of an update!'''

==Introduction==
When you start up your Overgrowth Alpha, you'll probably be faced with dozens of questions. "What should I do?," "How do I work the tools?," and "How far can I edit Overgrowth?" are few of the many questions that will be answered in this section. However, it could be profitable for you to also try to experiment on your own. The more you learn on your own, the more likely you'll be comfortable with the interface. Firstly, it is important that you get familiar with the tools and information you have at your command in game.

==The Interface==
[[Image:select.png‎‎|right|thumb|caption|Interface and Selecting]]

Firstly, we'll make sense of the information and windows accessible from in game. To begin with, you have the most noticeable window; the palette. This palette is very important because it contains all of the tools you'll use to edit and manipulate objects, decals, and hotspots. We'll explain more of the palette soon. Secondly, in the bottom left of your screen you'll see a number after the letters "FPS". Obviously, this means "Frames per Second". Overgrowth is incredibly de-optimized at this current stage, so most likely once you start getting some objects in there your FPS will go down considerably. Do not worry, some day this shall be changed, even then it's hard to get to a point where the FPS reaches low numbers.

Then we have the 'Misc Menu' on the bottom right of your screen. It should be hidden to begin with, but if you drag it upwards you should reveal that it is rather intricate. Firstly, you have the 'Live Shadow Update' on/off switch. This simply means that if you have shadows calculated, this will enable the shadows to update if an object moves. 'Calculate Shadows' and "Calculate AO' are the next switches on the Misc Menu. Calculate shadows (obviously) calculates the shadows for the map and all objects in it. Calculate AO turns the Ambient Occlusion on, which really just makes the map look prettier. '''Warning:''' Calculating either of these generally freezes Overgrowth up for sometimes over 15 minutes.

Next is the 'FOV' Scroller. This is comparable to changing the lens of a camera. Scroller left, the closer things appear, scroller right, the farther the things appear. The standard is 90.30. Also dealing with the camera is the 'Camera Collision Detection' switch. This switch turns off and on the ability for the camera to have contact with objects. This is generally on by default, but I'd advise to turn it off for complicated maps where you may need to get somewhere faster. Everything from 'Translation Jitter' to 'Collide with Objects' deals with changing the settings of the 'Brush' tool. These options shall be explained rather shortly.

Now that all of the apparent menus and information have been explained, we'll go over one last feature; the Console. Currently, the console seems to be nonfunctional, however, when it does come into use it will be rather important. The console uses [http://en.wikipedia.org/wiki/Javascript Javascript].

==The Palette==
[[Image:pallete.png‎‎|right|thumb|caption|Palette Tools]]

We've just gone over most of the general interface, now we shall go more in depth with the palette. Firstly, it's apparent that there are six tools, generally doing different things. To select any of these tools, simply click them once with the LMB. I've found it easy to accidentally not fully press a tool, so be aware. Here is a table of how to select each button.

{| border="1"
|+ align="Top" |''Browser''
|Load Button
|Click ‘Load’ button or CMD 'L'
|Pressing the 'Load' button will automatically open up a new browser in which you can load any object, decal, or hotspot into the game.
|}
{| border="1"
|+ align="Top" |''Tools''
|Translate Tool
|Click ‘translate’ button or press ‘4′
|Sets tool to translate tool. When hovering over a selected object, cursor will indicate the currently chosen tool.
|-
|Scale Tool
|Click ‘Scale’ button or press ‘5′
|Sets tool to Scale Tool.
|-
|Rotate Tool
|Click ‘Rotate’ button or press ‘6′
| Sets tool to Rotate Tool.
|-
|Omni Tool
|Click ‘Omni’ button or press ‘7′
| Sets tool to Omni Tool. This tool combines the Translate, Scale, and Rotate tool in one.
|-
|Brush Tool
|Click ‘Brush’ button, or press '3'
| Sets tool to Brush Tool. Hold P + LMB and drag.
|}

Now that you know what each tool is called it's almost time to move on to how they are specifically used. However, first it'd be best to go over the Browser first.

===The Browser===

The new browser combines the Object, Decal, and Hotspot browser into one functional one. For the most part, the object browser has almost every object listed in it as a image thumbnail, however if you've created your own object or want to load an object that isn't in the thumbnail form, you can simply press the 'Load External Object' button and search through the object folder with all the .xml's all over the place. You can also switch the tab to decal or hotspot browser, which also has all the assets in the thumbnail list. Also, by pressing the Heart located at the top right of every thumbnail, you can add to favorites and look at them in a separate section. Finally, one last feature is the search feature. Simply type the name of the .xml you're looking for and it'll pop up for you.

Okay, we're ready for some nice down and dirty work with the tools...

==Using the Tools==
[[Image:translate.png‎‎|right|thumb|caption|Translate Tool]]

So we've gone over the interface and how to access the tools, but now it's time to show you what each tool really does. As you can see below there is the actual palette. Familiarize yourself with it to make this process easier. Okay, now we'll start with the Translation tool first...

===Translation Tool===

This tool, like all manipulation tools, can affect Objects, Decals and Hotspots in generally the same way. For simplicity's sake, we'll explain these tools in regards to objects only. When an object is selected, this tool allows you to move it's position. So really, 'translation' is really just a fancy word for the 'move tool'. When hold down LMB on an object, you can freely move it without being tied down by a grid or plane. However, all tools can be used differently. If you use RMB on one of the sides of the object, the object will move bound to that plane. This is useful when making walls, buildings, or even Crete structures because you can put an object on the surface of another object, and then edit the position without worrying about depth. If you use RMB + Shift on a side, the object will move bound to that side's perpendicular line. You can use this along with hold Option and Shift, which will duplicate the object, while being snapped to grid and moving on one line. Good for making towers, roads, and other such structures. Another way to use the Translate tool is to use your arrows. In summary, the Translation tool will be one of your most used tools, so get comfortable with it as much as possible.

===Scale Tool===
[[Image:scale.png‎‎|right|thumb|caption|Scale Tool]]

The Scale tool is probably most similar to the Translation tool out of all the tools at your command. However, in the process of making your project, remember to use Rabbot as a standard of size. What do I mean by this? Well, it can be hard to judge size without any reference point, so use Rabbot to make sure your stuff isn't too large or too small. Also remember that not all object scale graciously. Certain object loose much of their quality when significantly enlarged. Moving on, if you use LMB on the object, this tool will scale the object in size from the center. It's basically a 'Make bigger' or 'make smaller' tool with LMB. Now, when you use RMB on one side, this will scale the object bound to that side you used RMB on. Also, like the translation tool, you can use RMB + Shift on one side to scale bound to that side's perpendicular line. Using the 'Control' button with the scaling will snap the scaling to it's grid, however it seems as if it doesn't exactly coincide with the Translation's grid. Pretty much you'd have to see it for yourself to understand completely.

Also, another feature with the scaling tool is the ability to mirror your object. It's rather simple actually, simply use RMB + Shift + Control on one side, and then drag the mouse over past the opposite side. This, if done properly, will result in your object being completely mirrored beside it.

===Rotate Tool===
[[Image:rotate.png‎‎|right|thumb|caption|Rotate Tool]]

Now we have the last of the Manipulation tools, the Rotation Tool. This tool is actually slightly less complicated than the other's because it's function is easier to grasp. This tool actually had some trouble in the earlier stages of development because the snap to grid function (Control) didn't exactly work so well. Luckily for us now, the Rotate tool works pretty much perfectly. You can use LMB to free rotate the object, kind of like how LMB affect objects with the Translation tool. Free rotating an object is good for when you need to make ruins, or something more natural. After all, Overgrowth is all about the natural environment of the map. However, if you ever did want to get a more defined result with rotation tool, simply use RMB on one of the sides of the object to rotate on that side's perpendicular axis. Using Control with the Rotate tool is very important. For instance, when making a house and you have a wall, you need to make a right angle. Using RMB + Control on the top side of the wall, you can rotate it into a right angle.

===Omni Tool===

This tool combines the Translate, Scale, and Rotate tool into one tool. This is useful because it saves time that you'd normally spend changing tools. When using this tool there are two ways in which it determines what tool to use. Firstly, it determines this by where your curser is in relation to the object. For Translation, hover over the center of a side. For Scale, hover near the verticies of the object. For rotate, hover near the edge of the object. This takes some getting used to along with a good amount of precision. However, another way to determine which tool to use goes as: Translation, hold T. Scale, hold E, Rotation, hold R. Now, don't be surprised when you press R and a Ragdoll spawns. It turns out that this hotkey is used for two functions.

===Brush Tool===

This tool is different from the other tools listed because it's not a Manipulation tool, it's more like an 'Add Object' tool. The brush tool allows you add objects to a map quickly and seamlessly. All you have to do is load an object via the Object Browser, but before adding it to the map, switch to the brush tool and hold P + LMB and drag over the map. You should end up with the object you loaded being spread on the map near where your curser is moving. As mentioned before, the Misc Menu can also change how the Brush tool works. Editing all the 'jitter' sliders will change how the brush works, and you can even set it so you can brush over objects as well.

==Other Tools==
[[Image:ColorPickerOpenedRed.png|right|thumb|caption|Two crete blocks. The left is the original, the right has had it's color altered by the color picker.]]
===Color Picker===
The Color Picker is used to change the base colors of selected objects using a color slider+gradient box combo. The color picker is opened by pressing CTRL+P (For Mac users: Command+P) while in edit mode. You are still free to manipulate/select/deselect objects in the world you're editing while the color picker is opened. The color picker consists of a color-gradient box, a rainbow slider, two boxes of different sizes showing the basic chosen color, RGB values, a hex value, and an OverBrightness slider and text box. The OverBrightness is essentially the overall brightness of the object. Using this basic tool, one can alter the colors of objects to something to more of their liking.

Character spawns can also be affected by the CTRL+P shortcut. If a character spawner is selected and CTRL+P is pressed, the spawner will alternate between a Rabbot and a Computer controlled spawn point. Using this technique, one can make computer controlled Rabbot characters for the player to fight. Though it is not recommended, as it appears that having a computer controlled rabbot character is severely laggy.

== Saving Combined Object As A Separate File ==

Once you have created something you wish to use elsewhere, press Ctrl+Shift+S (On Windows) or Command+Shift+S (on Mac) to open an object saving dialog. This way, you can save buildings, trees or obstacle courses made from many parts as a single XML object, ready to be imported back to Overgrowth.

==Summary==

So, in total we went over the general interface of Overgrowth, and went in depth on the functions of the Palette. In truth, once you get a hang of using the tools it gets easier from there. Even when editing Decals or Hotspots, it's all just a process of getting used to the way the editor works. Also, feel free to use any of the tutorial images on the right side as quick reference guides incase you forget anything. Also, the two links below are '''incredibly useful''', I'd highly recommend them.

Thanks to Phillip and the whole Wolfire team for any information I used from them.

[http://blog.wolfire.com/2009/03/map-editor-controls/ Philip's Map Editor Controls] - [http://forums.wolfire.com/viewtopic.php?f=13&t=4148 SPF Forum]

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Overgrowth Levels

2015-02-13T20:54:57Z

Poddus: /* Sky */

The base for every scene is the land and sky. The sky is [http://blog.wolfire.com/2009/02/creating-our-own-skydomes/ based on a panoramic photo], which is converted to a skybox at run-time. The terrain is based on a heightmap, which is then [http://blog.wolfire.com/2009/06/offthegrid-revisited/ simplified] using quadric error metrics and divided into patches for frustum culling. Finally the terrain and sky are combined into a new [http://blog.wolfire.com/2009/07/blending-land-and-sky/ skybox], and the edges of the terrain are [http://blog.wolfire.com/2009/02/terrain-edge-fading/ faded to blend in]. This new skybox is then blurred to use as a lookup for [http://blog.wolfire.com/2008/12/sky/ lighting and fog color]. The terrain also has [http://blog.wolfire.com/2009/12/Detail-textures four normal-mapped detail textures], which are blended based on a weight map, and [http://blog.wolfire.com/2009/12/Detail-texture-color-matching automatically tinted] to match the base color map. The detail textures [http://blog.wolfire.com/2009/12/Fading-detail-textures fade away in the distance] to avoid any visible tiling, but the heightmap normal mapping keeps the [http://blog.wolfire.com/2009/12/Close-up-and-distant-terrain-lighting large-scale detail]. This same technique is also used for some large objects, like buildings, cliffs and boulders.

===XML File===
<pre>
<?xml version="2.0" ?>

<Type>saved</Type>
<Name></Name>
<Description></Description>
<Shader>post</Shader>

<Terrain>
<Heightmap>[path here]</Heightmap>
<ColorMap>[path here]</ColorMap>
<WeightMap>[path here]</WeightMap>
<DetailMaps>
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Sky>
<DomeTexture>Data/Textures/skies/FILE.tga</DomeTexture>
<SunAngularRad>0.123456</SunAngularRad>
<SunColorAngle>6.8534</SunColorAngle>
<RayToSun r0="0.123456" r1="0.123456" r2="0.123456" />
<ExtraAO>0</ExtraAO>
</Sky>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

==Header==
'''<Type>''' - ??

'''<Name>''' - ??

'''<Description>''' - ??

'''<Shader>''' - ??

==Terrain==
'''<HeightMap>''' - A 16-bit grayscale image in the png format, with the value of each pixel corresponding to an elevation in the terrain.

'''<ColorMap>''' - A .tga file which maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

'''<WeightMap>''' - A .tga in which colors (RGB + Black) are used to define which DetailMap to use on which part of the terrain.

'''<DetailMap>''' - DetailMaps are used to tile various objects across the terrain, for example of a patch of gravel: a local change in terrain color to grey, a normal map that gives the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

==Sky==
'''<DomeTexture>''' - Filepath to the texture of the skydome. Some already exist in Data/Textures/skies/

'''<SunAngularRad>''' - Size of Sun in Radians?

'''<SunColorAngle>''' - ??

'''<RayToSun/>''' - This Tag has 4 Attributes, r0, r1, and r2. ''NOTE: Range? they have floating point values, generally close to 0. what do they do?''

Overgrowth Levels

2015-02-13T20:54:04Z

Poddus: /* Sky */

The base for every scene is the land and sky. The sky is [http://blog.wolfire.com/2009/02/creating-our-own-skydomes/ based on a panoramic photo], which is converted to a skybox at run-time. The terrain is based on a heightmap, which is then [http://blog.wolfire.com/2009/06/offthegrid-revisited/ simplified] using quadric error metrics and divided into patches for frustum culling. Finally the terrain and sky are combined into a new [http://blog.wolfire.com/2009/07/blending-land-and-sky/ skybox], and the edges of the terrain are [http://blog.wolfire.com/2009/02/terrain-edge-fading/ faded to blend in]. This new skybox is then blurred to use as a lookup for [http://blog.wolfire.com/2008/12/sky/ lighting and fog color]. The terrain also has [http://blog.wolfire.com/2009/12/Detail-textures four normal-mapped detail textures], which are blended based on a weight map, and [http://blog.wolfire.com/2009/12/Detail-texture-color-matching automatically tinted] to match the base color map. The detail textures [http://blog.wolfire.com/2009/12/Fading-detail-textures fade away in the distance] to avoid any visible tiling, but the heightmap normal mapping keeps the [http://blog.wolfire.com/2009/12/Close-up-and-distant-terrain-lighting large-scale detail]. This same technique is also used for some large objects, like buildings, cliffs and boulders.

===XML File===
<pre>
<?xml version="2.0" ?>

<Type>saved</Type>
<Name></Name>
<Description></Description>
<Shader>post</Shader>

<Terrain>
<Heightmap>[path here]</Heightmap>
<ColorMap>[path here]</ColorMap>
<WeightMap>[path here]</WeightMap>
<DetailMaps>
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Sky>
<DomeTexture>Data/Textures/skies/FILE.tga</DomeTexture>
<SunAngularRad>0.123456</SunAngularRad>
<SunColorAngle>6.8534</SunColorAngle>
<RayToSun r0="0.123456" r1="0.123456" r2="0.123456" />
<ExtraAO>0</ExtraAO>
</Sky>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

==Header==
'''<Type>''' - ??

'''<Name>''' - ??

'''<Description>''' - ??

'''<Shader>''' - ??

==Terrain==
'''<HeightMap>''' - A 16-bit grayscale image in the png format, with the value of each pixel corresponding to an elevation in the terrain.

'''<ColorMap>''' - A .tga file which maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

'''<WeightMap>''' - A .tga in which colors (RGB + Black) are used to define which DetailMap to use on which part of the terrain.

'''<DetailMap>''' - DetailMaps are used to tile various objects across the terrain, for example of a patch of gravel: a local change in terrain color to grey, a normal map that gives the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

==Sky==
'''<DomeTexture>''' - Filepath to the texture of the skydome. Some already exist in Data/Textures/skies/

'''<SunAngularRad>''' - Size of Sun in Radians?

'''<SunColorAngle>''' - ??

'''<RayToSun/>''' - This Tag has 4 Attributes, r0="0.0" r1="0.0" r2="0.0" ''NOTE: what do they do?''

3D Objects

2015-02-13T20:45:23Z

Poddus: /* Tags */ replaced normal mapping link to blog post

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=11227 this] forum post by member Markuss.''
There is a linked .zip file attached to the forum post. it can be found here:
http://www.markstockton.com/misc/Guide/Examples.zip

==Basics==
In Overgrowth 3D models use the [http://en.wikipedia.org/wiki/Wavefront_.obj_file .OBJ format] but the material counter-part (.MTL) is not used, instead an “object properties file” stores links to model and texture files as well as some other information. This is the file you choose when loading an object, it uses the .XML format and can be read/created in any text editor:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Markuss/Examples/Models/SimpleObject.obj</Model>
<ColorMap>Data/Custom/Markuss/Examples/Textures/SimpleObject_Color.tga</ColorMap>
<NormalMap>Data/Custom/Markuss/Examples/Textures/Blank_Norm.tga</NormalMap>
<ShaderName>cubemap</ShaderName>
<MaterialPath>Data/Materials/default.xml</MaterialPath>
</Object>
</pre>

===Tags===
'''<Model>''' - links to the model file (.OBJ)

'''<ColorMap>''' - links to the color texture file (.TGA .TIF)

'''<NormalMap>''' - links to the [http://blog.wolfire.com/2009/10/character-normal-maps/ normal map] texture file (.TGA .TIF)

'''<ShaderName>''' - refers to internal shader file (.FRAG .VERT, in Data/GLSL/), defines how object is rendered.

'''<MaterialPath>''' - links to internal material file (.XML), defines sound made by hitting the object.

====Additional tags====

'''<flags no_collision>''' - turns physics calculations on/off, true = off.

''NOTE:''

''“<ShaderName>” used to be “<ShaderPath>” and contained the full link instead of just the file name, expect similar update for “<MaterialPath>”.''

''Look at the example plant object for usage of the <flags no_collision> tag.''

===Model and Texture Requirements===

Models need to be constructed from squares and triangles only, so textures need to be square and not just “powers of 2”. (512x512 or 1024x1024 not 512x1024 or 1024x2048)

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Simple object and texture UV layout

==Alternative object System==
The engine automatically generates a simplified physics object and uses the object’s UV layout to place the shadow maps, these can be overridden by providing alternative .OBJ files that contain the desired information. These objects are placed in the same folder and share the same name as the original .OBJ file with a suffix to tell the engine what data they hold:

===Suffixes===
'''YourObject_COL.obj''' - contains simplified geometry for physics calculations

'''YourObject.obj_UV2''' - contains same object but with no overlapping UVs

'''YourObjectHULL.obj''' - same as _COL but has extra info, used with weapons

''NOTE:''

''The suffix formats are inconsistent, _COL is placed before the file extension while _UV2 is place after, and HULL doesn’t even have an underscore to separate it from the file name!''

===Physics objects (_COL)===
Simplified geometry such as boxes an cylinders which are used for collision detection, they are aligned to your object based on “relative position” in your 3D program so you should place the physics mesh on top of your render mesh upon export:

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Physics mesh should be placed on top of the render mesh

===Shadow UV objects (_UV2)===
These objects tell the engine how to place the shadow map on the rendered object if the original UV layout isn’t appropriate, the shadow maps require UV layouts with no over-lapping faces, this can usually be achieved using the “automatic unwrapping” tools found in most 3D applications.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Color texture UVs left, shadow UVs right, each face needs its own UV space.

===Hull objects (HULL)===
They are very similar to physics objects but are used for items and weapons, the only difference is that they contain a free-floating triangle which defines the object’s center of gravity.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Hull objects are placed over render mesh like physics objects.

==Items and Weapons==

Items and Weapons are aligned to the character based on their position relative to the center of the scene in your 3D app, you should load the .obj files of the example objects for reference. To make an object “pick-up-able” you need another .XML file that you load in place of the regular object properties file, it stores the info needed that is not defined in the regular object properties file:

<pre>
<?xml version="1.0" ?>
<item>
<type>weapon</type>
<appearance obj_path = "Data/Custom/Markuss/Examples/1-Handed.xml"/>
<grip ik_attach = "rightarm"
anim = "Data/Animations/r_dogweapongrip.anm"/>
<physics mass = "1 kg"/>
</item>
</pre>
Item properties file

===Tags===
'''<type>''' - defines what type of item the object is.

'''<appearance obj_path>''' - links to the regular object definition file.

'''<grip ik_attach anim>''' - defines what bone the object is attached to, links to an animation file.

'''<physics mass>''' - changes the pitch(?) of the sound made by the object hitting things.

'''<anim_override idle>''' - overrides the idle animation of a character holding the item.

''NOTE:''

''Not sure what the animation file in <grip ik_attach anim> does.''

''<anim_override idle> is only used for 2-handed weapons at the moment.''

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Example weapons, handles show the location of characters hands

''NOTE:''

''There is a bug that makes weapons turn invisible when loading levels with them already in it, you can fix this by having the “regular-object" version somewhere in the level as well.''

==Shaders==
'''Cubemap''' – closest thing to a “standard shader”, it has a cube-map based on the sky texture and a specular shine, the visibility of the cube map and shine is controlled with color texture’s alpha channel, white = fully reflective and shiny. Similarly, the normal-map texture’s alpha channel controls where color tinting happens, white = full effect. The cube map’s visibility is inversely affected by the brightness of the texture, you should make the color texture close to black for materials that are reflective such as chrome and glass.

'''CubemapObj''' - same as Cubemap but uses object-space normal maps instead of tangent space.

'''CubemapItem''' - same as Cubemap but the shine is sharper.

'''CubemapObjItem''' - object-space version of CubemapItem.

'''CubemapAlpha''' - has transparency controlled by the color texture’s alpha channel, cube map and shine are controlled by the normal-map texture’s alpha channel instead. CubemapAlpha has depth sorting issues with other transparent objects, enabling anti-aliasing fixes this somewhat.

'''CubemapObjChar''' - used for characters, shine is sharp, uses object space normals. There is no tangent-space version of CubemapObjChar and no object-space version of CubemapAlpha at the moment.

'''Plant''' - has transparency like CubemapAlpha but no cube map/shine. Translucency texture increases the brightness of the object while ignoring diffuse lighting, black = no effect. Wind texture defines intensity of a vertex ripple effect, black = no ripple. Both textures are linked in the object definition file using the <TranslucencyMap> and <WindMap> tags.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
CubemapAlpha

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Translucency (Plant Shader)

==Materials==

These are the sounds made and the particles emitted when you hit an object. I’ve set up some tiles for you to walk on to preview each material, here is a list:

: Cloth_Fabric
: Cloth_Leather
: Default
: Dirt
: DirtyRock
: Drygrass
: Grass
: Gravel
: Rock
: Rocks
: Sand
: Snow
: Wood

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Sound tiles

Note that some of these don’t emit particles.

Overgrowth Levels

2015-02-13T20:38:21Z

Poddus: merged intro from blog post http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview

Overgrowth Levels

2015-02-13T20:30:14Z

Poddus: /* Sky */

Overgrowth Levels are composed of a collection of files. The main file is a .xml and has the following basic structure:

===XML File===
<pre>
<?xml version="2.0" ?>

<Type>saved</Type>
<Name></Name>
<Description></Description>
<Shader>post</Shader>

<Terrain>
<Heightmap>[path here]</Heightmap>
<ColorMap>[path here]</ColorMap>
<WeightMap>[path here]</WeightMap>
<DetailMaps>
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Sky>
<DomeTexture>Data/Textures/skies/FILE.tga</DomeTexture>
<SunAngularRad>0.123456</SunAngularRad>
<SunColorAngle>6.8534</SunColorAngle>
<RayToSun r0="0.123456" r1="0.123456" r2="0.123456" />
<ExtraAO>0</ExtraAO>
</Sky>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

==Header==
'''<Type>''' - ??

'''<Name>''' - ??

'''<Description>''' - ??

'''<Shader>''' - ??

==Terrain==
'''<HeightMap>''' - A 16-bit grayscale image in the png format, with the value of each pixel corresponding to an elevation in the terrain.

'''<ColorMap>''' - A .tga file which maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

'''<WeightMap>''' - A .tga in which colors (RGB + Black) are used to define which DetailMap to use on which part of the terrain.

'''<DetailMap>''' - DetailMaps are used to tile various objects across the terrain, for example of a patch of gravel: a local change in terrain color to grey, a normal map that gives the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

==Sky==
'''<DomeTexture>''' - Filepath to the texture of the skydome. Some already exist in Data/Textures/skies/

'''<SunAngularRad>''' - Size of Sun in Radians?

'''<SunColorAngle>''' - ??

'''<RayToSun r0="0.0" r1="0.0" r2="0.0" />''' - ??

Particle Effects

2015-02-13T20:26:54Z

Poddus:

There isn't much information released about Overgrowth's particle system. Running or jumping on the ground creates small dust clouds at the characters' feet, and particle streams were added in [http://blog.wolfire.com/2011/04/Overgrowth-a128-video-changelog A128] along with blood dripping. Particles are controlled through scripts, examples below:

==Simple Particle Example==
<pre>
MakeParticle("Data/Particles/impactfast.xml",pos,vec3(0.0f));
</pre>

==Particle Stream Example==

<pre>
float blood_force = sin(time*_spurt_frequency)*0.5f+0.5f;
uint32 id = MakeParticle("Data/Particles/blooddrop.xml",bleed_pos,(head_transform*vec3(0.0f,blood_amount*blood_force,0.0f)+this_mo.velocity));
if(last_blood_particle_id != 0){
ConnectParticles(last_blood_particle_id, id);
}
last_blood_particle_id = id;
</pre>

==File Structure==
There appear to be two different kinds of particles. Both are defined by an .xml file, however, one version is based on a video file, while the other is based on a static texture.

===OGV-Based===
One Particle Effect is based on .ogv files found under Data/Textures/anims/ (though they are not referenced as .ogv but as .xml files in the Particle XML)


<pre>
<?xml version="1.0" ?>
<particle>
<textures animation_effect = "Data/Textures/anims/bigexplosion.xml"
shader = "theorabluescreen"
soft_shader = "theorabluescreensoft"/>
<size val="40.0"/>
<color red = "1.0"
green = "1.0"
blue = "1.0"
alpha = "1.0"/>
<behavior inertia="1.0" gravity="0.0" wind="0.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<no_rotation />
</particle>
</pre>

'''<textures/>''' - This tag has 3 attributes.
* animation_effect - this is the only attribute specific to ogv-based particles and references the file path, starting from the Data folder, to a video file. ''NOTE: for some reason, as of a209, the files referenced are xml format, however all files under Data/Textures/anims/ are ogv format. Is the reference is a typo?''
* shader - the name (not including file extension, typically .frag) of the shader in folder Data/GLSL/
* soft_shader - ?? usually just the name of the shader with the word "soft" appended to the end.

'''<size/>''' - This tag uses the attribute "val" (floating point number) to specify the size of the particle. ''NOTE: Units are unknown''

'''<color/>''' - This tag has a varying number of attributes, one for each channel (RGB + Alpha), while the Alpha Channel may be defined as a range, requiring two attributes, alpha_min and alpha_max ''Range? perhaps floating point values from 0.0 to 1.0''

'''<behavior/>''' - This tag has 5 attributes. All are likely floating point values from 0.0 to 1.0
* inertia - Rate at which the particle slows its initial speed
* gravity - Degree with which a downwards gravitational force acts upon the particle
* wind - Degree with which wind effects the particle vector
* size_decay_rate - Rate at which the size of the particle decreases ''NOTE: is this value range bounded by 0 & 1?''
* opacity_decay_rate - Rate at which the alpha channel values of the particle increase ''NOTE: is this value range bounded by 0 & 1?''

===Texture-Based===


<pre>
<?xml version="1.0" ?>
<particle>
<textures color_map = "Data/Textures/smoke.tga"
normal_map = "Data/Textures/smoke_normal.tga"
shader = "litsprite"
soft_shader = "litspritesoft"/>
<size min = "0.4" max = "0.7"/>
<color red = "0.5"
green = "0.5"
blue = "0.5"
alpha_min = "0.5" alpha_max = "1.0"/>
<behavior inertia="0.9" gravity="0.0" wind="1.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<quadratic_expansion speed="4.0"/>
<quadratic_dispersion persistence="1.0"/>
</particle>
</pre>

= Relevant blog posts =

[http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview A summary] of most blog posts explaining Overgrowth's graphical features, focusing on more technical details. There are additional links below, some of which are not mentioned in the summary.

http://blog.wolfire.com/2008/12/object-lighting-part-1/
http://blog.wolfire.com/2010/02/Gamma-correct-lighting

http://blog.wolfire.com/2009/09/character-rim-lighting/
http://blog.wolfire.com/2009/10/character-normal-maps/
http://blog.wolfire.com/2009/09/soft-normal-maps-for-fur/

http://blog.wolfire.com/2009/09/trees-in-the-breeze/
http://blog.wolfire.com/2010/10/Imposters

http://blog.wolfire.com/2009/05/decals-editor-part-one/
http://blog.wolfire.com/2009/05/decals-editor-part-two/
http://blog.wolfire.com/2009/06/decals-editor-part-three/

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Particle Effects

2015-02-13T20:26:17Z

Poddus: split post processing effects into separate article

= Particle Effects =
There isn't much information released about Overgrowth's particle system. Running or jumping on the ground creates small dust clouds at the characters' feet, and particle streams were added in [http://blog.wolfire.com/2011/04/Overgrowth-a128-video-changelog A128] along with blood dripping. Particles are controlled through scripts, examples below:

==Simple Particle Example==
<pre>
MakeParticle("Data/Particles/impactfast.xml",pos,vec3(0.0f));
</pre>

==Particle Stream Example==

<pre>
float blood_force = sin(time*_spurt_frequency)*0.5f+0.5f;
uint32 id = MakeParticle("Data/Particles/blooddrop.xml",bleed_pos,(head_transform*vec3(0.0f,blood_amount*blood_force,0.0f)+this_mo.velocity));
if(last_blood_particle_id != 0){
ConnectParticles(last_blood_particle_id, id);
}
last_blood_particle_id = id;
</pre>

==File Structure==
There appear to be two different kinds of particles. Both are defined by an .xml file, however, one version is based on a video file, while the other is based on a static texture.

===OGV-Based===
One Particle Effect is based on .ogv files found under Data/Textures/anims/ (though they are not referenced as .ogv but as .xml files in the Particle XML)


<pre>
<?xml version="1.0" ?>
<particle>
<textures animation_effect = "Data/Textures/anims/bigexplosion.xml"
shader = "theorabluescreen"
soft_shader = "theorabluescreensoft"/>
<size val="40.0"/>
<color red = "1.0"
green = "1.0"
blue = "1.0"
alpha = "1.0"/>
<behavior inertia="1.0" gravity="0.0" wind="0.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<no_rotation />
</particle>
</pre>

'''<textures/>''' - This tag has 3 attributes.
* animation_effect - this is the only attribute specific to ogv-based particles and references the file path, starting from the Data folder, to a video file. ''NOTE: for some reason, as of a209, the files referenced are xml format, however all files under Data/Textures/anims/ are ogv format. Is the reference is a typo?''
* shader - the name (not including file extension, typically .frag) of the shader in folder Data/GLSL/
* soft_shader - ?? usually just the name of the shader with the word "soft" appended to the end.

'''<size/>''' - This tag uses the attribute "val" (floating point number) to specify the size of the particle. ''NOTE: Units are unknown''

'''<color/>''' - This tag has a varying number of attributes, one for each channel (RGB + Alpha), while the Alpha Channel may be defined as a range, requiring two attributes, alpha_min and alpha_max ''Range? perhaps floating point values from 0.0 to 1.0''

'''<behavior/>''' - This tag has 5 attributes. All are likely floating point values from 0.0 to 1.0
* inertia - Rate at which the particle slows its initial speed
* gravity - Degree with which a downwards gravitational force acts upon the particle
* wind - Degree with which wind effects the particle vector
* size_decay_rate - Rate at which the size of the particle decreases ''NOTE: is this value range bounded by 0 & 1?''
* opacity_decay_rate - Rate at which the alpha channel values of the particle increase ''NOTE: is this value range bounded by 0 & 1?''

===Texture-Based===


<pre>
<?xml version="1.0" ?>
<particle>
<textures color_map = "Data/Textures/smoke.tga"
normal_map = "Data/Textures/smoke_normal.tga"
shader = "litsprite"
soft_shader = "litspritesoft"/>
<size min = "0.4" max = "0.7"/>
<color red = "0.5"
green = "0.5"
blue = "0.5"
alpha_min = "0.5" alpha_max = "1.0"/>
<behavior inertia="0.9" gravity="0.0" wind="1.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<quadratic_expansion speed="4.0"/>
<quadratic_dispersion persistence="1.0"/>
</particle>
</pre>

= Relevant blog posts =

[http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview A summary] of most blog posts explaining Overgrowth's graphical features, focusing on more technical details. There are additional links below, some of which are not mentioned in the summary.

http://blog.wolfire.com/2008/12/object-lighting-part-1/
http://blog.wolfire.com/2010/02/Gamma-correct-lighting

http://blog.wolfire.com/2009/09/character-rim-lighting/
http://blog.wolfire.com/2009/10/character-normal-maps/
http://blog.wolfire.com/2009/09/soft-normal-maps-for-fur/

http://blog.wolfire.com/2009/09/trees-in-the-breeze/
http://blog.wolfire.com/2010/10/Imposters

http://blog.wolfire.com/2009/05/decals-editor-part-one/
http://blog.wolfire.com/2009/05/decals-editor-part-two/
http://blog.wolfire.com/2009/06/decals-editor-part-three/

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Post Processing Effects

2015-02-13T20:16:29Z

Poddus: stub

{{stub}}

''Post processing effects are image filters that are applied as a final step before each rendered frame is drawn to the screen -- much like Photoshop filters.'' This explanation is lifted word-for-word from David's blog post on the subject. He doesn't go into much detail about it in his blog posts, but here's links to [http://blog.wolfire.com/2009/04/post-processing-part-one/ part one] and [http://blog.wolfire.com/2009/04/post-processing-part-two/ part two] any way.

= Shaders =
Overgrowth uses GLSL shader language, and the users can create custom shaders. Some blog posts explain how some of the shaders work, such as the posts about [http://blog.wolfire.com/2008/12/object-lighting-part-1/ Object Lightning], [http://blog.wolfire.com/2009/09/character-rim-lighting/ Character Rim Lighting] and [http://blog.wolfire.com/2009/09/trees-in-the-breeze/ Trees in the Breeze]. Overgrowth's character animation is also done through a shader, as David mentioned in [http://blog.wolfire.com/2009/10/character-normal-maps/#comment-18448230 a blog comment].

The skeletal animation is done in the vertex shader anyway, so it's actually
faster and smoother-looking to just apply the bone matrices to the object-space
normal map than it is to recalculate transformed normals and tangents for
each vertex.

= Motion Blur for Weapons =
Overgrowth's weapons use motion blur based on stippling. Stippling is also used to render soft shadows, and the technique of stippling is explained in [http://blog.wolfire.com/2009/10/transparent-shadows-using-stippling/ this old blog post]. The motion blur for weapons works by drawing the weapon several times along it spath using different stipple patterns for each instance, as mentioned in the [http://blog.wolfire.com/2011/06/Overgrowth-a135-video-changelog A135 video].

Portal:Overgrowth

2015-02-13T20:16:03Z

Poddus: /* Phoenix Engine Documentation */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
* [[3D Objects]]
* [[Character Models]]
* [[Particle Effects]]
* [[Post Processing Effects]]
* [[Overgrowth Levels]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Custom Terrain]]

==Alpha Testing==
* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Post Processing Effects

2015-02-13T20:15:40Z

Poddus: Created page with "''Post processing effects are image filters that are applied as a final step before each rendered frame is drawn to the screen -- much like Photoshop filters.'' This explanation ..."

''Post processing effects are image filters that are applied as a final step before each rendered frame is drawn to the screen -- much like Photoshop filters.'' This explanation is lifted word-for-word from David's blog post on the subject. He doesn't go into much detail about it in his blog posts, but here's links to [http://blog.wolfire.com/2009/04/post-processing-part-one/ part one] and [http://blog.wolfire.com/2009/04/post-processing-part-two/ part two] any way.

= Shaders =
Overgrowth uses GLSL shader language, and the users can create custom shaders. Some blog posts explain how some of the shaders work, such as the posts about [http://blog.wolfire.com/2008/12/object-lighting-part-1/ Object Lightning], [http://blog.wolfire.com/2009/09/character-rim-lighting/ Character Rim Lighting] and [http://blog.wolfire.com/2009/09/trees-in-the-breeze/ Trees in the Breeze]. Overgrowth's character animation is also done through a shader, as David mentioned in [http://blog.wolfire.com/2009/10/character-normal-maps/#comment-18448230 a blog comment].

The skeletal animation is done in the vertex shader anyway, so it's actually
faster and smoother-looking to just apply the bone matrices to the object-space
normal map than it is to recalculate transformed normals and tangents for
each vertex.

= Motion Blur for Weapons =
Overgrowth's weapons use motion blur based on stippling. Stippling is also used to render soft shadows, and the technique of stippling is explained in [http://blog.wolfire.com/2009/10/transparent-shadows-using-stippling/ this old blog post]. The motion blur for weapons works by drawing the weapon several times along it spath using different stipple patterns for each instance, as mentioned in the [http://blog.wolfire.com/2011/06/Overgrowth-a135-video-changelog A135 video].

Portal:Overgrowth

2015-02-13T20:14:16Z

Poddus: /* Phoenix Engine Documentation */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
* [[3D Objects]]
* [[Character Models]]
* [[Particle Effects]]
* [[Overgrowth Levels]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Custom Terrain]]

==Alpha Testing==
* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Effects System

2015-02-13T20:13:57Z

Poddus: moved Effects System to Particle Effects: Split Particle Effects and Post-Processing Effects into separate Articles

#REDIRECT [[Particle Effects]]

Particle Effects

2015-02-13T20:13:57Z

Poddus: moved Effects System to Particle Effects: Split Particle Effects and Post-Processing Effects into separate Articles

= Particle Effects =
There isn't much information released about Overgrowth's particle system. Running or jumping on the ground creates small dust clouds at the characters' feet, and particle streams were added in [http://blog.wolfire.com/2011/04/Overgrowth-a128-video-changelog A128] along with blood dripping. Particles are controlled through scripts, examples below:

==Simple Particle Example==
<pre>
MakeParticle("Data/Particles/impactfast.xml",pos,vec3(0.0f));
</pre>

==Particle Stream Example==

<pre>
float blood_force = sin(time*_spurt_frequency)*0.5f+0.5f;
uint32 id = MakeParticle("Data/Particles/blooddrop.xml",bleed_pos,(head_transform*vec3(0.0f,blood_amount*blood_force,0.0f)+this_mo.velocity));
if(last_blood_particle_id != 0){
ConnectParticles(last_blood_particle_id, id);
}
last_blood_particle_id = id;
</pre>

==File Structure==
There appear to be two different kinds of particles. Both are defined by an .xml file, however, one version is based on a video file, while the other is based on a static texture.

===OGV-Based===
One Particle Effect is based on .ogv files found under Data/Textures/anims/ (though they are not referenced as .ogv but as .xml files in the Particle XML)


<pre>
<?xml version="1.0" ?>
<particle>
<textures animation_effect = "Data/Textures/anims/bigexplosion.xml"
shader = "theorabluescreen"
soft_shader = "theorabluescreensoft"/>
<size val="40.0"/>
<color red = "1.0"
green = "1.0"
blue = "1.0"
alpha = "1.0"/>
<behavior inertia="1.0" gravity="0.0" wind="0.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<no_rotation />
</particle>
</pre>

'''<textures/>''' - This tag has 3 attributes.
* animation_effect - this is the only attribute specific to ogv-based particles and references the file path, starting from the Data folder, to a video file. ''NOTE: for some reason, as of a209, the files referenced are xml format, however all files under Data/Textures/anims/ are ogv format. Is the reference is a typo?''
* shader - the name (not including file extension, typically .frag) of the shader in folder Data/GLSL/
* soft_shader - ?? usually just the name of the shader with the word "soft" appended to the end.

'''<size/>''' - This tag uses the attribute "val" (floating point number) to specify the size of the particle. ''NOTE: Units are unknown''

'''<color/>''' - This tag has a varying number of attributes, one for each channel (RGB + Alpha), while the Alpha Channel may be defined as a range, requiring two attributes, alpha_min and alpha_max ''Range? perhaps floating point values from 0.0 to 1.0''

'''<behavior/>''' - This tag has 5 attributes. All are likely floating point values from 0.0 to 1.0
* inertia - Rate at which the particle slows its initial speed
* gravity - Degree with which a downwards gravitational force acts upon the particle
* wind - Degree with which wind effects the particle vector
* size_decay_rate - Rate at which the size of the particle decreases ''NOTE: is this value range bounded by 0 & 1?''
* opacity_decay_rate - Rate at which the alpha channel values of the particle increase ''NOTE: is this value range bounded by 0 & 1?''

===Texture-Based===


<pre>
<?xml version="1.0" ?>
<particle>
<textures color_map = "Data/Textures/smoke.tga"
normal_map = "Data/Textures/smoke_normal.tga"
shader = "litsprite"
soft_shader = "litspritesoft"/>
<size min = "0.4" max = "0.7"/>
<color red = "0.5"
green = "0.5"
blue = "0.5"
alpha_min = "0.5" alpha_max = "1.0"/>
<behavior inertia="0.9" gravity="0.0" wind="1.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<quadratic_expansion speed="4.0"/>
<quadratic_dispersion persistence="1.0"/>
</particle>
</pre>
{{stub}}

= Post Processing Effects =
''Post processing effects are image filters that are applied as a final step before each rendered frame is drawn to the screen -- much like Photoshop filters.'' This explanation is lifted word-for-word from David's blog post on the subject. He doesn't go into much detail about it in his blog posts, but here's links to [http://blog.wolfire.com/2009/04/post-processing-part-one/ part one] and [http://blog.wolfire.com/2009/04/post-processing-part-two/ part two] any way.

= Shaders =
Overgrowth uses GLSL shader language, and the users can create custom shaders. Some blog posts explain how some of the shaders work, such as the posts about [http://blog.wolfire.com/2008/12/object-lighting-part-1/ Object Lightning], [http://blog.wolfire.com/2009/09/character-rim-lighting/ Character Rim Lighting] and [http://blog.wolfire.com/2009/09/trees-in-the-breeze/ Trees in the Breeze]. Overgrowth's character animation is also done through a shader, as David mentioned in [http://blog.wolfire.com/2009/10/character-normal-maps/#comment-18448230 a blog comment].

The skeletal animation is done in the vertex shader anyway, so it's actually
faster and smoother-looking to just apply the bone matrices to the object-space
normal map than it is to recalculate transformed normals and tangents for
each vertex.

= Motion Blur for Weapons =
Overgrowth's weapons use motion blur based on stippling. Stippling is also used to render soft shadows, and the technique of stippling is explained in [http://blog.wolfire.com/2009/10/transparent-shadows-using-stippling/ this old blog post]. The motion blur for weapons works by drawing the weapon several times along it spath using different stipple patterns for each instance, as mentioned in the [http://blog.wolfire.com/2011/06/Overgrowth-a135-video-changelog A135 video].

= Relevant blog posts =

[http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview A summary] of most blog posts explaining Overgrowth's graphical features, focusing on more technical details. There are additional links below, some of which are not mentioned in the summary.

http://blog.wolfire.com/2008/12/object-lighting-part-1/
http://blog.wolfire.com/2010/02/Gamma-correct-lighting

http://blog.wolfire.com/2009/09/character-rim-lighting/
http://blog.wolfire.com/2009/10/character-normal-maps/
http://blog.wolfire.com/2009/09/soft-normal-maps-for-fur/

http://blog.wolfire.com/2009/09/trees-in-the-breeze/
http://blog.wolfire.com/2010/10/Imposters

http://blog.wolfire.com/2009/05/decals-editor-part-one/
http://blog.wolfire.com/2009/05/decals-editor-part-two/
http://blog.wolfire.com/2009/06/decals-editor-part-three/

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Particle Effects

2015-02-13T20:12:56Z

Poddus:

= Particle Effects =
There isn't much information released about Overgrowth's particle system. Running or jumping on the ground creates small dust clouds at the characters' feet, and particle streams were added in [http://blog.wolfire.com/2011/04/Overgrowth-a128-video-changelog A128] along with blood dripping. Particles are controlled through scripts, examples below:

==Simple Particle Example==
<pre>
MakeParticle("Data/Particles/impactfast.xml",pos,vec3(0.0f));
</pre>

==Particle Stream Example==

<pre>
float blood_force = sin(time*_spurt_frequency)*0.5f+0.5f;
uint32 id = MakeParticle("Data/Particles/blooddrop.xml",bleed_pos,(head_transform*vec3(0.0f,blood_amount*blood_force,0.0f)+this_mo.velocity));
if(last_blood_particle_id != 0){
ConnectParticles(last_blood_particle_id, id);
}
last_blood_particle_id = id;
</pre>

==File Structure==
There appear to be two different kinds of particles. Both are defined by an .xml file, however, one version is based on a video file, while the other is based on a static texture.

===OGV-Based===
One Particle Effect is based on .ogv files found under Data/Textures/anims/ (though they are not referenced as .ogv but as .xml files in the Particle XML)


<pre>
<?xml version="1.0" ?>
<particle>
<textures animation_effect = "Data/Textures/anims/bigexplosion.xml"
shader = "theorabluescreen"
soft_shader = "theorabluescreensoft"/>
<size val="40.0"/>
<color red = "1.0"
green = "1.0"
blue = "1.0"
alpha = "1.0"/>
<behavior inertia="1.0" gravity="0.0" wind="0.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<no_rotation />
</particle>
</pre>

'''<textures/>''' - This tag has 3 attributes.
* animation_effect - this is the only attribute specific to ogv-based particles and references the file path, starting from the Data folder, to a video file. ''NOTE: for some reason, as of a209, the files referenced are xml format, however all files under Data/Textures/anims/ are ogv format. Is the reference is a typo?''
* shader - the name (not including file extension, typically .frag) of the shader in folder Data/GLSL/
* soft_shader - ?? usually just the name of the shader with the word "soft" appended to the end.

'''<size/>''' - This tag uses the attribute "val" (floating point number) to specify the size of the particle. ''NOTE: Units are unknown''

'''<color/>''' - This tag has a varying number of attributes, one for each channel (RGB + Alpha), while the Alpha Channel may be defined as a range, requiring two attributes, alpha_min and alpha_max ''Range? perhaps floating point values from 0.0 to 1.0''

'''<behavior/>''' - This tag has 5 attributes. All are likely floating point values from 0.0 to 1.0
* inertia - Rate at which the particle slows its initial speed
* gravity - Degree with which a downwards gravitational force acts upon the particle
* wind - Degree with which wind effects the particle vector
* size_decay_rate - Rate at which the size of the particle decreases ''NOTE: is this value range bounded by 0 & 1?''
* opacity_decay_rate - Rate at which the alpha channel values of the particle increase ''NOTE: is this value range bounded by 0 & 1?''

===Texture-Based===


<pre>
<?xml version="1.0" ?>
<particle>
<textures color_map = "Data/Textures/smoke.tga"
normal_map = "Data/Textures/smoke_normal.tga"
shader = "litsprite"
soft_shader = "litspritesoft"/>
<size min = "0.4" max = "0.7"/>
<color red = "0.5"
green = "0.5"
blue = "0.5"
alpha_min = "0.5" alpha_max = "1.0"/>
<behavior inertia="0.9" gravity="0.0" wind="1.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<quadratic_expansion speed="4.0"/>
<quadratic_dispersion persistence="1.0"/>
</particle>
</pre>
{{stub}}

= Post Processing Effects =
''Post processing effects are image filters that are applied as a final step before each rendered frame is drawn to the screen -- much like Photoshop filters.'' This explanation is lifted word-for-word from David's blog post on the subject. He doesn't go into much detail about it in his blog posts, but here's links to [http://blog.wolfire.com/2009/04/post-processing-part-one/ part one] and [http://blog.wolfire.com/2009/04/post-processing-part-two/ part two] any way.

= Shaders =
Overgrowth uses GLSL shader language, and the users can create custom shaders. Some blog posts explain how some of the shaders work, such as the posts about [http://blog.wolfire.com/2008/12/object-lighting-part-1/ Object Lightning], [http://blog.wolfire.com/2009/09/character-rim-lighting/ Character Rim Lighting] and [http://blog.wolfire.com/2009/09/trees-in-the-breeze/ Trees in the Breeze]. Overgrowth's character animation is also done through a shader, as David mentioned in [http://blog.wolfire.com/2009/10/character-normal-maps/#comment-18448230 a blog comment].

The skeletal animation is done in the vertex shader anyway, so it's actually
faster and smoother-looking to just apply the bone matrices to the object-space
normal map than it is to recalculate transformed normals and tangents for
each vertex.

= Motion Blur for Weapons =
Overgrowth's weapons use motion blur based on stippling. Stippling is also used to render soft shadows, and the technique of stippling is explained in [http://blog.wolfire.com/2009/10/transparent-shadows-using-stippling/ this old blog post]. The motion blur for weapons works by drawing the weapon several times along it spath using different stipple patterns for each instance, as mentioned in the [http://blog.wolfire.com/2011/06/Overgrowth-a135-video-changelog A135 video].

= Relevant blog posts =

[http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview A summary] of most blog posts explaining Overgrowth's graphical features, focusing on more technical details. There are additional links below, some of which are not mentioned in the summary.

http://blog.wolfire.com/2008/12/object-lighting-part-1/
http://blog.wolfire.com/2010/02/Gamma-correct-lighting

http://blog.wolfire.com/2009/09/character-rim-lighting/
http://blog.wolfire.com/2009/10/character-normal-maps/
http://blog.wolfire.com/2009/09/soft-normal-maps-for-fur/

http://blog.wolfire.com/2009/09/trees-in-the-breeze/
http://blog.wolfire.com/2010/10/Imposters

http://blog.wolfire.com/2009/05/decals-editor-part-one/
http://blog.wolfire.com/2009/05/decals-editor-part-two/
http://blog.wolfire.com/2009/06/decals-editor-part-three/

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Particle Effects

2015-02-13T20:01:43Z

Poddus: added section on File Structure

= Particle Effects =
There isn't much information released about Overgrowth's particle system. Running or jumping on the ground creates small dust clouds at the characters' feet, and particle streams were added in [http://blog.wolfire.com/2011/04/Overgrowth-a128-video-changelog A128] along with blood dripping. Particles are controlled through scripts, examples below:

==Simple Particle Example==
<pre>
MakeParticle("Data/Particles/impactfast.xml",pos,vec3(0.0f));
</pre>

==Particle Stream Example==

<pre>
float blood_force = sin(time*_spurt_frequency)*0.5f+0.5f;
uint32 id = MakeParticle("Data/Particles/blooddrop.xml",bleed_pos,(head_transform*vec3(0.0f,blood_amount*blood_force,0.0f)+this_mo.velocity));
if(last_blood_particle_id != 0){
ConnectParticles(last_blood_particle_id, id);
}
last_blood_particle_id = id;
</pre>

==File Structure==
There appear to be two different kinds of particles. Both are defined by an .xml file, however, one version is based on a video file, while the other is based on a static texture.

===OGV-Based===
One Particle Effect is based on .ogv files found under Data/Textures/anims/ (though they are not referenced as .ogv but as .xml files in the Particle XML)


<pre>
<?xml version="1.0" ?>
<particle>
<textures animation_effect = "Data/Textures/anims/bigexplosion.xml"
shader = "theorabluescreen"
soft_shader = "theorabluescreensoft"/>
<size val="40.0"/>
<color red = "1.0"
green = "1.0"
blue = "1.0"
alpha = "1.0"/>
<behavior inertia="1.0" gravity="0.0" wind="0.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<no_rotation />
</particle>
</pre>

'''<textures/>''' - This tag has 3 attributes.
* animation_effect - this is the only attribute specific to ogv-based particles and references the file path, starting from the Data folder, to a video file. ''NOTE: for some reason, as of a209, the files referenced are xml format, however all files under Data/Textures/anims/ are ogv format. Is the reference is a typo?''

* shader - the name (not including file extension, typically .frag) of the shader in folder Data/GLSL/

* soft_shader - ?? usually just the name of the shader with the word "soft" appended to the end.

'''<size>''' - This tag uses the attribute "val" (floating point number) to specify the size of the particle. ''NOTE: Units are unknown''

===Texture-Based===


<pre>
<?xml version="1.0" ?>
<particle>
<textures color_map = "Data/Textures/smoke.tga"
normal_map = "Data/Textures/smoke_normal.tga"
shader = "litsprite"
soft_shader = "litspritesoft"/>
<size min = "0.4" max = "0.7"/>
<color red = "0.5"
green = "0.5"
blue = "0.5"
alpha_min = "0.5" alpha_max = "1.0"/>
<behavior inertia="0.9" gravity="0.0" wind="1.0" size_decay_rate="0.0" opacity_decay_rate="0.0"/>
<quadratic_expansion speed="4.0"/>
<quadratic_dispersion persistence="1.0"/>
</particle>
</pre>
{{stub}}

= Post Processing Effects =
''Post processing effects are image filters that are applied as a final step before each rendered frame is drawn to the screen -- much like Photoshop filters.'' This explanation is lifted word-for-word from David's blog post on the subject. He doesn't go into much detail about it in his blog posts, but here's links to [http://blog.wolfire.com/2009/04/post-processing-part-one/ part one] and [http://blog.wolfire.com/2009/04/post-processing-part-two/ part two] any way.

= Shaders =
Overgrowth uses GLSL shader language, and the users can create custom shaders. Some blog posts explain how some of the shaders work, such as the posts about [http://blog.wolfire.com/2008/12/object-lighting-part-1/ Object Lightning], [http://blog.wolfire.com/2009/09/character-rim-lighting/ Character Rim Lighting] and [http://blog.wolfire.com/2009/09/trees-in-the-breeze/ Trees in the Breeze]. Overgrowth's character animation is also done through a shader, as David mentioned in [http://blog.wolfire.com/2009/10/character-normal-maps/#comment-18448230 a blog comment].

The skeletal animation is done in the vertex shader anyway, so it's actually
faster and smoother-looking to just apply the bone matrices to the object-space
normal map than it is to recalculate transformed normals and tangents for
each vertex.

= Motion Blur for Weapons =
Overgrowth's weapons use motion blur based on stippling. Stippling is also used to render soft shadows, and the technique of stippling is explained in [http://blog.wolfire.com/2009/10/transparent-shadows-using-stippling/ this old blog post]. The motion blur for weapons works by drawing the weapon several times along it spath using different stipple patterns for each instance, as mentioned in the [http://blog.wolfire.com/2011/06/Overgrowth-a135-video-changelog A135 video].

= Relevant blog posts =

[http://blog.wolfire.com/2010/12/Overgrowth-graphics-overview A summary] of most blog posts explaining Overgrowth's graphical features, focusing on more technical details. There are additional links below, some of which are not mentioned in the summary.

http://blog.wolfire.com/2008/12/object-lighting-part-1/
http://blog.wolfire.com/2010/02/Gamma-correct-lighting

http://blog.wolfire.com/2009/09/character-rim-lighting/
http://blog.wolfire.com/2009/10/character-normal-maps/
http://blog.wolfire.com/2009/09/soft-normal-maps-for-fur/

http://blog.wolfire.com/2009/09/trees-in-the-breeze/
http://blog.wolfire.com/2010/10/Imposters

http://blog.wolfire.com/2009/05/decals-editor-part-one/
http://blog.wolfire.com/2009/05/decals-editor-part-two/
http://blog.wolfire.com/2009/06/decals-editor-part-three/

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Overgrowth Levels

2015-02-13T18:56:42Z

Poddus:

Overgrowth Levels are composed of a collection of files. The main file is a .xml and has the following basic structure:

===XML File===
<pre>
<?xml version="2.0" ?>

<Type>saved</Type>
<Name></Name>
<Description></Description>
<Shader>post</Shader>

<Terrain>
<Heightmap>[path here]</Heightmap>
<ColorMap>[path here]</ColorMap>
<WeightMap>[path here]</WeightMap>
<DetailMaps>
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Sky>
<DomeTexture>Data/Textures/skies/FILE.tga</DomeTexture>
<SunAngularRad>0.123456</SunAngularRad>
<SunColorAngle>6.8534</SunColorAngle>
<RayToSun r0="0.123456" r1="0.123456" r2="0.123456" />
<ExtraAO>0</ExtraAO>
</Sky>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

==Header==
'''<Type>''' - ??

'''<Name>''' - ??

'''<Description>''' - ??

'''<Shader>''' - ??

==Terrain==
'''<HeightMap>''' - A 16-bit grayscale image in the png format, with the value of each pixel corresponding to an elevation in the terrain.

'''<ColorMap>''' - A .tga file which maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

'''<WeightMap>''' - A .tga in which colors (RGB + Black) are used to define which DetailMap to use on which part of the terrain.

'''<DetailMap>''' - DetailMaps are used to tile various objects across the terrain, for example of a patch of gravel: a local change in terrain color to grey, a normal map that gives the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

==Sky==
'''<DomeTexture>''' - Filepath to the texture of the skybox. Some already exist in Data/Textures/skies/

'''<SunAngularRad>''' - Size of Sun in Radians?

'''<SunColorAngle>''' - ??

'''<RayToSun r0="0.0" r1="0.0" r2="0.0" />''' - ??

Overgrowth Levels

2015-02-13T18:42:12Z

Poddus: /* XML File */ generalized sky section

Overgrowth Levels are composed of a collection of files. The main file is a .xml and has the following basic structure:

===XML File===
<pre>
<?xml version="2.0" ?>

<Type>saved</Type>
<Name></Name>
<Description></Description>
<Shader>post</Shader>

<Terrain>
<Heightmap>[path here]</Heightmap>
//image is a 16-bit grayscale png
<ColorMap>[path here]</ColorMap>
//image is a tga
<WeightMap>[path here]</WeightMap>
//image is a tga that uses RBG and Black values to blend detailmaps
<DetailMaps> //used for tiling detail on the ground
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Sky>
<DomeTexture>Data/Textures/skies/FILE.tga</DomeTexture>
<SunAngularRad>0.123456</SunAngularRad> // Size of Sun in Radians?
<SunColorAngle>6.8534</SunColorAngle> // ??
<RayToSun r0="0.123456" r1="0.123456" r2="0.123456" />
<ExtraAO>0</ExtraAO>
</Sky>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

The xml contains references to a HeightMap, ColorMap, WeightMap, and multiple DetailMaps.

===Height Map===
{{stub}}
The Height Map is a 16-bit grayscale image, with the value of each pixel corresponding to an elevation in the terrain.

===Color Map===
{{stub}}
The Color Map maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

===Weight Map===
{{stub}}
The colors of the WeightMap is used to define which DetailMap to use on which part of the terrain.

===Detail Maps===
{{stub}}
DetailMaps are used to tile various objects across the terrain, for example normal maps that give the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

Overgrowth Levels

2015-02-13T18:38:54Z

Poddus: more xml parameters

Overgrowth Levels are composed of a collection of files. The main file is a .xml and has the following basic structure:

===XML File===
<pre>
<?xml version="2.0" ?>

<Type>saved</Type>
<Name></Name>
<Description></Description>
<Shader>post</Shader>

<Terrain>
<Heightmap>[path here]</Heightmap>
//image is a 16-bit grayscale png
<ColorMap>[path here]</ColorMap>
//image is a tga
<WeightMap>[path here]</WeightMap>
//image is a tga that uses RBG and Black values to blend detailmaps
<DetailMaps> //used for tiling detail on the ground
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Sky>
<DomeTexture>Data/Textures/skies/blue3.tga</DomeTexture>
<SunAngularRad>0.112145</SunAngularRad>
<SunColorAngle>6.8534</SunColorAngle>
<RayToSun r0="-0.018092" r1="0.749923" r2="0.661278" />
<ExtraAO>0</ExtraAO>
</Sky>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

The xml contains references to a HeightMap, ColorMap, WeightMap, and multiple DetailMaps.

===Height Map===
{{stub}}
The Height Map is a 16-bit grayscale image, with the value of each pixel corresponding to an elevation in the terrain.

===Color Map===
{{stub}}
The Color Map maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

===Weight Map===
{{stub}}
The colors of the WeightMap is used to define which DetailMap to use on which part of the terrain.

===Detail Maps===
{{stub}}
DetailMaps are used to tile various objects across the terrain, for example normal maps that give the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

Portal:Overgrowth

2015-02-13T07:37:15Z

Poddus: /* Phoenix Engine Documentation */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
* [[3D Objects]]
* [[Character Models]]
* [[Effects System]]
* [[Overgrowth Levels]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Custom Terrain]]

==Alpha Testing==
* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Overgrowth Levels

2015-02-13T07:36:50Z

Poddus: Created page with "Overgrowth Levels are composed of a collection of files. The main file is a .xml and has the following basic structure: ===XML File=== <pre> <Terrain> <Heightmap>[path here]..."

Overgrowth Levels are composed of a collection of files. The main file is a .xml and has the following basic structure:

===XML File===
<pre>
<Terrain>
<Heightmap>[path here]</Heightmap>
//image is a 16-bit grayscale png
<ColorMap>[path here]</ColorMap>
//image is a tga
<WeightMap>[path here]</WeightMap>
//image is a tga that uses RBG and Black values to blend detailmaps
<DetailMaps> //used for tiling detail on the ground
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
<DetailMap colorpath="[path here to image with color info]" normalpath="[path here to image with normal info]" materialpath="[path here -- to something in the material.xml format]" />
</DetailMaps>
<DetailObjects> //for grass and stuff
<DetailObject obj_path="Data/Objects/Plants/Groundcover/Grass/WildGrass.xml" weight_path="Data/Textures/Terrain/scrubby_hills/scrubby_hills_grass.png" normal_conform="0.900000" density="20.000000" min_embed="0.000000" max_embed="0.400000" min_scale="1.000000" max_scale="2.000000" view_distance="20.000000" jitter_degrees="10.000000" overbright="0.000000" />
</DetailObjects>
</Terrain>

<Objectives>[objective here]</Objectives>
//possible objectives: reach_a_trigger, reach_a_trigger_with_no_pursuers, collect
</pre>

The xml contains references to a HeightMap, ColorMap, WeightMap, and multiple DetailMaps.

===Height Map===
{{stub}}
The Height Map is a 16-bit grayscale image, with the value of each pixel corresponding to an elevation in the terrain.

===Color Map===
{{stub}}
The Color Map maps the color of each pixel to the color of a point on the terrain. This is used for rough texture, and can be used for example to make valleys green and mountain peaks grey.

===Weight Map===
{{stub}}
The colors of the WeightMap is used to define which DetailMap to use on which part of the terrain.

===Detail Maps===
{{stub}}
DetailMaps are used to tile various objects across the terrain, for example normal maps that give the impression of gravel, and the corresponding materialobject which generate a "gravel" sound when interacted with.

Portal:Overgrowth

2015-02-13T07:05:02Z

Poddus: reorganized tutorials

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
* [[3D Objects]]
* [[Character Models]]
* [[Effects System]]
* [[Level XML reference]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Custom Terrain]]

==Alpha Testing==
* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T07:03:40Z

Poddus:

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Effects System]]
* [[Level XML reference]]

==Modding Tutorials==
* [[Custom Terrain]]
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T06:59:47Z

Poddus: /* Engine Documentation & Modding */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Phoenix Engine Documentation ==
* [[Editor Interface]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Effects System]]
* [[Level XML reference]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T06:59:00Z

Poddus: /* Tutorials */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Engine Documentation & Modding ==
* [[Editor Interface]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Effects System]]
* [[Level XML reference]]

==Modding Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T06:57:39Z

Poddus: /* Engine Documentation & Modding */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Engine Documentation & Modding ==
* [[Editor Interface]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Effects System]]
* [[Level XML reference]]

==Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T06:57:01Z

Poddus: /* Modding */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Engine Documentation & Modding ==
* [[Editor Interface]]
* [[Phoenix Engine]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Level XML reference]]

==Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

User:Poddus

2015-02-13T06:54:40Z

Poddus: Created page with "hello world, it is I, the pod"

hello world, it is I, the pod

Control Reference

2015-02-13T06:52:18Z

Poddus: /* Translation */ rewording

This '''control reference''' page is a comprehensive list of all actions available in the [[Portal:Overgrowth|Overgrowth]] alpha. The main goal of this page is to detail all main functions and discrete maneuvers that can be executed. Please review this page with each alpha release.

=Player Controls=

These functions are used when controlling a Player Character.

'Cmd' refers to the '⌘' key on Macs, and the 'Ctrl' key on PCs.

==Character Movement==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Forward
| W || Moves player forward.
|-
! Backward
| S || Moves player backward.
|-
! Left
| A || Moves player left.
|-
! Right
| D || Moves player right.
|-
! Crouch
| Shift || Makes player crouch.
|-
! Roll
| Shift while Moving || Makes player roll along the ground, somersault while airborne, and regain control of its body when 'ragdolled.'
|-
! Jump
| Space || Makes player jump.
|-
! Wall Jump
| Space or Shift || Player jumps (space) or somersaults (shift) away from the wall.
|-
! Wall Run
| Hold space while running on a wall || Player runs up a wall when coming at it straight on; runs along a wall if coming at it from an angle.
|-
! Ledge Grab
| Hold right Mousebutton || Makes player grab horizontal ledges. Using the A and D keys will shimmy along the wall and even around corners. Using W will cause the character to pull himself up the ledge and releasing RMB allows the character to drop back to the ground. Note: The character must have free hands to ledge grab (e.g. weapons that cannot be sheathed will block ledge grabs)
|-
! Pick Up a Weapon/Item
| Hold Q || If close to a weapon or item, picks it up. Note: The character has a slight animation that must complete before you can release the Q key and still hold on to the weapon. Note 2: Weapons can even be picked up while rolling provided the character is close enough.
|-
! Drop a Weapon/Item
| Press Shift + Q || Drops weapon. Note: Character must be on the ground to drop weapons, applies to weapons in both hands.
|-
! Sheath/Unsheath a Weapon/Item
| Press E || Sheaths the item or weapon (only one-handed weapons can be sheathed). Note: Only applies to the characters primary hand. (e.g. a right-handed character with a weapon in both hands will only sheathe/unsheathe the right hand weapon unless the player changes the off-hand weapon onto his primary hand)
|-
! Switch hand holding Weapon
| Press B || Switches which hand the player holds the weapon with. Only weapons in the primary hand are used to fight. '''This has been changed as of a201''' to a spinning animation. Players can restore the switch weapons function by following instructions on the SPF: [http://forums.wolfire.com/viewtopic.php?f=13&t=18689#p198758 Here]
|}

==Attack and Defense==

Note: You need a live and hostile character less than around one meter away from you in order to be able to attack.
{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Punch/Kick
| Left mouse button || Context sensitive. Depends on whether or not the character is in motion and their distance. Exact attack may change depending on the controlled character.
|-
! Throw a Weapon
| Press Q || If close to an enemy, the weapon will be thrown. Larger weapons are less accurate; Knives and spears work best. If the enemy has detected you, he may catch and use the weapon.
|-
! Slash
| (While holding weapon) Left mouse button || Makes the player attack with a weapon in the hands.
|-
! Active Block
| Right mouse button || If you tap right mouse button as you're being attacked, you'll perform an active block that will leave your opponent open for a moment.
|-
! Active Dodge
| Movement Keys || If you move in a direction as you're being attacked, you'll perform an active dodge that will work against weapons while unarmed.
|-
! Judo Throw
| Hold right mouse button || If you press and hold right mouse button as you're being attacked, you'll perform a counter throw on your opponent, '''in a136 this was changed to only be possible after a successful active block'''.
|-
! Choke Hold
| Hold right mouse button || Choke holds are only possible if an enemy has not yet detected your presence. From a choke hold you can render the enemy unconscious with your hands, cut their throat with a weapon, or move them a short distance.
|-
! Throat Cut
| (While in choke hold) Press Left mouse button || Quickly cuts the throat of enemy in choke hold.
|-
! Leg Cannon
| (While airborne) Left mouse button || You'll kick with both legs towards the enemy's chest area, launching you towards the sky and your opponent to the ground.
|-
! Sweep
| (While crouching) Left mouse button || Makes the player sweep the feet of enemies.
|-
! Tech
| Tap Right Mouse Button as you are about to hit the ground || When you are about to hit the ground, recover quickly .
|-
|}

==Alpha Keys==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Restore characters
| X || Restores all characters to full health, wakes up any "unconscious" ones, and removes all blood from the environment.
|-
! Reload Level
| L || Restart the current level from the beginning.
|-
! Change character
| 1 to 8 || Changes the playable character into one of seven possible characters. The first two are different rabbits, the third one is a cat, the fourth is a rat, the fifth is a wolf, the sixth is a dog, and the seventh is Rabbot 2.0.
|-
! Active ragdoll
| Z || Puts all characters into ragdoll mode. At the moment, in Alpha 114, the ragdolls are the world famous Active ragdolls, which try to protect themselves from nearby objects. In previous alphas, Z button put all characters into normal ragdoll mode.
|-
! Pain ragdoll
| N || Makes the player and A.I fall to the ground in agony until you let go of the button. Added in Alpha 113, may disappear or change in future versions.
|-
! Floppy ragdoll
| M || Makes the player and A.I fall to the ground like normal until you let go. This shortcut was added in Alpha 114 and was 'Z' previously. It may be changed back to '>' in a future alpha.
|-
! Animal voice Test
| V || Plays a test voice phrase with lip sync. This shortcut was added in Alpha 117 and may disappear or change in future versions.
|-
! Combat mode toggle
| C || The A.I added with the editor will now attack any hostiles assigned to them.
|-
! Neck Wound
| , || The player suffers from a neck wound with blood gushing from it. Added in alpha 128 and may disappear in future versions. (press X or L to get up again)
|-
! Slo-Motion
| Tab || Slows down the whole game.
|-
! Freeze Scene
| Double-tap Tab || Freezes the game scene. '''Note''': The game must be unfrozen to change between controlling the player and editor mode.
|-
! Insta-kill
| F || Instantly kills nearby enemies with a death ray.
|}
<br>

=Editor Controls=

These functions are used when the [[Editor Interface]] is active.

'Cmd' refers to the '⌘' key on Macs, and the 'Ctrl' key on PCs.

See the [http://blog.wolfire.com/2009/03/map-editor-controls/ original blog post].

==Camera Movement==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Forward
| W || Moves camera forward.
|-
! Backward
| S || Moves camera backward.
|-
! Left
| A || Moves camera left.
|-
! Right
| D || Moves camera right.
|-
! Up
| Shift + W || Moves camera up.
|-
! Down
| Shift + S || Moves camera down.
|}

==Tool/Mode Selection==

{| class="wikitable"
|-
! Action !! Control !! Location !! Behavior
|-
! Omni Tool
| Click the Omni-Tool Button || Floating Toolbar || Allows simultaneous use of the Translate, Scale, and Rotate tools depending on context.
|-
! Translate
| Click 'translate' button || Floating Toolbar || Click and drag to translate objects
|-
! Scale
| Click 'scale' button || Floating Toolbar || Click and drag to perform a generic scale and right click and drag to perform a scale based on the plane the mouse is over with regard to the selected object.
|-
! Rotate
| Click 'rotate' button || Floating Toolbar || Click and drag to perform a generic rotation and right click and drag to perform a rotation only involving the plane the mouse is over with regard to the selected object.
|-
! Paintbrush
| Click 'paintbrush' button || Floating Toolbar || This tool appears to be broken in the current release (a201)
|-
! Game mode
| Click 'Rabbot' or press 8 || Home Tab || Switch to play mode. (from editor mode)
|-
! Editor mode
| press '9' or ESC || None || Back to editor mode. (from play mode)
|-
! In game webbrowser
| press 'F1' || None || Open the in game webbrowser.
|-
! Object browser
| Load Item Button || Home Tab || Opens the object browser. Click on an object and then left click in the editor to place it. Currently all "active" weapons have the prefix "weapon_" in the "o2" tab. To import items not shown click the folder icon on the object browser.
|-
! Decal Selection tool /decal editor mode
| press 'cmd-2' || None || To enter Decal selection/editor tool (This appears to have been removed in the current version, a201)
|-
|}

==Object Creation==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Load Object
| cmd-l (or click 'load' button) + left-mouse-click || Opens up a dialogue box in which the user may specify an xml file containing object data (anything in "./Data/Objects" or "./Data/Levels"). Places selected objects in scene, centered at mouse click.
|-
! Copy Objects
| cmd-c || Copies all selected objects (and their relative placement) into a copy buffer.
|-
! Paste Objects
| cmd-v || Adds to scene all objects in the copy buffer. Centers objects at mouse location.
|-
|}

==Object Selection==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Select single object
| double-left-click on object || Selects clicked on object and deselects all other objects. If the object is part of a group, the whole group is selected. Bounding box and slight glow indicate object is selected.
|-
! Toggle-select objects
| shift + double-left-click on objects || Toggles whether or not clicked on object is selected. Preserves other existing selections.
|-
! Box select objects
| left-click + right-click + drag, or left-click + 'b' + drag || Selects all objects whose centers lie within box drawn on screen. Deselects all other objects.
|-
! Box toggle-select objects
| shift + left-click + right-click + drag, or shift + left-click + 'b' + drag || Toggles selection state for all objects whose centers lie within box drawn on screen. Preserves other existing selections.
|-
! Select decal that is under another decal
| mouse wheel up/down || This onley works when you have atleast 2 decalsand one is on top of another. You need to select atleast 1 decal first and your mouse cursor needs to be on top of that one you want to select to do it
|-
! Select all
| cmd-a || Selects all objects.
|-
! Deselect all
| double-left-click away from all objects || Deselects all objects.
|}

==Change Object Properties==
{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Make player-controlled
| Shift+Cmd+P || Toggles whether a character is controlled by a human or by AI. A human-controlled character's spawn box has a green outline, an AI-controlled character's box has white outlines. If two characters are set to be human-controlled Overgrowth will start in split-screen mode the next time game-play is resumed from editor mode. The second player will be controllable via a USB controller.
|-
! Parameter Editor
| Press U || Allows you to modify character parameters such as team, attack speed, and handedness.
|-
! Palette Editor
| Press 'Cmd+P' || Allows you to modify character colors including but not limited to Leather, Fur, Pants, and Shirt. These color fields are different between the characters.
|-
|}

==Transformations==

For all transformations:

* In order to transform an object you must first select it.
* Hold ctrl to make movements snap by discrete increments.
* Hold alt to transform a clone of an object (or multiple objects), leaving the original object behind
* Left-click controls a 'generic' version of the transformation; right-click controls a version of the transformation contextually specific to the clicked on face. Holding shift locks the transformation to a single axis.
* Groups are transformed about the group center. Ungrouped objects, even if multiple are selected and transformed at once, are transformed about their own individual centers.

===Translation===

Set tool to 'translation', or set tool to 'omni tool' and hover mouse over central region of a bounding box face, or set tool to 'omni tool' and hold 't'.

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Camera relative
| left-click + drag || Translates clicked on object along plane parallel to the screen.
|-
! Locked to plane
| right-click + drag || Translates clicked on object along plane of clicked on face.
|-
! Locked to line
| shift + right-click + drag || Translates clicked on object along normal of clicked on face.
|-
! force decal(s) to map only one object/group
| hold i || selected decal will only map with that object that is directly underneath your mouse
|-
! force decal(s) to project only on selected objects
| press o || selected decal will only map with that object that is directly underneath your mouse
|-
! projection pox/angel
| press p || to make projection box for decal
|}

===Scale===

Set tool to 'scale', or set tool to 'omni tool' and hover mouse near bounding box vertices, or set tool to 'omni tool' and hold 'e'.

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! All dimensions
| left-click + drag || Scales clicked on object in all dimensions (x, y, and z) at once.
|-
! Locked to plane
| right-click + drag || Extends clicked on object along plane of clicked on face.
|-
! Locked to line
| shift + right-click + drag || Extrudes clicked on object along normal of clicked on face.
|}

===Mirror===

Just use the right-click scale tool, and scale down the object until it flips and its mirror image begins scaling up!

===Rotation===

Set tool to 'rotation', or set tool to 'omni tool' and hover mouse near bounding box edges, or set tool to 'omni tool' and hold 'r'.

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Free
| left-click + drag || Rotates clicked on object as if you are pushing the surface of a ball.
|-
! Locked to axis
| right-click + drag || Rotates clicked on object about normal of clicked on face.
|}

==Grouping==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Group objects
| cmd-g || All selected objects and groups are joined into a new group. Groups are hierarchical, so grouped groups are treated as subgroups. Objects in a group are selected as a unit and transform as a unit.
|-
! Ungroup objects
| cmd-shift-g || All selected groups are disbanded at their outermost level.
|}

==Undo/Redo==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Undo action
| cmd-z || Undoes the last completed action.
|-
! Redo action
| cmd-shift-z || Redoes the last undone action. Redo-able actions are cleared whenever the user completes a new action..
|}

==Object Removal==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Delete object
| delete or backspace || Deletes all selected objects
|}

==Saving==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Auto-save
| Automatic || Every 30 seconds or so the program automatically saves the entire level to the file "./Data/Levels/autosave.xml".
|-
! Save level
| cmd-s || Saves entire level to the same path as the level was opened from, overwriting the old level file.
|-
! Save selected objects
| cmd-shift-s || Saves-as all selected objects to a path specified by the user in a dialogue box.
|}

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Control Reference

2015-02-13T06:51:32Z

Poddus: /* Translation */ misspelled "onley"

This '''control reference''' page is a comprehensive list of all actions available in the [[Portal:Overgrowth|Overgrowth]] alpha. The main goal of this page is to detail all main functions and discrete maneuvers that can be executed. Please review this page with each alpha release.

=Player Controls=

These functions are used when controlling a Player Character.

'Cmd' refers to the '⌘' key on Macs, and the 'Ctrl' key on PCs.

==Character Movement==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Forward
| W || Moves player forward.
|-
! Backward
| S || Moves player backward.
|-
! Left
| A || Moves player left.
|-
! Right
| D || Moves player right.
|-
! Crouch
| Shift || Makes player crouch.
|-
! Roll
| Shift while Moving || Makes player roll along the ground, somersault while airborne, and regain control of its body when 'ragdolled.'
|-
! Jump
| Space || Makes player jump.
|-
! Wall Jump
| Space or Shift || Player jumps (space) or somersaults (shift) away from the wall.
|-
! Wall Run
| Hold space while running on a wall || Player runs up a wall when coming at it straight on; runs along a wall if coming at it from an angle.
|-
! Ledge Grab
| Hold right Mousebutton || Makes player grab horizontal ledges. Using the A and D keys will shimmy along the wall and even around corners. Using W will cause the character to pull himself up the ledge and releasing RMB allows the character to drop back to the ground. Note: The character must have free hands to ledge grab (e.g. weapons that cannot be sheathed will block ledge grabs)
|-
! Pick Up a Weapon/Item
| Hold Q || If close to a weapon or item, picks it up. Note: The character has a slight animation that must complete before you can release the Q key and still hold on to the weapon. Note 2: Weapons can even be picked up while rolling provided the character is close enough.
|-
! Drop a Weapon/Item
| Press Shift + Q || Drops weapon. Note: Character must be on the ground to drop weapons, applies to weapons in both hands.
|-
! Sheath/Unsheath a Weapon/Item
| Press E || Sheaths the item or weapon (only one-handed weapons can be sheathed). Note: Only applies to the characters primary hand. (e.g. a right-handed character with a weapon in both hands will only sheathe/unsheathe the right hand weapon unless the player changes the off-hand weapon onto his primary hand)
|-
! Switch hand holding Weapon
| Press B || Switches which hand the player holds the weapon with. Only weapons in the primary hand are used to fight. '''This has been changed as of a201''' to a spinning animation. Players can restore the switch weapons function by following instructions on the SPF: [http://forums.wolfire.com/viewtopic.php?f=13&t=18689#p198758 Here]
|}

==Attack and Defense==

Note: You need a live and hostile character less than around one meter away from you in order to be able to attack.
{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Punch/Kick
| Left mouse button || Context sensitive. Depends on whether or not the character is in motion and their distance. Exact attack may change depending on the controlled character.
|-
! Throw a Weapon
| Press Q || If close to an enemy, the weapon will be thrown. Larger weapons are less accurate; Knives and spears work best. If the enemy has detected you, he may catch and use the weapon.
|-
! Slash
| (While holding weapon) Left mouse button || Makes the player attack with a weapon in the hands.
|-
! Active Block
| Right mouse button || If you tap right mouse button as you're being attacked, you'll perform an active block that will leave your opponent open for a moment.
|-
! Active Dodge
| Movement Keys || If you move in a direction as you're being attacked, you'll perform an active dodge that will work against weapons while unarmed.
|-
! Judo Throw
| Hold right mouse button || If you press and hold right mouse button as you're being attacked, you'll perform a counter throw on your opponent, '''in a136 this was changed to only be possible after a successful active block'''.
|-
! Choke Hold
| Hold right mouse button || Choke holds are only possible if an enemy has not yet detected your presence. From a choke hold you can render the enemy unconscious with your hands, cut their throat with a weapon, or move them a short distance.
|-
! Throat Cut
| (While in choke hold) Press Left mouse button || Quickly cuts the throat of enemy in choke hold.
|-
! Leg Cannon
| (While airborne) Left mouse button || You'll kick with both legs towards the enemy's chest area, launching you towards the sky and your opponent to the ground.
|-
! Sweep
| (While crouching) Left mouse button || Makes the player sweep the feet of enemies.
|-
! Tech
| Tap Right Mouse Button as you are about to hit the ground || When you are about to hit the ground, recover quickly .
|-
|}

==Alpha Keys==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Restore characters
| X || Restores all characters to full health, wakes up any "unconscious" ones, and removes all blood from the environment.
|-
! Reload Level
| L || Restart the current level from the beginning.
|-
! Change character
| 1 to 8 || Changes the playable character into one of seven possible characters. The first two are different rabbits, the third one is a cat, the fourth is a rat, the fifth is a wolf, the sixth is a dog, and the seventh is Rabbot 2.0.
|-
! Active ragdoll
| Z || Puts all characters into ragdoll mode. At the moment, in Alpha 114, the ragdolls are the world famous Active ragdolls, which try to protect themselves from nearby objects. In previous alphas, Z button put all characters into normal ragdoll mode.
|-
! Pain ragdoll
| N || Makes the player and A.I fall to the ground in agony until you let go of the button. Added in Alpha 113, may disappear or change in future versions.
|-
! Floppy ragdoll
| M || Makes the player and A.I fall to the ground like normal until you let go. This shortcut was added in Alpha 114 and was 'Z' previously. It may be changed back to '>' in a future alpha.
|-
! Animal voice Test
| V || Plays a test voice phrase with lip sync. This shortcut was added in Alpha 117 and may disappear or change in future versions.
|-
! Combat mode toggle
| C || The A.I added with the editor will now attack any hostiles assigned to them.
|-
! Neck Wound
| , || The player suffers from a neck wound with blood gushing from it. Added in alpha 128 and may disappear in future versions. (press X or L to get up again)
|-
! Slo-Motion
| Tab || Slows down the whole game.
|-
! Freeze Scene
| Double-tap Tab || Freezes the game scene. '''Note''': The game must be unfrozen to change between controlling the player and editor mode.
|-
! Insta-kill
| F || Instantly kills nearby enemies with a death ray.
|}
<br>

=Editor Controls=

These functions are used when the [[Editor Interface]] is active.

'Cmd' refers to the '⌘' key on Macs, and the 'Ctrl' key on PCs.

See the [http://blog.wolfire.com/2009/03/map-editor-controls/ original blog post].

==Camera Movement==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Forward
| W || Moves camera forward.
|-
! Backward
| S || Moves camera backward.
|-
! Left
| A || Moves camera left.
|-
! Right
| D || Moves camera right.
|-
! Up
| Shift + W || Moves camera up.
|-
! Down
| Shift + S || Moves camera down.
|}

==Tool/Mode Selection==

{| class="wikitable"
|-
! Action !! Control !! Location !! Behavior
|-
! Omni Tool
| Click the Omni-Tool Button || Floating Toolbar || Allows simultaneous use of the Translate, Scale, and Rotate tools depending on context.
|-
! Translate
| Click 'translate' button || Floating Toolbar || Click and drag to translate objects
|-
! Scale
| Click 'scale' button || Floating Toolbar || Click and drag to perform a generic scale and right click and drag to perform a scale based on the plane the mouse is over with regard to the selected object.
|-
! Rotate
| Click 'rotate' button || Floating Toolbar || Click and drag to perform a generic rotation and right click and drag to perform a rotation only involving the plane the mouse is over with regard to the selected object.
|-
! Paintbrush
| Click 'paintbrush' button || Floating Toolbar || This tool appears to be broken in the current release (a201)
|-
! Game mode
| Click 'Rabbot' or press 8 || Home Tab || Switch to play mode. (from editor mode)
|-
! Editor mode
| press '9' or ESC || None || Back to editor mode. (from play mode)
|-
! In game webbrowser
| press 'F1' || None || Open the in game webbrowser.
|-
! Object browser
| Load Item Button || Home Tab || Opens the object browser. Click on an object and then left click in the editor to place it. Currently all "active" weapons have the prefix "weapon_" in the "o2" tab. To import items not shown click the folder icon on the object browser.
|-
! Decal Selection tool /decal editor mode
| press 'cmd-2' || None || To enter Decal selection/editor tool (This appears to have been removed in the current version, a201)
|-
|}

==Object Creation==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Load Object
| cmd-l (or click 'load' button) + left-mouse-click || Opens up a dialogue box in which the user may specify an xml file containing object data (anything in "./Data/Objects" or "./Data/Levels"). Places selected objects in scene, centered at mouse click.
|-
! Copy Objects
| cmd-c || Copies all selected objects (and their relative placement) into a copy buffer.
|-
! Paste Objects
| cmd-v || Adds to scene all objects in the copy buffer. Centers objects at mouse location.
|-
|}

==Object Selection==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Select single object
| double-left-click on object || Selects clicked on object and deselects all other objects. If the object is part of a group, the whole group is selected. Bounding box and slight glow indicate object is selected.
|-
! Toggle-select objects
| shift + double-left-click on objects || Toggles whether or not clicked on object is selected. Preserves other existing selections.
|-
! Box select objects
| left-click + right-click + drag, or left-click + 'b' + drag || Selects all objects whose centers lie within box drawn on screen. Deselects all other objects.
|-
! Box toggle-select objects
| shift + left-click + right-click + drag, or shift + left-click + 'b' + drag || Toggles selection state for all objects whose centers lie within box drawn on screen. Preserves other existing selections.
|-
! Select decal that is under another decal
| mouse wheel up/down || This onley works when you have atleast 2 decalsand one is on top of another. You need to select atleast 1 decal first and your mouse cursor needs to be on top of that one you want to select to do it
|-
! Select all
| cmd-a || Selects all objects.
|-
! Deselect all
| double-left-click away from all objects || Deselects all objects.
|}

==Change Object Properties==
{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Make player-controlled
| Shift+Cmd+P || Toggles whether a character is controlled by a human or by AI. A human-controlled character's spawn box has a green outline, an AI-controlled character's box has white outlines. If two characters are set to be human-controlled Overgrowth will start in split-screen mode the next time game-play is resumed from editor mode. The second player will be controllable via a USB controller.
|-
! Parameter Editor
| Press U || Allows you to modify character parameters such as team, attack speed, and handedness.
|-
! Palette Editor
| Press 'Cmd+P' || Allows you to modify character colors including but not limited to Leather, Fur, Pants, and Shirt. These color fields are different between the characters.
|-
|}

==Transformations==

For all transformations:

* In order to transform an object you must first select it.
* Hold ctrl to make movements snap by discrete increments.
* Hold alt to transform a clone of an object (or multiple objects), leaving the original object behind
* Left-click controls a 'generic' version of the transformation; right-click controls a version of the transformation contextually specific to the clicked on face. Holding shift locks the transformation to a single axis.
* Groups are transformed about the group center. Ungrouped objects, even if multiple are selected and transformed at once, are transformed about their own individual centers.

===Translation===

Set tool to 'translation', or set tool to 'omni tool' and hover mouse over central region of a bounding box face, or set tool to 'omni tool' and hold 't'.

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Camera relative
| left-click + drag || Translates clicked on object along plane parallel to the screen.
|-
! Locked to plane
| right-click + drag || Translates clicked on object along plane of clicked on face.
|-
! Locked to line
| shift + right-click + drag || Translates clicked on object along normal of clicked on face.
|-
! force decal(s) to map only one object/group
| hold i || selected decal will only map with that object that is directly underneath your mouse
|-
! force decal(s) to project only those object(s) that you want them to
| press o || selected decal will only map with that object that is directly underneath your mouse
|-
! projection pox/angel
| press p || to make projection box for decal
|}

===Scale===

Set tool to 'scale', or set tool to 'omni tool' and hover mouse near bounding box vertices, or set tool to 'omni tool' and hold 'e'.

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! All dimensions
| left-click + drag || Scales clicked on object in all dimensions (x, y, and z) at once.
|-
! Locked to plane
| right-click + drag || Extends clicked on object along plane of clicked on face.
|-
! Locked to line
| shift + right-click + drag || Extrudes clicked on object along normal of clicked on face.
|}

===Mirror===

Just use the right-click scale tool, and scale down the object until it flips and its mirror image begins scaling up!

===Rotation===

Set tool to 'rotation', or set tool to 'omni tool' and hover mouse near bounding box edges, or set tool to 'omni tool' and hold 'r'.

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Free
| left-click + drag || Rotates clicked on object as if you are pushing the surface of a ball.
|-
! Locked to axis
| right-click + drag || Rotates clicked on object about normal of clicked on face.
|}

==Grouping==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Group objects
| cmd-g || All selected objects and groups are joined into a new group. Groups are hierarchical, so grouped groups are treated as subgroups. Objects in a group are selected as a unit and transform as a unit.
|-
! Ungroup objects
| cmd-shift-g || All selected groups are disbanded at their outermost level.
|}

==Undo/Redo==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Undo action
| cmd-z || Undoes the last completed action.
|-
! Redo action
| cmd-shift-z || Redoes the last undone action. Redo-able actions are cleared whenever the user completes a new action..
|}

==Object Removal==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Delete object
| delete or backspace || Deletes all selected objects
|}

==Saving==

{| class="wikitable"
|-
! Action !! Control !! Behavior
|-
! Auto-save
| Automatic || Every 30 seconds or so the program automatically saves the entire level to the file "./Data/Levels/autosave.xml".
|-
! Save level
| cmd-s || Saves entire level to the same path as the level was opened from, overwriting the old level file.
|-
! Save selected objects
| cmd-shift-s || Saves-as all selected objects to a path specified by the user in a dialogue box.
|}

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

Configuring Overgrowth

2015-02-13T06:50:28Z

Poddus: /* Settings */ changed tablestyle

Currently (as of a209), it is possible to edit many settings in game. However, to access the settings, you need to be in the level editor. Open a level and press the Escape Key. This will bring you into the Level Editor. From here, press the Escape Key once more to access a menu with a "Settings" option. From there you can change thing such as Screen Resolution, Controller Setup, etc.

If the game does not open, or it is not possible to access the settings as described above, users may adjust their configuration by modifying their '''config.txt''' file. The file is a plain text file that is readable by any normal text editor (such as TextEdit for Mac or Notepad for Windows).

'''Note''': There is now a community made tool available, the [http://forums.wolfire.com/viewtopic.php?f=13&t=14201 SUMLauncher], which includes a config editor.

==Mac Location==
<code>Macintosh HD/Users/~/Library/Application Support/Overgrowth/Data/config.txt</code>

where ~ is your username.

'''Note:''' If you are using Lion, your library folder is hidden by default... in the finder, click the "Go" menu, then Press Option, and Library will appear in the list.

Alternatively you can find out how to unhide your Library folder permanently [http://gothick.org.uk/2011/07/19/revealing-lions-hidden-library-folder/| here].

==Windows Location==
<code>My Documents\Wolfire\Overgrowth\Data\config.txt</code>

'''Note:''' NOT Program Files\Wolfire\Overgrowth\Data!

==Linux Location==
<code>~/.local/share/Overgrowth/Data/config.txt</code>

The configuration file will be created when Overgrowth is started for the first time.

==Settings==

{| class="wikitable"
|-
! Setting !! Default Value !! Description
|-
! screenwidth
| 800 || The game's horizontal resolution.
|-
! screenheight
| 600 || The game's vertical resolution.
|-
! fullscreen
| false || Determines whether to run in full screen or windowed mode.
|-
! vsync
| false || Limits the framerate to match the user's monitor refresh rate (smooths out the framerate).
|-
! multisample
| 0 || Determines the level of anti-aliasing (smooths out jagged edges, at the cost of performance).
|-
! anisotropy
| 0 || Determines the level of anisotropic filtering (increases the quality of textures drawn far away, at the cost of performance).
|-
! post_effects
| false || Determines whether to display post effects.
|-
! shaders
| true || Determines whether to use shaders.
|-
! texture_reduce
| 1 || Determines the level to which the texture resolutions should be reduced (higher numbers will cause blurriness, but increase performance).
|-
! gamma_correct
| true || Determines whether to auto-correct gamma levels.
|-
! fps_label
| false || Determines whether to display the current fps (frames per second) on screen.
|-
! sound_label
| false || Determines whether to display all active sounds on screen.
|-
! visible_raycasts
| false || Determines whether to display lines representing all AIs' visibility.
|-
! visible_sound_spheres
| false || Determines whether to display spheres representing the distance sounds travel (such as running).
|-
! editor_mode
| false || Determines whether to start the game in player mode (false) or editor mode (true).
|-
! invert_y_look
| false || Determines whether to invert the y-axis controls (looking up/down).
|-
! music
| true || Determines whether the in-game music is enabled.
|-
! media_mode
| false || Determines whether to disable the in-game interface.
|-
! baked_shadows
| true || Determines whether to use the pre-baked shadows (true) or cascaded shadow maps (false).
|-
! debug_key_presses
| false || Determines whether to enable the use of debug keys.
|-
! auto_camera
| false || Determines whether to have the camera automatically return to a position behind the player.
|-
! key[quit]
| esc || Exits from player mode into editor mode, and opens a menu allowing the user to return to the main menu.
|-
! key[slow]
| tab || Toggles slow motion.
|-
! key[fast]
| \ ||
|-
! key[crouch]
| lshift || Causes the player to crouch.
|-
! key[jump]
| space || Causes the player to jump.
|-
! key[screenshot]
| f7 || Captures a screenshot (saved in ''/Data/Screenshots/'')
|-
! key[console]
| ` || Toggles the game console.
|-
! key[left]
| a || Causes the player to move to the left.
|-
! key[right]
| d || Causes the player to move to the right.
|-
! key[up]
| w || Causes the player to move forward.
|-
! key[down]
| s || Causes the player to move backward.
|-
! key[item]
| e || Causes the player to put a weapon to your waist or into a scabbard on your waist.
|-
! key[drop]
| q || Causes the player to pick up the weapon, combination of left shift and q will drop an item.
|-
! key[chat]
| t || Brings up the chat interface.
|-
! key[rclick]
| rshift || Alternate key used for "right clicking".
|-
! xbox_look_sensitivity
| 1.5 || Sensitivity of an attached Xbox controller.
|-
! xbox[jump]
| RB || Xbox jump button.
|-
! xbox[crouch]
| LB || Xbox crouch button.
|-
! xbox[attack]
| RT || Xbox attack button.
|-
! xbox[grab]
| LT || Xbox grab button.
|-
! xbox[item]
| A || Xbox item button.
|-
! xbox[drop]
| X || Xbox drop button.
|-
! controller[movex]
| axis1 || Controller axis mapped for movement along the x-axis.
|-
! controller[movey]
| axis2 || Controller axis mapped for movement along the y-axis.
|-
! controller[lookx]
| axis5 || Controller axis mapped for looking along the x-axis.
|-
! controller[looky]
| axis4 || Controller axis mapped for looking along the y-axis.
|-
! controller[jump]
| button6 || Controller jump button.
|-
! controller[crouch]
| button5 || Controller crouch button.
|-
! controller[item]
| button1 || Controller item button.
|-
! controller[drop]
| button3 || Controller drop button.
|-
! controller[attack]
| axis3<-0.5 || Controller attack "button" (default mapping is set to an axis being less than half full in a negative direction).
|-
! controller[grab]
| axis3>0.5 || Controller grab "button" (default mapping is set to an axis being greater than half full in a positive direction).
|-
! blood
|1 || Disable or enable blood
|}

[[Category: Tutorials]]
[[Category: Modding]]
[[Category: Overgrowth]]

==Controller Setup==

Since alpha 150, external controller options have been added to the '''config.txt''' file. The following guide will help you configure your controller to properly work with Overgrowth.

Note: Currently the guide only targets Windows 7 users. Mac users may refer to [http://forums.wolfire.com/viewtopic.php?f=13&t=12631 Anton's guide].

First, make sure your controller is plugged in to your computer.

Next, open the start menu and click on ''Control Panel'' (located on the right side). Once opened, make sure the view is set to ''Large Icons'' (switchable in the upper right corner). Select ''Devices and Printers''.

You should see your controller listed under ''Devices''. Right click it, and select ''Game Controller Settings''. The ''Game Controllers'' window will appear. Make sure your controller is selected, then click on ''Properties''.

Once again, a new window should appear - make sure that the view is set to the ''Test'' tab. In this view, you will be able to determine which physical button is mapped to each virtual button. Play around with your controller to confirm that everything is working properly, and take note of the button mappings.

Now navigate to and open up your '''config.txt''' file (as described above). Rearrange the mappings in the file to match your desired controller setup.

Once you have everything modified, save the '''config.txt''' file and launch Overgrowth in order to test the new configuration.

Portal:Overgrowth

2015-02-13T06:19:40Z

Poddus:

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development of Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Modding ==
* [[Editor Interface]]
* [[Phoenix Engine]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Level XML reference]]

==Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T03:56:03Z

Poddus: added a tutorials section

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development for Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Modding ==
* [[Editor Interface]]
* [[Phoenix Engine]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Custom Decals]]
* [[Level XML reference]]

==Tutorials==
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-13T03:49:29Z

Poddus: /* Modding */ added link to Character Models

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development for Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Modding ==
* [[Editor Interface]]
* [[Phoenix Engine]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Character Models]]
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Level XML reference]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Custom Characters

2015-02-13T03:48:51Z

Poddus: Created page with "''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=24827 this] forum post by member Markuss.'' There are two linked .zip file attached to the forum post. they can be fou..."

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=24827 this] forum post by member Markuss.''

There are two linked .zip file attached to the forum post. they can be found here:

http://www.markstockton.com/misc/Guide2/ExampleMan.zip

http://www.markstockton.com/misc/Guide2/Blender-Overgrowth-Win.zip

This guide assumes you are familiar with [[3D Objects]].

==Basics==

Characters in overgrowth consist of 4 .XML files, an .OBJ file and a .PHXBN file. The .PHXBN file is created in Blender and contains the skeleton and skin weighting info. The XML files just contain links to themselves and other files. They contain the following:

1 - Links to the .OBJ and .PHXBN files that the engine needs to rig the character.
<pre>
<?xml version="1.0" ?>
<rig bone_path = "Data/Custom/Markuss/ExampleMan/Models/ExampleMan.phxbn"
model_path = "Data/Custom/Markuss/ExampleMan/Models/ExampleMan.obj"/>
</pre>

2 - A regular object file as described in the [[3D_Objects#Basics | 3D reference guide]].
<pre>
<?xml version="1.0"?>
<Object>
<Model>Data/Custom/Markuss/ExampleMan/Models/ExampleMan.obj</Model>
<ColorMap>Data/Custom/Markuss/ExampleMan/Textures/ExampleMan_Color.TGA</ColorMap>
<NormalMap>Data/Custom/Markuss/ExampleMan/Textures/ExampleMan_Norm.TGA</NormalMap>
<ShaderName>cubemapobjchar</ShaderName>
</Object>
</pre>

3 - Links to the first 2 files, and a load of animation files for each action.
<pre>
<?xml version="1.0" ?>
<character>
<appearance obj_path = "Data/Custom/Markuss/ExampleMan/XMLFiles/ExampleMan_Object.xml"
skeleton = "Data/Custom/Markuss/ExampleMan/XMLFiles/ExampleMan_RigFiles.xml"/>
<animations idle = "Data/Animations/r_idle2.xml"
jump = "Data/Animations/r_jump.xml"
roll = "Data/Animations/r_roll.xml"
movement = "Data/Animations/r_movement.xml"
wall = "Data/Animations/r_wall.xml"
ledge = "Data/Animations/r_ledge.anm"
medrightblock = "Data/Animations/r_activeblockmedright.anm"
medleftblock = "Data/Animations/r_activeblockmedleft.anm"
highrightblock = "Data/Animations/r_activeblockhighright.anm"
highleftblock = "Data/Animations/r_activeblockhighleft.anm"
lowrightblock = "Data/Animations/r_activeblocklowright.anm"
lowleftblock = "Data/Animations/r_activeblocklowleft.anm"
blockflinch = "Data/Animations/r_activeblockflinch.anm"/>
<attacks moving_close = "Data/Attacks/haymaker.xml"
stationary_close = "Data/Attacks/thrustpunch.xml"
moving = "Data/Attacks/spinkick.xml"
stationary = "Data/Attacks/frontkick.xml"
moving_low = "Data/Attacks/soccerkick.xml"
low = "Data/Attacks/sweep.xml"
air = "Data/Attacks/legcannon.xml" />
</character>
</pre>

4 - Links to the third file and an AI script, this is the file you choose when loading a character.
<pre>
<?xml version="1.0" ?>
<Actor>
<Character>Data/Custom/Markuss/ExampleMan/XMLFiles/ExampleMan_AnimList.xml</Character>
<ControlScript>enemycontrol.as</ControlScript>
</Actor>
</pre>

==Model and Texture Requirements==
Models have to be triangles only and centered to the middle of the scene with location, rotation and scale set to zero. It should loosely match the pose and proportions of the overgrowth characters, you can use the following file:

: Data/Models/Characters/Rabbit/rabbit.obj
<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Character Model Faces Z-axis

''NOTE: If your character is not symmetrical, ignore the center line in the geometry, it has to be the ‘true’ the center of the model, otherwise you will get errors''

The normal map has to be object-space, there is currently no character shader that supports tangent-space. The normal map's alpha channel controls a side-glow effect when the sun is behind the character, black = no effect. It is possible to use a blank (blue) normal map with the Cubemap shader, the character is rendered brighter, but it is acceptable, most community characters are like this.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
This is what a Blank/Flat object-space normal map looks like.

'''Color Space''':

Blue = light from top

Red = light from right

Green = light from front

3D Objects

2015-02-13T03:23:25Z

Poddus: /* Tags */

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=11227 this] forum post by member Markuss.''
There is a linked .zip file attached to the forum post. it can be found here:
http://www.markstockton.com/misc/Guide/Examples.zip

==Basics==
In Overgrowth 3D models use the [http://en.wikipedia.org/wiki/Wavefront_.obj_file .OBJ format] but the material counter-part (.MTL) is not used, instead an “object properties file” stores links to model and texture files as well as some other information. This is the file you choose when loading an object, it uses the .XML format and can be read/created in any text editor:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Markuss/Examples/Models/SimpleObject.obj</Model>
<ColorMap>Data/Custom/Markuss/Examples/Textures/SimpleObject_Color.tga</ColorMap>
<NormalMap>Data/Custom/Markuss/Examples/Textures/Blank_Norm.tga</NormalMap>
<ShaderName>cubemap</ShaderName>
<MaterialPath>Data/Materials/default.xml</MaterialPath>
</Object>
</pre>

===Tags===
'''<Model>''' - links to the model file (.OBJ)

'''<ColorMap>''' - links to the color texture file (.TGA .TIF)

'''<NormalMap>''' - links to the [http://en.wikipedia.org/wiki/Normal_mapping normal map] texture file (.TGA .TIF)

'''<ShaderName>''' - refers to internal shader file (.FRAG .VERT, in Data/GLSL/), defines how object is rendered.

'''<MaterialPath>''' - links to internal material file (.XML), defines sound made by hitting the object.

====Additional tags====

'''<flags no_collision>''' - turns physics calculations on/off, true = off.

''NOTE:''

''“<ShaderName>” used to be “<ShaderPath>” and contained the full link instead of just the file name, expect similar update for “<MaterialPath>”.''

''Look at the example plant object for usage of the <flags no_collision> tag.''

===Model and Texture Requirements===

Models need to be constructed from squares and triangles only, so textures need to be square and not just “powers of 2”. (512x512 or 1024x1024 not 512x1024 or 1024x2048)

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Simple object and texture UV layout

==Alternative object System==
The engine automatically generates a simplified physics object and uses the object’s UV layout to place the shadow maps, these can be overridden by providing alternative .OBJ files that contain the desired information. These objects are placed in the same folder and share the same name as the original .OBJ file with a suffix to tell the engine what data they hold:

===Suffixes===
'''YourObject_COL.obj''' - contains simplified geometry for physics calculations

'''YourObject.obj_UV2''' - contains same object but with no overlapping UVs

'''YourObjectHULL.obj''' - same as _COL but has extra info, used with weapons

''NOTE:''

''The suffix formats are inconsistent, _COL is placed before the file extension while _UV2 is place after, and HULL doesn’t even have an underscore to separate it from the file name!''

===Physics objects (_COL)===
Simplified geometry such as boxes an cylinders which are used for collision detection, they are aligned to your object based on “relative position” in your 3D program so you should place the physics mesh on top of your render mesh upon export:

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Physics mesh should be placed on top of the render mesh

===Shadow UV objects (_UV2)===
These objects tell the engine how to place the shadow map on the rendered object if the original UV layout isn’t appropriate, the shadow maps require UV layouts with no over-lapping faces, this can usually be achieved using the “automatic unwrapping” tools found in most 3D applications.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Color texture UVs left, shadow UVs right, each face needs its own UV space.

===Hull objects (HULL)===
They are very similar to physics objects but are used for items and weapons, the only difference is that they contain a free-floating triangle which defines the object’s center of gravity.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Hull objects are placed over render mesh like physics objects.

==Items and Weapons==

Items and Weapons are aligned to the character based on their position relative to the center of the scene in your 3D app, you should load the .obj files of the example objects for reference. To make an object “pick-up-able” you need another .XML file that you load in place of the regular object properties file, it stores the info needed that is not defined in the regular object properties file:

<pre>
<?xml version="1.0" ?>
<item>
<type>weapon</type>
<appearance obj_path = "Data/Custom/Markuss/Examples/1-Handed.xml"/>
<grip ik_attach = "rightarm"
anim = "Data/Animations/r_dogweapongrip.anm"/>
<physics mass = "1 kg"/>
</item>
</pre>
Item properties file

===Tags===
'''<type>''' - defines what type of item the object is.

'''<appearance obj_path>''' - links to the regular object definition file.

'''<grip ik_attach anim>''' - defines what bone the object is attached to, links to an animation file.

'''<physics mass>''' - changes the pitch(?) of the sound made by the object hitting things.

'''<anim_override idle>''' - overrides the idle animation of a character holding the item.

''NOTE:''

''Not sure what the animation file in <grip ik_attach anim> does.''

''<anim_override idle> is only used for 2-handed weapons at the moment.''

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Example weapons, handles show the location of characters hands

''NOTE:''

''There is a bug that makes weapons turn invisible when loading levels with them already in it, you can fix this by having the “regular-object" version somewhere in the level as well.''

==Shaders==
'''Cubemap''' – closest thing to a “standard shader”, it has a cube-map based on the sky texture and a specular shine, the visibility of the cube map and shine is controlled with color texture’s alpha channel, white = fully reflective and shiny. Similarly, the normal-map texture’s alpha channel controls where color tinting happens, white = full effect. The cube map’s visibility is inversely affected by the brightness of the texture, you should make the color texture close to black for materials that are reflective such as chrome and glass.

'''CubemapObj''' - same as Cubemap but uses object-space normal maps instead of tangent space.

'''CubemapItem''' - same as Cubemap but the shine is sharper.

'''CubemapObjItem''' - object-space version of CubemapItem.

'''CubemapAlpha''' - has transparency controlled by the color texture’s alpha channel, cube map and shine are controlled by the normal-map texture’s alpha channel instead. CubemapAlpha has depth sorting issues with other transparent objects, enabling anti-aliasing fixes this somewhat.

'''CubemapObjChar''' - used for characters, shine is sharp, uses object space normals. There is no tangent-space version of CubemapObjChar and no object-space version of CubemapAlpha at the moment.

'''Plant''' - has transparency like CubemapAlpha but no cube map/shine. Translucency texture increases the brightness of the object while ignoring diffuse lighting, black = no effect. Wind texture defines intensity of a vertex ripple effect, black = no ripple. Both textures are linked in the object definition file using the <TranslucencyMap> and <WindMap> tags.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
CubemapAlpha

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Translucency (Plant Shader)

==Materials==

These are the sounds made and the particles emitted when you hit an object. I’ve set up some tiles for you to walk on to preview each material, here is a list:

: Cloth_Fabric
: Cloth_Leather
: Default
: Dirt
: DirtyRock
: Drygrass
: Grass
: Gravel
: Rock
: Rocks
: Sand
: Snow
: Wood

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Sound tiles

Note that some of these don’t emit particles.

3D Objects

2015-02-13T03:23:12Z

Poddus: /* Tags */ added path for shaders

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=11227 this] forum post by member Markuss.''
There is a linked .zip file attached to the forum post. it can be found here:
http://www.markstockton.com/misc/Guide/Examples.zip

==Basics==
In Overgrowth 3D models use the [http://en.wikipedia.org/wiki/Wavefront_.obj_file .OBJ format] but the material counter-part (.MTL) is not used, instead an “object properties file” stores links to model and texture files as well as some other information. This is the file you choose when loading an object, it uses the .XML format and can be read/created in any text editor:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Markuss/Examples/Models/SimpleObject.obj</Model>
<ColorMap>Data/Custom/Markuss/Examples/Textures/SimpleObject_Color.tga</ColorMap>
<NormalMap>Data/Custom/Markuss/Examples/Textures/Blank_Norm.tga</NormalMap>
<ShaderName>cubemap</ShaderName>
<MaterialPath>Data/Materials/default.xml</MaterialPath>
</Object>
</pre>

===Tags===
'''<Model>''' - links to the model file (.OBJ)

'''<ColorMap>''' - links to the color texture file (.TGA .TIF)

'''<NormalMap>''' - links to the [http://en.wikipedia.org/wiki/Normal_mapping normal map] texture file (.TGA .TIF)

'''<ShaderName>''' - refers to internal shader file (.FRAG .VERT, in /Data/GLSL/), defines how object is rendered.

'''<MaterialPath>''' - links to internal material file (.XML), defines sound made by hitting the object.

====Additional tags====

'''<flags no_collision>''' - turns physics calculations on/off, true = off.

''NOTE:''

''“<ShaderName>” used to be “<ShaderPath>” and contained the full link instead of just the file name, expect similar update for “<MaterialPath>”.''

''Look at the example plant object for usage of the <flags no_collision> tag.''

===Model and Texture Requirements===

Models need to be constructed from squares and triangles only, so textures need to be square and not just “powers of 2”. (512x512 or 1024x1024 not 512x1024 or 1024x2048)

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Simple object and texture UV layout

==Alternative object System==
The engine automatically generates a simplified physics object and uses the object’s UV layout to place the shadow maps, these can be overridden by providing alternative .OBJ files that contain the desired information. These objects are placed in the same folder and share the same name as the original .OBJ file with a suffix to tell the engine what data they hold:

===Suffixes===
'''YourObject_COL.obj''' - contains simplified geometry for physics calculations

'''YourObject.obj_UV2''' - contains same object but with no overlapping UVs

'''YourObjectHULL.obj''' - same as _COL but has extra info, used with weapons

''NOTE:''

''The suffix formats are inconsistent, _COL is placed before the file extension while _UV2 is place after, and HULL doesn’t even have an underscore to separate it from the file name!''

===Physics objects (_COL)===
Simplified geometry such as boxes an cylinders which are used for collision detection, they are aligned to your object based on “relative position” in your 3D program so you should place the physics mesh on top of your render mesh upon export:

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Physics mesh should be placed on top of the render mesh

===Shadow UV objects (_UV2)===
These objects tell the engine how to place the shadow map on the rendered object if the original UV layout isn’t appropriate, the shadow maps require UV layouts with no over-lapping faces, this can usually be achieved using the “automatic unwrapping” tools found in most 3D applications.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Color texture UVs left, shadow UVs right, each face needs its own UV space.

===Hull objects (HULL)===
They are very similar to physics objects but are used for items and weapons, the only difference is that they contain a free-floating triangle which defines the object’s center of gravity.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Hull objects are placed over render mesh like physics objects.

==Items and Weapons==

Items and Weapons are aligned to the character based on their position relative to the center of the scene in your 3D app, you should load the .obj files of the example objects for reference. To make an object “pick-up-able” you need another .XML file that you load in place of the regular object properties file, it stores the info needed that is not defined in the regular object properties file:

<pre>
<?xml version="1.0" ?>
<item>
<type>weapon</type>
<appearance obj_path = "Data/Custom/Markuss/Examples/1-Handed.xml"/>
<grip ik_attach = "rightarm"
anim = "Data/Animations/r_dogweapongrip.anm"/>
<physics mass = "1 kg"/>
</item>
</pre>
Item properties file

===Tags===
'''<type>''' - defines what type of item the object is.

'''<appearance obj_path>''' - links to the regular object definition file.

'''<grip ik_attach anim>''' - defines what bone the object is attached to, links to an animation file.

'''<physics mass>''' - changes the pitch(?) of the sound made by the object hitting things.

'''<anim_override idle>''' - overrides the idle animation of a character holding the item.

''NOTE:''

''Not sure what the animation file in <grip ik_attach anim> does.''

''<anim_override idle> is only used for 2-handed weapons at the moment.''

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Example weapons, handles show the location of characters hands

''NOTE:''

''There is a bug that makes weapons turn invisible when loading levels with them already in it, you can fix this by having the “regular-object" version somewhere in the level as well.''

==Shaders==
'''Cubemap''' – closest thing to a “standard shader”, it has a cube-map based on the sky texture and a specular shine, the visibility of the cube map and shine is controlled with color texture’s alpha channel, white = fully reflective and shiny. Similarly, the normal-map texture’s alpha channel controls where color tinting happens, white = full effect. The cube map’s visibility is inversely affected by the brightness of the texture, you should make the color texture close to black for materials that are reflective such as chrome and glass.

'''CubemapObj''' - same as Cubemap but uses object-space normal maps instead of tangent space.

'''CubemapItem''' - same as Cubemap but the shine is sharper.

'''CubemapObjItem''' - object-space version of CubemapItem.

'''CubemapAlpha''' - has transparency controlled by the color texture’s alpha channel, cube map and shine are controlled by the normal-map texture’s alpha channel instead. CubemapAlpha has depth sorting issues with other transparent objects, enabling anti-aliasing fixes this somewhat.

'''CubemapObjChar''' - used for characters, shine is sharp, uses object space normals. There is no tangent-space version of CubemapObjChar and no object-space version of CubemapAlpha at the moment.

'''Plant''' - has transparency like CubemapAlpha but no cube map/shine. Translucency texture increases the brightness of the object while ignoring diffuse lighting, black = no effect. Wind texture defines intensity of a vertex ripple effect, black = no ripple. Both textures are linked in the object definition file using the <TranslucencyMap> and <WindMap> tags.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
CubemapAlpha

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Translucency (Plant Shader)

==Materials==

These are the sounds made and the particles emitted when you hit an object. I’ve set up some tiles for you to walk on to preview each material, here is a list:

: Cloth_Fabric
: Cloth_Leather
: Default
: Dirt
: DirtyRock
: Drygrass
: Grass
: Gravel
: Rock
: Rocks
: Sand
: Snow
: Wood

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Sound tiles

Note that some of these don’t emit particles.

3D Objects

2015-02-13T02:59:11Z

Poddus: /* Basics */

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=11227 this] forum post by member Markuss.''
There is a linked .zip file attached to the forum post. it can be found here:
http://www.markstockton.com/misc/Guide/Examples.zip

==Basics==
In Overgrowth 3D models use the [http://en.wikipedia.org/wiki/Wavefront_.obj_file .OBJ format] but the material counter-part (.MTL) is not used, instead an “object properties file” stores links to model and texture files as well as some other information. This is the file you choose when loading an object, it uses the .XML format and can be read/created in any text editor:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Markuss/Examples/Models/SimpleObject.obj</Model>
<ColorMap>Data/Custom/Markuss/Examples/Textures/SimpleObject_Color.tga</ColorMap>
<NormalMap>Data/Custom/Markuss/Examples/Textures/Blank_Norm.tga</NormalMap>
<ShaderName>cubemap</ShaderName>
<MaterialPath>Data/Materials/default.xml</MaterialPath>
</Object>
</pre>

===Tags===
'''<Model>''' - links to the model file (.OBJ)

'''<ColorMap>''' - links to the color texture file (.TGA .TIF)

'''<NormalMap>''' - links to the [http://en.wikipedia.org/wiki/Normal_mapping normal map] texture file (.TGA .TIF)

'''<ShaderName>''' - refers to internal shader file (.FRAG .VERT), defines how object is rendered.

'''<MaterialPath>''' - links to internal material file (.XML), defines sound made by hitting the object.

====Additional tags====

'''<flags no_collision>''' - turns physics calculations on/off, true = off.

''NOTE:''

''“<ShaderName>” used to be “<ShaderPath>” and contained the full link instead of just the file name, expect similar update for “<MaterialPath>”.''

''Look at the example plant object for usage of the <flags no_collision> tag.''

===Model and Texture Requirements===

Models need to be constructed from squares and triangles only, so textures need to be square and not just “powers of 2”. (512x512 or 1024x1024 not 512x1024 or 1024x2048)

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Simple object and texture UV layout

==Alternative object System==
The engine automatically generates a simplified physics object and uses the object’s UV layout to place the shadow maps, these can be overridden by providing alternative .OBJ files that contain the desired information. These objects are placed in the same folder and share the same name as the original .OBJ file with a suffix to tell the engine what data they hold:

===Suffixes===
'''YourObject_COL.obj''' - contains simplified geometry for physics calculations

'''YourObject.obj_UV2''' - contains same object but with no overlapping UVs

'''YourObjectHULL.obj''' - same as _COL but has extra info, used with weapons

''NOTE:''

''The suffix formats are inconsistent, _COL is placed before the file extension while _UV2 is place after, and HULL doesn’t even have an underscore to separate it from the file name!''

===Physics objects (_COL)===
Simplified geometry such as boxes an cylinders which are used for collision detection, they are aligned to your object based on “relative position” in your 3D program so you should place the physics mesh on top of your render mesh upon export:

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Physics mesh should be placed on top of the render mesh

===Shadow UV objects (_UV2)===
These objects tell the engine how to place the shadow map on the rendered object if the original UV layout isn’t appropriate, the shadow maps require UV layouts with no over-lapping faces, this can usually be achieved using the “automatic unwrapping” tools found in most 3D applications.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Color texture UVs left, shadow UVs right, each face needs its own UV space.

===Hull objects (HULL)===
They are very similar to physics objects but are used for items and weapons, the only difference is that they contain a free-floating triangle which defines the object’s center of gravity.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Hull objects are placed over render mesh like physics objects.

==Items and Weapons==

Items and Weapons are aligned to the character based on their position relative to the center of the scene in your 3D app, you should load the .obj files of the example objects for reference. To make an object “pick-up-able” you need another .XML file that you load in place of the regular object properties file, it stores the info needed that is not defined in the regular object properties file:

<pre>
<?xml version="1.0" ?>
<item>
<type>weapon</type>
<appearance obj_path = "Data/Custom/Markuss/Examples/1-Handed.xml"/>
<grip ik_attach = "rightarm"
anim = "Data/Animations/r_dogweapongrip.anm"/>
<physics mass = "1 kg"/>
</item>
</pre>
Item properties file

===Tags===
'''<type>''' - defines what type of item the object is.

'''<appearance obj_path>''' - links to the regular object definition file.

'''<grip ik_attach anim>''' - defines what bone the object is attached to, links to an animation file.

'''<physics mass>''' - changes the pitch(?) of the sound made by the object hitting things.

'''<anim_override idle>''' - overrides the idle animation of a character holding the item.

''NOTE:''

''Not sure what the animation file in <grip ik_attach anim> does.''

''<anim_override idle> is only used for 2-handed weapons at the moment.''

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Example weapons, handles show the location of characters hands

''NOTE:''

''There is a bug that makes weapons turn invisible when loading levels with them already in it, you can fix this by having the “regular-object" version somewhere in the level as well.''

==Shaders==
'''Cubemap''' – closest thing to a “standard shader”, it has a cube-map based on the sky texture and a specular shine, the visibility of the cube map and shine is controlled with color texture’s alpha channel, white = fully reflective and shiny. Similarly, the normal-map texture’s alpha channel controls where color tinting happens, white = full effect. The cube map’s visibility is inversely affected by the brightness of the texture, you should make the color texture close to black for materials that are reflective such as chrome and glass.

'''CubemapObj''' - same as Cubemap but uses object-space normal maps instead of tangent space.

'''CubemapItem''' - same as Cubemap but the shine is sharper.

'''CubemapObjItem''' - object-space version of CubemapItem.

'''CubemapAlpha''' - has transparency controlled by the color texture’s alpha channel, cube map and shine are controlled by the normal-map texture’s alpha channel instead. CubemapAlpha has depth sorting issues with other transparent objects, enabling anti-aliasing fixes this somewhat.

'''CubemapObjChar''' - used for characters, shine is sharp, uses object space normals. There is no tangent-space version of CubemapObjChar and no object-space version of CubemapAlpha at the moment.

'''Plant''' - has transparency like CubemapAlpha but no cube map/shine. Translucency texture increases the brightness of the object while ignoring diffuse lighting, black = no effect. Wind texture defines intensity of a vertex ripple effect, black = no ripple. Both textures are linked in the object definition file using the <TranslucencyMap> and <WindMap> tags.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
CubemapAlpha

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Translucency (Plant Shader)

==Materials==

These are the sounds made and the particles emitted when you hit an object. I’ve set up some tiles for you to walk on to preview each material, here is a list:

: Cloth_Fabric
: Cloth_Leather
: Default
: Dirt
: DirtyRock
: Drygrass
: Grass
: Gravel
: Rock
: Rocks
: Sand
: Snow
: Wood

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Sound tiles

Note that some of these don’t emit particles.

3D Objects

2015-02-13T02:56:52Z

Poddus: /* Tags */ added link to wikipedia normal mapping

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=11227 this] forum post by member Markuss.''
There is a linked .zip file attached to the forum post. it can be found here:
http://www.markstockton.com/misc/Guide/Examples.zip

==Basics==
In Overgrowth 3D models use the .OBJ format but the material counter-part (.MTL) is not used, instead an “object properties file” stores links to model and texture files as well as some other information. This is the file you choose when loading an object, it uses the .XML format and can be read/created in any text editor:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Markuss/Examples/Models/SimpleObject.obj</Model>
<ColorMap>Data/Custom/Markuss/Examples/Textures/SimpleObject_Color.tga</ColorMap>
<NormalMap>Data/Custom/Markuss/Examples/Textures/Blank_Norm.tga</NormalMap>
<ShaderName>cubemap</ShaderName>
<MaterialPath>Data/Materials/default.xml</MaterialPath>
</Object>
</pre>

===Tags===
'''<Model>''' - links to the model file (.OBJ)

'''<ColorMap>''' - links to the color texture file (.TGA .TIF)

'''<NormalMap>''' - links to the [http://en.wikipedia.org/wiki/Normal_mapping normal map] texture file (.TGA .TIF)

'''<ShaderName>''' - refers to internal shader file (.FRAG .VERT), defines how object is rendered.

'''<MaterialPath>''' - links to internal material file (.XML), defines sound made by hitting the object.

====Additional tags====

'''<flags no_collision>''' - turns physics calculations on/off, true = off.

''NOTE:''

''“<ShaderName>” used to be “<ShaderPath>” and contained the full link instead of just the file name, expect similar update for “<MaterialPath>”.''

''Look at the example plant object for usage of the <flags no_collision> tag.''

===Model and Texture Requirements===

Models need to be constructed from squares and triangles only, so textures need to be square and not just “powers of 2”. (512x512 or 1024x1024 not 512x1024 or 1024x2048)

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Simple object and texture UV layout

==Alternative object System==
The engine automatically generates a simplified physics object and uses the object’s UV layout to place the shadow maps, these can be overridden by providing alternative .OBJ files that contain the desired information. These objects are placed in the same folder and share the same name as the original .OBJ file with a suffix to tell the engine what data they hold:

===Suffixes===
'''YourObject_COL.obj''' - contains simplified geometry for physics calculations

'''YourObject.obj_UV2''' - contains same object but with no overlapping UVs

'''YourObjectHULL.obj''' - same as _COL but has extra info, used with weapons

''NOTE:''

''The suffix formats are inconsistent, _COL is placed before the file extension while _UV2 is place after, and HULL doesn’t even have an underscore to separate it from the file name!''

===Physics objects (_COL)===
Simplified geometry such as boxes an cylinders which are used for collision detection, they are aligned to your object based on “relative position” in your 3D program so you should place the physics mesh on top of your render mesh upon export:

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Physics mesh should be placed on top of the render mesh

===Shadow UV objects (_UV2)===
These objects tell the engine how to place the shadow map on the rendered object if the original UV layout isn’t appropriate, the shadow maps require UV layouts with no over-lapping faces, this can usually be achieved using the “automatic unwrapping” tools found in most 3D applications.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Color texture UVs left, shadow UVs right, each face needs its own UV space.

===Hull objects (HULL)===
They are very similar to physics objects but are used for items and weapons, the only difference is that they contain a free-floating triangle which defines the object’s center of gravity.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Hull objects are placed over render mesh like physics objects.

==Items and Weapons==

Items and Weapons are aligned to the character based on their position relative to the center of the scene in your 3D app, you should load the .obj files of the example objects for reference. To make an object “pick-up-able” you need another .XML file that you load in place of the regular object properties file, it stores the info needed that is not defined in the regular object properties file:

<pre>
<?xml version="1.0" ?>
<item>
<type>weapon</type>
<appearance obj_path = "Data/Custom/Markuss/Examples/1-Handed.xml"/>
<grip ik_attach = "rightarm"
anim = "Data/Animations/r_dogweapongrip.anm"/>
<physics mass = "1 kg"/>
</item>
</pre>
Item properties file

===Tags===
'''<type>''' - defines what type of item the object is.

'''<appearance obj_path>''' - links to the regular object definition file.

'''<grip ik_attach anim>''' - defines what bone the object is attached to, links to an animation file.

'''<physics mass>''' - changes the pitch(?) of the sound made by the object hitting things.

'''<anim_override idle>''' - overrides the idle animation of a character holding the item.

''NOTE:''

''Not sure what the animation file in <grip ik_attach anim> does.''

''<anim_override idle> is only used for 2-handed weapons at the moment.''

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Example weapons, handles show the location of characters hands

''NOTE:''

''There is a bug that makes weapons turn invisible when loading levels with them already in it, you can fix this by having the “regular-object" version somewhere in the level as well.''

==Shaders==
'''Cubemap''' – closest thing to a “standard shader”, it has a cube-map based on the sky texture and a specular shine, the visibility of the cube map and shine is controlled with color texture’s alpha channel, white = fully reflective and shiny. Similarly, the normal-map texture’s alpha channel controls where color tinting happens, white = full effect. The cube map’s visibility is inversely affected by the brightness of the texture, you should make the color texture close to black for materials that are reflective such as chrome and glass.

'''CubemapObj''' - same as Cubemap but uses object-space normal maps instead of tangent space.

'''CubemapItem''' - same as Cubemap but the shine is sharper.

'''CubemapObjItem''' - object-space version of CubemapItem.

'''CubemapAlpha''' - has transparency controlled by the color texture’s alpha channel, cube map and shine are controlled by the normal-map texture’s alpha channel instead. CubemapAlpha has depth sorting issues with other transparent objects, enabling anti-aliasing fixes this somewhat.

'''CubemapObjChar''' - used for characters, shine is sharp, uses object space normals. There is no tangent-space version of CubemapObjChar and no object-space version of CubemapAlpha at the moment.

'''Plant''' - has transparency like CubemapAlpha but no cube map/shine. Translucency texture increases the brightness of the object while ignoring diffuse lighting, black = no effect. Wind texture defines intensity of a vertex ripple effect, black = no ripple. Both textures are linked in the object definition file using the <TranslucencyMap> and <WindMap> tags.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
CubemapAlpha

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Translucency (Plant Shader)

==Materials==

These are the sounds made and the particles emitted when you hit an object. I’ve set up some tiles for you to walk on to preview each material, here is a list:

: Cloth_Fabric
: Cloth_Leather
: Default
: Dirt
: DirtyRock
: Drygrass
: Grass
: Gravel
: Rock
: Rocks
: Sand
: Snow
: Wood

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Sound tiles

Note that some of these don’t emit particles.

Portal:Overgrowth

2015-02-12T18:11:26Z

Poddus: /* Modding */

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development for Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Modding ==
* [[Editor Interface]]
* [[Phoenix Engine]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Objects]]
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Level XML reference]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

Portal:Overgrowth

2015-02-12T18:10:49Z

Poddus: /* Modding */ added link to 3d Models article

<noinclude>[[Category:Portals|{{PAGENAME}}]] [[Category:Overgrowth|{{PAGENAME}}]] </noinclude>
{{Overgrowth Portal Header}}

-----

[http://www.wolfire.com/overgrowth Overgrowth] is a cross-platform game in development by Wolfire Games, an independent game company consisting of David Rosen, founder and lead programmer, and Aubrey Serr, lead artist. Overgrowth is the spiritual successor to [[Lugaru]], a game also developed by Wolfire. Development for Overgrowth was officially announced on September 17th, 2008. The game is currently in Alpha and is playable via [http://www.wolfire.com/overgrowth/preorder preorder].

Gameplay emphasises 3rd-person, fluid, fast-paced melee combat, and 3D-platforming. Overgrowth uses a custom game engine codenamed "[[Phoenix Engine|Phoenix]]", and a lot of work has been put into making it accessible to [[Editor_Interface|modding]].

The game currently consists of a collection of maps (some of which are populated by enemies) which the player is able to explore (and modify if they are so inclined). As of Alpha v197, there is are two additional gameplay modes, one dubbed "Arena", in which the player is pitted against procedurally generated enemies in gladiatorial matches, and one dubbed "Challenge", a collection of 12 levels in which the player must complete a certain task or set of tasks.

As of yet there is no definite story line. However, in a 2012 interview with British video gaming website zConnection, the Wolfire team stated that they are planning on continuing the story of [[Turner]], a couple of years after the events of [[Lugaru]]. In addition to anthropomorphic rabbits and wolves, the Overgrowth Universe now already includes cats, dogs, and rats (see article: [[Races]]).

== Getting Started ==
* [[Getting_Started | First Steps]]
* [[Configuring Overgrowth]]
* [[Control Reference]]
* [[Overgrowth Alpha FAQ| Overgrowth FAQ]]
* [[Alpha List]]

== Modding ==
* [[Editor Interface]]
* [[Phoenix Engine]]
* [[Scripting]]
* [[Custom Terrain]]
* [[3D Models]]
* [[Making New Models & Textures]]
* [[Importing Models & Textures]]
* [[Custom Decals]]
* [[Level XML reference]]

==Alpha Testing==

* [[Overgrowth tests]] {{stub}}

== The Overgrowth Universe ==
* [[Races]]
* [[Locations]]
* [[Characters]]
* [[Equipment and Weapons]]
* [[Alpha Stages]]
* [[Lore]]

== Misc ==
* [[Useful Links]]
* [[Supported Video Cards]]
* [[Overgrowth_Linux|Linux]]

3D Objects

2015-02-12T18:10:09Z

Poddus:

''based on [http://forums.wolfire.com/viewtopic.php?f=16&t=11227 this] forum post by member Markuss.''
There is a linked .zip file attached to the forum post. it can be found here:
http://www.markstockton.com/misc/Guide/Examples.zip

==Basics==
In Overgrowth 3D models use the .OBJ format but the material counter-part (.MTL) is not used, instead an “object properties file” stores links to model and texture files as well as some other information. This is the file you choose when loading an object, it uses the .XML format and can be read/created in any text editor:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Markuss/Examples/Models/SimpleObject.obj</Model>
<ColorMap>Data/Custom/Markuss/Examples/Textures/SimpleObject_Color.tga</ColorMap>
<NormalMap>Data/Custom/Markuss/Examples/Textures/Blank_Norm.tga</NormalMap>
<ShaderName>cubemap</ShaderName>
<MaterialPath>Data/Materials/default.xml</MaterialPath>
</Object>
</pre>

===Tags===
'''<Model>''' - links to the model file (.OBJ)

'''<ColorMap>''' - links to the color texture file (.TGA .TIF)

'''<NormalMap>''' - links to the normal map texture file (.TGA .TIF)

'''<ShaderName>''' - refers to internal shader file (.FRAG .VERT), defines how object is rendered.

'''<MaterialPath>''' - links to internal material file (.XML), defines sound made by hitting the object.

====Additional tags====

'''<flags no_collision>''' - turns physics calculations on/off, true = off.

''NOTE:''

''“<ShaderName>” used to be “<ShaderPath>” and contained the full link instead of just the file name, expect similar update for “<MaterialPath>”.''

''Look at the example plant object for usage of the <flags no_collision> tag.''

===Model and Texture Requirements===

Models need to be constructed from squares and triangles only, so textures need to be square and not just “powers of 2”. (512x512 or 1024x1024 not 512x1024 or 1024x2048)

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Simple object and texture UV layout

==Alternative object System==
The engine automatically generates a simplified physics object and uses the object’s UV layout to place the shadow maps, these can be overridden by providing alternative .OBJ files that contain the desired information. These objects are placed in the same folder and share the same name as the original .OBJ file with a suffix to tell the engine what data they hold:

===Suffixes===
'''YourObject_COL.obj''' - contains simplified geometry for physics calculations

'''YourObject.obj_UV2''' - contains same object but with no overlapping UVs

'''YourObjectHULL.obj''' - same as _COL but has extra info, used with weapons

''NOTE:''

''The suffix formats are inconsistent, _COL is placed before the file extension while _UV2 is place after, and HULL doesn’t even have an underscore to separate it from the file name!''

===Physics objects (_COL)===
Simplified geometry such as boxes an cylinders which are used for collision detection, they are aligned to your object based on “relative position” in your 3D program so you should place the physics mesh on top of your render mesh upon export:

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Physics mesh should be placed on top of the render mesh

===Shadow UV objects (_UV2)===
These objects tell the engine how to place the shadow map on the rendered object if the original UV layout isn’t appropriate, the shadow maps require UV layouts with no over-lapping faces, this can usually be achieved using the “automatic unwrapping” tools found in most 3D applications.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Color texture UVs left, shadow UVs right, each face needs its own UV space.

===Hull objects (HULL)===
They are very similar to physics objects but are used for items and weapons, the only difference is that they contain a free-floating triangle which defines the object’s center of gravity.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Hull objects are placed over render mesh like physics objects.

==Items and Weapons==

Items and Weapons are aligned to the character based on their position relative to the center of the scene in your 3D app, you should load the .obj files of the example objects for reference. To make an object “pick-up-able” you need another .XML file that you load in place of the regular object properties file, it stores the info needed that is not defined in the regular object properties file:

<pre>
<?xml version="1.0" ?>
<item>
<type>weapon</type>
<appearance obj_path = "Data/Custom/Markuss/Examples/1-Handed.xml"/>
<grip ik_attach = "rightarm"
anim = "Data/Animations/r_dogweapongrip.anm"/>
<physics mass = "1 kg"/>
</item>
</pre>
Item properties file

===Tags===
'''<type>''' - defines what type of item the object is.

'''<appearance obj_path>''' - links to the regular object definition file.

'''<grip ik_attach anim>''' - defines what bone the object is attached to, links to an animation file.

'''<physics mass>''' - changes the pitch(?) of the sound made by the object hitting things.

'''<anim_override idle>''' - overrides the idle animation of a character holding the item.

''NOTE:''

''Not sure what the animation file in <grip ik_attach anim> does.''

''<anim_override idle> is only used for 2-handed weapons at the moment.''

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Example weapons, handles show the location of characters hands

''NOTE:''

''There is a bug that makes weapons turn invisible when loading levels with them already in it, you can fix this by having the “regular-object" version somewhere in the level as well.''

==Shaders==
'''Cubemap''' – closest thing to a “standard shader”, it has a cube-map based on the sky texture and a specular shine, the visibility of the cube map and shine is controlled with color texture’s alpha channel, white = fully reflective and shiny. Similarly, the normal-map texture’s alpha channel controls where color tinting happens, white = full effect. The cube map’s visibility is inversely affected by the brightness of the texture, you should make the color texture close to black for materials that are reflective such as chrome and glass.

'''CubemapObj''' - same as Cubemap but uses object-space normal maps instead of tangent space.

'''CubemapItem''' - same as Cubemap but the shine is sharper.

'''CubemapObjItem''' - object-space version of CubemapItem.

'''CubemapAlpha''' - has transparency controlled by the color texture’s alpha channel, cube map and shine are controlled by the normal-map texture’s alpha channel instead. CubemapAlpha has depth sorting issues with other transparent objects, enabling anti-aliasing fixes this somewhat.

'''CubemapObjChar''' - used for characters, shine is sharp, uses object space normals. There is no tangent-space version of CubemapObjChar and no object-space version of CubemapAlpha at the moment.

'''Plant''' - has transparency like CubemapAlpha but no cube map/shine. Translucency texture increases the brightness of the object while ignoring diffuse lighting, black = no effect. Wind texture defines intensity of a vertex ripple effect, black = no ripple. Both textures are linked in the object definition file using the <TranslucencyMap> and <WindMap> tags.

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
CubemapAlpha

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Translucency (Plant Shader)

==Materials==

These are the sounds made and the particles emitted when you hit an object. I’ve set up some tiles for you to walk on to preview each material, here is a list:

: Cloth_Fabric
: Cloth_Leather
: Default
: Dirt
: DirtyRock
: Drygrass
: Grass
: Gravel
: Rock
: Rocks
: Sand
: Snow
: Wood

<pre>IMAGE MISSING, UNABLE TO UPLOAD</pre>
Sound tiles

Note that some of these don’t emit particles.