pegot wrote:No we have an entire thread on the motion blur issue. Internal MB dose not work. Only Subframe MB seems to work. But that gives poor results and appears not to use Motion Vectors.
Additionally, other problems arise when using Movable or Reshapable proxy. As the animation progresses, each frame shows the previous as well as current mesh, so all frames are rendered together. This might be an issue with Flip Fluids and the properties tab (there is also an entire thread on that).
linograndiotoy wrote:...I'll get in touch with the FLIP Fluid developers (as I did in the past already to get the MB issue solved) and see on which side the issue is. For sure we'll make it work in Octane for Blender 2.8...
ChrisH wrote:Criticism and questioning can be done without ill-intent!
ChrisH wrote:Sure, it's no big deal to do some extra work for the properties that's missing, but it does take away from the efficiency as well as the streamlining of workflows (don't you think? ;D ).
pegot wrote:I’m not taking your comments as criticism at all.
pegot wrote:As for gLTF 2.0 support, that has been promised (in Standalone at least) for some time now.
pegot wrote:But for Octane Blender to remain competitive I think a big effort should be made (or continue to be made) ensuring as many features as possible work with major Blender Addons.
pegot wrote:No, not for my use case. I am always going to need high quality renders with the more specialized material features that Cycles or Octane supports. But I also need to bring these models into PowerPoint as live 3d objects in a more economical and flexible way than a rendered animation provides.
pegot wrote:The conversion back and forth between Octane and Cycles PBR Principled shaders is a real drag. The ability to use the same node setups in Cycles and then instantly output that to my gLTF file destined for PowerPoint is priceless. And this is not just a conversion done once. [...] But it is a hassle and quickly leads to the two sets growing further and further out of sync when changes are continually made to one or the other. So for my particular workflow, Octane having the ability to export to gLTF 2.0 would go a long way in solving this.
Users browsing this forum: WIA and 2 guests