In App-Purchase. Let users buy more AI tagging credits at any time.
I create both my own library of assets (for example frames with photos inside) as well as regularly buy assets which means it's not hard for me to exhaust even 4000 tags in a month. Please make it possible for a user to do "in-app" purchases of additional credits as required. This feature might make your CFO happy too 🙂
14 Replies
It is something we are planning on looking into down the line for sure!
Right now it is not something that is easily fixed sadly.
But what I could offer you if you are interested, is setting up a custom payment link and going in and changing your license manually.🤔
Either I could permanently increase your monthly limit, or I could increase it temporarily for one month and reset it back to 4K next month.
Would you be interested in one of them? 🙂
Hi Daniel~
I have the same demand like this and would like to inquire about the second option: If I want to temporarily activate unlimited tag usage for one month to organize the existing local asset library, what would the cost be approximately? (If the price is acceptable, I am very keen to start this work in the upcoming February.)🥹
Hey, thanks for reaching out with this!
As mentioned we don't have a structure for this, but I can set up a payment link and change your limit manually for one month for sure!
Have not thought about it much at all actually, but here are some suggested prices, feel free to share honest thoughts!
One month extra tags prices idea:
1. 3000 Tags - 5 USD
2. 7000 Tags - 10 USD
3. 15000 Tags - 20 USD
4. Unlimited - Maybe 70 USD? 😄
Thank you for your prompt response!
...To be honest, the pricing far exceeds what is acceptable, especially given that Dash's current functionality for managing tagged assets is not ideal...
As briefly mentioned in a previous email, my initial motivation for including Dash in my permanent toolkit was to use it as an asset manager. However, based on my current experience, it feels like Dash's functionality for managing tagged assets is almost non-existent (for example: it's not possible to apply computer tags just to selected assets; there's no convenient way to batch manage the .json-file folders of already tagged assets; the cache data under UnrealContentLibrary seems to only support one level of folder recognition, so it's not even possible to create separate folders within for assets from the same asset pack which shared the same UE project for better organization;; Therefore, if tagged assets are moved, it's not easy to batch modify the tagged data or choose to delete and retag them, etc.)🥹
The current monthly tag limit is more suited for one-time use rather than managing a local asset library, so I felt the pricing plan you've provided to be unacceptably high: a few thousand tags are just a drop in the bucket when dealing with a large asset library; but the $70 for just one month of unlimited use exceeds the lifetime cost of many even more expensive UE toolkits...😅
Thanks for sharing your thoughts!
It definitely has some limitations that's true, and we have plans for larger improvements in this quarter 👍
Regarding the pricing, it was definitely just a first idea, so would love to hear your thoughts, should it be decreased by 50%, 75%? 🤔
…for the temporary usage needs of current version (←cause the tag database built in the current version may need completely rebuilt in future versions), I think a price of $5-10 for one month of unlimited tagging may be a more acceptable range for users (approximately equivalent to the price of one month of Dash's monthly subscription during the early promotional period).🥹
(To be more honester, I personally hope it would be around $5.)😆 💥
We would never reset your tagged cache so no worries about that 😁
How many assets are you looking to tag approximately? Need to remind myself of our tagging cost (it is a API cost for us for each asset tag users make) before knowing if your suggsted price is doable or not😅
Hmm... The concern about the tagged database stems from the issue of needing to edit the tagged cache when reorganizing assets or changing the storage location of some tagged assets during future use.
I noticed that in the current version, the storage location of each asset is recorded in the metadata.json file of its cached data. If a tagged asset is moved to a new location, the storage path recorded in each asset's .json file needs to be manually updated, which is difficult to achieve in bulk with the current version's cache management functionality...🥲 🥹
Ah... I hadn’t fully understood the issue of API costs before💥 that's indeed an additional direction worth to think about! 💦
I haven’t calculated the exact number of tags needed yet, I’ll come back to continue the discussion later if I calculate them out~😋
Thanks for sharing your concerns! I will relay this to the main Content Browser guy!🙌
Sounds good, we can continue the discussion then! 🙌
This limitation is one of the main reasons I haven't yet even decided to try Dash yet. I currently have about 1000 asset packs between Fab (not even including Megascans) and Cosmos that I have been collecting over the years...so even using a small percentage of those would put me over the limit within a very short period of time. Mind you, thinking about it...I probably wouldn't be using a small percentage all at once all the time (or even for one project) but the limitation has me worried. Only a few people here are also worried about the limitation (that we know of) ...but this definitely needs to be analyzed...especially for devs with a ton of assets....and large scale projects. Hoping this becomes more reasonable quickly.
Hey @PhoenixSpyder 🙂
Thanks for sharing your thoughts, very useful.
Just to make sure we are talking about the same thing, you mean the limit we have on how many assets you can add search tags to per month? (You can of course, compute and add in all your assets to the Dash Content Browser without using the AI tagging feature, and then there is of course no limits)
@Daniel - COO yes, the limit for tagging is what I mean. I wasn't aware that computing assets was separate. Thanks for clarifying that this is 2 different things
No worries!