|
1 | 1 | ---
|
2 |
| -title: Get information about a converted model |
3 |
| -description: Description of all model conversion parameters |
| 2 | +title: Get information about conversions |
| 3 | +description: Get information about conversions |
4 | 4 | author: malcolmtyrrell
|
5 | 5 | ms.author: matyrr
|
6 | 6 | ms.date: 03/05/2020
|
7 | 7 | ms.topic: how-to
|
8 | 8 | ---
|
9 | 9 |
|
10 |
| -# Get information about a converted model |
| 10 | +# Get information about conversions |
11 | 11 |
|
12 |
| -The arrAsset file produced by the conversion service is solely intended for consumption by the rendering service. There may be times, however, when you want to access information about a model without starting a rendering session. Therefore, the conversion service places a JSON file beside the arrAsset file in the output container. For example, if a file `buggy.gltf` is converted, the output container will contain a file called `buggy.info.json` beside the converted asset `buggy.arrAsset`. It contains information about the source model, the converted model, and about the conversion itself. |
| 12 | +## Information about a conversion: The result file |
| 13 | + |
| 14 | +When the conversion service converts an asset, it writes a summary of any issues into a "result file". |
| 15 | +For example, if a file `buggy.gltf` is converted, the output container will contain a file called `buggy.result.json`. |
| 16 | + |
| 17 | +The result file lists any errors and warnings that occurred during the conversion and gives a result summary, which is one of `succeeded`, `failed` or `succeeded with warnings`. |
| 18 | +The result file is structured as a JSON array of objects, each of which has a string property that is one of `warning`, `error`, `internal warning`, `internal error`, and `result`. |
| 19 | +There will be at most one error (either `error` or `internal error`) and there will always be one `result`. |
| 20 | + |
| 21 | +## Example *result* file |
| 22 | + |
| 23 | +The following example describes a conversion that successfully generated an arrAsset. |
| 24 | +However, since there was a missing texture, the resulting arrAsset may not be as intended. |
| 25 | + |
| 26 | +```JSON |
| 27 | +[ |
| 28 | + {"warning":"4004","title":"Missing texture","details":{"texture":"buggy_baseColor.png","material":"buggy_col"}}, |
| 29 | + {"result":"succeeded with warnings"} |
| 30 | +] |
| 31 | +``` |
| 32 | + |
| 33 | +## Information about a converted model: The info file |
| 34 | + |
| 35 | +The arrAsset file produced by the conversion service is solely intended for consumption by the rendering service. There may be times, however, when you want to access information about a model without starting a rendering session. To support this workflow, the conversion service places a JSON file beside the arrAsset file in the output container. For example, if a file `buggy.gltf` is converted, the output container will contain a file called `buggy.info.json` beside the converted asset `buggy.arrAsset`. It contains information about the source model, the converted model, and about the conversion itself. |
13 | 36 |
|
14 | 37 | ## Example *info* file
|
15 | 38 |
|
@@ -120,6 +143,12 @@ This section records information calculated from the converted asset.
|
120 | 143 | * `recenteringOffset`: When the `recenterToOrigin` option in the [ConversionSettings](configure-model-conversion.md) is enabled, this value is the translation that would move the converted model back to its original position.
|
121 | 144 | * `boundingBox`: The bounds of the model.
|
122 | 145 |
|
| 146 | +## Deprecated features |
| 147 | + |
| 148 | +The conversion service writes the files `stdout.txt` and `stderr.txt` to the output container, and these had been the only source of warnings and errors. |
| 149 | +These files are now deprecated. Instead, please use |
| 150 | +[result files](#information-about-a-conversion-the-result-file) for this purpose. |
| 151 | + |
123 | 152 | ## Next steps
|
124 | 153 |
|
125 | 154 | * [Model conversion](model-conversion.md)
|
|
0 commit comments