![]() Quote from steamworks page: Future ISteamUGC Direction You could either keep some backwards compatible code on the first release with ISteamUGC or do a automated update of all items once using a tool.Īs you can read from the changelog, it eliminates the 200MB limit on the workshop files, reducing the amount of workshop files to download (take the stargate (CAP) or GMod Tower for example), which in turn reduces the amount of search paths gmod needs to look trough upon loading, reducing loading times and increasing overall performance (depending on the situation but for most cases). Yes, however once updated to ISteamUGC, the ISteamRemoteStorage API will no longer work with that workshop item. Q: Is it possible to update an item published using ISteamRemoteStorage with ISteamUGC? The new API is not backwards compatible with old items created with ISteamRemoteStorage.Ībout the last sentence, no you don't need to re-upload all those workshop files, to quote the docs: So the game doesn't need to fetch them using ISteamRemoteStorage anymore. Subscribed workshop items will be placed in unique subfolders in the install folder, Regular content depots, resulting in faster and smaller downloads due to delta patching. ![]() It uses the same content system that handles Added a new Workshop item content API in ISteamUGC that is easy to use, allows multiple files per item without any size limits.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |