Quick question Stephen - if I want to test the latest version SiToA to try this out, can it coexist with the old (licensed) 2.8.0 if I install the latest version in a new workgroup?
Yes. I've got many versions of SItoA in different workgroups. On Fri, Oct 31, 2014 at 11:53 AM, Morten Bartholdy <[email protected]> wrote: > Aw, bummer. Thanks for looking into it Stephen! I was actually hoping > to find a way to render emFluids with motionblur so my holdouts and the > fluids for that matter would be motionblurred providing better integration > with our rendered scenes (Maya/VRay) > > > > Who knows - maybe this is my ticket to a SiToA update... > > > > BTW, if anyone has compiled the VDB_Softimage_Shaders_ai.dll against Arnold > Core 4.0.14.0 I am all ears! > > > > Quick question Stephen - if I want to test the latest version SiToA to try > this out, can it coexist with the old (licensed) 2.8.0 if I install the > latest version in a new workgroup? > > > > > > Morten > > > > > > Den 31. oktober 2014 kl. 16:44 skrev Stephen Blair < > [email protected]>: > > Hi > > With the kick that comes with SItoA 2.8, I get: > > > WARNING | VDB_Softimage_Shaders_ai.dll was compiled against > non-compatible Arnold 4.1.3.0 > > > That's with OpenVDB_to_Softimage_v0.8 > > SItoA 2.8 uses the Arnold Core 4.0.14.0 > > > Sorry > > Stephen > > > On Fri, Oct 31, 2014 at 11:12 AM, Morten Bartholdy < [email protected] > > wrote: > > I just realized I should put your import sipyutils line in the top > which fixed the ai red triangle problem. I still have another problem > though when trying to renderregion the cloud example scene: > > > > # WARNING : [arnold] node "VDBVolumeShaderSimple_ai" is not installed # > ERROR : [sitoa]: Unable to load VDBVolumeShaderSimple_ai from the Arnold > plugins (first occurrence: > Sources.Materials.DefaultLib.Scene_Material.VDBVolumeShaderSimple_ai) > > > > Is this because the OpenVDB workgroup should be loaded before the SiToA > workgroup? > > > > Morten > > > > > > > > Den 31. oktober 2014 kl. 15:51 skrev Stephen Blair < > [email protected] >: > > No, just try replacing this line > dllPath_release = Application.Plugins("Arnold > Shaders"). OriginPath + "bin\\nt-x86-64\\tbb42.dll"; > with > dllPath_release = __sipath__ + "//tbb42.dll"; > > > > > On Fri, Oct 31, 2014 at 10:45 AM, Morten Bartholdy < [email protected] > > wrote: > > If I read this correctly I should list the OpenVDB workgroup (Olegs > installation workgroup) before the SiToA workgroup!? > > > Morten > > > > > > > Den 31. oktober 2014 kl. 15:03 skrev Stephen Blair < > [email protected] >: > > Hi Morton > > > Try applying my suggested change and see. > The SItoA 2.8 tbb.dll isn't the same as the OpenVDB supplied version, so > if that worked before, then it should still work with the Mootz version. > I don't remember if I ever tried installing OpenVDB with SItoA 2.8 > > > > > SItoA 2.8 > - ships with tbb.dll > - has "Arnold Shaders" plugin, not "ArnoldStaShaders", but using " > Application.Plugins("Arnold > Shaders").OriginPath " is a bad idea. For example, if OpenVDB is a > workgroup plugin. > > http://xsisupport.com/2014/04/01/loading-order-of-workgroup-plugins-and-addons/ > > > > > > > > > On Fri, Oct 31, 2014 at 9:46 AM, Morten Bartholdy < [email protected] > > wrote: > > Thanks for chiming in Stephen. Now it get's slightly complicated - I am > on SiToA 2.8.0 so I don't know where it fits in here. > > > > I am actually using a tbb.dll that Erik Mootz provided with emFluid5 for > it to work alongside SiToA. Would tbb.dll and tbb42.dll conflict? > > > > I can of course just try your method and see what happens. > > > > > > Morten > > > > > > > > > > > > Den 31. oktober 2014 kl. 14:25 skrev Stephen Blair < > [email protected] >: > > Hi > > That will work if he's using an old version of SItoA (however, I don't > remember which came first: we removed tbb.dll, or we switched to > ArnoldStaShaders, or we did both the same release) > > But in summary: > > That third-party plugin is a bit old now and so it is doing a few things > wrong, if you have a recent version of SItoA: > > - There is no SItoA plugin called "Arnold Shaders" > - SItoA doesn't ship tbb42.dll > > In Application\Plugins\bin\nt- x86-64\VDB_shaderDefs_ai.pys, add this > line: > > import sipyutils > > > and then replace this line > dllPath_release = Application.Plugins("Arnold Shaders"). OriginPath > + "bin\\nt-x86-64\\tbb42.dll"; > with > dllPath_release = __sipath__ + "//tbb42.dll"; > > > Stephen > Solid Angle Support > > On Fri, Oct 31, 2014 at 9:13 AM, Francois Lord < [email protected] > > wrote: > > > in the VDB_shaderDefs_ai.pys, replace this line > dllPath_release = Application.Plugins("Arnold Shaders").OriginPath + > "bin\\nt-x86-64\\tbb42.dll"; > by > dllPath_release = Application.Plugins("ArnoldStaShaders").OriginPath + > "bin\\nt-x86-64\\tbb42.dll"; > > > On 31-Oct-14 08:48, Morten Bartholdy wrote: > > > > I just installed Oleg Bliznuks exciting OpenVDB stuff but ran in to a snag > - I get this error when doing a renderregion on the cloud demo scene: > > ' WARNING : [arnold] node "VDBVolumeShaderSimple_ai" is not installed > ' ERROR : [sitoa]: Unable to load VDBVolumeShaderSimple_ai from the Arnold > plugins (first occurrence: > Sources.Materials.DefaultLib.Scene_Material.VDBVolumeShaderSimple_ai) > > Upon Inspecting the Plugin Manager I can see that VDB_shaderDefs_ai.pys > has a red triangle and checking its properties it says 262$This script > plug-in contains erors and could not be loaded: <path: "path to workgroup > installation" > > I do have vcredist_x64 installed. Does anyone here know - could this be > caused by the annoying tbb.dll conflict with Arnold? > > > > I am exploring the various ways to render emFluids and would really like > to try Olegs shader out. > > > > > > Cheers > > Morten > > > > > > > > > > > > > > > > >
