We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
问题:waifu-tips.js 进行资源加载时error ! 如图所示:
描述:live2d source Loading problem 加载模型:Live2D 模型 6-0 加载完成后出现错误 html page error msg : Package size exceeded the configured limit of 50 MB. Try https://github.com/fghrsh/live2d_api/tree/1.0.0/model/HyperdimensionNeptunia/nepnep/general/pose.json instead.
已尝试解决方案: 切换文件内部资源加载链接为本地: 42行 script.src = "https://cdn.jsdelivr.net/gh/GalaxyMimi/CDN/asteroids.js"; 54行 open("https://github.com/stevenjoezhang/live2d-widget");
仍未解决;分析原因可能不是因为这两份资源导致。 如大佬有时间请看一下是否能处理,不胜感激。
说明:通过demo进行测试人物切换一样的问题。 我是按照顺序切换模型的,当切换至模型6时就出现资源403问题。 下载demo在本地测一样的结果,demo1; 我这边环境为 macOS Mojave 10.14.3 目前 测试了两款浏览器:google、Microsoft Edge 均浮现,我觉得可能是因为加载了人物说话声音的资源导致的。因为不发声的人物没有问题
The text was updated successfully, but these errors were encountered:
似乎和这个 Issue 是一样的 #4
Sorry, something went wrong.
好像是跟#4一样,解决了吗?
Create pose.json
439a60c
2a9b337
我的问题是,直接人物没出来,用的是谷歌,用ie就没问题
No branches or pull requests
问题:waifu-tips.js 进行资源加载时error !
如图所示:
描述:live2d source Loading problem
加载模型:Live2D 模型 6-0 加载完成后出现错误
html page error msg :
Package size exceeded the configured limit of 50 MB. Try https://github.com/fghrsh/live2d_api/tree/1.0.0/model/HyperdimensionNeptunia/nepnep/general/pose.json instead.
已尝试解决方案:
切换文件内部资源加载链接为本地:
42行 script.src = "https://cdn.jsdelivr.net/gh/GalaxyMimi/CDN/asteroids.js";
54行 open("https://github.com/stevenjoezhang/live2d-widget");
仍未解决;分析原因可能不是因为这两份资源导致。
如大佬有时间请看一下是否能处理,不胜感激。
说明:通过demo进行测试人物切换一样的问题。
我是按照顺序切换模型的,当切换至模型6时就出现资源403问题。
下载demo在本地测一样的结果,demo1;
我这边环境为 macOS Mojave 10.14.3 目前 测试了两款浏览器:google、Microsoft Edge 均浮现,我觉得可能是因为加载了人物说话声音的资源导致的。因为不发声的人物没有问题
The text was updated successfully, but these errors were encountered: