I don’t have much money to spend at the moment and don’t have any immediate prospects of making money with Rhino. I am not a big company with a revenue stream that can just think about a Rhino purchase as “necessary tools” and an easily justifiable expense, where I would lose money for not having it, or whatever. If not, in the intervening time, when I have to withdraw from using Rhino, it is possible I’ll learn to live without it. I then have to decide if I can justify that. So if Rhino 8 will be released in three months, that means it costs me $133/month to have Rhino until then. If I plan to be up to date when V8 is released, in essence, the cost of the upgrade is what I pay to have Rhino in the meantime. One could think about it in my case like this. If I buy now and V8 is released in three months, and I want to be current, I will have to spend $1,400. If you bought early, three months after release, you will still be current and will have only spent $1,000. It would still mean probably $1,200 to be up to date upon new release, but that’s not quite so painful.Ĭonsider that if I buy now and upgrade when V8 is released, I will in essence be paying more to be current. If a newly released version were $1000 and the same version a few months before a new release were only $800, it would help get buyers over the hump. You are buying somewhat behind-the-times software, after all. Perhaps as a software version ages, the price should go down, maybe more steeply as a new release approaches. Maybe pricing should reflect this, to try to even out value for customers buying at different times. Those of you who have had V7 were able to use some V8 features for a while. Consider that if I buy just before release, I will never get to use or play with a WIP version. It is a little like buying an old or slightly used model of a car for the price of new. People who buy just before release get the least. People who happen to buy right after a release get the most value. Something else that occurs to me is that customers who buy at different times in the release cycle get different amounts of value. Maybe it is useful for McNeel to get feedback from someone like me, as I am surely not alone in this. I just find myself hesitating and thought I’d share my thoughts. Rhino is only potentially part of that picture. There are many aspects to the craft I am working on developing. It isn’t so straightforward though, as I can invest the intervening time in other valuable things. I understand the cost/benefit considerations for me. Rhino 7 has come one step closer to the holy grail with the introduction of the _Reflect command.I appreciate the thoughts you all have shared!.See: Adding GoZ to Rhino now make much more sense - #15 by Akash Now with SubD, It’s clear that Rhino needs better ZBrush support.Please don’t direct to 3rd party websites offering a mixed bag of for sale and subpar free assets. With the current revolt against the subscription model, this user group seems ripe for the taking. Additionally, suppliers and manufacturers appear to be paying a premium to list 3D models of their products in this space. The number one reason my colleagues in the profession of architecture refuse to switch to Rhino from another popular 3D modeling software is their robust user-generated asset libraries where you can download anything from people to trees or a coffee pot directly into your scene.What's the best approach for creating this transitional surface? Rhino needs better tools to solve complex patches and transitional surfaces.(We get an embedded files folder sometimes but there is no way to create this folder on command.) As Rhino CPU/GPU rendering comes to maturity with Cycles, this feature is imperative for effective file management. We need linked file manager for texture images and the ability to see broken links all in one place, relink, and package them all into a folder that can be sent along with a.See: Images do not migrate to Illustrator or any other application - #49 by sthode66 Better support for scaling linework upon export. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |