Categories
- All Categories
- 1.3K Cubism Editor
- 1K Help
- 56 Tips and Tricks
- 155 Feature requests
- 50 Other Live2D Products and Tools
- Cubism Viewer (for OW, for Unity)
- 3 Material Separation Photoshop Plug-in
- 47 Other Live2D Products and Tools (Other Photoshop Scripts, Sample Data, etc.)
- 268 Cubism SDK
- 241 Help
- 11 Tips and Tricks
- 16 Feature Requests
- 8 SDK for Unreal Engine alpha
- 4 Download
- 1 Manual and Update History
- 3 Bug
- Feature Request
- 181 Community
- 37 General Discussions
- 9 Feature Requests
- 26 Projects, Showcase & Critiques
If you have any questions, reports, suggestions, or requests about Live2D, please send them to this forum.
※We cannot guarantee statements or answers from Live2D staff. Thank you for your understanding in advance.
Live2D Cubism
Cubism Products and Downloads
Cubism product manuals and tutorials
Cubism Editor Manual Cubism Editor Tutorial Cubism SDK Manual Cubism SDK Tutorial
※We cannot guarantee statements or answers from Live2D staff. Thank you for your understanding in advance.
Live2D Cubism
Cubism Products and Downloads
Cubism product manuals and tutorials
Cubism Editor Manual Cubism Editor Tutorial Cubism SDK Manual Cubism SDK Tutorial
Editor Error Causing Screen Glitch?
Hi there, I'm not exactly sure where to start. My partner uses Live2D to do animated bg's and logos and such and after they recently updated to the newest version, 4.2.04, they've run into this error that makes it so they can't do their job.
What happens is they go to open a file they're working on and it opens, everything seems fine for a few moments then the image/canvas/work area goes black and their main monitor that they're not even working on, as it's a duel monitor setup, starts to glitch and twitch and it stays glitching/twitching even after Live2D is closed. While the program itself is open and running, they can even still access menus and everything, but the work area is blacked out. The labels for each component still pops up when you hover even. We're so confused as to what to do as up until this latest update theprogram ran just fine and nothing seemed broken.
I updated drivers, cleared space, uninstalled/reinstalled the whole program and nothing worked. Nothing on the pc itself or windows is damaged/out of date and no other program they use is messing up or causes their screen to freak out. This thread here seems to be as relatable as I can find to it but even trying the provided help in it didn't solve the issue. The folder they said to delete doesn't exist on the pc anywhere and the screens are both set to normal 100% resolution. Any help would be great thank you! The PC is a Dell Inspiron 5400 AIO and I've included a screenshot of the described problem plus the PC specs itself!
What happens is they go to open a file they're working on and it opens, everything seems fine for a few moments then the image/canvas/work area goes black and their main monitor that they're not even working on, as it's a duel monitor setup, starts to glitch and twitch and it stays glitching/twitching even after Live2D is closed. While the program itself is open and running, they can even still access menus and everything, but the work area is blacked out. The labels for each component still pops up when you hover even. We're so confused as to what to do as up until this latest update theprogram ran just fine and nothing seemed broken.
I updated drivers, cleared space, uninstalled/reinstalled the whole program and nothing worked. Nothing on the pc itself or windows is damaged/out of date and no other program they use is messing up or causes their screen to freak out. This thread here seems to be as relatable as I can find to it but even trying the provided help in it didn't solve the issue. The folder they said to delete doesn't exist on the pc anywhere and the screens are both set to normal 100% resolution. Any help would be great thank you! The PC is a Dell Inspiron 5400 AIO and I've included a screenshot of the described problem plus the PC specs itself!
Comments
I have an update! We finally got the logs to pull up and it seems like it's constantly calculating screen size and creating a back up of the file like it expects the program to crash when the program locks up like the canvas/work area is about to black out. They've been trying to work through it as the canvas/work area hasn't blacked out this time but I just wanted to add that.
Update again. Here's a screenshot of the log itself!