![]() To echo Helvetosaur, we really only want you to buy Rhino when there’s something in it that you value, need, and are delighted to pay for. ![]() And in many cases, we actually make Rhino smaller by removing code that doesn’t work. I’m guessing that ShrinkWrap added less than 20MB to the size of Rhino, which by the bulk metric above means we should probably just leave it out. I’m kidding - it seems like the metric based on file size is really appropriate for video game content, but not so much when you’re making the content. So it sounds like we need to add 500MB of textures with each service release? Soon we will have 200GB of additional bulk, and it will be worth the price of the upgrade? So you “shipped” 33 “service releases”/3yrs, 2500 bug fixes etc., so my question would be how many gigabytes of data is the initial release? and how many gigabytes of data in “updates” were there in 3 yrs? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |