sunag
sunag
> I am okay going with XML for now. THREE.MaterialXLoader sounds amazing. @sunag what do you think? It sounds good. The use of `WASM` it's still unclear to me, seems...
If we think about Surface let's consider this implementation -> https://github.com/mrdoob/three.js/pull/21322 I think that we can fork the core code of `transmission`, `subsurface`, `sheen` and others and implement using `FunctionNode`...
@donmccurdy I'll be working on it, thanks in advance for your work so far.
@donmccurdy Could we use the functions `mx_*` of `GLSL` from `MaterialX` on Three.js? I say this because I have doubts about the license, maybe you know something about it?
I'm getting this message of error most part of times that I tested:
Closing in favor of https://github.com/mrdoob/three.js/pull/28894
The problem was in NodeFrame which was not restoring the scene from the previous render in the call tree, I still have to see the best solution, but I already...
I have to improve `filterNode` to support VSM too, I think that after we merge this PR.
It looks like we have another issue in `WebGLBackend`.
This PR https://github.com/mrdoob/three.js/pull/29326 should fix it, sorry the delay, I had to deconstruct the code step by step to find the source of the problem.