Product Size Before Purchase

in The Commons
Is there a way to know before purchasing a product what the download size will be? For example, I want to compare several 'long hairs', but want the least file load among them.
Comments
No, it's not listed on product pages or readme; Your best chance is asking in the forums.
I would love this as well. I have had multiple products that I've bought on a whim, and then went to download them only to discover it was a few gigabytes and then just never downloaded them.
The western saloon that was on clearance the other day is the most recent example. It seemed like a small set that I might repurpose some props from, so I bought it. And then discovered it was over a gigabyte in size
Too big? Hard drives are so cheap nowadays. I find this hard to believe. 2 TB drives have seemed to bottom out at about $50 for a long time now, and 4 TB for like $75-80.
You could run a script or use optimizer to resize. If they're too small, you can't do anything to increase quality.
I would love to see this feature implemented as well... it would be very helpful to know not just the file size of individual products (before and after purchase), but also the file size of our entire collection of "owned" products.
For some, the drive space is a limiting factor, but bloated (1GB+) installation files are often a symptom of much more severe problems - Something like 80% of those cases are because of poor execution on the creators side, causing the product to hoard much more resources than would be necessary for the same level of quality if resource planning was made better. The worst case that I have seen so far was materials for a insignificant surface eating almost 1GB of RAM when only 20MB's would have been enough for exactly the same level of quality. (and no, the optimizer or decimator would not have helped)
The remaining 20% does have a reason for large file sizes, usually large number of texture sets, which do not waste resources as just one texture set is used at a time.
If we were allowed to see the size of the installation package, that would help us to see what kind of product it is before making the purchase.
this
Concidering that some people have a capped ISP download limit this suggestion has merit. Renderosity and most other sites provide file sizes as a courtesy to its customers but sadly not Daz. One can only conclude that Daz sees such information as a disincentive to sales.
Aren't we getting polycount on the sales page now? (We have to put it in when uploading) and we've had number and size of texture maps for a while, though not always enough detail there to know. Of course some sets may look big but have multiple options (so you're not loading all the maps at once but choosing 'clean' or 'used' textures, for example).
Having total download file size would be good too, if only to avoid the shock