Errors descriptions in logs

CAMA

Hello.

As part of unofficial user support, I would like to request a more thorough elaboration of the description for errors that the user receives in case of unsuccessful export, saving and other program errors.
I often encounter banal lack of memory, problems with project resources, etc., but usually the logs are uninformative both for the average user and for me. And in the end I have to check the project file myself to find the cause. I believe that it is possible to make simpler text formulations in human language based on the received common problems.

It is clear that a certain part of the logs is needed to understand technical issues, but it is difficult for an ordinary user to navigate the web of errors.



Another example that doesn't allow you to see the picture:

ERROR java.lang.Throwable$WrappedPrintStream -1 println - at com.live2d.cubism.CEAppCtrl.command_exportVideo(Unknown Source)

For some errors there are no results other than "I am programming in Java and I encountered this error".

ERROR java.lang.Throwable$WrappedPrintStream -1 println - javax.imageio.IIOException: I/O error writing PNG file!

It's really great when there's at least text like the one in the quote below. When there's the name of the artmesh, deformer, parameter or something else that is causing the problem. And unfortunately it's still poorly written.

[ERROR] Exception in thread "AWT-EventQueue-0" java.lang.IllegalStateException: illegal_state : Failed to get default key form guid

Why should users usually settle for vague phrases like "Scene are failed to output"? I'm sure there aren't a million reasons for things to go wrong. Most of the cases are absolutely trivial.



Please don't think that I am angry or rude in my request. On the contrary, I want the program to continue to develop successfully and make the process of troubleshooting easier. I really appreciate your efforts in developing and delivering better software. That's why I ask you to take the time to work on this important aspect.

Thank you and have a nice day.

obsidian

I totally agree. I suppose outputting logs is better than not outputting them at all, however, more user-friendly logs would empower us to troubleshoot a wider range of problems ourselves.

ookubo(staff)

Hi @CAMA and @obsidian

Thanks for using our products.

Your request has been shared with our development team.

Best regards.