-
Notifications
You must be signed in to change notification settings - Fork 19
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
Cannot load animation loaders #3
Comments
Hi, aframe-vrm.js loads animation modules from threejs.org, but it no longer works because the module resolving on the site has changed. I added following importmap ( https://github.com/WICG/import-maps ) to htmls as a workaround.
On my end, it works fine on the latest Chrome, but for future stability, this should be resolved at build time, without relying on threejs.org. I can't start working on it right away :-), so I have added a new issue: #4 |
Thank you and sorry for the late reply. I could not solve it as you wrote but I could solve it by pulling your latest updates, forking the repo, putting BVHLoader.js, CCDIKloader.js, and MMDLoader.js under the utils folder, and linking them as below on vmd.ts there was also another error on dist/aframe-vrm.module.js that I think is not directly related to animations
I couldn't figure out what was happening so commented out the dispose function...obviously, this may break something but so far looks like everything works fine...later on if I can solve it I will send a pull request dispose() { |
Hi
I am trying to load animations but getting below errors. Our app uses three-133 so I tried forking the repo and updating three version to 133 and 137. Tried calling models from imported Three, as written here without success. I am trying to load VMD animation (that works with three-pixie and others) but when I load your BVHs they don't work as well. Looks like BHVs in your demo don't work too, the console gives out some three issues. This is a very nice component you have here and want to use it in production, will be glad if you have an idea about the issue. thank you.
The text was updated successfully, but these errors were encountered: