Alexey Knyazev

Results 137 comments of Alexey Knyazev

As we have already two engines not supporting such models, let's proceed with treating non-morphed primitives as having zero morph targets (and asserting all conformance implications of that).

More references on the derivative-based approach: - [Bump Mapping Unparametrized Surfaces on the GPU](https://mmikk.github.io/papers3d/mm_sfgrad_bump.pdf) (Morten S. Mikkelsen, 2010) - Follow-up: https://mmikkelsen3d.blogspot.com/2011/07/derivative-maps.html - Explainer: https://www.rorydriscoll.com/2012/01/11/derivative-maps/ - [Surface Gradient–Based Bump Mapping Framework](https://jcgt.org/published/0009/03/04/)...

Yes, the extension specs need to be upgraded: - to the new JSON schema version; - to use BCP 14 normative language; - to use AsciiDoc tooling (long-term).

For now, I'd say that extension schema files are "located" in the same folder as the core schema files for the purposes of reference resolution. Long-term, we should plan for...

The JSON-Schema `$id` property is semantically close to XML namespaces and JSON-LD contexts. It does not require any network operations on its own.

@emackey Direct quotes from the JSON-Schema spec: >The `"$id"` keyword identifies a schema resource with its canonical URI. > >Note that this URI is an identifier and not necessarily a...

Yes. Added to `2.0.x` milestone to keep it around.

- [x] Section 2.3 mentions `push_back` and `assign` from `std::vector`. But besides those, bitstream spec uses: `back`, `begin`, `end`, `insert`, and `size`. That section should mention them too. - [x]...

- [x] `GetNumComponents()` isn't defined. - [x] `ProcessInteriorEdges()` isn't defined. - [x] Statement with `is_crease_edge_pos` from `MeshPredictionSchemeConstrainedMultiParallelogramDecoder_ComputeOriginalValues` lacks function name. - [x] `ReadEncodedData` isn't used, also title doesn't match: ![image](https://user-images.githubusercontent.com/3479527/31341768-a5e85308-ad1b-11e7-9029-d96afea93eb2.png)...

- [x] Please replace `[size]` with actual names of variables that should be used in: - `ParseMetadataElement` - `ParseSubMetadataKey` - `DecodeRawSymbols` - `DecodeTaggedSymbols` - [x] Consider naming constant integer values...