PSwiki - User contributions [en]

Tools pipeline

2013-09-01T10:34:08Z

Apalazzi: /* Levels */

__NOTOC__

== Overview ==

This page has been created to list the '''tested''' tool chain for every path in art. It's important to note that this page lists what has been tested with real models starting from the 3d tool up to addition in game. '''This guide needs to be updated!'''

== Characters ==

New characters follow the table below. Existing characters with a rig and animation have to be edited in the application they have been built originally.

=== Geometry + UV ===

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

Blender
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d cmf
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

3dsmax -> cal3d cmf in game

=== Rigging + Animations ===

PlaneShift uses CAL3D as animation library. So all rigging/animation made for PlaneShift need to be then exported to CAL3D.

==== Maya ====

Not supported.

==== Blender ====
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d caf -> in game
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

Note: the 2.6x exporter needs a patch to work on latest Blender (to be provided); moreover it seems that the binary format is obsolete or somehow broken, so you have to export as xml then conver to binary with the converter in the miniviewer zip.

==== 3DSMax ====

3dsmax -> (using the cal3d exporter) -> cal3d caf in game

==== Notes ====

It seems that the PS engine only understands cal3d binary format (caf, csf, ...) and not xml formats (.xaf, .xsf, etc.)
Convert your XAF, XMF, XSF, ... to Cxx format with [http://www.planeshift.it/download/prospects/cal3d_converter_cal3d_010.zip Cal3d binary converter]

To view your models exported in CAL3D format, you need the "miniviewer" program.

[[File:Tools.png]] Miniviewer for [http://www.planeshift.it/download/prospects/cal3d_miniviewer_svn_507.zip Windows], for Linux (?), for MacOSX (?)

== Items ==

Existing items can easily be ported to different tools with obj format and edited.

Items which needs to be rigged/weighted with the character follow the same rules of the chapter "Characters" above. Examples: A sword, a helmet, a bracer are not rigged with the character. A hair set, a robe, a plate mail torso are rigged with the character.

=== Geometry + UV ===

==== Maya ====

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

==== Blender ====

Blender (2.68, with other versions YMMV) -> [https://svn.code.sf.net/p/crystal/code/CS/trunk/scripts/blender/ io_scene_cs] -> crystal space

Blender (including blender 2.5x) -> obj -> 3dsmax

Blender2.49 -> blend2cs -> meshfact (not supported on blender 2.5x but under developpement by CS team)

==== 3dsmax ====

3dsmax -> maxscript exporter -> meshfact in game

== Levels ==

Existing levels should be edited in the original application those were built in. It's possible to export in obj a part of the level and have it edited in another tool, then import it back, but this process is not preferred.

=== Geometry + UV ===

Maya -> obj -> 3dsmax -> maxscript exporter -> world in game

Blender(including blender 2.5x) -> obj -> 3dsmax -> maxscript exporter -> world in game

3dsmax -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/max/ maxscript exporter]] -> world in game

Blender -> [https://svn.code.sf.net/p/crystal/code/CS/trunk/scripts/blender/ io_scene_cs] -> world

Documentation on how to use it is [http://www.crystalspace3d.org/docs/online/manual/Blender.html here].

After exporting the world file you'll need to rename it to the name area in Planeshift; you'll also need to move the definitions of the materials and textures into materials/materials.cslib , and move the ''textures'' directory under ''materials'' directory or zipfile.

=== Dynamic Lights ===

Dynamic lights are the ones for the crystal and for lanterns that change intensity during the day based on the time change or an event.

Those are exported in a PS specific XML format.

Maya -> not supported

Blender 2.49-> not tested

Blender 2.5x-> Not supported

3dsmax -> maxscript for lights -> world in game

Tools pipeline

2013-09-01T10:30:22Z

Apalazzi: /* Items */

__NOTOC__

== Overview ==

This page has been created to list the '''tested''' tool chain for every path in art. It's important to note that this page lists what has been tested with real models starting from the 3d tool up to addition in game. '''This guide needs to be updated!'''

== Characters ==

New characters follow the table below. Existing characters with a rig and animation have to be edited in the application they have been built originally.

=== Geometry + UV ===

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

Blender
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d cmf
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

3dsmax -> cal3d cmf in game

=== Rigging + Animations ===

PlaneShift uses CAL3D as animation library. So all rigging/animation made for PlaneShift need to be then exported to CAL3D.

==== Maya ====

Not supported.

==== Blender ====
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d caf -> in game
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

Note: the 2.6x exporter needs a patch to work on latest Blender (to be provided); moreover it seems that the binary format is obsolete or somehow broken, so you have to export as xml then conver to binary with the converter in the miniviewer zip.

==== 3DSMax ====

3dsmax -> (using the cal3d exporter) -> cal3d caf in game

==== Notes ====

It seems that the PS engine only understands cal3d binary format (caf, csf, ...) and not xml formats (.xaf, .xsf, etc.)
Convert your XAF, XMF, XSF, ... to Cxx format with [http://www.planeshift.it/download/prospects/cal3d_converter_cal3d_010.zip Cal3d binary converter]

To view your models exported in CAL3D format, you need the "miniviewer" program.

[[File:Tools.png]] Miniviewer for [http://www.planeshift.it/download/prospects/cal3d_miniviewer_svn_507.zip Windows], for Linux (?), for MacOSX (?)

== Items ==

Existing items can easily be ported to different tools with obj format and edited.

Items which needs to be rigged/weighted with the character follow the same rules of the chapter "Characters" above. Examples: A sword, a helmet, a bracer are not rigged with the character. A hair set, a robe, a plate mail torso are rigged with the character.

=== Geometry + UV ===

==== Maya ====

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

==== Blender ====

Blender (2.68, with other versions YMMV) -> [https://svn.code.sf.net/p/crystal/code/CS/trunk/scripts/blender/ io_scene_cs] -> crystal space

Blender (including blender 2.5x) -> obj -> 3dsmax

Blender2.49 -> blend2cs -> meshfact (not supported on blender 2.5x but under developpement by CS team)

==== 3dsmax ====

3dsmax -> maxscript exporter -> meshfact in game

== Levels ==

Existing levels should be edited in the original application those were built in. It's possible to export in obj a part of the level and have it edited in another tool, then import it back, but this process is not preferred.

=== Geometry + UV ===

Maya -> obj -> 3dsmax -> maxscript exporter -> world in game

Blender(including blender 2.5x) -> obj -> 3dsmax -> maxscript exporter -> world in game

3dsmax -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/max/ maxscript exporter]] -> world in game

Blender -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/blender/ blender2cs]] -> world in game (needs to be tested) Documentation on how to use it is [http://www.crystalspace3d.org/docs/online/manual/Blender.html here].

=== Dynamic Lights ===

Dynamic lights are the ones for the crystal and for lanterns that change intensity during the day based on the time change or an event.

Those are exported in a PS specific XML format.

Maya -> not supported

Blender 2.49-> not tested

Blender 2.5x-> Not supported

3dsmax -> maxscript for lights -> world in game

Tools pipeline

2013-08-31T18:18:16Z

Apalazzi: /* Items */

__NOTOC__

== Overview ==

This page has been created to list the '''tested''' tool chain for every path in art. It's important to note that this page lists what has been tested with real models starting from the 3d tool up to addition in game. '''This guide needs to be updated!'''

== Characters ==

New characters follow the table below. Existing characters with a rig and animation have to be edited in the application they have been built originally.

=== Geometry + UV ===

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

Blender
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d cmf
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

3dsmax -> cal3d cmf in game

=== Rigging + Animations ===

PlaneShift uses CAL3D as animation library. So all rigging/animation made for PlaneShift need to be then exported to CAL3D.

==== Maya ====

Not supported.

==== Blender ====
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d caf -> in game
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

Note: the 2.6x exporter needs a patch to work on latest Blender (to be provided); moreover it seems that the binary format is obsolete or somehow broken, so you have to export as xml then conver to binary with the converter in the miniviewer zip.

==== 3DSMax ====

3dsmax -> (using the cal3d exporter) -> cal3d caf in game

==== Notes ====

It seems that the PS engine only understands cal3d binary format (caf, csf, ...) and not xml formats (.xaf, .xsf, etc.)
Convert your XAF, XMF, XSF, ... to Cxx format with [http://www.planeshift.it/download/prospects/cal3d_converter_cal3d_010.zip Cal3d binary converter]

To view your models exported in CAL3D format, you need the "miniviewer" program.

[[File:Tools.png]] Miniviewer for [http://www.planeshift.it/download/prospects/cal3d_miniviewer_svn_507.zip Windows], for Linux (?), for MacOSX (?)

== Items ==

Existing items can easily be ported to different tools with obj format and edited.

Items which needs to be rigged/weighted with the character follow the same rules of the chapter "Characters" above. Examples: A sword, a helmet, a bracer are not rigged with the character. A hair set, a robe, a plate mail torso are rigged with the character.

=== Geometry + UV ===

==== Maya ====

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

==== Blender ====

Blender (2.68, with other versions YMMV) -> io_scene_cs -> crystal space

Blender (including blender 2.5x) -> obj -> 3dsmax

Blender2.49 -> blend2cs -> meshfact (not supported on blender 2.5x but under developpement by CS team)

==== 3dsmax ====

3dsmax -> maxscript exporter -> meshfact in game

== Levels ==

Existing levels should be edited in the original application those were built in. It's possible to export in obj a part of the level and have it edited in another tool, then import it back, but this process is not preferred.

=== Geometry + UV ===

Maya -> obj -> 3dsmax -> maxscript exporter -> world in game

Blender(including blender 2.5x) -> obj -> 3dsmax -> maxscript exporter -> world in game

3dsmax -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/max/ maxscript exporter]] -> world in game

Blender -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/blender/ blender2cs]] -> world in game (needs to be tested) Documentation on how to use it is [http://www.crystalspace3d.org/docs/online/manual/Blender.html here].

=== Dynamic Lights ===

Dynamic lights are the ones for the crystal and for lanterns that change intensity during the day based on the time change or an event.

Those are exported in a PS specific XML format.

Maya -> not supported

Blender 2.49-> not tested

Blender 2.5x-> Not supported

3dsmax -> maxscript for lights -> world in game

Tools pipeline

2013-08-31T18:17:34Z

Apalazzi: /* Items */

__NOTOC__

== Overview ==

This page has been created to list the '''tested''' tool chain for every path in art. It's important to note that this page lists what has been tested with real models starting from the 3d tool up to addition in game. '''This guide needs to be updated!'''

== Characters ==

New characters follow the table below. Existing characters with a rig and animation have to be edited in the application they have been built originally.

=== Geometry + UV ===

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

Blender
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d cmf
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

3dsmax -> cal3d cmf in game

=== Rigging + Animations ===

PlaneShift uses CAL3D as animation library. So all rigging/animation made for PlaneShift need to be then exported to CAL3D.

==== Maya ====

Not supported.

==== Blender ====
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d caf -> in game
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

Note: the 2.6x exporter needs a patch to work on latest Blender (to be provided); moreover it seems that the binary format is obsolete or somehow broken, so you have to export as xml then conver to binary with the converter in the miniviewer zip.

==== 3DSMax ====

3dsmax -> (using the cal3d exporter) -> cal3d caf in game

==== Notes ====

It seems that the PS engine only understands cal3d binary format (caf, csf, ...) and not xml formats (.xaf, .xsf, etc.)
Convert your XAF, XMF, XSF, ... to Cxx format with [http://www.planeshift.it/download/prospects/cal3d_converter_cal3d_010.zip Cal3d binary converter]

To view your models exported in CAL3D format, you need the "miniviewer" program.

[[File:Tools.png]] Miniviewer for [http://www.planeshift.it/download/prospects/cal3d_miniviewer_svn_507.zip Windows], for Linux (?), for MacOSX (?)

== Items ==

Existing items can easily be ported to different tools with obj format and edited.

Items which needs to be rigged/weighted with the character follow the same rules of the chapter "Characters" above. Examples: A sword, a helmet, a bracer are not rigged with the character. A hair set, a robe, a plate mail torso are rigged with the character.

=== Geometry + UV ===

==== Maya ====

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

==== Blender ====

Blender (2.68, with other versions YMMV) -> io_export_cs -> crystal space

Blender (including blender 2.5x) -> obj -> 3dsmax

Blender2.49 -> blend2cs -> meshfact (not supported on blender 2.5x but under developpement by CS team)

==== 3dsmax ====

3dsmax -> maxscript exporter -> meshfact in game

== Levels ==

Existing levels should be edited in the original application those were built in. It's possible to export in obj a part of the level and have it edited in another tool, then import it back, but this process is not preferred.

=== Geometry + UV ===

Maya -> obj -> 3dsmax -> maxscript exporter -> world in game

Blender(including blender 2.5x) -> obj -> 3dsmax -> maxscript exporter -> world in game

3dsmax -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/max/ maxscript exporter]] -> world in game

Blender -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/blender/ blender2cs]] -> world in game (needs to be tested) Documentation on how to use it is [http://www.crystalspace3d.org/docs/online/manual/Blender.html here].

=== Dynamic Lights ===

Dynamic lights are the ones for the crystal and for lanterns that change intensity during the day based on the time change or an event.

Those are exported in a PS specific XML format.

Maya -> not supported

Blender 2.49-> not tested

Blender 2.5x-> Not supported

3dsmax -> maxscript for lights -> world in game

Tools pipeline

2013-08-11T16:30:45Z

Apalazzi: /* Rigging + Animations */

__NOTOC__

== Overview ==

This page has been created to list the '''tested''' tool chain for every path in art. It's important to note that this page lists what has been tested with real models starting from the 3d tool up to addition in game. '''This guide needs to be updated!'''

== Characters ==

New characters follow the table below. Existing characters with a rig and animation have to be edited in the application they have been built originally.

=== Geometry + UV ===

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

Blender
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d cmf
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

3dsmax -> cal3d cmf in game

=== Rigging + Animations ===

PlaneShift uses CAL3D as animation library. So all rigging/animation made for PlaneShift need to be then exported to CAL3D.

==== Maya ====

Not supported.

==== Blender ====
* 2.49 -> [http://www.planeshift.it/download/prospects/export_cal3d_py_0.9.zip export_cal3d.py version 0.9] -> cal3d caf -> in game
* 2.5 / 2.6 -> https://github.com/alexeyd/blender2cal3d -> cal3d caf (some testing is needed on this new script)

Note: the 2.6x exporter needs a patch to work on latest Blender (to be provided); moreover it seems that the binary format is obsolete or somehow broken, so you have to export as xml then conver to binary with the converter in the miniviewer zip.

==== 3DSMax ====

3dsmax -> (using the cal3d exporter) -> cal3d caf in game

==== Notes ====

It seems that the PS engine only understands cal3d binary format (caf, csf, ...) and not xml formats (.xaf, .xsf, etc.)
Convert your XAF, XMF, XSF, ... to Cxx format with [http://www.planeshift.it/download/prospects/cal3d_converter_cal3d_010.zip Cal3d binary converter]

To view your models exported in CAL3D format, you need the "miniviewer" program.

[[File:Tools.png]] Miniviewer for [http://www.planeshift.it/download/prospects/cal3d_miniviewer_svn_507.zip Windows], for Linux (?), for MacOSX (?)

== Items ==

Existing items can easily be ported to different tools with obj format and edited.

Items which needs to be rigged/weighted with the character follow the same rules of the chapter "Characters" above. Examples: A sword, a helmet, a bracer are not rigged with the character. A hair set, a robe, a plate mail torso are rigged with the character.

=== Geometry + UV ===

Maya -> obj -> 3dsmax

Maya -> obj -> Blender

Blender (including blender 2.5x) -> obj -> 3dsmax

3dsmax -> maxscript exporter -> meshfact in game

Blender2.49 -> blend2cs -> meshfact (not supported on blender 2.5x but under developpement by CS team)

== Levels ==

Existing levels should be edited in the original application those were built in. It's possible to export in obj a part of the level and have it edited in another tool, then import it back, but this process is not preferred.

=== Geometry + UV ===

Maya -> obj -> 3dsmax -> maxscript exporter -> world in game

Blender(including blender 2.5x) -> obj -> 3dsmax -> maxscript exporter -> world in game

3dsmax -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/max/ maxscript exporter]] -> world in game

Blender -> [[https://crystal.svn.sourceforge.net/svnroot/crystal/CS/trunk/scripts/blender/ blender2cs]] -> world in game (needs to be tested) Documentation on how to use it is [http://www.crystalspace3d.org/docs/online/manual/Blender.html here].

=== Dynamic Lights ===

Dynamic lights are the ones for the crystal and for lanterns that change intensity during the day based on the time change or an event.

Those are exported in a PS specific XML format.

Maya -> not supported

Blender 2.49-> not tested

Blender 2.5x-> Not supported

3dsmax -> maxscript for lights -> world in game

Engine Others

2013-07-24T11:09:33Z

Apalazzi:

== Core information ==

*[[BuildGuide|Build Guide]]
*[[CodingStandards|Coding Standards]]
* [http://www.vaikene.net/planeshift/api/ PlaneShift's API]

== Helper applications ==

=== ccheck ===

''ccheck'' is an helper application to parse, check and rearrange art files:

<code>
~$ ccheck --help
Art Conflict Checker.

This application checks for duplicate meshfact and texture inclusions in art files.

Options:

-in The vfs path to directory to search in. Defaults to /this/ccheck/

-check Whether to do a meshfact conflict check.

-process Whether to process art into a optimal format for bgloader.

-strip Whether to strip data not needed for collision.

-out The vfs path to the directory to output processed art files in. Defaults to /this/ccheckout/

Usage: ccheck(.exe) -path=/this/path/to/directory/
</code>

== Others ==

*[[Links]]
*[[Web Console Design]]

[[Category:Engine documents]]

Creating Art and mods

2013-07-01T18:19:51Z

Apalazzi: /* Overview */

__NOTOC__

== Overview ==

This wiki page has been created to give you detailed information on how to create art for PlaneShift, this goes through the assets needed, the tools and the techniques. Please remember this is a collaborative effort, so EDIT this page if you think you have good information to share!!

This page is only about ''creating'' contents for the game; if you want to add contents to your own server based on the PlaneShift engine see [[Adding_assets_to_a_server|Adding assets to a server]].

== Assets Needed ==

Here is a list of assets you may decide to create and contribute to PlaneShift:
* Screenshots used as advertizing or press material
* Sketches and concept art
* Fan made videos
* Icons
* Textures for existing models
* New 3d items (geometry, UVs, textures) used as props
* Full areas (for example a new cave level)
* Monster or character model (geometry, UV, textures)
* Monsters or character rigging (skeleton/bones setup)
* Monsters or characters animation
* Skins for the game User Interface
* Rendered scenes used as advertizing or press material (example youtube channel)

For each of the items above there are different tools and techniques to use, which we are documented here below.

== Screenshots ==

Taking screenshots of the game seems a simple task, but it's actually very useful. We use screenshots in our "pic of the day", in articles, contact with press and on our web sites. If you want to provide nice screenshots, please do so! You can post your screenshots [http://www.hydlaaplaza.com/smf/index.php?topic=40396.0 here].

Important Notes:
* To take screenshots disable text labels (from the game option menu)
* be sure to use high resolution settings and shader quality in pslaunch options.
* Screenshots from 1024x768 or more are good.
* To save a screenshot you can use the in game command : /screenshot (the image is saved in the %appdata% dir)
* To save a screenshot without the UI use: /screenshot nogui
* If you want to save to high quality no compression PNG use: /screenshot lossless

== Sketches and concept art ==
We definitely need to enrich our world with more buildings, tools, cloths, items, etc... all of them need to be race based. The idea is that each race has a special/unique style and looking at a building you should be able to tell which race created it.

Important Notes:
* Be sure to play the game first and get a feeling of the current art
* Be sure to read the [http://www.planeshift.it/races.html Races page] on main site. There are sketches of their architecture already
* Items, tools, faces, clothes, special characters, weapons, etc.. all are good and useful to us

== Fan made videos ==

We may use fan made videos to spread the word about the game, and what it looks like in game. You should record the videos using an external program, and then edit the video as you wish. There are already a number of fan made videos on youtube, and having more is surely a benefit for advertizing PS. Also if you think your video is great, you can submit it to us to be posted in the [http://www.youtube.com/user/PlaneShiftOfficial Official PlaneShift YouTube channel].

== Icons ==

Quite often we add new items in game and we do not have the time or resources to add new icons to be displayed in the inventory window. In general we tend to reuse existing/similar icons, mainly for quest items. In certain cases a new icon is anyway nice to have because there is no other similar already in game. If you want to create any of those, you can test your icons by opening art/materias.zip in your planeshift folder and checking the files name "*_icon.dds". Please do a backup of that file in case you are modifying it or the updater will find it broken/different and will redownload it all. For information about DDS and DXT compression, see [[Game Textures|this article]].

== Textures for existing models ==

PlaneShift always under development, so any improvement to existing textures is very welcome. The easiest way to redo/improve a texture is to go to your PlaneShift folder, navigate into the "art" directory and open the zip called materials.zip. This file contains all textures of the game. PlaneShift uses DDS format in the released binaries. DDS format is pretty popular amongst game developers, and you can find tools to view them on the web, example [http://developer.nvidia.com/nvidia-texture-tools-adobe-photoshop here]. It's important to note that DDS is a lossy format, so you always work with PNG as source.

You can read [[Game Textures|this article]] for making textures.

== New 3d items ==

To create new 3D items for PlaneShift it's important you need this tool:

[[File:Tools.png]] Viewmesh : for [http://planeshift.it/download/prospects/PlaneShift_Viewmesh507.zip Windows] (Mar 2011) for Linux (?) for MacOSX (?)

Here is a guide on [[How to use Viewmesh]]

You can use any 3d program you wish to create items, as long as the program can export to OBJ format.

See our [[tools pipeline]] document for details.

== Full areas ==

Making a new full area is not an easy task! So we suggest you to start with simpler items first and also to contact us directly discussing which areas you want to create.

In any case to create an area, review our [[tools pipeline]] document.

Also you will need walktest to be able to view the exported level. The level CANNOT be seen directly in PlaneShift client as it requires to be packaged together with all other levels. That's not something you can do by yourself.

[[File:Tools.png]] Walktest : for [http://www.planeshift.it/download/prospects/PlaneShift_Walktest_Viemesh.zip Windows] (Apr 2011) for Linux (?) for [http://www.planeshift.it/download/prospects/PlaneShift_Walktest_macosx.zip MacOSX] (Feb 2012)

== Monster or character model ==

See our [[tools pipeline]] document for details.

== Skins for the game User Interface ==

One good resource for UI changes and skins is [http://greatshift.111mb.de/ GreatShift]

== Rendered scenes ==

Mainly for press, articles and advertizing we need trailers, rendered scenes and videos. Those can be made of existing models or new models. If you are interested in creating such kind of rendered scenes, it's bests if you first contact us, as you will probably need access to the existing models.

Adding assets to a server

2013-06-29T15:06:39Z

Apalazzi: Added premble on vfs.cfg and file format

This page describes the steps necessary to add assets to a private server; it's not possible to add assets to the official Planeshift server if you're not in the developers team.

The process to create such contents is described in the [[Creating Art and mods]] page.

== Preamble ==

The location of the various assets is defined in the file ''vfs.cfg''. By default the resources are grouped toghether in a zip file, and most of the xml files are converted in binary format with CS's docconv utility; however, for better clarity we'll assume in this page that the files are unzipped in an appropriate directory (materials for materials.zip, meshes for meshes.zip, etc).

== Materials (textures) ==

== Items (meshes) ==

== Music ==

== Sound ==

== Effects ==

== Animations ==

== Areas ==

Adding assets to a server

2013-06-29T14:59:13Z

Apalazzi: First draft