Any feedback you may have got is now gone because anybody with feedback to give doesn’t use the feature. Most importantly however is that if you add a new feature but immediately give people the option to disable it, you’ll never figure out how to improve upon it. Anything that works for Cycles and Rhino Render but doesn’t work for Rendered is counter to the whole idea behind rendered viewports. The Rendered Viewport is basically a preview of what happens if you were to actually render the scene, or it can be thought of as a render engine in its own right. We want GH to be able to push geometry and materials to the render engines (Rhino Render, Cycles, Vray, all of them). It also makes the software unfriendly to new or casual users.Īnother reason is consistency. The more options you expose the harder it becomes to support people when problems arise. For example I’m worried about option-bloat. Well, a number of reasons for, some against. Why not just let the user decide to keep smthing that some ppl got completely used to?
0 Comments
Leave a Reply. |