MEC4D said:

What do you mean by transparency ?  Cutout opacity ? it always worked , there was some issues when it was set at 50%, but it is not how it should be used in first place 

RexRed said:

Am I imagining things or did Filament just get an update?

When I first tried it transparencies did not work in Filament, now they do.

It seems to coincide with an update a few days ago.

I guess he means more the refraction part, that has changed somehow. At least in my "test" setup it seem to work better. Anyways, it's still not there and i could just repeat what you said: "...but it is not how it should be used in first place"

Sorry, yes, the original release of DS with Filament used that texture shaded style icon for the Filament viewport.  I've been using the BETA version of DS since I have an older DS 4.9 version as the GA release. 

The icon was changed to the light bulb icon with subsequent DS BETA release.  DS 4.14.1.22 BETA is the current BETA I have installed.  I'm suprised the first DS GA release with Filament was released the texture shaded icon.

Unfortunately, I have no idea why the Filament viewport is not working for you.

Lindsey said:

RE: Your Filament rendering issue

In your picture showing Filament is not working, the view port icon you have selected is the "Cartoon Shaded" view. 
Select the Filament view port shown in the attached pic.

if you look closely at my picture filament doesnt look like a light bulb like yous does if you compare my screen shot to yours.

Padone said:

j cade said:

The more accurate comparison for Filament is Blender's Material previw in the viewport

This ^. They really needed something better than multipass opengl, to get out of mesozoic.

Yeah, but Blender's material preview in the viewport is still Eevee now.  You can turn on tons of features for the viewport and set resolution so that viewport is exactly the same as the actual render.  There really is no "viewport" material preview that is different from the render.  The only thing that changes now from viewport to render, with Eevee,  is the samples.

What do you mean by transparency ?  Cutout opacity ? it always worked , there was some issues when it was set at 50%, but it is not how it should be used in first place 

RexRed said:

Am I imagining things or did Filament just get an update?

When I first tried it transparencies did not work in Filament, now they do.

It seems to coincide with an update a few days ago.

Am I imagining things or did Filament just get an update?

When I first tried it transparencies did not work in Filament, now they do.

It seems to coincide with an update a few days ago.

j cade said:

The more accurate comparison for Filament is Blender's Material previw in the viewport

This ^. They really needed something better than multipass opengl, to get out of mesozoic.

RE: Your Filament rendering issue

In your picture showing Filament is not working, the view port icon you have selected is the "Cartoon Shaded" view. 
Select the Filament view port shown in the attached pic.

Phantom Daz Studio in task manager is a common occurrence if you build complex scenes, or your G8/G3/G2/G character has lots of morphs available. Daz Studio will eventually self terminate, after the single thread process has taken care of a series of undocumented tasks. If you didn't edit the GUI, you can usually safely kill the process. If you have, and kill the process, you will need to edit the GUI again next time.

Iray can crash if you are at the limit of your available GPU memory. I've experienced this with the unbiased version as well, and it often fails when the post denoiser kicks in and places on the GPU a demand for which not enough resources exist. The GPU will stop processing, but you will need to kill Studio to terminate the broken Iray instance and free up the GPU memory. Monitor your graphics card memory via Task Manager (Performance tab) if you are on the latest releases of Windows 10. Otherwise, use MSI Afterburner or similar.

I haven't experimented with Filament enough to experience that.

Hi all,

I'm running Daz Studio 4.14 on Windows 10 using an nVidia GTX 970.

And I'm having a few issues. Just wonder if any body else is getting similar.

• When I exit DS, although it looks like it's existed, if I open Task Manager it's still running in the background and I have to end the task before I can restart it.
• When rendering, if I use the Interactive (Biased) Render Mode, if I try to cancel a render, it seems to cancel, but if I try to restart a render it says there is one already running.
• The new Filament display type is awesome when it works, but does seem to crash a lot.

Anybody else getting anything like this?

Thanks.

DAZ_ann0314 said:

We are still working on getting up all the info for everyone. I'll be adding more screenshots etc as the evening goes on. Please feel free to ask any questions not seen in the information above and we will try to answer them for you all as quickly as possible

