When you apply a preset, is it apparent in the preview window, or is it only noticeable after rendering? . . . I’ve selected the “lava skin” preset, and you can see that the cube has turned to pure white (you can also see that the specular color has changed to a brownish color more appropriate to lava), and it will render out as pure white, not as a lava cube.
From what I recall (it’s been a while since I’ve used these), the effects only show in the completed renders, not in the preview window. Render your lava-skin test and see what that gets you.
It gets me a pure white cube, not a lava cube. (This is REALLY annoying and frustrating…)
Huh! I can imagine. Okay, I’ve got nothing, sorry.
When you apply a preset, is it apparent in the preview window, or is it only noticeable after rendering? . . . I’ve selected the “lava skin” preset, and you can see that the cube has turned to pure white (you can also see that the specular color has changed to a brownish color more appropriate to lava), and it will render out as pure white, not as a lava cube.
From what I recall (it’s been a while since I’ve used these), the effects only show in the completed renders, not in the preview window. Render your lava-skin test and see what that gets you.
It gets me a pure white cube, not a lava cube. (This is REALLY annoying and frustrating…)
Huh! I can imagine. Okay, I’ve got nothing, sorry.
That’s cool. Thanks for the help, and thanks to everyone who’s helped with this.
Set all colours to black and see if a render gives a white surface still. If it does, file a bug report about the 64 bits version of pwEffect. The log file (Help->Troubleshooting->View Log File, scroll at the bottom just after applying pwEffect) may also contain some useful information
Set all colours to black and see if a render gives a white surface still. If it does, file a bug report about the 64 bits version of pwEffect. The log file (Help->Troubleshooting->View Log File, scroll at the bottom just after applying pwEffect) may also contain some useful information
Thank you, I tried that. I went through and changed every single color channel to black—and then the object rendered out to a neutral grey. What it looks like is happening, is that when I apply pwEffect, the pure white is the ambient channel being set to white at 100%. When I cranked it back down, the object was simply neutral grey, even with all of the other channels set to black. I just don’t think the 64-bit pw shaders are working with DS4P RC3 64-bit.
Oh good point, Ambient in pwEffect acts as minimum colour of a surface, which is different from what DS uses (DS is the odd one out in that regard). You really have to dial it back a lot if you are used to the DAZ default material.
I tried applying the shader to Genesis’ torso, without applying any preset, and setting the Diffuse, Ambient and Specular colours to black yielded what looks to me like a black torso.
Yeah, the effects look great—that’s why I finally bought them a month or so ago. I’ve been beating my head on my keyboard, trying to figure out what it is I’m doing wrong, and then it hit me that even though they’ve been updated, they probably don’t work with the RC3 version of DS, much like Reality isn’t working right now. I’ve submitted a bug report with some test renders and a copy of the log file, so maybe I can get some help with that.
Just tried myself and pwEffect is working in 4.5 RC3 here (not ordered in bundle, but as single product). Do you got the latest version? As they got updated for the RC3 build according to the RC3 announcement as well.
10. We would suggest that in order to use the PW Shaders you should reset your downloads to get the latest version to run with DAZ Studio 4.5 RC3.
To add: My download is “5387_pwEffect_1.2_ds.zip”.
YAY! They work! They pw effects are NOT apparent in the preview window (at least on my machine; I dunno about anyone else’s) other than the object they’re being applied to changes color. You have to render to see the full effect—but, at least they work now…
Wasn’t anything I did—simply a matter of having installers that work. I figured it was an incompatibility with the RC3 release and not something I was doing wrong, and it’s a relief to know I wasn’t making a mistake somewhere. Now I can try all the ideas I’ve been working on. Thank you to everyone who helped with this.