In fact, the more they talk the less they do. What a company says about their future and dedications to a platform is completely unrelated to what they do. The chances that it will disappear, or get acquired by Autodesk and killed are very very very high. This is why I have zero interest in a new commercial plugin these days unless they are very fast to ramp up and very affordable. We are both old enough so see how this has played out for most Rhino plugins. No one can predict the future and most plug-in companies have very weak/unsustainable business models. I actually completely disagree about this.
Octane for rhino 6 software#
It’s good to keep in mind, which software has the best potential for the future?ĭepending in your situation. making materials with edge bump and other bump maps is a bit tedious to set up materials with multiple layered textures can become complex to keep overview of(screams for node based editor like 3ds max) no way to fix the render view (always active view is used) Handling of duplicate materials not working smoothly yet interactive rendering crashes Rhino with auto save Some features missing or not fully working on GPU fast rendering of scenes with many lights search filter for assets (huge time saver when you have many assets) lens effects work very well and non destructive. many additional render channels for post production and analysis all controls in one place (asset manager) powerful V-Ray frame buffer to do lots of post processing directly in Rhino scriptable settings and material properties many built in procedural and utility textures (like gradient, color correction, curves, many powerful mix maps, Tri-Planar) Works with clipping plane and clipping geometry (the latter only cpu) built in camera settings for panoramas /vr fast setup, just a few parameters to take care of ships with pretty large material library Let me sum up some of the pros and cons of V-Ray, hopefully others can do this for other render engines as well: For us, today, Octane seems the best compromise: good product, good price, good support, fast rendering. Rendering in Rhino still sucks, no mater what you use. The reality is still the same IMO: ‘All talk, no good solutions’. Hopefully that will get better.Īll the rendering developers (McNeel and 3rd party) talk like rendering in Rhino is an important task/priority/market. For us a CPU rendering option in 2020 is a non-starter, and the bugs in Vray GPU are also a non-starter for a tool that we need to rely on daily. …or No, if what you are looking for is a real-time solution, because octane it’s not one.Ī lot of people like Vray too. Just keep in mind that you need a really good (or even better multiple) video cards to really take advantage of its speed and that you need to invest time to make a good material/scenes library to make it more useable. In summary: Yes, I think Octane is the best option for Rhino, but it takes a ton of work to setup right. We tried a bunch of stuff, (inside Rhino plugins, stand-alone products, inside Modo…) and everything else is more buggy, slower, and or has a lot less active development (some options no development and support at all). Still, I think it’s the best (or least worst?) option to make high quality renderings that do not take a loooong time to do. and most Rhino rendering features are not compatible with Octane. There’s also no materials library, no samples scenes, no easy-way-in. The integration is not good (rendered viewport and octane appearance only barely match in only some types of materials, but it’s still improving lately). I’m not sure if technically is even possible to eliminate cashing completely, but that would be nice. Never versions are trying to speed up cashing so that will get better. So what should take a couple of hours to render can take 5X that. In complex scenes that geometry cashing takes longer that the frame renderings. Not only Octane is not real-time, In fact if you are trying to render an animation in Octane you will have to add to the render time of each frame, the geometry cashing time too. McNeel will probably never make a library for it, so you will have to invest time to make your own. Also in V7 there is now support for PRB materials in rendered viewport as of last month. The only realtime options in Rhino right now are the shaded and rendered viewports. You are talking about two different things here:
0 kommentar(er)
