Importing character models - Revision history

Iritscen: +integrate

2025-12-03T23:54:54Z

+integrate

← Older revision		Revision as of 23:54, 3 December 2025
Line 1:		Line 1:
			{{integrate\|1=Actually it's linked from the talk page: [https://web.archive.org/web/20160224202204/http://oni.bungie.org/forum/viewtopic.php?id=2423]. This is old but should be appraised for useful information.<br>Also see suggestions on talk page for restructuring, but note they are older than the latest additions to this page.}}
	This article covers the importing of new character models into Oni, but also how to export models from Oni. Generally speaking, you are going to want to use [[wp:COLLADA\|COLLADA]] as the "passthrough" format between your 3D program and Oni. In this article, COLLADA is referred to as "Collada" (because who enjoys being shouted at?), or as a ".dae file" (the file suffix for COLLADA).		This article covers the importing of new character models into Oni, but also how to export models from Oni. Generally speaking, you are going to want to use [[wp:COLLADA\|COLLADA]] as the "passthrough" format between your 3D program and Oni. In this article, COLLADA is referred to as "Collada" (because who enjoys being shouted at?), or as a ".dae file" (the file suffix for COLLADA).

Iritscen: punctuation

2024-05-13T15:47:54Z

punctuation

← Older revision		Revision as of 15:47, 13 May 2024
Line 120:		Line 120:
	"Schema validation (Error): Error: ERROR_REQUIRED_ATTRIBUTE_MISSING Element: technique, Attribute: sid"		"Schema validation (Error): Error: ERROR_REQUIRED_ATTRIBUTE_MISSING Element: technique, Attribute: sid"

	Solution: Open the .dae file in a text editor, find all instances of <tt><technique></tt> and replace with <tt><technique sid="common"></tt>		Solution: Open the .dae file in a text editor, find all instances of <tt><technique></tt> and replace with <tt><technique sid="common"></tt>.

	==Poses==		==Poses==

Iritscen: link fix

2023-12-19T20:14:59Z

link fix

← Older revision		Revision as of 20:14, 19 December 2023
Line 24:		Line 24:
	First, you need to find the class name for the character you want to export. You can accomplish this by going into Oni, loading the level in which the desired character appears, and then enabling the shapeshifter cheat – but you have to do this by turning on [[Developer Mode]], not by entering the "shapeshifter" cheat code, because the regular cheat code does not display the console output that you need. Once Dev Mode is on, press F8 until you reach the desired character. You should see the message "character class ''number'' '''''string'''''". The number is unimportant, but write down the string, because that is the class name which provides the basis for the names of the ONCC and TRBS.		First, you need to find the class name for the character you want to export. You can accomplish this by going into Oni, loading the level in which the desired character appears, and then enabling the shapeshifter cheat – but you have to do this by turning on [[Developer Mode]], not by entering the "shapeshifter" cheat code, because the regular cheat code does not display the console output that you need. Once Dev Mode is on, press F8 until you reach the desired character. You should see the message "character class ''number'' '''''string'''''". The number is unimportant, but write down the string, because that is the class name which provides the basis for the names of the ONCC and TRBS.

	In this example, we'll export one of Konoko's models. For Konoko, we don't even need to open Oni to find the name of an ONCC because we have [[Konoko~~#In-game~~ outfits\|this handy table]]. Let's use Konoko in her police uniform; you can see from the table that this is ONCCk3 and that it's found in level2_Final.		In this example, we'll export one of Konoko's models. For Konoko, we don't even need to open Oni to find the name of an ONCC because we have [[Konoko's outfits\|this handy table]]. Let's use Konoko in her police uniform; you can see from the table that this is ONCCk3 and that it's found in level2_Final.

	Next, you need to decide on the pose in which your character will be exported. See the "Poses" section below for guidance. Without making this example more complicated, we only have two choices for pose: default (folded) and -noanim (standing at attention); we are going to use the second option, for a more visually pleasing result. Here are the steps for getting your desired character in .dae format. Substitute backward slashes for forward ones if you are in Windows.		Next, you need to decide on the pose in which your character will be exported. See the "Poses" section below for guidance. Without making this example more complicated, we only have two choices for pose: default (folded) and -noanim (standing at attention); we are going to use the second option, for a more visually pleasing result. Here are the steps for getting your desired character in .dae format. Substitute backward slashes for forward ones if you are in Windows.

Iritscen: linking to OBLS is misleading because the game was never going to have realtime radiosity; OBLS was probably for casting shadows

2023-12-10T23:09:59Z

linking to OBLS is misleading because the game was never going to have realtime radiosity; OBLS was probably for casting shadows

← Older revision		Revision as of 23:09, 10 December 2023
Line 9:		Line 9:
	[[Blender]] is the community's current software of choice for 3D modeling, animating, and more.		[[Blender]] is the community's current software of choice for 3D modeling, animating, and more.

	Blender rocks when it comes to [[~~Lightmapping levels\|~~lightmapping levels]]. XSI is closed-source and can only lightmap one mesh at a time with one lightmap texture per mesh. Blender is more flexible because of its scripting API, and it supports radiosity, i.e., emissive materials – which is exactly how Oni's lighting was done ~~initially (see~~ [[~~OBLS~~]]).		Blender rocks when it comes to [[lightmapping levels]]. XSI is closed-source and can only lightmap one mesh at a time with one lightmap texture per mesh. Blender is more flexible because of its scripting API, and it supports radiosity, i.e., emissive materials – which is exactly how Oni's lighting was done before they tore out [[Pre-beta features#Lightmapping\|the lightmap feature]].

	====XSI====		====XSI====

Iritscen: imagine not linking once to OniSplit in this article…

2023-11-20T15:26:45Z

imagine not linking once to OniSplit in this article…

← Older revision		Revision as of 15:26, 20 November 2023
Line 3:		Line 3:
	==Modding tools==		==Modding tools==
	===OniSplit===		===OniSplit===
	~~This~~ is the program that we use to get models into and out of Oni. It is a command line tool. There is a GUI wrapper for OniSplit that covers most of its functions called [[Vago (tool)\|Vago]], but modders sometimes have to call OniSplit from the command line or use Vago's command-line input feature to take full advantage of its abilities.		[[OniSplit]] is the program that we use to get models into and out of Oni. It is a command line tool. There is a GUI wrapper for OniSplit that covers most of its functions called [[Vago (tool)\|Vago]], but modders sometimes have to call OniSplit from the command line or use Vago's command-line input feature to take full advantage of its abilities.

	===3D programs===		===3D programs===

Iritscen: /* Working example */ localized image

2023-03-04T23:33:53Z

Working example: localized image

← Older revision		Revision as of 23:33, 4 March 2023
Line 215:		Line 215:

	====Working example====		====Working example====
	~~{\|align=right~~		[[Image:Gally PSX model.png\|right]]
	~~\|http~~:~~//geyser.oni2.net/edition/characters/gally/GLB_shot~~.png
	\|}
	For the sake of this sorta tutorial, we shall pretend three things:		For the sake of this sorta tutorial, we shall pretend three things:
	*Berserker Gally from GUNNM Martian Memory (a PSX game) is, like, the coolest model ever (see picture on the right);		*Berserker Gally from GUNNM Martian Memory (a PSX game) is, like, the coolest model ever (see picture on the right);

Iritscen: some initial copy-editing

2022-11-24T03:46:22Z

some initial copy-editing

← Older revision		Revision as of 03:46, 24 November 2022
Line 1:		Line 1:
	This article covers the importing of new character models into Oni, but also how to export models from Oni. Generally speaking, you are going to want to use [[~~wikipedia~~:COLLADA\|COLLADA]] as the "passthrough" format between your 3D program and Oni~~, as this is exactly what COLLADA was designed for~~. In this article, COLLADA is referred to as "Collada" (because who enjoys being shouted at?), or by ".dae file" (~~because that is~~ the file suffix for COLLADA).		This article covers the importing of new character models into Oni, but also how to export models from Oni. Generally speaking, you are going to want to use [[wp:COLLADA\|COLLADA]] as the "passthrough" format between your 3D program and Oni. In this article, COLLADA is referred to as "Collada" (because who enjoys being shouted at?), or as a ".dae file" (the file suffix for COLLADA).

	==Modding tools==		==Modding tools==
	===OniSplit===		===OniSplit===
	This is the program that we use to get models into and out of Oni. It is a command line tool. There ~~are~~ GUI ~~wrappers~~ for OniSplit that ~~cover~~ most of its functions ~~(see~~ [[Vago (tool)]], but modders sometimes have to call it from the command line (or use ~~the direct~~ command line input feature ~~in a GUI)~~ to take full advantage of ~~OniSplit's~~ abilities.		This is the program that we use to get models into and out of Oni. It is a command line tool. There is a GUI wrapper for OniSplit that covers most of its functions called [[Vago (tool)\|Vago]], but modders sometimes have to call OniSplit from the command line or use Vago's command-line input feature to take full advantage of its abilities.

	===3D programs===		===3D programs===
	====Blender====		====Blender====
	[[Blender]] is the community's current 3D software of choice~~, allowing~~ for 3D modeling, animating, and more.		[[Blender]] is the community's current software of choice for 3D modeling, animating, and more.

	Blender rocks when it comes to [[Lightmapping levels\|lightmapping levels]]. XSI is closed source and can only lightmap one mesh at a time with one lightmap texture per mesh. Blender is more flexible because of its ~~free-for-all~~ scripting API, and ~~a nice touch is that~~ it supports radiosity, i.e., emissive materials ~~-- and that's~~ exactly how Oni's lighting was done initially (see [[OBLS]]).		Blender rocks when it comes to [[Lightmapping levels\|lightmapping levels]]. XSI is closed-source and can only lightmap one mesh at a time with one lightmap texture per mesh. Blender is more flexible because of its scripting API, and it supports radiosity, i.e., emissive materials – which is exactly how Oni's lighting was done initially (see [[OBLS]]).

	====XSI====		====XSI====
	Softimage XSI is a Windows-only 3D software that ~~went~~ discontinued in 2014~~, and~~ [https://www.moddb.com/downloads/autodesk-softimage-mod-tool-75 a free version of it from 2008] used to to be the community's modding tool of choice before moving on to Blender. A number of Oni-related ~~addons~~, tools and tutorials were developed for it can be still found and used. It has detailed documentation and is versatile, whether working with characters or levels, though highly obsolete.		Softimage XSI is Windows-only 3D software that was discontinued in 2014; [https://www.moddb.com/downloads/autodesk-softimage-mod-tool-75 a free version of it from 2008] used to to be the community's modding tool of choice before moving to Blender. A number of Oni-related add-ons, tools and tutorials were developed for it can be still found and used. It has detailed documentation and is versatile, whether working with characters or levels, though highly obsolete.


	===File converters===		===File converters===
Line 23:		Line 22:
	OniSplit allows you to export .dae files from both [[TRBS]] and [[ONCC]]. Though all the 3D data is in the TRBS, the textures are listed in the [[TRMA]] file, which is only visible from the ONCC, not the TRBS. Thus, if you want to use the textures while editing the model, convert the ONCC, not the TRBS, into Collada. The instructions below assume that you want the textured model, and thus illustrate how to export the ONCC.		OniSplit allows you to export .dae files from both [[TRBS]] and [[ONCC]]. Though all the 3D data is in the TRBS, the textures are listed in the [[TRMA]] file, which is only visible from the ONCC, not the TRBS. Thus, if you want to use the textures while editing the model, convert the ONCC, not the TRBS, into Collada. The instructions below assume that you want the textured model, and thus illustrate how to export the ONCC.

	First, you need to find the class name for the character you want to export. You can accomplish this by going into Oni, loading the level in which the desired character appears, and then enabling the shapeshifter cheat -- but you have to do this by turning on [[Developer Mode]], not by entering the "shapeshifter" cheat code, because the regular cheat code does not display the console output that you need. Once Dev Mode is on, press F8 until you reach the desired character. You should see the message "character class ''number'' '''''string'''''". The number is unimportant, but write down the string, because that is the class name which provides the basis for the names of the ONCC and TRBS.		First, you need to find the class name for the character you want to export. You can accomplish this by going into Oni, loading the level in which the desired character appears, and then enabling the shapeshifter cheat – but you have to do this by turning on [[Developer Mode]], not by entering the "shapeshifter" cheat code, because the regular cheat code does not display the console output that you need. Once Dev Mode is on, press F8 until you reach the desired character. You should see the message "character class ''number'' '''''string'''''". The number is unimportant, but write down the string, because that is the class name which provides the basis for the names of the ONCC and TRBS.

	In this example, we'll export one of Konoko's models. For Konoko, we don't even need to open Oni to find the name of an ONCC because we have [[Konoko#In-~~game_outfits~~\|this handy table]]. Let's use Konoko in her police uniform; you can see from the table that this is ONCCk3 and that it's found in level2_Final.		In this example, we'll export one of Konoko's models. For Konoko, we don't even need to open Oni to find the name of an ONCC because we have [[Konoko#In-game outfits\|this handy table]]. Let's use Konoko in her police uniform; you can see from the table that this is ONCCk3 and that it's found in level2_Final.

	Next, you need to decide on the pose in which your character will be exported. See the "Poses" section below for guidance. Without making this example more complicated, we only have two choices for pose: default (folded) and -noanim (standing at attention); we are going to use the second option, for a more visually pleasing result. Here are the steps for getting your desired character in .dae format. Substitute backward slashes for forward ones if you are in Windows.		Next, you need to decide on the pose in which your character will be exported. See the "Poses" section below for guidance. Without making this example more complicated, we only have two choices for pose: default (folded) and -noanim (standing at attention); we are going to use the second option, for a more visually pleasing result. Here are the steps for getting your desired character in .dae format. Substitute backward slashes for forward ones if you are in Windows.
Line 59:		Line 58:
	:# TRBSnewchar_high.dae		:# TRBSnewchar_high.dae

	An ONCC contains much more information than just links to TRBS and TRMA, and thus ~~can not~~ be generated automatically. See [[XML:ONCC]] on how to create such a file, and then import the character with this class data into Oni. The easiest way to try out an imported character in Oni is to name your imported TRBS so that it replaces an existing one and no ONCC editing is needed. The next step up is to clone an existing ONCC (in XML) and modify it to link to your new TRBS file(s).		An ONCC contains much more information than just links to TRBS and TRMA, and thus cannot be generated automatically. See [[XML:ONCC]] on how to create such a file, and then import the character with this class data into Oni. The easiest way to try out an imported character in Oni is to name your imported TRBS so that it replaces an existing one and no ONCC editing is needed. The next step up is to clone an existing ONCC (in XML) and modify it to link to your new TRBS file(s).

	==Blender-specific OniSplit information==		==Blender-specific OniSplit information==
	~~This section contains OniSplit commands specific to Blender, and related settings in Blender necessary for assets to work.~~

	===Blender settings for importing and exporting COLLADA files===		===Blender settings for importing and exporting COLLADA files===
	====Importing====		====Importing====
Line 77:		Line 74:
	\|-		\|-
	\|}		\|}

	====Exporting====		====Exporting====
	When exporting TRBS, be sure to delete the default light and camera from the scene, or you can select all 19 body parts, then in the Export Main Tab, select Selection Only.		When exporting TRBS, be sure to delete the default light and camera from the scene, or you can select all 19 body parts, then in the Export Main Tab, select Selection Only.
Line 89:		Line 87:
	\|-		\|-
	\|}		\|}


	===Blender-specific OniSplit commands===		===Blender-specific OniSplit commands===
Line 106:		Line 103:
	-extract:'''xml''' To_blender -anim-body:Original\TRBSkonoko_body_high.oni -blender Original\TRAMKONCOMkick_heavy.oni		-extract:'''xml''' To_blender -anim-body:Original\TRBSkonoko_body_high.oni -blender Original\TRAMKONCOMkick_heavy.oni

	This will create a TRAM.dae along with an .xml file, which is needed for importing back to Oni. You will be also able to tell that everything went okay when you see		This will create a TRAM.dae along with an .xml file, which is needed for importing back to Oni. You will be also able to tell that everything went okay when you see <mark><tt>AnimationDaeWriter: custom axis conversion</tt></mark> in the output. If you don’t, you’re most likely doing something wrong.
	<mark><tt>AnimationDaeWriter: custom axis conversion</tt></mark>
	on output. If you don’t, you’re most likely doing something wrong.


Line 120:		Line 115:

	===Troubleshooting===		===Troubleshooting===

	Known Issues between Blender 2.83 and OniSplit 0.9.99.2:		Known Issues between Blender 2.83 and OniSplit 0.9.99.2:

Line 137:		Line 131:
	\| \| x ^		\| \| x ^
	18-o-17-o-16-o-15-o 6-o-5-o-4-o ^		18-o-17-o-16-o-15-o 6-o-5-o-4-o ^
	This is a ~~conventional reference~~ used in all of Oni. For any animation of any character in Oni, the rotations of the body parts are calculated with respect to a default pose such as this one. This allows the characters to share animations, even if their "skeletons" ([[TRTA]]) have slightly different proportions.		This is a convention used in all of Oni. For any animation of any character in Oni, the rotations of the body parts are calculated with respect to a default pose such as this one. This allows the characters to share animations, even if their "skeletons" ([[TRTA]]) have slightly different proportions.

	In the default pose, the XYZ axes of all the bones are oriented the same way. Thus, in the default pose, you can see the "true" translations (offsets) of every body part with respect to its parent, as stored in the "translation array" (TRTA). For example, in Konoko's case, the "mid" section (part 7), is translated by 1.67 WU along X (i.e., 16.7 cm towards the top of the spine), and by 0.25 along Y (i.e., 2.5 cm towards the front of the spine). Remember that this translation is ''in the "local" frame of reference of the pelvis'', i.e., with respect to the ''origin'' of the pelvis ''and'' to its local XYZ axes (which are generally different from the world axes). Basically, the local X of the pelvis always points up the spine, the local Y points forward, the local Z points left, and the same goes for "mid", "chest", "neck", and "head".		In the default pose, the XYZ axes of all the bones are oriented the same way. Thus, in the default pose, you can see the "true" translations (offsets) of every body part with respect to its parent, as stored in the "translation array" (TRTA). For example, in Konoko's case, the "mid" section (part 7), is translated by 1.67 WU along X (i.e., 16.7 cm towards the top of the spine), and by 0.25 along Y (i.e., 2.5 cm towards the front of the spine). Remember that this translation is ''in the "local" frame of reference of the pelvis'', i.e., with respect to the ''origin'' of the pelvis ''and'' to its local XYZ axes (which are generally different from the world axes). Basically, the local X of the pelvis always points up the spine, the local Y points forward, the local Z points left, and the same goes for "mid", "chest", "neck", and "head".

Iritscen: fix links to moved images

2022-11-24T03:13:03Z

fix links to moved images

← Older revision		Revision as of 03:13, 24 November 2022
Line 74:		Line 74:
	! Collada import settings !! Scene settings		! Collada import settings !! Scene settings
	\|-		\|-
	\| [[Image:~~BlenderImportSettings~~.png\|200px\|frameless\|center]] \|\| [[Image:~~BlenderSceneSettings~~.png\|300px\|frameless\|center]]		\| [[Image:Blender import settings.png\|200px\|frameless\|center]] \|\| [[Image:Blender scene settings.png\|300px\|frameless\|center]]
	\|-		\|-
	\|}		\|}
Line 86:		Line 86:
	! Blender Collada export settings		! Blender Collada export settings
	\|-		\|-
	\| [[Image:~~BlenderColladaExportSettings~~.png\|500px\|frameless\|center]]		\| [[Image:Blender Collada export settings.png\|500px\|frameless\|center]]
	\|-		\|-
	\|}		\|}

Delano762: /* Blender-specific OniSplit information - minor adjustments */

2022-11-21T10:39:17Z

Blender-specific OniSplit information - minor adjustments

← Older revision		Revision as of 10:39, 21 November 2022
Line 68:		Line 68:
	In the Collada Import Data Options, make sure to check Import Units. Failure to do so will result in scaling issues, which are not easy to fix.		In the Collada Import Data Options, make sure to check Import Units. Failure to do so will result in scaling issues, which are not easy to fix.

	Before importing TRAM files, set the scene frame rate to ~~60fps~~.		Before importing TRAM files, set the scene frame rate to 60 FPS. Failure to do so will result in keyframes being placed incorrectly on the timeline.

	{\| class="wikitable"		{\| class="wikitable"
Line 78:		Line 78:
	\|}		\|}
	====Exporting====		====Exporting====
	When exporting TRBS, be sure to delete the default light and camera from the scene, or you can select all 19 body parts, then in the Export Main Tab, select Selection Only		When exporting TRBS, be sure to delete the default light and camera from the scene, or you can select all 19 body parts, then in the Export Main Tab, select Selection Only.

	When exporting TRAM, select all 19 body parts, then in the Collada export options, under the Main Tab: select Selection Only, Geom Tab: select Triangulate, Anim Tab: select Curves.		When exporting TRAM, select all 19 body parts, then in the Collada export options, under the Main Tab: select Selection Only, Geom Tab: select Triangulate, Anim Tab: select Curves.
Line 121:		Line 121:
	===Troubleshooting===		===Troubleshooting===

	Known Issues between Blender 2.83 and OniSplit 0.9.99.2		Known Issues between Blender 2.83 and OniSplit 0.9.99.2:

	1) Importing a .dae file results in the following error message:		1) Importing a .dae file results in the following error message:

