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/
> <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]
> <mailto:[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] <mailto:[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]
> > > <mailto:[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
> > > > > 
> > > > > 
> > 
> > 

Reply via email to