Filament is not working and a product error. i included some screenshots. latest daz 4.14 update and now a lot is happening.

aniMate2 can work as an NLA in Studio letting you easily build up your characters motions using layers, so you can have more complex animations...doing different things at the same time.

I understand the improvents in Blender, but again when they make a change as in Eevee you run into one of the big negatives and bad surprises.

I still think Daz characters look the best rendered in DS with Iray. And I was looking at some renders done with wowie's old plugin in 3DL that were not bad. With the tips of other animators and the faster Nvidia cards animation is more doable. Free Nomon has figured out how to get some OK results in DS with Filament and has light sets to improve the look over on his YouTube channel. He hopes to have the plugins in the store soon. His Iray speed tips are great as well.

With the motion capture files site iClone has setup now, if you can afford it, it's possible to get more done if you can get their files into DS. But it's not an easy export option yet but with Unreal, Unity, Maya, Blender options maybe they'll add Daz.

That's the thing. New tools are and will be developed. I hope to see even better versions of Filament, Iray, and perhaps entirely different rendering engines in the future.

Luciel said:

There was a minor update which was mostly bug fixes I think.

However, Filament supports shadows from the first 6 lights and i'm kind of pretty sure it was first 3 before (maybe). Though maybe not.

Ah. Okay. Thanks for the info, and replying.

For such a small update, it's totally messed up my installation, and content library. :/

gniiial said:

I guess you did not make a render yet. The loading time is not the only hiccup. I imagine there will be soon another update, to get the shading back to where it was?! If not and this will be the way, i think a lot of vendors have to update their products. But my guess is, that there went something wrong. Also the light is again stronger in Filament and the shadows behave in another, really interesting way.

Something like that has been annoying me too, but I can't reproduce it.  Here are a pair of renders originating in a bug report I submitted in March 2019; the first is from 2019 so, IRC, 4.12.  The second I just made with 4.14.1.22.  To double check I diffed the two images with PS 2021; that's the third PNG.

It's really annoying; there's not change there but I don't know if I'm seeing a bug in  other cases or just changing something consequential in the lighting and getting a bad render.

It would be really good if you could submit a bug with the scene file with the original, pre-4.14.1.22, render and the current beta render.  Iray renders should not change in the way you demonstrate.

brainmuffin said:

gregsgraphics_cafd0962a0 said:

brainmuffin said:

As they both crash for me, I find them to be identical.

Sounds like you either have an older system that doesn't support the minimum OpenGL drivers, or your graphics drivers are just out of date.  Both Eevee and Filament should run on most computers from the last 8 years!  As long as your graphics drivers support OpenGL 3.3 or higher.  Filament might even be more forgiving than that right now.  You also need to be sure you have a 64bit CPU with a minimum of 4gb of system ram.  I found that 4gb is still too low.  8gb minimum should be the actual lowest spec for RAM.

10 year old iMac with 16 GB RAM. Cycles now crashes too. On my Linux box, I only have 8GB RAM. Eevee always crashes. Cycles sometimes runs out of memory. The Nvidia card on the Linux machine has 4GB RAM.

Ah, it's a Mac.  I can't speak to the stability of any software package for Mac, but if you do a Google for "graphics drivers for Mac unstable" you will find a ton of threads, even on Apple.com, complaining about display drivers and software crashes related to graphics card drivers on the Mac, especially when it comes to hardware-accelerated video rendering.  This goes for everything from video conferencing to graphics software apps like Blender.  Apple blames the software, but the software companies are pointing the finger at Apple.  Since these issues do not seem to be a problem on PC, I don't know.

As far as your Linux box having the same issue, that could be something entirely different, but again I find Nvidia drivers are notoriously unstable on Linux as well.  AMD does a little better on that platform, but AMD drivers, in general, are a hit and miss too.

Richard Haseltine said:

Sevrin said:

Richard Haseltine said:

battfield said:

In conclusion, the problems to be solved by the Filament engine have not been improved at all.
Problems with hair transparency, emissive information not being reflected, etc. First of all, I think Daz needs to work on this problem as hard as possible.
They need to be able to draw that pressure on the operation to either make PBR buildable in the shader builder or release an official FilamentShader.
I call it the do-it-yourself disease, as is often the case in creative fields, but I know that relying on it will not help you make progress or progress.

