Workshop maximum file size.

[Bleurei]

Anyone knew the maximum upload file size for gmod's workshop?
Thanks

[E7ajamy]

400mb maximum, or at least under 400mb maximum file size.

[Mailer]

The reoccuring limit mentioned at facepunch is compressing down to 200MB. You are more likely to get halted by the compression method failing because the file is too big than the workshop telling you the same thing, so it might be hard to set a concrete limit.
Furthermore, if you are ever to breach that limit then you are most likely using an overcompensating texture-format for a lot of textures.

[Bleurei]

Originally posted by Mailer:

The reoccuring limit mentioned at facepunch is compressing down to 200MB. You are more likely to get halted by the compression method failing because the file is too big than the workshop telling you the same thing, so it might be hard to set a concrete limit.
Furthermore, if you are ever to breach that limit then you are most likely using an overcompensating texture-format for a lot of textures.

Sorry, I'm a bit confused. Do you mean custom textures?

I'm pretty new to mapping and stuff, so far I've only use the already existing textures from the hammer.

[Mailer]

Originally posted by Tofu:

Originally posted by Mailer:

The reoccuring limit mentioned at facepunch is compressing down to 200MB. You are more likely to get halted by the compression method failing because the file is too big than the workshop telling you the same thing, so it might be hard to set a concrete limit.
Furthermore, if you are ever to breach that limit then you are most likely using an overcompensating texture-format for a lot of textures.

Sorry, I'm a bit confused. Do you mean custom textures?

I'm pretty new to mapping and stuff, so far I've only use the already existing textures from the hammer.

I am referring to any (but not limited to) .vtf-files that you are wanting to upload with your addon. The actual textures, that is. And these .vtf-files, if you've been using VTFEdit specifically, can be associated with a lot of different formats. Some are compressed like DXT1 and DXT5, but others aren't. And those that aren't are going to make your addon increasingly big if you have a lot of textures included in it that use them. Textures are more often than not going to account for most of the file-size so if you ever run into problems with that then try to optimize your textures first, if possible.
If your map uses textures from already existing assets like CSS then you shouldn't have to worry that much about it.

[Mailer]

Originally posted by Mailer:

Originally posted by Tofu:

Sorry, I'm a bit confused. Do you mean custom textures?

I'm pretty new to mapping and stuff, so far I've only use the already existing textures from the hammer.

I am referring to any (but not limited to) .vtf-files that you are wanting to upload with your addon. The actual textures, that is. And these .vtf-files, if you've been using VTFEdit specifically, can be associated with a lot of different formats. Some are compressed like DXT1 and DXT5, but others aren't. And those that aren't are going to make your addon increasingly big if you have a lot of textures included in it that use them. Textures are more often than not going to account for most of the file-size so if you ever run into problems with that then try to optimize your textures first, if possible.
If your map uses textures from already existing assets like CSS then you shouldn't have to worry that much about it.

To further clarify what I am referring to, anything that you are keeping in

[my_addon_name]/materials/[etc...]

contributes to the file-size by, most likely, the largest margin.