Jump to content

Please improve error/warning messages


photo

Recommended Posts

Posted

Hi,

At load time (2.15), we have a lot of warning or errors and fixing them is tedious because the message itself is not always clear, so we lose time trying to actually find the error.

A few examples:

// the DIS type is not printed in a human readable form
Config::loadEntityTypes: duplicate entity type id 67174400 (XXXXX)
  
// Here also the DIS type is not readable  
Config::loadEntityTypes: can't find node 'XXXXXXXX.node' for 352845825 entity type
  
// Here the parent material was lost. But having the last known name would greatly help
"XXXXXXX.mat" can't find material : 1fc1440f7fd46222eea37b19833929a4bdf168b3
  
// These kind of errors routinely pop up when a .runtime has been left behind (typically
// because the runtimes are stored in SCM). It would be great then to simply state that, or remove it when found
// or inform of which file this runtime file refers to.
ERROR:	FileSystemAssets::load_runtime(): invalid runtime "0d1c07ebd7f5fc4eda11d755726fc0b06411dc4f.basemat.private" guid
ERROR:	FileSystemAssets::load_runtime(): unknown "19de75abad500f0e67dd4b1503a32170aefa460f" asset guid
// Note that these messages can be repeated hundreds of time with the exact same guid: noisy and useless!
  
// These messages are frightening for no reason, because in this case we actually expect a null, as the
// parameter of the component is optional in our use-case.
// How do we remove or prevent them? Is there an 'optional' flag?
WARNING:	ComponentBase::null_check(): parameter "XXXX" of the property "XXXXXXComponent" is null

// It looks like during reimport of OBJ/FBX, the importer moved the texture to the wrong folder and with the wrong format.
ERROR:	ImageLoaderPNG::load(): wrong signature in "/not/the/path/of/the/source/image/XXXXXX.png" file
ERROR:	"ImportTextureStage: Image file saving error. (Source filepath: /not/the/path/of/the/source/image/XXXXXX.png)"
  
  

Thanks!

Posted

Hi Stephane,

Thanks for the feedback. We will see what can be done there.

I'm afraid not all the messages are trivial to fix (especially with GUIDs) since there is no reliable way to get the correct name that we can show (and wrong guessed name can result in even worse situation).

Quote

// It looks like during reimport of OBJ/FBX, the importer moved the texture to the wrong folder and with the wrong format.

Importer is not doing anything with original files, so the root cause of this issue is still unknown. Maybe FBX contains JPG image in the PNG or somebody changed FBX and all the textures paths / names inside.

 

Quote

// These messages are frightening for no reason, because in this case we actually expect a null, as the
// parameter of the component is optional in our use-case.
// How do we remove or prevent them? Is there an 'optional' flag?
WARNING:    ComponentBase::null_check(): parameter "XXXX" of the property "XXXXXXComponent" is null

You can adjust warning level via API as well (setWarningLevel): https://developer.unigine.com/en/docs/2.16.1/api/library/common/logic/component_system/cpp/class.componentsystem?rlang=usc#setWarningLevel_int_void

How to submit a good bug report
---
FTP server for test scenes and user uploads:

×
×
  • Create New...