abstrax wrote:Btw, some good news: I just updated one of our thirdparty libraries and the editor freeze of that massively instanced scene you sent me a while ago, is goneIf we can't find any issues with it, we will release it with the next alpha and probably also merge it to v2.
Yes, we are still busy working on major feature enhancement to the volumetric support you're seeing in alpha 3. The volume node will look substantially different very soon, but in terms of priority, colour ramps for volumes will be done before the step length enhancement.linvanchene wrote:Is there any chance that the volume step length can be set on an object level in the future?
A major reason we took on OpenCL was to support the MacPro. Today the MacPro/OSX is still on OpenCL 1.2 which is very old - you have Android phones with full OCL 2.1 support coming this year through Vulkan. It is looking more and more likely that Metal is the future of GPGPU on OSX. If that's the case, we need to factor this into the long term OSX roadmap. In the meantime, we will do all we can do get Octane running with OCL 1.2, but as Marcus said, it's just at the bare minimum that Octane requires.chupinsky27 wrote:I'm not going to lie, this news comes as a disappointment. OpenCl and the promise of running Octane on virtually any computer, to me, was the headlining feature of v3. I have been using Octane for freelance and personal work for sometime now and I LOVE Octane. Going back to C4D's built in renderer feels so archaic and cumbersome, yet that is what I am forced to use in my professional work environment. I work for a major sports broadcasting network with ~50 Mac Pro workstations loaded with C4D in our location with many more locations globally. After serious consideration, our engineers ruled out the possibility of implementing Octane into our workflow for the fact of the steep investment for external graphics card boxes for individual workstations, server room space, and added complexity of managing said equipment. With OpenCl (or another universal code), Implementation would be a breeze. I can imagine this is true across the industry.abstrax wrote:OpenCL has been on hiatus for quite a while and we will continue working on it after OSL has been done, i.e. it may become available around middle of the year. Please be aware, that there is a chance that we may run into unsurmountable problems and we can't get it working (Octane is not a simple path tracer anymore). I didn't run into any issues during my initial tests, but everybody tells me how bad it is, so we will have to see.Yan wrote:When will you release support for OpenCL?
Thanks!
There is also a small possibility that AMD's CUDA implementation as part of AMD's Boltzman initiative could be used instead of an OpenCL implementation, but we will see, when we get there. Most likely it will not be useful for Octane.
If universal support is seriously on the chopping block, we need a better solution for medium-large studio environments other than adding (Nvidia exclusive) graphics cards to individual workstations.
I will continue to use Octane at home and for side jobs with the same enthusiasm as before yet knowing I may never use it in my current professional environment.
Working offline is not possible with v3 alpha beta test versions. You have to use v2 if you need to work offlineDmi3ryd wrote:Offline activation didn't work?
I've activate 3.0 version and after restart windows activation needs again.
Is it bug or feature?
For those who buy it, yes.Dmi3ryd wrote:Did you plan to add offline action in 3v ?
