Lets me just include a file with
enable_language(XXX)
or make a wrapper CMakeLists that
add_subdirectory()s the otiginal project, and has a project() with languages you want? not sure how that propagates into nested projects tho
which extra languages you need?
hint: it starts with ass :eyes:
This blows up in try_compile because it doesn't look for a C compiler so it can't match that C feature
sounds like you're pretty deep in this, what was the original problem? :D
but with master half the tests fail now and I'm about to give up
that doesn't seem like a feature worth dying for :D
and i thought you did not want to touch assimp ever again?
no use putting all that work in until there's a new tagged release, anyway
that's a lot of open checkboxes
yeah exactly, and i gave up (they're apparently reworking this to be less shit), so from the PR i would only take the custom materials, which is the very last checkbox, nothing else
assimp has a clear set of types (nice) and predefined attribute name strings with varying level of shittiness (ew), which, if imported as-is (without trying to make sense of) could work as at least some way of providing access to, say, FBX PBR attributes
sheen was the only one I saw that can be done with a layer (color + roughness)
the thinfilm extension looked like a good candidate for a layer as well
iridescence is an extension on its own i think
I remember reading this paper https://belcour.github.io/blog/research/publication/2017/05/01/brdf-thin-film.html
that explains why i thought it's two separate things
i'm a forever pbr noob
no visible results
i already saw a dataset that used like 10 of those fancy new extensions
though honestly i like this better than a total silence for 5 years and then "here's glTF 2.1 with PBR Next, enjoy!" with no community involvement
i imagine this is how the internal vulkan extension development looks like as well, only we don't see it :D
