Add new art to the client - Revision history

Talad at 17:44, 4 November 2013

2013-11-04T17:44:49Z

← Older revision		Revision as of 17:44, 4 November 2013
Line 77:		Line 77:
	Usage: ccheck(.exe) -path=/this/path/to/directory/		Usage: ccheck(.exe) -path=/this/path/to/directory/
	</code>		</code>


			=== file locations after ccheck ===

			Example stonecave

			meshes.zip:
			_auto_stonecave_stonefloor:
			<meshfact name="_auto_stonecave_stonefloor">

			bindata/
			_auto_stonecave_stonefloor_n
			_auto_stonecave_stonefloor_submesh1_0_i
			_auto_stonecave_stonefloor_submesh1_i
			_auto_stonecave_stonefloor_tc
			_auto_stonecave_stonefloor_v

			materials.zip
			lava5.mng
			lightmaps/
			stonecave_0.png
			stonecave_1.png
			...

			world.zip:
			stonecave (world file)
			<meshobj name="stonecave_stonefloor">
			...
			<renderbuffer file="bindata/stonecave_stonefloor_lm" name="texture coordinate lightmap" />
			...
			bindata\stonecave_stonefloor_lm

Talad: /* Adding new art */

2013-11-02T15:13:57Z

Adding new art

← Older revision		Revision as of 15:13, 2 November 2013
Line 2:		Line 2:

	There are two separate topics related to adding new art to the PlaneShift Engine:		There are two separate topics related to adding new art to the PlaneShift Engine:
	* Creating new art		# Creating new art
	* Packaging the art with the client and server		# Packaging the art with the client and server

	For the first point please refer to this page: [[Creating Art and mods]]		For the first point please refer to this page: [[Creating Art and mods]]

Talad: /* Adding new art */

2013-11-02T15:13:02Z

Adding new art

← Older revision		Revision as of 15:13, 2 November 2013
Line 2:		Line 2:

	There are two separate topics related to adding new art to the PlaneShift Engine:		There are two separate topics related to adding new art to the PlaneShift Engine:
	1) Creating new art		* Creating new art
	2) Packaging the art with the client and server		* Packaging the art with the client and server

	For the first point please refer to this page: [Creating Art and mods]		For the first point please refer to this page: [[Creating Art and mods]]

	For the second topic you can continue to read this page.		For the second topic you can continue to read this page.

Talad: /* ccheck */

2013-10-31T13:23:44Z

ccheck

← Older revision		Revision as of 13:23, 31 October 2013
Line 53:		Line 53:
	Then we just have to zip each one and move the files to the client art/ directory.		Then we just have to zip each one and move the files to the client art/ directory.

	=== ccheck ===		=== ccheck reference ===

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

Talad: /* Overview */

2013-10-31T13:23:29Z

Overview

← Older revision		Revision as of 13:23, 31 October 2013
Line 34:		Line 34:
	...		...

	When we want to package a release, the first steps is to zip the content of the dirs, please note "npcroom1.zip" below is a zip file, same for the others.		When we want to package a release, the first steps is to zip the content of the dirs above and place all zip files in a single directory, please note "npcroom1.zip" below is a zip file, same for the others.

	/planeshift/trunk/		/planeshift/trunk/
	~~art/~~		artin/
	~~world~~/
	npcroom1.zip		npcroom1.zip
	akkaio.zip		akkaio.zip
	...		...
	~~things/~~
	weapons.zip		weapons.zip
	potions.zip		potions.zip
	...		...

			Then we launch the ccheck program to package the art in the final form. Please note the two directories HAVE to exist or it will not work.

			./ccheck -in=/this/artin/ -out=/this/artout/ -process

			This will create inside artout/ three directories: materials, meshes, world.

			Then we just have to zip each one and move the files to the client art/ directory.

	=== ccheck ===		=== ccheck ===

Talad: Created page with "== Adding new art == There are two separate topics related to adding new art to the PlaneShift Engine: 1) Creating new art 2) Packaging the art with the client and server Fo..."

2013-10-31T13:16:08Z

Created page with "== Adding new art == There are two separate topics related to adding new art to the PlaneShift Engine: 1) Creating new art 2) Packaging the art with the client and server Fo..."

New page

== Adding new art ==

There are two separate topics related to adding new art to the PlaneShift Engine:
1) Creating new art
2) Packaging the art with the client and server

For the first point please refer to this page: [Creating Art and mods]

For the second topic you can continue to read this page.

=== Overview ===

To check if the art provided by the artists is in the correct format, the best way is to open it with Viewmesh and Walktest (both are included in the standard CS distribution).

At PlaneShift the art assets are stored unzipped in a standard directory tree, until we have to package a new release. Please note the "characters.zip" below is actually a directory, named "characters.zip", same for the others.

/myartrepo/
characters.zip/
dermf.zip/
dermf.cal3d
dermf_arm.dds
dermf_attack.CAF
...
enkif.zip/
enkif.cal3d
...
...
things/
weapons.zip/
doubleaxe01a.meshfact
doubleaxe01a.dds
doubleaxe01a_icon.dds
...
...

When we want to package a release, the first steps is to zip the content of the dirs, please note "npcroom1.zip" below is a zip file, same for the others.

/planeshift/trunk/
art/
world/
npcroom1.zip
akkaio.zip
...
things/
weapons.zip
potions.zip
...

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