Delano762: /* Blender-specific OniSplit information, formatting plus images */

2022-11-20T23:43:06Z

Blender-specific OniSplit information, formatting plus images

← Older revision		Revision as of 23:43, 20 November 2022
Line 69:		Line 69:

	Before importing TRAM files, set the scene frame rate to 60fps.		Before importing TRAM files, set the scene frame rate to 60fps.

			{\| class="wikitable"
			\|-
			! Collada import settings !! Scene settings
			\|-
			\| [[Image:BlenderImportSettings.png\|200px\|frameless\|center]] \|\| [[Image:BlenderSceneSettings.png\|300px\|frameless\|center]]
			\|-
			\|}
	====Exporting====		====Exporting====
	When exporting TRBS, be sure to delete the default light and camera from the scene, or you can select all 19 body parts, then in the Export Main Tab, select Selection Only		When exporting TRBS, be sure to delete the default light and camera from the scene, or you can select all 19 body parts, then in the Export Main Tab, select Selection Only

	When exporting TRAM, select all 19 body parts, then in the Collada export options, under the Main Tab: select Selection Only, Geom Tab: select Triangulate, Anim Tab: select Curves.		When exporting TRAM, select all 19 body parts, then in the Collada export options, under the Main Tab: select Selection Only, Geom Tab: select Triangulate, Anim Tab: select Curves.
	~~===Troubleshooting===~~

	~~Known Issues between~~ Blender 2.~~83 and OniSplit 0.9.99.2~~		{\| class="wikitable"
			\|-
			! Blender Collada export settings
			\|-
			\| [[Image:BlenderColladaExportSettings.png\|500px\|frameless\|center]]
			\|-
			\|}

	~~1) When importing .dae file you get the error message "Schema validation (Error): Error: ERROR_REQUIRED_ATTRIBUTE_MISSING Element: technique, Attribute: sid"~~

	~~Solution~~: ~~Open the~~ .~~dae file in a text editor, find all instances of <technique> and replace with <technique sid="common">~~		===Blender-specific OniSplit commands===
			*Convert TRBS.oni to Blender compatible dae:
			-extract:'''dae''' To_blender -noanim -blender Original\TRBSkonoko_body_high.oni

			*Convert ONCC.oni to Blender compatible dae with textures:

	~~===Blender-specific OniSplit commands===~~		-extract:'''dae''' To_blender -noanim -blender Original\ONCCkonoko_generic.oni
	~~Convert TRBS.oni to Blender compatible dae:~~
	-extract:dae To_blender -noanim -blender Original\~~TRBSkonoko_body_high~~.oni

	~~Convert~~ ONCC.oni ~~to Blender compatible dae with textures:~~		Be sure to include the TMXP.oni files with the ONCC.oni file.

	~~-extract:dae To_blender -noanim -blender Original\ONCCkonoko_generic.oni~~

	~~Be sure to include the TMXP~~.oni ~~files~~ with ~~the ONCC.oni file~~		*Convert TRAM.oni to Blender compatible dae - '''textureless''', as exporting animations with textured models does not work yet:

	~~Convert TRAM~~.oni ~~to Blender compatible dae~~ - ~~textureless, as exporting animations with textured models does not work yet:~~		-extract:'''xml''' To_blender -anim-body:Original\TRBSkonoko_body_high.oni -blender Original\TRAMKONCOMkick_heavy.oni

	~~-extract:~~xml ~~To_blender -anim-body~~:~~Original\TRBSkonoko_body_high~~.~~oni -blender Original\TRAMKONCOMkick_heavy~~.~~oni~~		This will create a TRAM.dae along with an .xml file, which is needed for importing back to Oni. You will be also able to tell that everything went okay when you see
			<mark><tt>AnimationDaeWriter: custom axis conversion</tt></mark>
			on output. If you don’t, you’re most likely doing something wrong.

	~~This will create a TRAM.dae along with an .xml file, which is needed for importing back to Oni.~~
	~~You will be also able to tell that everything went okay when you see~~
	~~AnimationDaeWriter: custom axis conversion.~~
	~~on output. If you don’t, you’re most likely doing something wrong.~~

	Convert TRBS.dae from Blender to .oni:		*Convert TRBS.dae from Blender to .oni:
	-create:trbs From_blender -blender From_blender\TRBSkonoko_body_high.dae		-create:'''trbs''' From_blender -blender From_blender\TRBSkonoko_body_high.dae

	Convert TRAM.dae from Blender to .oni		*Convert TRAM.dae from Blender to .oni
	-create From_blender -blender From_blender\TRAMKONCOMkick_heavy.xml		-create From_blender -blender From_blender\TRAMKONCOMkick_heavy.xml
	The TRAMKONCOMkick_heavy.xml links to the TRAMKONCOMkick_heavy.dae from Blender which needs to be in the same location as the .xml file.		The TRAMKONCOMkick_heavy.xml links to the TRAMKONCOMkick_heavy.dae from Blender which needs to be in the same location as the .xml file.


			===Troubleshooting===

			Known Issues between Blender 2.83 and OniSplit 0.9.99.2

			1) Importing a .dae file results in the following error message:
			"Schema validation (Error): Error: ERROR_REQUIRED_ATTRIBUTE_MISSING Element: technique, Attribute: sid"

			Solution: Open the .dae file in a text editor, find all instances of <tt><technique></tt> and replace with <tt><technique sid="common"></tt>

	==Poses==		==Poses==