S3o using blender - Revision history

Flozi: recat

2013-03-21T10:38:50Z

recat

← Older revision		Revision as of 11:38, 21 March 2013
Line 72:		Line 72:
	* [2] http://www.lastlog.de/misc/s3o-template.zip		* [2] http://www.lastlog.de/misc/s3o-template.zip

	[[Category: ~~Unit_development~~]]		[[Category: 3D Models]]

Mrz: /* Links */

2010-09-11T10:58:59Z

Links

← Older revision		Revision as of 11:58, 11 September 2010
Line 71:		Line 71:
	* [1] http://springrts.com/phpbb/viewtopic.php?f=9&t=17026		* [1] http://springrts.com/phpbb/viewtopic.php?f=9&t=17026
	* [2] http://www.lastlog.de/misc/s3o-template.zip		* [2] http://www.lastlog.de/misc/s3o-template.zip

			[[Category: Unit_development]]

Mrz: /* units/armsolar.fbi: Valid for s3o */

2010-09-11T10:57:50Z

units/armsolar.fbi: Valid for s3o

← Older revision		Revision as of 11:57, 11 September 2010
Line 61:		Line 61:
	=== units/armsolar.fbi: Valid for s3o ===		=== units/armsolar.fbi: Valid for s3o ===
	[UNITINFO] {		[UNITINFO] {
	unitname=armsolar.s3o;		'''unitname=armsolar.s3o;'''
	name=Solar Collector;		name=Solar Collector;
	description=Produces Energy;		description=Produces Energy;

Mrz: /* Valid for s3o */

2010-09-11T10:48:31Z

Valid for s3o

← Older revision		Revision as of 11:48, 11 September 2010
Line 59:		Line 59:
	we have to modify this in order to make it s3o aware with:		we have to modify this in order to make it s3o aware with:

	=== Valid for s3o ===		=== units/armsolar.fbi: Valid for s3o ===
	[UNITINFO] {		[UNITINFO] {
	unitname=armsolar.s3o;		unitname=armsolar.s3o;

Mrz: /* Valid for 3do */

2010-09-11T10:48:19Z

Valid for 3do

← Older revision		Revision as of 11:48, 11 September 2010
Line 48:		Line 48:

	Open the '/mods/modname/units/armsolar.fbi' and you will see:		Open the '/mods/modname/units/armsolar.fbi' and you will see:
	=== Valid for 3do ===		=== units/armsolar.fbi: Valid for 3do ===
	[UNITINFO] {		[UNITINFO] {
	unitname=armsolar;		unitname=armsolar;
Line 58:		Line 58:

	we have to modify this in order to make it s3o aware with:		we have to modify this in order to make it s3o aware with:

	=== Valid for s3o ===		=== Valid for s3o ===
	[UNITINFO] {		[UNITINFO] {

Mrz: /* Deployment & Testing */

2010-09-11T10:47:37Z

Deployment & Testing

← Older revision		Revision as of 11:47, 11 September 2010
Line 42:		Line 42:
	* /mods/modname/unittextures/		* /mods/modname/unittextures/

	* As your first model is a unit replacement, don't forget to modify the unitname.fbi (in case of the 'armsolar' replacement: use armsolar.fbi) and add your model there.		As your first model is a unit replacement, don't forget to modify the unitname.fbi (in case of the 'armsolar' replacement: use armsolar.fbi) and add your model there.
	* /mods/modname/units/armsolar.fbi		* /mods/modname/units/armsolar.fbi

Elvaron: /* Notes on working with the Template */

2010-09-11T10:46:26Z

Notes on working with the Template

← Older revision		Revision as of 11:46, 11 September 2010
Line 27:		Line 27:
	When you start working on the base mesh, remember not to delete the object itself. Go into Edit Mode, select all vertices and delete them. Then add primitives/vertices/... to your empty mesh of the still-valid base object.		When you start working on the base mesh, remember not to delete the object itself. Go into Edit Mode, select all vertices and delete them. Then add primitives/vertices/... to your empty mesh of the still-valid base object.

	After meshing out your model, remember to check if you need to move/scale the empties that you see in the node viewer. The cubic empty sets the ground midpoint of the object, the arrow empty is used for height purposes and the spheric empty defines the model's boundary box.		After meshing out your model, remember to check whether you need to move/scale the empties that you see in the node viewer. The cubic empty sets the ground midpoint of the object, the arrow empty is used for height purposes and the spheric empty defines the model's boundary box.

	== Notes on the export step ==		== Notes on the export step ==

Elvaron: Updated

2010-09-11T10:45:30Z

Updated

← Older revision		Revision as of 11:45, 11 September 2010
Line 1:		Line 1:
	==motivation==		== motivation ==
	~~this~~ guide helps you to create a '.s3o' unit for spring using:		This guide helps you to create a '.s3o' unit for spring using:
	* 'blender' - for 3d moddeling		* 'blender' - for 3d moddeling
	* 'gimp' - for texturing		* 'gimp' - for texturing (or similar tools for 2d art)

	==~~the tools~~==		== The Tools ==
	~~first~~ download/install blender, then install a blender-compatible python version. ~~finally~~ download the exporter for blender, found at [1].		First download/install blender, then install a blender-compatible python version. The command shell window for blender will tell you which version of python it was compiled with, get specifically that version of python. Finally download the exporter for blender, found at [1].

	Once all is installed you can either work from scratch or start working based on a template [2]. if you start from scratch, have a look at [1] to ~~met~~ all requirements for the exporter script.		Once all is installed you can either work from scratch or start working based on a template [2]. If you start from scratch, have a look at [1] to meet all requirements for the exporter script, such as naming conventions and necessary empties.

	== ~~editing~~ and ~~exporting~~ ==		== Editing and Exporting ==
	The parenting system of blender is used to find the chain of children for exporting. Each child must have a unique name which can later be used for rigging.		The parenting system of blender is used to find the chain of children for exporting. Each child must have a unique name which can later be used for rigging.

Line 22:		Line 22:
	**A for transparency (standard ARB shader supports only 1 bit that is: either render the pixel, or not)		**A for transparency (standard ARB shader supports only 1 bit that is: either render the pixel, or not)

	== ~~notes~~ on the export step ==		=== Notes on working with the Template ===
			Everything should be properly configured for export, with necessary empties etc present. If objects are hidden from view for better editing, press ALT+H to unhide all objects.

			When you start working on the base mesh, remember not to delete the object itself. Go into Edit Mode, select all vertices and delete them. Then add primitives/vertices/... to your empty mesh of the still-valid base object.

			After meshing out your model, remember to check if you need to move/scale the empties that you see in the node viewer. The cubic empty sets the ground midpoint of the object, the arrow empty is used for height purposes and the spheric empty defines the model's boundary box.

			== Notes on the export step ==
	The active selection does not influence the exporter therefore you don't need to select any object (still you can) to make a valid export.		The active selection does not influence the exporter therefore you don't need to select any object (still you can) to make a valid export.
	The exporter will loop over all objects in the scene automatically.		The exporter will loop over all objects in the scene automatically.

	Please note that the template you can download from [2] also includes a modified exporter script for blender.		Please note that the template you can download from [2] also includes a modified exporter script for blender that allows it to export the objects even while cameras and light setups are present in the scene for preview-rendering.

	== ~~deployment~~ & ~~testing~~==		== Deployment & Testing==
	Copy the '.s3o' in the folder:		Copy the '.s3o' in the folder:
	* /mods/modname/objects3d/		* /mods/modname/objects3d/
Line 41:		Line 48:

	Open the '/mods/modname/units/armsolar.fbi' and you will see:		Open the '/mods/modname/units/armsolar.fbi' and you will see:
	===~~valid~~ for 3do ===		=== Valid for 3do ===
	[UNITINFO] {		[UNITINFO] {
	unitname=armsolar;		unitname=armsolar;
Line 51:		Line 58:

	we have to modify this in order to make it s3o aware with:		we have to modify this in order to make it s3o aware with:
	===~~valid~~ for s3o ===		=== Valid for s3o ===
	[UNITINFO] {		[UNITINFO] {
	unitname=armsolar.s3o;		unitname=armsolar.s3o;
Line 60:		Line 67:
	...		...

	== ~~links~~ ==		== Links ==
	* [1] http://springrts.com/phpbb/viewtopic.php?f=9&t=17026		* [1] http://springrts.com/phpbb/viewtopic.php?f=9&t=17026
	* [2] http://www.lastlog.de/misc/s3o-template.zip		* [2] http://www.lastlog.de/misc/s3o-template.zip

Mrz: /* notes on the export step */

2010-09-11T10:38:19Z

notes on the export step

← Older revision		Revision as of 11:38, 11 September 2010
Line 25:		Line 25:
	The active selection does not influence the exporter therefore you don't need to select any object (still you can) to make a valid export.		The active selection does not influence the exporter therefore you don't need to select any object (still you can) to make a valid export.
	The exporter will loop over all objects in the scene automatically.		The exporter will loop over all objects in the scene automatically.

			Please note that the template you can download from [2] also includes a modified exporter script for blender.

	== deployment & testing==		== deployment & testing==

Mrz at 10:35, 11 September 2010

2010-09-11T10:35:53Z

← Older revision		Revision as of 11:35, 11 September 2010
Line 10:		Line 10:

	== editing and exporting ==		== editing and exporting ==
	~~Edit the 'base' and extend it with childs.~~ The parenting system of blender is used to find a chain of ~~childs which get exported. Objects which are no childs of the base objects are NOT exported~~. Each child must have a unique name which can later be used for rigging.		The parenting system of blender is used to find the chain of children for exporting. Each child must have a unique name which can later be used for rigging.

	Important: the model MUST have exactly two textures:		Important: the model MUST have exactly two textures: