jgltf-model tests do not pass
See original GitHub issueCloning a fresh copy of this repo produces errors when running mvn compile package
due to test failures in jgltf-model
. The buffers of the generated models do not match the expected values, it seems. Replicated on two machines with completely different configurations.
I don’t know enough about this code, yet, to know what is actually causing this.
Using Java 10 on one machine and Java 9 on another.
Issue Analytics
- State:
- Created 5 years ago
- Comments:25 (11 by maintainers)
Top Results From Across the Web
Cannot load a GLTF model in a unit test - three.js forum
Hi, I'm currently writing unit tests for my app and am running into some issues getting the models to load. Here is what...
Read more >GLTF Loader not working and doesn't load 3D model
js , OrbitControls and GLTFLoader are ES6 modules. In this case, you can create an instance of GLTFLoader without the THREE namespace. Same...
Read more >cx20/gltf-test: Testing the glTF Loader and WebGL Library
The number of tests is approximate. Format Tests. Test environment : Windows 11 + Chrome 108. Format and Sample Model, Three.js r147 ...
Read more >How to Load a 3D model in Three.js - YouTube
In this video, I show you how to load a 3D model ( gltf /glb) in your browser using the GLTFLoader class in...
Read more >How to Import GLTF Models in Three.js - YouTube
In this coding tutorial, we go over importing GLTF models in Three JS. We start off by learning when it is useful to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Note that this is not about the JSON part. (This case is already handled). This is about the GLSL files. These files are read and converted into a base64 string for the embedded glTF. The point is that the base64 string representations of the GLSL shader code differ, because the shader code is once read from a file with
\r\n
and once from a file with\n
line endings.(However, the GLSL code could also be written in a single line - that’s another option that I considered. I’ll basically have to figure out the “least ugly” option here…)
Sounds like very good sense.
Thanks for the responsiveness on such an old issue…