結論から言いますと、Filamentエンジンで解決すべき問題点は全く改善されておりません。
髪の透過問題、エミッシブ情報が反映されない問題など。まずDazはこの問題に全力で取り組まないとダメだと思います。
PBRをシェーダービルダーで組めるようにするか、正式なFilamentShaderをリリースするか、そのプレッシャーを運営に描ける必要があります。
クリエイティブな分野によくありがちですが、自分で何とかしろ病と呼んでいますが、これに頼っては進歩するものも進歩しないものと心得ます。

Please do bear in mind that Filament is billed by Daz as a drawstyle, not a as a Render Engine.

Since when does Daz release shaders for "drawstyles"?

If it's intended as a drawstyle it may not get the depth of support that a render engine may receive.  I don't know how far Daz is intending to take it, and PAs of course may offer support regardless, I just wished to caution against expecting more than may be forthcoming.

Well, from the Daz3D tutorial on YouTube

In this tutorial you'll get a quick overview on how to use Filament, our new real time renderer. We'll show you how to change your viewport, adjust tonemapping, how to work with your environment, textures, shadows, and skin, and finally how to render with Viewport.

 It's being promoted as a "renderer".

Richard Haseltine said:

Sevrin said:

Richard Haseltine said:

battfield said:

In conclusion, the problems to be solved by the Filament engine have not been improved at all.
Problems with hair transparency, emissive information not being reflected, etc. First of all, I think Daz needs to work on this problem as hard as possible.
They need to be able to draw that pressure on the operation to either make PBR buildable in the shader builder or release an official FilamentShader.
I call it the do-it-yourself disease, as is often the case in creative fields, but I know that relying on it will not help you make progress or progress.

結論から言いますと、Filamentエンジンで解決すべき問題点は全く改善されておりません。
髪の透過問題、エミッシブ情報が反映されない問題など。まずDazはこの問題に全力で取り組まないとダメだと思います。
PBRをシェーダービルダーで組めるようにするか、正式なFilamentShaderをリリースするか、そのプレッシャーを運営に描ける必要があります。
クリエイティブな分野によくありがちですが、自分で何とかしろ病と呼んでいますが、これに頼っては進歩するものも進歩しないものと心得ます。

Please do bear in mind that Filament is billed by Daz as a drawstyle, not a as a Render Engine.

Since when does Daz release shaders for "drawstyles"?

If it's intended as a drawstyle it may not get the depth of support that a render engine may receive.  I don't know how far Daz is intending to take it, and PAs of course may offer support regardless, I just wished to caution against expecting more than may be forthcoming.

 

Sevrin said:

Richard Haseltine said:

battfield said:

In conclusion, the problems to be solved by the Filament engine have not been improved at all.
Problems with hair transparency, emissive information not being reflected, etc. First of all, I think Daz needs to work on this problem as hard as possible.
They need to be able to draw that pressure on the operation to either make PBR buildable in the shader builder or release an official FilamentShader.
I call it the do-it-yourself disease, as is often the case in creative fields, but I know that relying on it will not help you make progress or progress.

結論から言いますと、Filamentエンジンで解決すべき問題点は全く改善されておりません。
髪の透過問題、エミッシブ情報が反映されない問題など。まずDazはこの問題に全力で取り組まないとダメだと思います。
PBRをシェーダービルダーで組めるようにするか、正式なFilamentShaderをリリースするか、そのプレッシャーを運営に描ける必要があります。
クリエイティブな分野によくありがちですが、自分で何とかしろ病と呼んでいますが、これに頼っては進歩するものも進歩しないものと心得ます。

Please do bear in mind that Filament is billed by Daz as a drawstyle, not a as a Render Engine.

Since when does Daz release shaders for "drawstyles"?

If it's intended as a drawstyle it may not get the depth of support that a render engine may receive.  I don't know how far Daz is intending to take it, and PAs of course may offer support regardless, I just wished to caution against expecting more than may be forthcoming.