Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Ah. Okay. Thanks for the info, and replying.
For such a small update, it's totally messed up my installation, and content library. :/
However, as it is clear here, there is a certain amount of demand and expectation for filaments in terms of drawing speed.
First of all, the problem of hair penetration and the problem of not reflecting emissive should be solved. It's a draw style so it's not a problem to give up.
That means we've entered a stage where Daz can't afford to make excuses.
Again, it's an urgent task for Daz to solve this problem. Draw style
It might just be my imagination.. but hair does seem a little better looking (less flickery anyway).
But gah, installation issues are always a pain.
The filament preview window consistently crashes my DAZ Studio Pro Public Beta 4.14.1.22 for the scene I have used to make my avatar. It's actually done so pretty consistently on prior versions although I did manage to get it to filament render a few times on the 2nd released of the 4.14.x public betas that have filament.
Looks like this filament introduced a lot of new crashes into Daz.
Most of them happen when you try o switch rendering engines, and typically attempt to use iray and filament at the same time will need badly so if you are trying to do final rendering or want to use iRay viewport preview you can have a filament running or open at the same time
although it is quite strange that filament manages to run faster than opengl for some reason
Officialy IS a Render Engine:
The advanced openGL is slower to render on my PC than an iRay render.
I am getting my Filament crashes just switching from whatever viewstyle in the ViewPort to Filament. It also doesn't matter what I have the actual renderer set to either: 'Viewport', iRay. 3DL, switching to Filament in the Viewport crashes DAZ Studio PB 4.14.1.22
This isn't universal. I've no issues switching to the Filament draw-style in the latest public build, at least with the simple scenes I've tried it with. My DS is pretty vanilla, though. No Octane, or anything.
yeah the only issue I have faced is trying to render in iray with Filament viewport, simply run out of VRAM
I usually switch to bounding box anyway if rendering in iray, the lowest viewport setting to tax my card the least as even openGL textured uses a fair bit of VRAM so not really an issue
That's the whole idea. there are no problems with simple scenes
1) Go to the right hand corner of your viewport in 4.14 and choose the icon next to the camera selection, and from the drop down choose filament PBR
2) Profit
Step 3: If you want it to render outside the viewport so you can make it bigger or save it or whatever: Under Render Settings there is a dropdown named 'Engine'. Select 'Viewport'. Now when you do a render it will render to whatever you selected in step 1 above, in this cas filament. Now when you push the render button you get a filament render.
Whatever you do though, don't skip step 2!LOL, same as Enjoy but weird way to say it
https://knowyourmeme.com/memes/profit
The hair is looking better. It also seems to be handling transparent clothing a little better too (but that's only going by one scene that I'm working on).
I've never had to deal with these issues before. I can't work out if it's Daz Studio, or my external HDD that's the problem :/
So much for that. Lost about an hour's setup when I forgot that this was a thing. Disabled the Filament plugin until I hear it's safe to go back to it.
I haven't had this happen yet
The official version. I don't have the Beta installed either.
DS 4.14.0.10, latest 460.89 NVidia driver. No crashes or other problems while working on it.
Tried this out for the first time last night and am pleasantly surprised.
The issue I noticed though was that it shares tone mapping values with iRay when they aren't cross compatible. Are they going to introduce individual values?
As for losing an hours work due to crashes, I've long ago gotten into the habit of frequently saving a scene I'm working on, because DS does have a tendancy to crash out from under me... tho fortunately it hasn't done it much lately.
That said, I should probably start poking this Filiment thing with a stick. :D
You might want to upgrade to smacking it with a baseball bat
Hi. I believe I am setting up Filament correctly, but in my viewport anything I have there shows as solid white with no textures. The texures show up in Iray or Texture shaded, just not in Filament.
Am I missing something to make this work?
Filament is generlaly more reactive to light sources. You have to dial them down when you switch between Iray and Filament as your intended output.
I'm guessing it's the default HDRI that is causing your trouble.
Turning the Environment intensity down to like .15 or so should "fix" it.
Hi, thanks. I just tried that, and made no difference at all to the scene preview. Maybe should also mention I have the Render Settings to Engine Viewport, Active Viewport. And when I render, I just get a totally blank result.
If it comes out as white-"blank", then it's most likely overexposed. Too many lights for the camera's eye, and Filament's eye is more sensitive than Iray.
(It's it's black-"blank", then you don't have enough lights... which tends to be more of an Iray condition rather than Filament. Transparent/grey blank also has its own look, of course.)
What kind of scene are you using? Is it a pre-made Iray scene? Did you light it?
I'm guessing it's a light issue, not a surface/texture issue. Filament is supposed to handle 3DL better, but it also treats Iray mostly fine. Things with translucency/transparent surfaces/opacity maps don't react the same way at all... so if your scene is all translucent surfaces, that could be a problem.
I would just comb through the Surfaces, turn down any lights that you have, turn down all of the point lights & spotlights, and also turn off the Headlamp (if it's on by default).
no, it's not a ligting issue. I've added, removed lights, changed the lights. And when I try a viewport render, all I get is completely blank render.
I've attached a scene with a sphere with a simple blue color, lit by a distant spotlight. The images are the Iray Rendered viewport, the Filament rendered viewport, and the result when I render the viewport.
I am thinking something with my system? Windows 10, and twin Nvidia 980Ti video cards.