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
[BUG] Transformation tools locks up the Editor when Lock Default Deformer is checked
I'm on Live2D 4.1, here's how to reproduce the bug:
- Select a Warp deformer
- Check the Lock Default Deformer ON
- Pick any new Transform tools (Envelope, Perspective, Temporary Deform Warp/Path, etc)
- There's a message "Only Objects that can be deformed on Canvas are valid"
- Deformers and Parts palette are greyed out, locked, no transformation handles in the canvas, no button or shortcut to get out the "Transform" mode.
Granted you can go back to the menu to "Deselect the Temporary Deform Tool" but it's kind of hidden away and might confuse even any experienced users. When the first time I met this 'error' I restarted the whole Editor thinking it's a severe bug.
Please add an easily accessible button on the canvas to "Deselect" the tool.
- Select a Warp deformer
- Check the Lock Default Deformer ON
- Pick any new Transform tools (Envelope, Perspective, Temporary Deform Warp/Path, etc)
- There's a message "Only Objects that can be deformed on Canvas are valid"
- Deformers and Parts palette are greyed out, locked, no transformation handles in the canvas, no button or shortcut to get out the "Transform" mode.
Granted you can go back to the menu to "Deselect the Temporary Deform Tool" but it's kind of hidden away and might confuse even any experienced users. When the first time I met this 'error' I restarted the whole Editor thinking it's a severe bug.
Please add an easily accessible button on the canvas to "Deselect" the tool.
Comments
Thank you for your contact and report!
I'm sorry for causing you concern.
Successfully reproduced the problem and understood the bug.
I have shared this bug with the developers.
It will be fixed in a future update.
We appreciate your cooperation.
Thank you.