When working with Live Update it would be really helpful if resource errors has a higher granularity. As it is now, any failure to create a resource (resource.cpp > DoCreateResource) often result in the generic dmResource::RESULT_FORMAT_ERROR.
Take res_render_script.cpp as an example where ResRenderScriptCreate() will return RESULT_FORMAT_ERROR when it
- fails to load the protobuf file using
dmDDF::LoadMessage
- fails to create submodules using
dmGameObject::RegisterSubModules
- fails to create the render script using
dmRender::NewRenderScript
(the same kind of scenario exists for res_script.cpp as well).
It would be very helpful if I as a developer knew if it was breaking change in the protobuf format (unlikely) or if my liveupdate archive has a reference to a file that doesn't exist (more likely).
When working with Live Update it would be really helpful if resource errors has a higher granularity. As it is now, any failure to create a resource (resource.cpp > DoCreateResource) often result in the generic
dmResource::RESULT_FORMAT_ERROR.Take
res_render_script.cppas an example whereResRenderScriptCreate()will returnRESULT_FORMAT_ERRORwhen itdmDDF::LoadMessagedmGameObject::RegisterSubModulesdmRender::NewRenderScript(the same kind of scenario exists for res_script.cpp as well).
It would be very helpful if I as a developer knew if it was breaking change in the protobuf format (unlikely) or if my liveupdate archive has a reference to a file that doesn't exist (more likely).