Categories
- All Categories
- 1.4K Cubism Editor
- 1.2K Help
- 54 Tips and Tricks
- 200 Feature requests
- 51 Other Live2D Products and Tools
- 1 Cubism Viewer (for OW, for Unity)
- 3 Material Separation Photoshop Plug-in
- 47 Other Live2D Products and Tools (Other Photoshop Scripts, Sample Data, etc.)
- 302 Cubism SDK
- 266 Help
- 11 Tips and Tricks
- 25 Feature Requests
- 182 Community
- 40 General Discussions
- 10 Feature Requests
- 26 Projects, Showcase & Critiques
Parameter not moving when I enable 'Randomize Parameters' option
in Help
Hello! I'm having some trouble with this function and I really need it fixed since I use it religiously to check the motions of my model.
Here's how it played out, I open Live2D and get to work on my model, I add the Mesh to a part and animate it with three points on a normal parameter in a folder I made for that area. It's been a while and I finally check it and the 'Randomize Parameters' function is working just fine for everything but this one part in particular. I don't think I've done something crazy to it, but I don't know what has happened, any help is appreciated!
Here's how it played out, I open Live2D and get to work on my model, I add the Mesh to a part and animate it with three points on a normal parameter in a folder I made for that area. It's been a while and I finally check it and the 'Randomize Parameters' function is working just fine for everything but this one part in particular. I don't think I've done something crazy to it, but I don't know what has happened, any help is appreciated!
Tagged:
Answers
When I test, I can never get EyeL Open and EyeR Open to work during Randomize
Have you tried seeing if your parameter moves with Randomize A or Randomize B presets?
The Random Playback feature is just a feature that allows you to play the parameters at random.
Playing all the parameters is not a feature.
There are also some parameters that will not be played.
@Chibox
Thank you for the help!
@Enoko(Staff) No problem. Can you confirm if my statement to BeeilistBonk is accurate. This is what I found with my own testing, but I'm unsure if this is a consistent workaround.