From 2faf5a36fe7a2194dd1a873fbec4d30d4d1e5886 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A4r=20Winzell?= Date: Fri, 15 Dec 2017 09:56:42 -0800 Subject: [PATCH] Allow normalized integers for 'rotation' path Change JSON-Schema to allow rotation animation values to be provided as normalized integers. This is already the law of the land according to the spec's README.md & glTF-Validator. --- specification/2.0/schema/animation.sampler.schema.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/2.0/schema/animation.sampler.schema.json b/specification/2.0/schema/animation.sampler.schema.json index e3f1532c6f..14855c3647 100644 --- a/specification/2.0/schema/animation.sampler.schema.json +++ b/specification/2.0/schema/animation.sampler.schema.json @@ -35,7 +35,7 @@ "output": { "allOf": [ { "$ref": "glTFid.schema.json" } ], "description": "The index of an accessor, containing keyframe output values.", - "gltf_detailedDescription": "The index of an accessor containing keyframe output values. When targeting TRS target, the `accessor.componentType` of the output values must be `FLOAT`. When targeting morph weights, the `accessor.componentType` of the output values must be `FLOAT` or normalized integer where each output element stores values with a count equal to the number of morph targets." + "gltf_detailedDescription": "The index of an accessor containing keyframe output values. When targeting translation or scale paths, the `accessor.componentType` of the output values must be `FLOAT`. When targeting rotation or morph weights, the `accessor.componentType` of the output values must be `FLOAT` or normalized integer. For weights, each output element stores `SCALAR` values with a count equal to the number of morph targets." }, "extensions": { }, "extras": { }