Increase Compressed Upload Size to 15 MB
A number of us creators have run into a problem where our characters meet all of the geometry requirements for upload to the cloud, but the compressed size of their character file isn't quite less than 10 MB.
I do think a compressed filesize limit is reasonable, but could it possibly be increased to 15 MB? I doubt it will be needed in most cases, but for those edge cases, a little more breathing room would be nice.
Comments
0
vote sum by 0 users.
Suggestion status
Implemented.
was not a probleme before but now it's a thing yeah glb is way much bigger the obj or the fvne cloth one
same comparison from png to jpg, exept glb offer so much more this is a must have !
Get up peasants, raise your torch and fork !!!
@AltTab
...politely!
@MobiusScarf
of course ! and patiently !
but don't forget the torch it's important.
50% increase is not a "little more", people would use it all the way up to 15mb compressed size anyway. No matter what standard you set it to, people will maximize even if they could optimize.
Just like with 10mb.
The idea of the limit is for keeping the characters in a server and making them not be too big when used and whatnot. 50% increase is... a lot.
@Craket
First of all, I would be curious to see what the average compressed character size is for the characters in the cloud, because I doubt most uploads push the upload filesize limit that frequently.
Second, as @AltTab pointed out, the recent inclusion of glb files, which do not always compress as well as OBJ files, has caused an overall increase in character size. What would have fit within the 10 MB limit before interactions no longer fits. This feels like a fallacious slippery slope argument to me, especially since I'm not asking for an increase in the geometry limit or draw calls or anything like that. Just compressed size.
@Craket
When you frame it like that, I suppose it SOUNDS like a lot, but when the current cost of storing yl2c character files in the cloud is probably somewhere in the ballpark of $10/year, a theoretical 50% increase would be another $5/year. Not exactly a massive business expense. And that's assuming paying the standard prices.
I would very much welcome that, then the resolution of the textures wouldn't always have to bumble around at 512.
@MobiusScarf Excuse me but, Where did you hear that storing Yl2c character files in a server costs only 10dollars a year?
I dont think it is that cheap, a single character costing 50% more will add up.
And you only mentioned as a single one, if 10 dollars * 1000 characters a year, thats 10000dollars a year. And with interactions, its going to be even more. The Interaction exported characters are already pretty big in size if handled locally, and each updated versions of a character is also, their own.
Essentially, a server is holding the characters/interactions that is being payed for. You dont want the size of the files to have a standard of being too big in general with an increasing number of characters as long as people make characters.
With the question of average compressed size of a character uploaded. my guess is 8mb. If 15mb would be the case, I would predict it being 13mb. Thats only because im assuming people arent optimizing, and im not that great in that either.
@Craket
I work in IT, I know what current cloud storage costs. Plus that information is publicly available: $0.02/GB per month for standard cloud storage through Google.
@Craket
The cost I gave wasn't for one character, it was for literally all of them. There are only 1500 or so characters in the cloud, but let's be generous and say that if you include previous versions, there's 4000. Let's be even more generous and say that all 4000 of them indeed take up a full 10 MB. That adds up to 40 GB, At a standard price of $0.02 per GB per month, that's $0.80/month or $9.60/year.
Increase the max to 15 MB and it goes from 40 GB to 60 GB, and the monthly cost goes to $1.20 and the yearly cost goes to $14.40, about $5 more.
At a price of $0.02/GB, the monthly cost of 5 MB is just $0.0001. So on a per-character basis we're talking about a maximum possible difference between $0.0002 and $0.0003.
And that's also assuming they use standard prices for all the storage. There's a decent chance they'd actually pay less depending on the tier of storage used for some of the data. Like, I doubt they'd have to pay standard prices for old revisions of characters since those get loaded much less frequently.
@MobiusScarf
Does it matter if they are loaded? Dont they have to be stored?Interactions as an extension to all of this will increase things further, using older versions of a character if the character was updated after the interaction and etc (An assumption).
And with 15mb limitation, people will still find themselves over that limit. Because people arent optimizing as well as they should. And in one way, the 10mb is good because it helps people learn how to better optimize.
We already see a hard limitation of how many characters we can use in an interaction, if the character size limit is 15mb, that number of characters gets more taxing for a server to hold. Which is why I initially claimed it as "50% more" even if its language I personally do not like using. Im just realizing that, the increase might spill over more areas than just, the character uploaded to the cloud.
The real fault in it all (I think) is many of the in-app models now are glb which are larger, which made a lot of characters larger in size in general. This topic only came up because of this alone, not the limitation itself.
@Craket
But here and there, at least for me, you are forced to leave out "elements" when the characters become more and more complex. As you've probably already noticed, I had to separate the emotions for Loona and Queen Bee, for example. I can optimize the clothes and textures, but with the "user expressions" it gets tight at a certain level. A little more, I would be happy with an increase to 12Mb.