meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
expcustom [2020/03/31 10:24] – external edit 127.0.0.1expcustom [2023/09/07 09:22] (current) steph.jorgensen
Line 1: Line 1:
-======Exporting Custom Formats======+======Exporting custom formats======
  
 In addition to the export formats natively supported by the SpeedTree Modeler, you can create a custom exporter that will translate SpeedTree data into any final format. This custom exporter can be used during [[expstaticmesh|static mesh]] or [[expgame|game]] exports. In addition to the export formats natively supported by the SpeedTree Modeler, you can create a custom exporter that will translate SpeedTree data into any final format. This custom exporter can be used during [[expstaticmesh|static mesh]] or [[expgame|game]] exports.
  
->**Note:** Custom format exports are only available in SpeedTree Cinema and SpeedTree for Games (not subscription versions). 
  
- +=====The exporter application=====
-=====The Exporter Application=====+
  
 Custom mesh exporting from the Modeler was designed to be as flexible as possible for the developer writing the exporter. For this reason, temporary files are used to pass data from the application to the exporters. This allows the exporter application to be written in any programming language or framework since it is not tied to a specific API/language/version that can interface with the Modeler.  Custom mesh exporting from the Modeler was designed to be as flexible as possible for the developer writing the exporter. For this reason, temporary files are used to pass data from the application to the exporters. This allows the exporter application to be written in any programming language or framework since it is not tied to a specific API/language/version that can interface with the Modeler. 
Line 15: Line 13:
  
  
-=====Running the Custom Exporter=====+=====Running the custom exporter=====
  
 In order for the Modeler to be able to find and run a custom exporter, it must be placed in the <apps>/custom_exporters directory. This directory may need to be created. In order for the Modeler to be able to find and run a custom exporter, it must be placed in the <apps>/custom_exporters directory. This directory may need to be created.
Line 42: Line 40:
  
  
-=====Raw File Format=====+=====Raw file format=====
  
 The basic hierarchy of the XML in the raw file is fairly simple. See the description of each major section below... The basic hierarchy of the XML in the raw file is fairly simple. See the description of each major section below...