Mudstack

We have just launched 1.24.1, which adds a new queue system and a host of other minor improvements and bug fixes! This update significantly improves push/pull performance and gives full visibility on the progress in totality and of each individual file as they are uploaded and downloaded. ?? New Stuff This addition to Mudstack gives significantly more visibility and stability during downloads, uploads, thumbnail generation, fetching, and other future large batch tasks. These tasks are now done asynchronously, speeding up your workflow time rather than waiting on processes to complete in Mudstack. You'll now get a time estimate for completion, spinners on file in the file search view that are still downloading, and dramatically reduced Disable sync times for team that have reduced disk space. We have also added some other QoL features - Added File Size column in push table - Deleting a folder with ignored files will now delete the ignored content and fully remove the folder - Cancel Commit Item on a Error in order to retry or fix an issue ???Bug Fixes - Added a button to go up a level in the files view next to back and forward - Added X button to clear search input field - After opening a file, Auto Sync should be set properly - Hanging commits edge cases should be captured and handled better - Updated the timestamps on the Diffs in the Sync view to show correct date - Handle additional 401 errors on membership and revocation calls - Check if the Mudstack temp folder exists before getting new versions of files - Delete workspace UI was missing - Warn user when downloading while not mapped properly - Mudstack Temp now creates a unique filename each time a download occurs - Settings/Account Settings/Workspaces/Details permission edge case handling and recovery ?? What's next? We have a host of other optimizations we are looking forward to cleanup, primarily focusing on the Staged ? Push start speed and importing large sets of data before sending to cloud (think initial data migrations to Mudstack)

We are thrilled to announce some big news! We just raised $4M from Anthos Capital, Khosla Ventures, A16Z GAMES, Pioneer Square Labs joining existing investors Hyperplane, Overline, and Forum Ventures. Also James Gwertzman, previously co-founder and CEO of Azure PlayFab, is joining as CEO. James brings decades of experience in the industry, a huge passion for solving core infrastructure problems, and a big vision for Mudstack and what's possible! We are also announcing new customers Paradox Interactive and Metacore, and we want you as a customer too!

Investing in a Digital Asset Management (DAM) tool is a big decision for a game studio, but is it a decision your studio even needs to make right now? There are several reasons why you might want to defer the decision for later. Here are our top 5: 1: You Have a Small Team & It's Not Growing If you have just a handful of artists on staff, managing the content created— locations, versions, approvals, etc— is probably not a pain for your team. If you don't have plans to grow (and that is 100% fine), your existing processes are likely serving you well enough to not have to bother with a DAM. 2: You Know Where to Find Every File Your file naming conventions, folder structures and workflow practices have joined forces, enabling you to find what you need in seconds. If this is true, congratulations! You might not need a DAM. 3: Version Control is Easy for Your Artists Your artists love Git or Perforce, and they don't struggle with branching, shelving, locking or checking out files. Or perhaps you don't even bother to version source assets, and have decided that the risk is worth the reduced hassle of dealing with versioning these files. 4: Your Feedback Process is Working Great If your remote/async team is happy managing feedback across Slack/Teams/Jira/Miro etc, and feedback being disconnected from the files hasn't proven to be a problem, then you might not need a DAM. Reason 5: You Have Limited Resources You've already paid for Google Workspace for your email, so why not rely on Google Drive for your cloud storage? If your team primarily works on 2D assets, this is probably the right decision — after all, you can preview these file formats even in Drive, and deal with its suboptimal versioning abilities. You might not have the option to entertain additional costs for a custom DAM built for game studios till you have more resources. ----------- If, however, these reasons don't resonate, you might want to consider a DAM custom built for game studios. You know where to find us ??.

Investing in a Digital Asset Management (DAM) tool is a big decision for a game studio, but is it a decision your studio even needs to make right now? There are several reasons why you might want to defer the decision for later. Here are our top 5: 1: You Have a Small Team & It's Not Growing If you have just a handful of artists on staff, managing the content created— locations, versions, approvals, etc— is probably not a pain for your team. If you don't have plans to grow (and that is 100% fine), your existing processes are likely serving you well enough to not have to bother with a DAM. 2: You Know Where to Find Every File Your file naming conventions, folder structures and workflow practices have joined forces, enabling you to find what you need in seconds. If this is true, congratulations! You might not need a DAM. 3: Version Control is Easy for Your Artists Your artists love Git or Perforce, and they don't struggle with branching, shelving, locking or checking out files. Or perhaps you don't even bother to version source assets, and have decided that the risk is worth the reduced hassle of dealing with versioning these files. 4: Your Feedback Process is Working Great If your remote/async team is happy managing feedback across Slack/Teams/Jira/Miro etc, and feedback being disconnected from the files hasn't proven to be a problem, then you might not need a DAM. Reason 5: You Have Limited Resources You've already paid for Google Workspace for your email, so why not rely on Google Drive for your cloud storage? If your team primarily works on 2D assets, this is probably the right decision — after all, you can preview these file formats even in Drive, and deal with its suboptimal versioning abilities. You might not have the option to entertain additional costs for a custom DAM built for game studios till you have more resources. ----------- If, however, these reasons don't resonate, you might want to consider a DAM custom built for game studios. You know where to find us ??.