Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 539 All Categories
- 234 Cubism Editor
- 170 Help
- 41 Tips and Tricks
- 19 Feature requests
- 8 Cubism Viewer
- 8 Help
- 68 Cubism SDK for Unity
- 65 Help
- Tips and Tricks
- 3 Feature Requests
- 72 Cubism SDK
- 61 Help
- 6 Tips and Tricks
- 5 Feature Requests
- 13 Euclid
- 7 Editor
- 6 SDK
- 121 Community
- 11 General Discussions
- 7 Feature Requests
- 13 Projects, Showcase & Critiques
- 106 Archive
Dear Users,
Now, we are seeking users who can give us a hand with expertise to evolve our software more dynamically.
If you are willing to help us, we’d like you to make a registration for “Live2D Creators Circle” via the link below.
Designers, programmers, translators are especially welcomed so far.
(More detailed explanation will be given to you before we ask you to do tasks)
https://docs.google.com/forms/d/1G5KK_GL3ozwPXtTHrpi_ktbsI8UZf8jlYRSlDworyBo/viewform?usp=send_form
Now, we are seeking users who can give us a hand with expertise to evolve our software more dynamically.
If you are willing to help us, we’d like you to make a registration for “Live2D Creators Circle” via the link below.
Designers, programmers, translators are especially welcomed so far.
(More detailed explanation will be given to you before we ask you to do tasks)
https://docs.google.com/forms/d/1G5KK_GL3ozwPXtTHrpi_ktbsI8UZf8jlYRSlDworyBo/viewform?usp=send_form
set clippingMeshId bug
The clippingMeshId can't be set when the viewport is not the home view, X and Y is not zero.
Comments
Did you said the clipping ID only work when X and Y is 0?
what Cubism version do you use? 2.1 or 3.0?
It turned out that the symptom in your report was bug. Now we are working on fixing it and it would be fixed by the next update with our earliest schedule.
Thank you so much for your contribution.
This problem was fixed in the last update. If you still meet the same issue, I'd like you to let me know. I appreciate for your patience.
Sincerely,
I've asked the team and the the issue is likely to be fixed in the next update. I apologize for our miscommunication and my telling you a wrong information.