Andreas Atteneder

All right, a fix that invokes `SetNodeName` right after a node was created is scheduled for the next release. Thanks for your help

Thanks for the suggestion. Although I see the value in this feature request, I don't think glTFast should put effort into fixing corrupt or sub-optimal input data (at least before...

Hi @JaXt0r , I investigated that a Vector4 texture coordinate is not covered by the [glTF 2.0 specification](https://registry.khronos.org/glTF/specs/2.0/glTF-2.0.html). I manually crafted such a file and the validation failed with the...

@JaXt0r Yeah sure. As stated before, technically there's no obstacle to add vec3/vec4 UV support to glTFast. The problem is that those glTFs are not within the specification and when...

Update: On the *Draco for Unity* side of things we're about to release version 5.4.0 next week which will bring submesh support. I've taken you work, re-based and adjusted it...

Hi @CodeNewWorlds , the good news is, I've got a working PoC for visionOS. Here's what's required for a release: - [ ] Add visionOS binaries (device and simulator SDKs)...

VisionOS support was added in [KTX for Unity 3.4.0](https://docs.unity3d.com/Packages/[email protected]/changelog/CHANGELOG.html#340---2024-04-17)

Sorry about the inconvenience, I think I resolved that in the current development version that's about to be released this week as 6.15.0. If you want me to reassure, please...

Hi folks 👋 , this issue somehow found its way to me Unity-internally :) I couldn't reproduce it with 6000.0.55f1 and UnityGLTF 2.15.0 (the pre-installed 2.14.0 was not working anymore,...

Thanks for the info. I tried again with 6000.0.33f1 (the most recent version @ROBYER1 reported he could still reproduce the issue) and it seems to work fine on my machines...