Tree: 63cb469b29

apple-crashy-msaa-default-framebuffer

audio-import

catastrophic-cross

chainsaw-surgery

dpi-change-events

euler-xxx

findsdl-include-root

gltestlib-symbol-duplication

gpu-preference

inverted-ranges

ktx1-detection

master

meshdata-cereal-killer

mousecapture

multiwindow

next

sceneconverter

scenedata-optimizations

simd

vectorfields

zerocopy

snapshot-2013-08

snapshot-2013-10

snapshot-2014-01

snapshot-2014-01-compatibility

snapshot-2014-06

snapshot-2014-06-compatibility

snapshot-2015-05

snapshot-2015-05-compatibility

v2013.08

v2013.10

v2014.01

v2014.06

v2015.05

v2018.02

v2018.04

v2018.10

v2019.01

v2019.10

v2020.06

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '63cb469b29'

${ noResults }

Commit Graph

4 Commits (63cb469b292fa7427c6cee17cb2e352721248792)

Author	SHA1	Message	Date
Vladimír Vondruš	3d136503d8	Updated copyright year.	5 years ago
Vladimír Vondruš	44f67e7748	Trade: rethink common material texture coordinate transform/sets. ... There's actually a lot of code involved in checking if all textures use the same transform or coordinate set, especially when considering all fallback variants and potential future expansion with separate texture offset/scale/rotation attributes. A lot of the complexity was thus hidden in plugin implementations, which were each trying to find a common value for all textures to save the user from doing the same. All that code can now be removed and left up to the material APIs themselves -- now it's just about checking hasCommonTextureTransformation() and then retrieving that one common transformation, independently on how the material actually defines it.	6 years ago
Vladimír Vondruš	271b7a7629	Trade: usage docs for MaterialData.	6 years ago
Vladimír Vondruš	417471b83c	Trade: add FlatMaterialData.	6 years ago