blocks2assets: debug filepath on reading unsupported blocks #92885
No reviewers
Labels
No Label
legacy module
Platforms, Builds, Tests & Devices
legacy project
Blender Asset Tracer
legacy project
Platform: Windows
Priority::Normal
Status::Archived
Status::Confirmed
Status::Needs Triage
Status::Resolved
Type::Design
Type::Report
Type::To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-asset-tracer#92885
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "oliverpool/blender-asset-tracer:blocks2assets_print_filepath"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To ease support of other data blocks in the future, this PR logs the filepath to the debug message on unsupported block types (if present).
To test this PR, you need to have a blend file with an unsupported block type, which contains a
filepath
property.For instance VDB volumes of scene_with_vdb_and_fluid_cache.zip are not supported yet (PR pending in #92884). As long as VDB are not supported by BAT, the log will read:
When rendering a scene prepared by BAT, having the filepath of the block in the log will help a lot, to know what kind of asset could not be read.
Please update the PR description, so that it actually describes what the PR is for.
The code is getting quite nested now, which I think can easily be resolved. Also I would suggest using
%r
for printing the filepath, rather than%s
, such that trailing spaces and empty strings are recognisable. Finally, it would help to know that the 2nd string that's printed is actually thefilepath
property.This would combine into something like:
Could you also add some instructions to the PR description on how to test this particular branch of the code? That'll make testing & accepting this PR a lot easier.
5088f6d569
to589dbd6752
I implemented your suggestion and rebased on top of main (hence the force-push)
This one is still missing, though.
Sorry, I overlooked this part of your comment.
You can use the .blend file of #92884: scene_with_vdb_and_fluid_cache.zip, the log will output:
Looks good, thanks!