Hey, can’t you add another hook to loader2 so we can use custom logic for the search algorithm?
For instance, we’re using a very customized system to handle published files, so we can handle pbr materials (based on textures and udims, for instance). Therefore, we’d need to search differently.
I’ve tried to add the logic in the filter publishes hook, but it keeps executing it even if we just move the UI window, so it becomes very slow.
Can you not filter in the app setup like this?
Thanks for the idea, but that doesn’t work for me because I use a very customized file-handling approach. For instance, I’m not using PublishedFiles directly. Instead, I’m using a custom class passed to the plugins. That allows a unified approach for handling and publishing files from Houdini without starting the tk-multi-publish2 plugin—we’re using a two-step approach for file publishing. That’s why we need first to publish using Houdini’s PDG, and after validation, we may publish from the UI.
That is proving to be a far more manageable (and better) approach to file handling from within Houdini.
I’m using the custom classes and methods in the filter hook, but even moving the UI window triggers the execution of the hook’s code, forcing me to store the result anywhere in Houdini for better performance.
If even moving the UI triggers the filtering hook then that should be a defect because that should not happen.
Best to make a ticket to support, or, if you find the defect in the code, make a pull request.
I’ll do that, thanks!
1 Like