-
-
Notifications
You must be signed in to change notification settings - Fork 35.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ColladaLoader: Error while parsing/building skeleton #13335
Comments
File: https://drive.google.com/drive/folders/1jR--PnBAwM6R2cgb0CvrIkGbVaD99WHI I see multiple problems with this |
Your model should now load with the latest |
Yeah, you're right. I've added a change to my local The problem is that the file refers to the skeleton in an unusual way. It does not refer to the top most bone but to the node of the visual scene. <skeleton>#ID8</skeleton> to <skeleton>#ID9</skeleton> the file should actually load ( |
I asked stackoverflow, and the first comment suggested it may be a bug that I should report.
I give a detailed report in my post here:
https://stackoverflow.com/questions/48796931/why-cant-colladaloader-js-from-three-js-load-my-file/48797863#48797863
And here's extra relevant info not mentioned on stackoverflow.
Chrome requesting http://127.0.0.1:5000/raptor
Flask web server returns raptor.html that imports three.js and ColladaLoader.js and contains the script to import the raptor.dae.
Substituting raptor.dae with the elf.dae from the demo works.
Windows 10
NVIDIA GeForce GTX 950
Files saved and server run on Samsung 128GB USB 3.0 Flash Drive Fit (MUF-128BB/AM) https://www.amazon.com/dp/B017DH3O5A/ref=cm_sw_r_cp_apa_m3pHAbXRXVACJ
Everything I've done is self taught, and this issue is just the one obstacle where I don't have the knowledge to solve it, let alone the minimum amount of knowledge to search for the answer.
Any guidance I can get would be greatly appreciated.
The text was updated successfully, but these errors were encountered: