What is its Problem?
JOdel
Posts: 6,316
Could someone explain to me what the problem is? The file path is exactly what it's supposed to be acto the alert message. The file name is exactly what it's supposed to be named. I've redownloaded and reinstalled the shader and it still throws me this alert *every single time* I try to apply the shader.
It throws me what is effectively the same alert when I try to load the environment sphere.
Mind you, I was never able to get it to work before I updated the program either, but I've seen other people post renders using these shaders so I know that *someone* has managed to get them to work.
Screen_shot_2015-01-11_at_3.41_.36_PM_.png
605 x 582 - 119K

Comments
Does the path to the folder holding the Data folder match what's in Content Directory Manager for DAZ Studio Formats? If it's on an external drive, is that drive permanently connected so that OSX doesn't assign its alias to something else?
More likely whatever preset you're using is the problem. My guess is the preset has an absolute path rather than a relative path.
You can edit the dsf file and change for the folder path references to correct the issue.
The presets actually seem to apply. The partials do not. I get this alert on *all* of the package. Every single preset. Every single partial. Everything in the whole package throws out the alert.
Yes, the content library is on an external drive, and yes, the drive is permanently connected. I have no idea what the Content Directory Manager says about the path to the external. All of my shaders (apart from things like the ones that are part of a specific package like the Supersuit) live in that library. None of the other ones throw me that alert. Just things from AoA.
And I haven't double-checked to see if the subsurface shaders do the same thing too. I seem to recall having some problems with them, too.