Wolfire Games Wiki - User contributions [en]

Supported Video Cards

2011-05-21T12:30:06Z

Cody: updated ati 4350 and added intel 3000

This is a list of video cards tested with the Overgrowth Alpha, pulled right from [http://forums.wolfire.com/viewtopic.php?f=13&t=6406 this thread].

Unless Proven: Netbooks are NOT supported!

{| style="border: 1px solid #ccc; background:#fff;" border="0" cellpadding="2" cellspacing="5"
!colspan="5"|Key
|-
|Working
|style="background: #bf0000; color:#fff;"|Not Working
|style="background: #5d1000; color:#fff;"|Very Poor
|style="background: #40BF00; color:#fff;"|Possibly Working
|style="background: #ffa500; color:#fff;"|Testing
|}

== '''ATI VIDEO CARD SECTION''' ==

{|{{Table}}
!Card
!Status
!Style
!OS
!Alpha tested
!Submitter
!Confirmed by
!Notes
!Screenshots
|-
|ATI Mobillity Radeon HD 2500
|Working
|Mobile
|Windows 7
|a113
|Numbie
|
|21-30fps. 1-2 bots (depends on the map)
|
|-
|ATI Mobillity Radeon HD 4500
|Working
|Mobile
|Windows
|112
|Lord of Sausage
|TehFifthHorseman
|Runs at a decent speed with Turner + 4 bots max, then drops off.
|

|-
|ATI Mobillity Radeon HD 5870
|Working
|Mobile
|Windows
|116
|Dorx
|
|Stumbles onto some trouble when adding more than 5 bots. Usually on 60 FPS, but drops randomly every once in a while.
|

|-
|ATI Radeon HD 2400
|Working
|Desktop
|Mac 10.6.4
|91
|Spinnacre
|
|
|

|-
|ATI Radeon HD 2600
|Working
|Desktop
|
|79
|Pablopa99
|
|
|

|-
|ATI HD 3200
|style="background: #5d1000; color:#fff;"|Very Poor
|Desktop
|
|79
|iDiedByCyanide
|
|3-6FPS, ground is very blurry, only ground, no prefabs.
|

|-
|ATI HD 3300 IGP (AMD 790GX)
|Working
|Desktop
|
|79
|OneEyedOdin
|
|
|

|-
|ATI HD 3870 (Saphire Ed.)
|Working
|Desktop
|
|79
|Timen
|
|
|

|-
|ATI Radeon HD 4350
|Working
|Desktop
|Windows 7 64-bit
|79
|cody
|
|Acer Aspire M3800
|

|-
|ATI Radeon HD 4850
|Working
|Desktop
|
|79
|Wally World
|
|Glitchy first 3-4 times.
|

|-
|ATI Radeon HD 4870
|Working
|Desktop
|
|79
|Adam
|
|
|

|-
|ATI Radeon HD 4870 x2 2GB
|Working
|Desktop
|Windows 7 64-bit
|79, 113
|Dudeman
|Kayouu
|
|

|-
|ATI Radeon HD 4890
|Working
|Desktop
|
|79
|Orillian
|Stophe (Saphire Ed.)
|Does not work at 2048x1152
|

|-
|ATI Radeon HD 5670
|Working
|Desktop
|
|79
|pancakewagon
|
|
|

|-
|AMD Radeon HD 6850
|Working
|Desktop
|
|
|Timbo59
|
|
|

ATI HD Radeon

|-
|AMD Radeon HD 6870
|Working
|Desktop
|Windows 7 64-bit
|109,111-1
|Buglish
|burny209
|
|

|-
|ATI Radeon X1600
|Working
|Mobile
|Mac 10.6.6
|112
|Kroc
|
|
|

|}

== '''Nvidia VIDEO CARD SECTION''' ==

{|{{Table}}
!Card
!Status
!Style
!OS
!Alpha tested
!Submitter
!Confirmed by
!Notes
!Screenshots

|-
|NVIDIA GeForce 320M
|Working
|Mobile
|Mac OS X 10.6.7 & Windows 7 Pro x64 (Bootcamp)
|a129
|viemmsakh
|
|As noted below with similiar gfx card game runs beautifully.
|[http://www.youtube.com/watch?v=Rd6e7ZChitw youtube]

|-
|NVIDIA GeForce 320M
|Working
|Mobile
|Mac OS X 10.6.6
|118
|Zeigerpuppy
|Archangelus
|Surprisingly good 60-100 fps @ fullscreen 1366x768 post processing: 1; anisotropy: 1; multisampling not supported; MacbookAir 11" 1.4GHz.
|

|-
|nVidia GeForce 6100
|style="background: #5d1000; color:#fff;"|Very Poor
|Desktop
|
|79
|Fruckert
|
|Less than 5 fps, load time very long.
|

|-
|nVidia GeForce 7300 LE
|style="background: #ffa500; color:#fff;"|Testing
|Desktop
|
|79
|Radu
|
|
|

|-
|nVidia GeForce 7600
|style="background: #40BF00; color:#fff;"|Possibly Working
|Desktop
|
|79
|Catmana
|
|
|

|-
|nVidia GeForce 7900
|Working
|Desktop
|
|79
|nutcracker
|
|
|

|-
|nVidia GeForce 8500 GT
|Working
|Desktop
|Windows 7
|118
|imaginationac
|
|
|

|-
|nVidia GeForce 8600
|Working
|Desktop
|Windows 7
|122
|nutcracker
|YuroFoxclaw
|
|

|-
|nVidia GeForce 8600M GT
|Working
|Mobile
|
|79
|tomascokis
|
|
|

|-
|nVidia GeForce 8800 GTS
|Working
|Desktop
|
|79
|Crab
|
|
|

|-
|nVidia GeForce 9400M
|Working
|Mobile
|Mac 10.6.4
|90
|k123dave
|jo-shadow
|
|

|-
|nVidia GeForce 9400M
|Working
|Mobile
|Windows 7
|90
|k123dave
|jo-shadow
|
|

|-
|nVidia GeForce 9600M GT
|Working
|Mobile
|
|79
|Freshbite
|
|
|

|-
|nVidia GeForce 9800M GT
|Working
|Mobile
|
|79
|Blorx
|
|
|

|-
|nVidia GeForce 9800 GT
|Working
|Desktop
|Windows 7 64 bit
|91
|Silverfish
|
|
|

|-
|nVidia GeForce 9800 GTX
|Working
|Desktop
|
|79
|BadRabbit
|
|
|

|-
|nVidia GTX 260 Core 216 (BFG)
|Working
|Desktop
|
|79
|Radu
|
|
|

|-
|nVidia GeForce GTS 250
|Working
|Desktop
|
|79
|style="color:#800080;"|Skofo
|style="color:#800080;"|Endoperez
|
|

|-
|nVidia GeForce GTX 260
|Working
|Desktop
|
|79
|Dudeman
|
|
|

|-
|nVidia GeForce GTX 285
|Working
|Desktop
|
|79
|Dudeman
|
|
|

|-
|nVidia GeForce GTX 285
|Working
|Desktop
|Mac OS X 10.6.4
|118
|Zeigerpuppy
|
|Excellent Frame Rate 100-200 fps @ 1920x1200, Hackintosh i920, 2.8Ghz.
|

|-
|nVidia GeForce GTX 295
|Working
|Desktop
|Windows 7
|106
|Steff0o
|
|
|

|-
|nVidia GeForce 330M
|Working
|Mobile
|OSX 10.6.5
|109
|Lynge
|
|
|

|-
|nVidia GeForce GTS 450
|style="background: #bf0000; color:#fff;"|Not Working
|Desktop
|Windows 7 x64
|129
|Booljayj
|
|Crashes, thinks the card doesn't support shaders
|

|-
|nVidia GeForce GTX 460 1GB
|style="background: #bf0000; color:#fff;"|Not Working
|Desktop
|Windows 7
|89
|WarlockSyno
|
|Crashes card driver
|[http://imgur.com/K7BLZ.png 1]

|-
|nVidia GeForce GTX 460 1GB
|Working
|Desktop
|Mac OSX 10.6.5
|112
|PacketCollision
|
|Hackintosh Core i5, 2.93Ghz. Seems to run perfectly.
|

|-
|nVidia GeForce GTX 470
|Working
|Desktop
|
|79
|FluxCapacitor
|Numbie /a117
|
|

|-
|nVidia GeForce 210
|Working
|Desktop
|Windows XP SP3; 32-bit
|113
|T3RR0RH4WK
|
|Works flawlessly in windowed-mode (800x600, 720x480) and slows only slightly when in full-screen (1280x720, 1366x768)
|

|-
|nVidia ION
|style="background: #bf0000; color:#fff;"|Not Working
|Mobile
|
|79
|SentientAfro
|
|
|

|}

== '''Intel VIDEO CARD SECTION''' ==

{|{{Table}}
!Card
!Status
!Style
!OS
!Alpha tested
!Submitter
!Confirmed by
!Notes
!Screenshots

|-
|Intel 950 Express
|style="background: #bf0000; color:#fff;"|Not Working
|Mobile
|
|79
|Fruckert
|
|Strange Colors/Textures.
|[http://imgur.com/2Mwnn.png 1]

|-
|Intel 965 Express
|style="background: #bf0000; color:#fff;"|Not Working
|Mobile
|
|79
|Sorin
|
|No Shader Support.
|

|-
|Intel HD Graphics 3000
|style="background: #40BF00; color:#fff;"|Possibly Working
|Mobile
|Mac OS X 10.6
|a113
|Otter.
|
|MacBook Pro
|

|-
|Intel GMA X3100
|style="background: #bf0000; color:#fff;"|Not Working
|Mobile
|
|79
|style="color:#800080;"|Radu
|style="color:#800080;"|Sandruz
|No shader support.
|
|

|-
|Intel GMA 945/950
|style="background: #bf0000; color:#fff;"|Not Working
|Mobile
|
|79
|Pablopa99
|cody
|No shader support.

|-
|Intel 82865G
|style="background: #bf0000; color:#fff;"|Not Working
|Desktop
|
|79
|keen101
|
|No Shader Support.
|

|}

[[Category:Overgrowth]]
[[Category:Help]]
[[Category:Secret Preorder Forum]]

Template:Dup

2010-07-06T09:36:33Z

Cody:

<noinclude>{{CT|Templates}} {{CT|Improvement Needed Templates}}</noinclude><includeonly>{{CT|Improvement Needed}}</includeonly>
----
[[Image:Edit.png|45px]]
'''This page duplicates, in whole or part, the scope of other page(s) or section(s).'''
 
Please [[{{TALKPAGENAME}}|discuss]] this issue on the talk page, or spin off the repeated text into an article in its own right.
----
[[Category:Duplicate]]

Template:Not Whaleman Friendly

2010-07-06T09:31:46Z

Cody:

<noinclude>

{{CT|Templates}} {{CT|Improvement Needed Templates}}

== Unhappy Whalemen ==
Use this template to put some angry whaleman on a page. '''Use with caution!'''

== Instructions ==
In an inprovement needed style page or template, simply insert {{Not Whaleman Friendly}} into the code, preferably at the top. (Because Whaleman is special)
For added effect insert {{Not Whaleman Friendly| Your Whaleman Related Message Here }} for a caption to appear below the image.
</noinclude>


[[Image:NotWhalemanFriendly.png|150px|thumb|top|alt=Whaleman does NOT approve!|{{{1|Whaleman Does NOT Approve!}}}]]

Template:Wip

2010-07-06T09:30:26Z

Cody:

Template:Link Page

2010-07-06T09:29:38Z

Cody:

File:Edit.png

2010-07-06T09:26:30Z

Cody:

Template:Stub

2010-07-06T09:19:13Z

Cody:

Supported Video Cards

2010-06-01T10:23:36Z

Cody:

Supported Video Cards

2010-05-28T21:47:17Z

Cody: added ati radeon hd 4350 and confirmed gma 945/950

Talk:Tutorial 1: Making a house

2010-02-18T22:55:48Z

Cody: New page: == Broken Images == There is a bunch of broken links to images on this page, they should probably have the appropriate images uploaded or the image links removed.

== Broken Images ==
There is a bunch of broken links to images on this page, they should probably have the appropriate images uploaded or the image links removed.

Editor Interface

2010-02-18T22:54:09Z

Cody: /* Using the Tools */ removed dead image link

{{WQA in Progress}}

=Basic Controls=
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], a high powered code which allows for a lot of functions and such.

==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.

== Saving Combined Object As A Separate File ==

Once you have created someone 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:Overgrowth]]
[[Category:Editing]]

Template:Wip

2010-02-18T22:53:43Z

Cody: made button smaller, seems to otherwise, interfere with page contents on page displaying the template

Template:Overgrowth Portal Header

2010-02-18T22:50:24Z

Cody: removed overgrowth templates, changed to just templates

<noinclude>{{CT|Templates}} {{CT|Wiki Navigation}}</noinclude>{{Portal Header
| width=450
| image=Overgrowth_Header.png
| title1= Welcome to the Overgrowth Portal!
| title2= Click [[Main_Page|Here]] to return to the Main Page.
| contents= Here you will find everything related to Overgrowth!
| linklist= [http://www.wolfire.com/overgrowth Overgrowth Homepage] • [http://forums.wolfire.com/viewforum.php?f=13 SPF] • [http://www.wolfire.com/contact Help]
| pagenumbers= [[:Category:Overgrowth | {{PAGESINCAT:Overgrowth}}]] pages.
}}

Template:Link Page

2010-02-18T22:48:16Z

Cody: corrected typo

<noinclude>{{CT|Templates}} {{CT|Improvement Needed Templates}}</noinclude><includeonly>{{CT|Improvement Needed}}</includeonly>
== Uh oh, this page is a has too many links and, not enough content! ==
'''This page should probably be recreated as a category. Feel free to help out.'''
 
 
----
[[Category:Link Page]]

Scripting

2010-02-18T22:46:11Z

Cody: added category

Overgrowth is using AngelScript as its core scripting language. The best AngelScript reference is here: [http://www.angelcode.com/angelscript/sdk/docs/manual/index.html]

Checking for Keypresses:

You can check for keypresses by using the '''boolean''' check function '''GetInputDown()''':

Syntax examples:

{| class="wikitable" border="1"
|-
|GetInputDown("a")
|returns true if the 'a' key is being pressed, returns false if not
|-
|GetInputDown("attack")
|returns true if the left mouse button is being pressed, returns false if not
|-
|GetInputDown("move_left")
|returns true if the "left key" is being pressed, returns false if not (by default this key is defined in the config.txt to be the 'a' key)
|}

The following controls are designed to be relative to the player's preferences and are given a binding in the config.txt file.

'''Config.txt Dependent References'''
{| class="wikitable" border="1"
|-
! Predefined Term
! Default binding in Config.txt
! Scripting Reference Name
|-
| Left Key
| a
| move_left
|-
| Right Key
| d
| move_right
|-
| Up Key
| w
| move_up
|-
| Down Key
| s
| move_down
|-
| Crouch Key
| left shift
| crouch
|-
| Jump Key
| space
| jump
|}

'''Generic Key References'''
{| class="wikitable" border="1"
|-
! Desired Input Key
! Scripting Representation
|-
| left mouse button
| attack
|-
| right mouse button
| grab
|-
| a
| a
|-
| b
| b
|-
| c
| c
|-
| d
| d
|-
| e
| e
|-
| f
| f
|-
| g
| g
|-
| h
| h
|-
| i
| i
|-
| j
| j
|-
| k
| k
|-
| l
| l
|-
| m
| m
|-
| n
| n
|-
| o
| o
|-
| p
| p
|-
| q
| q
|-
| r
| r
|-
| s
| s
|-
| t
| t
|-
| u
| u
|-
| v
| v
|-
| w
| w
|-
| x
| x
|-
| y
| y
|-
| z
| z
|}

[[Category:Overgrowth]]

Overgrowth Alpha FAQ

2010-02-18T22:44:53Z

Cody: fixed references

This is the Overgrowth Alpha FAQ.

* This FAQ is intended for useful tips for new users as well as answer common bug-related questions.
* This FAQ ''NOT'' intended as a place for you to post bugs you might have found. If you want to report a bug please do so on [http://trac.wolfire.net/spf/overgrowth/report/6 Wolfire's Trac].

Please feel free to contribute to this FAQ, and the wiki as a whole!

Any entry concerning bugs should be formatted as an informative title, followed by any of the following:
* Symptoms that the bug might exhibit.
* Details about the bug.
* Links to forum topics where the issue mentioned has been discussed/resolved.
* Workarounds to help avoid this bug.
* Fixing instructions to help fix the bug if it occurs.
* Any other relevant information.

==General==
===Something-Something Won't Work! AHHH!===
First and foremost, Don't Panic.

''Disclaimer'': Be prepared for it to just not work at times. Overgrowth is still in its Alpha stage of development, and the team is focusing more on getting essential features in than working out bugs and compatibility issues. The team ''will'' get to them, and will try to occasionally fix very pressing bugs, but sadly sometimes it will just take a while. However that doesn't mean that there's nothing you can do!

Here's what you can do:
* Look at the rest of this FAQ to see if there are any that might fit your situation.
* Check the [http://forums.wolfire.com/viewforum.php?f=13 Secret Preorder Forum] and use the lovely search feature. For example if on your Windows 7 PC, Overgrowth crashes when your character jumps, search for "Windows 7 Jump Crash".
* Ask on Wolfire's [http://www.wolfire.com/irc IRC channel]. Many users are long time Alpha testers and will be happy to help you.
* Ask John on [http://www.wolfire.com/contact Meebo]. Although John's time is a valuable, non-renewable resource, he will be happy to help you if you need to talk with someone on the team.

''Note'': if you decide to request help anywhere please include relevant information such as:
* Alpha Number
* If you're running windows, mac or linux
* what version your OS is
* Relevant system information such as what graphics card your computer has, how Much RAM you have, etc.
* Any Error messages that you see.

===I can't access all of the GUI. The window crops important parts of the screen.===
This turned up, when the default resolution was lowered from 1024x768 to 800x600. You can resolve this issue by changing the settings, either to a higher resolution or to full screen mode. Changing display settings is done in the 'config.txt'-file in the Overgrowth data folder.

The first lines of the default config file should look like this:
<pre>
screenwidth: 800
screenheight: 600
fullscreen: false
</pre>
You can change the resolution by changing the values for screenwidth/screenheight and go to fullscreen mode by changing the 'false' to 'true'.

=== When I try to load a Model it won't work ===
You need to make sure that you're not loading the model file, but the object file.
* A Model file is a 3d mesh saved as a *.obj file. this file contains no textures or shader data and so cannot be loaded by itself.
* An Object file is an XML that stores the filepaths for all the relevant data of an object, including the Model file as well as the textures and shader.
For example if you are trying to load a file located in Data/Models/example.obj you should really be opening Data/Objects/example.xml

=== My Custom Map Won't Load in the main menu ===
# Make sure that you typed the name correctly, including the *.xml ending
# Make sure that it exists in Data/Levels/

* Recently (as at alpha 65) there have been some issues with loading custom maps from the main menu. to make sure this isn't the case:
# Back up the map 'DesertFort_IGF.xml' (for example add "backup" to the name)
# Rename your map as 'DesertFort_IGF.xml'
# Attempt to load it by clicking the Desert map in the main menu.

==Windows==
===Error: cannot create the C:\program files\Overgrowth\Data\config.txt file. ... ===
This error applies to both Lugaru and Overgrowth.

Symptom: When attempting to edit the config.txt file the following error message is displayed:
cannot create the C:\program files\Overgrowth\Data\config.txt file. Make sure the path and file name are correct.

Explanation: Windows Vista & 7 like to save the config file in a different location to the actual directory. As discussed in a thread on the forums[http://forums.wolfire.com/viewtopic.php?f=7&t=4890&p=78033#p78033], The file is actually stored in: C:\Users\USERNAME\Application Data\Local Virtual Store\Program Files/Overgrowth/config.txt

==Mac==
===I can't find the Data folder===
With the Mac version of Overgrowth, the Data folder is located within the application package.
You can access it by right clicking the "Overgrowth" application and choosing 'Show Contents", and then browsing to Contents/MacOS/Data

To make future access easier right click 'Data' and choose 'Make Alias'. Now drag this alias out of the application, somewhere easy to find, on your Desktop for example.

Then, next time you need to open a file from within the Overgrowth package, simply navigate to the alias and you should have access to the Contents of the Data folder.

===It says on the forums/blog that you can right click with command+click, but it won't work!===
Unfortunately in recent alphas this functionality has been broken. Right clicking is currently only possible with an external mouse, or on a trackpad with enabled two-finger right click.

==Linux==
===Running Overgrowth on Linux===
Currently there is no native Linux version of Overgrowth, but it's comming[http://forums.wolfire.com/viewtopic.php?f=13&t=6044]. However, you may be able to emulate the Windows version under [http://www.winehq.org/ Wine]. This will also require the Visual C++ 2005 libraries, which can be installed through [http://wiki.winehq.org/winetricks winetricks].

[[Category:Secret_Preorder_Forum]]

Overgrowth Alpha FAQ

2010-02-18T22:42:40Z

Cody: categorized page and revised contents

This is the Overgrowth Alpha FAQ.

* This FAQ is intended for useful tips for new users as well as answer common bug-related questions.
* This FAQ ''NOT'' intended as a place for you to post bugs you might have found. If you want to report a bug please do so on [http://trac.wolfire.net/spf/overgrowth/report/6 Wolfire's Trac].

Please feel free to contribute to this FAQ, and the wiki as a whole!

Any entry concerning bugs should be formatted as an informative title, followed by any of the following:
* Symptoms that the bug might exhibit.
* Details about the bug.
* Links to forum topics where the issue mentioned has been discussed/resolved.
* Workarounds to help avoid this bug.
* Fixing instructions to help fix the bug if it occurs.
* Any other relevant information.

==General==
===Something-Something Won't Work! AHHH!===
First and foremost, Don't Panic.

''Disclaimer'': Be prepared for it to just not work at times. Overgrowth is still in its Alpha stage of development, and the team is focusing more on getting essential features in than working out bugs and compatibility issues. The team ''will'' get to them, and will try to occasionally fix very pressing bugs, but sadly sometimes it will just take a while. However that doesn't mean that there's nothing you can do!

Here's what you can do:
* Look at the rest of this FAQ to see if there are any that might fit your situation.
* Check the [http://forums.wolfire.com/viewforum.php?f=13 Secret Preorder Forum] and use the lovely search feature. For example if on your Windows 7 PC, Overgrowth crashes when your character jumps, search for "Windows 7 Jump Crash".
* Ask on Wolfire's [http://www.wolfire.com/irc IRC channel]. Many users are long time Alpha testers and will be happy to help you.
* Ask John on [http://www.wolfire.com/contact Meebo]. Although John's time is a valuable, non-renewable resource, he will be happy to help you if you need to talk with someone on the team.

''Note'': if you decide to request help anywhere please include relevant information such as:
* Alpha Number
* If you're running windows, mac or linux
* what version your OS is
* Relevant system information such as what graphics card your computer has, how Much RAM you have, etc.
* Any Error messages that you see.

===I can't access all of the GUI. The window crops important parts of the screen.===
This turned up, when the default resolution was lowered from 1024x768 to 800x600. You can resolve this issue by changing the settings, either to a higher resolution or to full screen mode. Changing display settings is done in the 'config.txt'-file in the Overgrowth data folder.

The first lines of the default config file should look like this:
<pre>
screenwidth: 800
screenheight: 600
fullscreen: false
</pre>
You can change the resolution by changing the values for screenwidth/screenheight and go to fullscreen mode by changing the 'false' to 'true'.

=== When I try to load a Model it won't work ===
You need to make sure that you're not loading the model file, but the object file.
* A Model file is a 3d mesh saved as a *.obj file. this file contains no textures or shader data and so cannot be loaded by itself.
* An Object file is an XML that stores the filepaths for all the relevant data of an object, including the Model file as well as the textures and shader.
For example if you are trying to load a file located in Data/Models/example.obj you should really be opening Data/Objects/example.xml

=== My Custom Map Won't Load in the main menu ===
# Make sure that you typed the name correctly, including the *.xml ending
# Make sure that it exists in Data/Levels/

* Recently (as at alpha 65) there have been some issues with loading custom maps from the main menu. to make sure this isn't the case:
# Back up the map 'DesertFort_IGF.xml' (for example add "backup" to the name)
# Rename your map as 'DesertFort_IGF.xml'
# Attempt to load it by clicking the Desert map in the main menu.

==Windows==
===Error: cannot create the C:\program files\Overgrowth\Data\config.txt file. ... ===
This error applies to both Lugaru and Overgrowth.

Symptom: When attempting to edit the config.txt file the following error message is displayed:
cannot create the C:\program files\Overgrowth\Data\config.txt file. Make sure the path and file name are correct.

Explanation: Windows Vista & 7 like to save the config file in a different location to the actual directory. As discussed in a thread on the forums<ref>[http://forums.wolfire.com/viewtopic.php?f=7&t=4890&p=78033#p78033]</ref>, The file is actually stored in: C:\Users\USERNAME\Application Data\Local Virtual Store\Program Files/Overgrowth/config.txt

==Mac==
===I can't find the Data folder===
With the Mac version of Overgrowth, the Data folder is located within the application package.
You can access it by right clicking the "Overgrowth" application and choosing 'Show Contents", and then browsing to Contents/MacOS/Data

To make future access easier right click 'Data' and choose 'Make Alias'. Now drag this alias out of the application, somewhere easy to find, on your Desktop for example.

Then, next time you need to open a file from within the Overgrowth package, simply navigate to the alias and you should have access to the Contents of the Data folder.

===It says on the forums/blog that you can right click with command+click, but it won't work!===
Unfortunately in recent alphas this functionality has been broken. Right clicking is currently only possible with an external mouse, or on a trackpad with enabled two-finger right click.

==Linux==
===Running Overgrowth on Linux===
Currently there is no native Linux version of Overgrowth, but it's comming<ref>[http://forums.wolfire.com/viewtopic.php?f=13&t=6044]</ref>. However, you may be able to emulate the Windows version under [http://www.winehq.org/ Wine]. This will also require the Visual C++ 2005 libraries, which can be installed through [http://wiki.winehq.org/winetricks winetricks].

[[Category:Secret_Preorder_Forum]]

Custom Decals

2009-11-21T01:55:22Z

Cody:

Tutorial on how to create and import custom decals into Overgrowth:
* http://forums.wolfire.com/viewtopic.php?f=13&t=5064&p=82123&hilit=custom+texture#p82123

[[Category:Overgrowth]]

Making New Models & Textures

2009-11-21T01:55:18Z

Cody:

'''This tutorial does not contain all the links and pictures it should yet.'''

This tutorial is based on jo-shadow's tutorial [http://forums.wolfire.com/viewtopic.php?f=13&t=4712 ''How to make your own models for OG''].

This tutorial will teach you everything you need to know to make your own objects and how to get them into the game.

Please keep in mind that this method is by no means the only way of making and adding Objects. It is merely one of very many ways, but doing it this way should be easy to learn and understand for anyone. Some experience with 3D programs would help, but even the most inexperienced beginner should be able to get results with this guide.

== What you will learn ==

This tutorial will cover how to do the following:

* Creating a 3D model.
* UV mapping the model.
* Generating a texture from the UV data.
* Editing the texture.
* Changing the reflectivity of the texture.
* Making a normal map for the texture.
* Setting up the folder.
* Making the XML file.
* Testing the object in the engine.

== What you will need ==

You will need the following for this tutorial:
* A 3D modeling program with simple UV mapping capabilities.
** This tutorial will use [http://en.wikipedia.org/wiki/Wings3d Wings3D], an open source, cross platform polygonal modeler. It is much simpler when it comes to features than [http://en.wikipedia.org/wiki/Blender_(software) Blender] or other major 3D packages, but it should be much easier to learn for beginners.
** If you prefer blender or another program the basic concepts are the same, but this tutorial only covers Wings3D.
* An image editor.
** This tutorial will use [http://en.wikipedia.org/wiki/Photoshop Photoshop], however any image editor will work just fine. As a free, cross-platform alternative I would suggest using [http://en.wikipedia.org/wiki/GIMP GIMP].
* A text editor.
** Any will do. Mac users can use [http://en.wikipedia.org/wiki/Textedit Textedit] and Windows users [http://en.wikipedia.org/wiki/Notepad_(Windows) Notepad].
* The latest [http://blog.wolfire.com/category/alpha/ Overgrowth alpha].
** This tutorial was originally written for and tested on [http://forums.wolfire.com/viewtopic.php?f=13&t=4701 alpha 16].

Please make sure that you have these necessary programs before you start.

== Getting started ==

It is advised, but not necessary, that you first take a look at the [http://internap.dl.sourceforge.net/sourceforge/wings/wings3d_manual1.6.1.pdf Wings3D manual] to help you become comfortable with its interface. It contains some very quick and easy tutorials that will teach you everything you need to know for this tutorial and then some.

Here are some quick Wings3D basics:
* Go into ''Edit -> Preferences''
** Check ''Force Axis-Aligned Ortho''. This will make editing along an axis easier.
** Single-button Mac users should in the ''Camera'' tab select the one button control mode.
* Change between ''Vertex'', ''Edge'', ''Face'' and ''Object'' mode by pressing the buttons on the top bar or the keystrokes: '''V''', '''E''', '''F''' and '''B''' respectively
* Select stuff by clicking on it.
* Deselect with space.
* Focus the view on what you have selected by pressing '''A'''.
* Reset the view with '''R'''.
* Right clicking (control + click will from now on by implied for Macs as right click) brings up a context-dependent drop-down menu. Its contents changes depending on what you have selected. This is where most of the features we will use are located.
* For most of the keyboard shortcuts look under ''Help -> Defined Hotkeys''.

So without further ado, let's begin.

== Creating a 3D model ==

Because it has been so widely requested in the [SPF], and for the sake of simplicity, in this tutorial we will make a simple textured 3D cylinder. However, taking it a step further to more advanced models should not be a problem.

[[Image:Model_4.png|200px|thumb|right|Our finished cylinder.]]
# Open Wings 3D
# Right click anywhere and choose ''Cylinder'' from the drop-down menu ([[Media:Model_1.png|picture]]). This will spawn a default 16-sided cylinder, to spawn a customized cylinder press the little box on the same line instead. We will now change the proportions of the cylinder to our liking.
# Go into object mode ('''B''') and select the cylinder ([[Media:Model_2.png|picture]]).
# Right click anywhere to open the drop-down menu and select ''Scale -> Radial Y'' ([[Media:Model_3.png|picture]]).
# Now drag the mouse side to side to change the width of the cylinder. Click once it is scaled to your liking to accept, or press tab to manually input a value.
# For the purpose of this tutorial our cylinder model is now finished.

Now we need to generate a UV map for the object so we can texture it.

=== UV Mapping the model ===

When you want to apply a texture to a 3D model, you might run into some problems. The best way we know how to deal with textures is as a 2D image, but how do we take a 3D model, and make a 2D image out of it? Well let's imagine that we have an orange painted like a globe like this:

[[Image:Globe_1.png]]

And we want to make its surface flat kinda like this:

[[Image:Globe_2.png]]

The solution is we peel away the surface, cutting it in a certain way so that it lies flat:

[[Image:Globe_3.png]]

Please note that there are many ways of doing this, but some work better than others. For example one of the more accurate ways of doing this with the earth is what's known as ''Fuller's Projection'':

[[Image:Globe_4.png]]

([http://earthvoyage.googlepages.com/UNFOLD.MOV Click for animation])

This is what we have to do with our cylinder: We have to cut it up so that we can lay it flat on a 2D plane.

Each vertex of the model, which already has a 3D coordinate of (X,Y,Z) will now also have a 2D coordinate on this special plane, so that we know how to fit the texture onto our object. This 2D coordinate is defined as (U,V), which is why this is called [http://en.wikipedia.org/wiki/Uv_mapping UV mapping]. This is a simplified way of describing UV mapping, but for this tutorial it will do.

''Note: there are other methods for applying textures to models, but this guide only covers UV mapping.''

# Select the entire object, and at the bottom of the drop-down menu choose ''UV Mapping -> Direct''. A new window with the object will pop up with a title of ''AutoUV Segmenting''.
PICTURE

and the name of your object:
PICTURE

Now we have to Divide the object into different shapes so that it can unfold it properly, just like in the globe example.
This can be done Automatically or Manually. For the sake of practice let's do it by hand:
You can separate different pieces either by marking which edges to cut, by coloring the faces that should go together, or both.

# In face mode (F) select the top Face and press 'i' (select similar) so both the top and bottom are selected.
Choose one of the nine colors Labeled AuvChart1-9 from the drop-down menu. Doing so will mark these faces as being separate from the rest of the model.

# Clear your selection with space, and select one of the vertical side pieces.
Select the rest by selecting similar (i), then mark these with a different color.

# Because the cylindrical part of the model is still in a loop we need to mark a cut.
In Edge mode (E) select of the vertical edges and choose 'mark edges for cut' from the drop down menu.

# The marking of your model is now complete, and it is ready to be unfolded.
Choose Continue->Unfolding from the drop down menu

# A window showing the unfolded model will open up. This is the UV map.
To show what part of the UV map belongs to what part of the model, there is a colorful grid and letter pattern that you can also see on your model. When you Select a face you see it on both the model and the UV map.

You can also scale and move parts of the model around on the UV map, and the changes will be apparent on the model. Making a face take up more of the UV map will make give it a denser more detailed texture. This is often used to make important features of a model more detailed, like the hands and dace of a character.

If for whatever reason you don't like how the unfolding ended up you can select your object, and in the drop down menu Choose UV Mapping-> Force Segment (delete previous) to start from a clean slate.

It's important to note that there can be many different ways of cutting an object and the resulting UV maps can look very different.

There are two automated methods, Projection and Feature Detection:
UV_5.png (12.56 KiB) Viewed 597 times

Depending on your model one might be better than the other, sometimes they both suck and you have to do it manually, and sometimes if your model is simple like this one they will both give you the same result.

If you cut the object in weird ways it will end up unfolding weirdly, like this for example:
PICTURE

Once again, the best way to understand how this works is to experiment and try out the various features.

Although there are many different ways of mapping any Model, as a rule you want its faces to use the UV space as efficiently as possible, because any texture that isn't under the mapped Faces will not be seen anywhere when the texture is applied.

There are entire programs devoted simply to finding the best way to generate the UV map for any given model, and the tools wings3D provides are much more basic. However they are sufficient for a simple object like this.
With practice you can even manage more complex ones.

Now that We've Finished UV mapping let's generate the texture for the model. Rest assured, the hardest part is done.

Generating a texture from the UV Data

We have our lovely UV map, and now we need to generate a texture we can then edit.

# With the UV map Window still open, choose 'Create Texture' from the drop-down menu. A small window will pop up:

Choose a size depending on how big the object will end up being, and how detailed you want it to be. The larger the image, the more detailed the texture will look on the model.
It wouldn't make sense to have a super-high detailed texture for a fork, and you wouldn't want a low quality texture for a skyscraper either. For this object 512x512 will work just fine.

# Because we want to edit this texture manually later we need to know where on the texture the edges of the object are, so we know where on the object we are drawing.
Set the first as 'Background' and the second as 'Draw Edges' so the edges appear on the texture. Press OK.

# It might seem like the UV map disappeared, but don't fear, the texture was created and is now applied to the object. You simply cannot see it well because it is white with black lines that are right under the wire-frame. You can tell when you zoom in really closely:

# Export the model by going into File -> Export -> Wavefront (.obj)

Then make a new folder in a location of your choosing and save it as whatever title you like.
It will save a .obj and a .mtl file. Delete the .mtl file. It has to do with materials that we don't need.

# Sometimes the texture is saved along with the object, but sometimes it isn't. If there is no texture file in the folder you exported to, go into Window->Outliner, and locate the texture:
PICTURE

Right click it, Choose export and save it in the same folder as the obj, name it whatever you want, preferably the name of your object plus _Color.
For example:

Texture_5.png (13.25 KiB) Viewed 582 times

You are now done with Wings3D!

== Editing the texture ==

Now it's time to get creative!

# Load the Texture file into whichever image editing program of your choice

# Create your actual texture now however you wish. It helps to keep your 'Template' in a separate layer than the texture you want to be on your object.

Here is one way of doing it in photoshop, that allows you to keep the Template's lines above your texture for reference:

* Double click the layer name and accept the pop up prompt to unlock it.
* Rename the layer "template".
* Create two layers bellow it, the lower one called background, the upper one called texture.
* Fill The background layer with white and lock it.
Image_2.png (19.76 KiB) Viewed 579 times

* Select the Template layer, which is above all the other layers, and set its layer mode to multiply.
Image_3.png (37.59 KiB) Viewed 580 times

This will make the white in it transparent, and the black remain as an overlay. you can use it as a guide. lock it as well.
* Draw in the texture layer to your heart's content.

I just used some stock photography I found online. The area with the red text is wasted space that could have been better managed when I made the UV map. It will not appear on the final Model, but will take up space in memory none-the-less.

Here is my finished texture:
Image_5.png (326.33 KiB) Viewed 578 times

Once done, make sure to save the image -without- the Template, unless you want it as part of the final Texture. Don't worry too much about what format you save it as. Thanks to the built in image converter almost any file type will work in the engine. I personally would advise you to use .tga or .png.

=== Changing the Reflectivity of the texture ===

If you were to use this texture as it is, the resulting object would look very shiny.
That is because Phoenix will set the reflectivity, or inherent 'shininess' of an object depending on the transparency, or alpha value of the texture.

If you want your object to look more matte you need to add transparency to your texture. There are several ways to do this:

The Simple way:
* This method will make the whole texture less shiny:
* Look in the Layer window and change the Opacity of the Layer that contains your texture.
Reflect_1.png (15.61 KiB) Viewed 576 times

* You're done. Save the texture, but make sure that the format you save it as supports Transparency. .tga and .png both do.

The Advanced way:
* This method will allow you to change the shininess of different parts of the texture.
* Find the Channel window. You should see 3 channels, Red, Green and Blue (RGB is simply the sum of all 3):
Reflect_2.png (15.26 KiB) Viewed 575 times

* Add a new Channel (the icon next to the trashcan) By default this is an Alpha Channel.
Reflect_3.png (15.46 KiB) Viewed 570 times

* Like all channels it is black and white. Black is Transparent, and will make the object matte, and White is Opaque, and will make the object reflective.
* If you show the rest of the channels while the alpha channel is visible the parts that are hidden will appear red by default:
* When Finished save the file, but make sure to save it as .tga The alpha layer will -not- be saved if you choose .png

=== Making a normal map for the texture ===

This tutorial does not yet include Instructions for making a normal map. Until someone writes it up, just use the following blank normal map:
blanknormal.png (5.36 KiB) Viewed 566 times

== Setting up the folders ==

Phoenix, Overgrowth's engine uses XML files to tell it where an object's files are located.
These XML files are by default located in Data/Objects. For example the Rock1a.xml file:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Models/Environments/Rocks/Rock1a.obj</Model>
<ColorMap>Data/Textures/Environments/Rocks/Rock1_Color.tga</ColorMap>
<NormalMap>Data/Textures/Environments/Rocks/Rock1_NormalOS.tga</NormalMap>
<ShaderPath>Data/GLSL/cubemapobj</ShaderPath>
<ShaderName>normalmap</ShaderName>
</Object>
</pre>

The way the file works is self explanatory. The tags indicate what the provided file path points to. As you can see all the file paths have Data as their root. Because of this you'll want your files to be inside the Data folder.

For mac users right click the Alpha, click 'Show Package Contents', Contents->Data. For easy access then drag it into your Sidebar:
Folder_1.png (46.58 KiB) Viewed 563 times

Until the team implements a more elegant solution I suggest that in the Data folder you make a folder called Custom and keep all your files in there. I chose to imitate the file structure in Custom that the Data folder uses by default:
PICTURE

However you can save it any way you choose. If you want to share your Objects with others it is be best to keep all the files in one Folder inside Data/Custom. ultimately in the engine it doesn't make a difference, as long as the XML file is defined correctly

== Making the XML file ==

Now that everything is in the right place you can make the xml Object file.
# Copy any .xml file from the Objects Folder, paste it into your custom folder and rename it as whatever you want. make sure to keep the extension ".xml"
# Open the XML file with a text editor and change the paths to match that of your file.
Here's mine:

<pre>
<?xml version="1.0" ?>
<Object>
<Model>Data/Custom/Models/Demo/Cylinder.obj</Model>
<ColorMap>Data/Custom/Textures/Demo/Cylinder_Color.png</ColorMap>
<NormalMap>Data/Custom/Textures/Demo/Blank_Normal.png</NormalMap>
<ShaderPath>Data/GLSL/cubemap</ShaderPath>
<ShaderName>cubemap</ShaderName>
</Object>
</code>
</pre>

I don't quite know how the shaders work, but I tested each out and listed them here.
Cubemap will work best for most objects.

== Testing the object in the engine ==

Now the moment you've been waiting for:

# Start up the Latest Alpha
# Click the first Button in the toolbar
# Find your .xml object file and click Open
# Pray that you've done everything right and click on the terrain
# Breathe a sigh of relief as your object appears:

The above Object uses a texture without transparency and so looks shiny.

This Object uses a texture with transparency and so has matte areas:

If you get an error message saying that a file cannot be found make sure that the file-paths in the XML Object file are correct.

Here is the final Custom Folder which I made for this tutorial. It contains two objects: one with changed reflectivity, and one without.

FILE

unzip it, make sure the resulting folder is called 'Custom" (otherwise the xml file paths would be incorrect) and place it in the Data folder.

(Notice that I actually did a bad job with the UV mapping, because I chose to automate it and not do it manually, and the texture is not a continuous band, but broken up into 4 parts.)

== Conclusion ==

I really hope that this Guide will be helpful to you.
A-lot of thought and effort went into it, plus at least a good 5+ hours of work

One thing I cannot stress enough is that this guide is by no means perfect, and there are likely better ways of doing this.

My challenge to you is to not just use this guide, but expand on it: Try texturing a sphere, a rock, a Tree, never stop experimenting. Apply what you've learned here and use it to help you make some great content for this game.

If you have ''any'' questions or problems when trying to recreate what is illustrated here, please feel free to ask the friendly people in our [http://www.wolfire.com/irc IRC channel].

== Other Resources ==

LINKS

[[Category:Overgrowth]]

Custom Terrain

2009-11-21T01:55:05Z

Cody:

Tutorials on how to create and import your custom terrain into Overgrowth. The two tutorials cover two entirely different approaches.
* [http://forums.wolfire.com/viewtopic.php?f=13&t=4732 How to make your own Terrains for OG - Crash Course]
* [http://forums.wolfire.com/viewtopic.php?f=13&t=5457 Custom Terrain Tutorial]

[[Category:Overgrowth]]

Overgrowth Map Editing

2009-11-21T01:50:09Z

Cody:

Overgrowth features a set of tools that can be used to modify the game.

The current alpha version allows the user to:
* Place and transform [[models]] and [[decals]].
* Place [[hotspots]] to trigger [http://en.wikipedia.org/wiki/Javascript JavaScript] files.
* Modify the [[lighting]].
* [[Rigging Editor|Rig]] and [[Animation Editor|animate]] any model
Apart from the functionality built into the editor, there are some other, more advanced ways of modifying the game by importing new [[Custom_Terrain|terrain]], [[Custom_Models_%26_Textures|models]] or UIs for example. Look under the ''Modding Overgrowth'' headline [[Overgrowth|here]] for that.

== Getting Started ==
* [[Introduction to Editing in Overgrowth]] - An introduction to the basic principles of map editing in Overgrowth.
* [[Overgrowth Controls]] - How to use the mouse and keyboard to navigate and manipulate objects.

== Reference ==
* [[Toolbars]]
* [[Tools]]
* [[Hotkeys]]

== Misc ==
* [[Known Bugs]]

[[Category:Overgrowth]]

Template:Overgrowth Portal Header

2009-11-13T22:44:25Z

Cody:

<noinclude>{{CT|Templates}} {{CT|Wiki Navigation}} {{CT|Overgrowth Templates}}</noinclude>{{Portal Header
| width=450
| image=Overgrowth_Header.png
| title1= Welcome to the Overgrowth Portal!
| title2= Click [[Main_Page|Here]] to return to the Main Page.
| contents= Here you will find everything related to Overgrowth!
| linklist= [http://www.wolfire.com/overgrowth Overgrowth Homepage] • [http://forums.wolfire.com/viewforum.php?f=13 SPF] • [http://www.wolfire.com/contact Help]
| pagenumbers= [[:Category:Overgrowth | {{PAGESINCAT:Overgrowth}}]] pages since November 2009.
}}

Template:Overgrowth Portal Header

2009-11-13T22:43:48Z

Cody:

<noinclude>{{CT|Templates}} {{CT|Wiki Navigation}} {{CT|Overgrowth Templates}}</noinclude>{{Portal Header
| image=Overgrowth_Header.png
| title1= Welcome to the Overgrowth Portal!
| title2= Click [[Main_Page|Here]] to return to the Main Page.
| contents= Here you will find everything related to Overgrowth!
| linklist= [http://www.wolfire.com/overgrowth Overgrowth Homepage] • [http://forums.wolfire.com/viewforum.php?f=13 SPF] • [http://www.wolfire.com/contact Help]
| pagenumbers= [[:Category:Overgrowth | {{PAGESINCAT:Overgrowth}}]] pages since November 2009.
}}