To be fair, flash died because iOS didn't support it (and other issues), not because OSX didn't support it.pjmc377 wrote: ↑Mon Jan 13, 2020 11:26 amOctane and Redshift are already developing their renderers for Metal in light of the fact that Apple dropped Nvidia and Nvidea will no longer support Cuda on Mac.
If Maxwell wants to slip even further down the list than they have, they will ignore this as they have other things.
I for one will move to redshift or Octane if Maxwell slips behind again, and Maxwell has been my main renderer since its Beta days.
Apple are very influential in what they support and don't support. remember when they dropped Flash while every website was using it ? how many flash websites do you see today ? none. I hope Maxwell doesn't fall behind the curve again.
“OTOY is incredibly excited about the all-new Mac Pro and how it will empower our users. Octane X — the 10th anniversary edition of Octane — has been rewritten from the ground up in Metal for Mac Pro, and is the culmination of a long and deep collaboration with Apple’s world-class engineering team. Mac Pro is like nothing we’ve seen before in a desktop system. Octane X will be leveraging this unprecedented performance to take interactive and production GPU rendering for film, TV, motion graphics and AR/VR to a whole new level. Octane X is truly a labor of love, and we can’t wait to get it into the hands of our Mac customers later this year.” — Jules Urbach, CEO and founder, OTOY
“Tapping into the amazing performance of the new Mac Pro, we’re excited to develop Redshift for Metal, and we’re working with Apple to bring an optimized version to the Mac Pro for the first time by the end of the year. We’re also actively developing Metal support for Cinema 4D, which will provide our Mac users with accelerated workflows for the most complex content creation. The new Mac Pro graphics architecture is incredibly powerful and is the best system to run Cinema 4D.” — David McGavran, CEO, Maxon
Well, more than if, is when. If we plan new features, now we think about doing them for CPU and GPU, it make non sense to make engines more different. Optimization first step than can improve CPU engine is on preprocess, voxelization... That will make better both worlds. A future option for me (and I recall for me, it's not anything planned yet), it to make CPU code (and I mean code, not algorithm) more similar to GPU one. That would make code easier to fix, mantain and make new things, and probably will make code faster on systems with lot of cores.
Thanks Luis. I am slowly getting my head around th[…]
I had some very strong highlights in some material[…]
Thanks everyone! I didn't want to use volumetrics […]
just installed latest version for Rhino V6 when I[…]