Dash Asset Tagging Questions
Dash Asset Tagging
I've searched high and low for a systematic tutorial on asset tagging in Dash.
If anyone knows of one, then please...
I set up a project with the intention of using that to tag all my assets, which probably numbers a lot more than 4,000, so who knows how long this might take but I can set and forget for a day or 3.
Firstly, must the assets reside within a project folder, or can they be contained within my Megascans asset folder, which is not a project folder?
Second issue and a question, does Dash in a UE5.5 project read assets created or residing within a UE5.4 or 5.3 project etc.?
I have no answer to these questions because whenever I try to set a path to any external folder (that is external to the source project folder) to tag assets,I get the error message: “The selected directory is not a valid project library”. This happens irrespective of whether I select a project folder, a Content folder within a project folder, or a non-project general folder such as my constipated Megascans folder.
A non-specific error which provides no direction or solution.
Anyone any ideas?
3 Replies
Hey @RickD 🙂
I will try and answer all your questions! (the GPT response is quite bad and wrong 😬 )
1. I actually wrote a new page in our docs regarding this yesterday, so that's worth checking for sure: https://docs.polygonflow.io/how-it-works/centralized-asset-browser
2. We are only able to tag/compute assets that have been added to your project and also are within the Content folder.
3. If you have downloaded Megascans from Bridge plugin or FAB, we have separate views in our Content Browser for these, so no need of computing them as with your custom project assets 🙂
4. The external library settings are actually about other UE projects where you have already computed assets with Dash. So if you have computed assets in Proj_1, and in Proj_2, then when you are in Proj_3 you can browse, search and use the assets from Proj_1 and Proj_2. (We import the assets when you decide to drag them in and use them.)
So external library settings is about if you want to show assets from other UE projects where you have computed assets 🙂
5. So yee the GPT answer is not great. Yes you can only tag assets within a project, but as mentioned, once you have done that, the assets with their tags are available to use in other projects. So the method there for Master Asset Library is a good start but point 4 is in reality: Now in this new project, you can browse, search and use all of these assets you computed in Master_Asset_Library. So no need to migrate anything manually. We handle the import when you actually use assets in the new project 🙂
Centralized Asset Browser | Dash Documentation
With Dash's Content Browser, you can tag all your assets, making them easy to find and also create a Centralized Asset Browser. Meaning that you can access all your UE5 assets from any Unreal project.
I hope this helps a bit @RickD, happy to discuss further if needed! 🙂
And if you have feedback on the new page in the docs about this, let me know!