Why does everyone think that just because Daz added Filament that the whole program is completely different??! You can have the EXACT SAME INTERFACE that you've always used, right down to the open gl preview if you want. Nothing has changed EXCEPT for the addition of Filament, which you can use - OR NOT.

Laurie

I'm starting to think there must have been a thread on another forum spreading some misinformation about the newest Daz Studio release. I can't explain, otherwise, why people are coming out of the woodwork falsely claiming things like the program being really different. I'm going to put on a tinfoil hat for a second and wonder if it has anything to do with Poser getting a new version recently as well. lol *Removes tinfoil hat.*

LOL.

If someone takes 5 minutes and sets up a default scene, they'd never even know that Filament had been added except for the Tonemapping and Environment options now in the scene tab. And even those you still use the same as always (same settings). Other than that...

Laurie

Why does everyone think that just because Daz added Filament that the whole program is completely different??! You can have the EXACT SAME INTERFACE that you've always used, right down to the open gl preview if you want. Nothing has changed EXCEPT for the addition of Filament, which you can use - OR NOT.

Laurie

I'm starting to think there must have been a thread on another forum spreading some misinformation about the newest Daz Studio release. I can't explain, otherwise, why people are coming out of the woodwork falsely claiming things like the program being really different. I'm going to put on a tinfoil hat for a second and wonder if it has anything to do with Poser getting a new version recently as well. lol *Removes tinfoil hat.*

I keep seeing the same forum users coming into these threads, I am doing an animated Filament render on my older PC without a graphics card while I wait for them to arrive here

Why does everyone think that just because Daz added Filament that the whole program is completely different??! You can have the EXACT SAME INTERFACE that you've always used, right down to the open gl preview if you want. Nothing has changed EXCEPT for the addition of Filament, which you can use - OR NOT.

Laurie

I'm starting to think there must have been a thread on another forum spreading some misinformation about the newest Daz Studio release. I can't explain, otherwise, why people are coming out of the woodwork falsely claiming things like the program being really different. I'm going to put on a tinfoil hat for a second and wonder if it has anything to do with Poser getting a new version recently as well. lol *Removes tinfoil hat.*

Why does everyone think that just because Daz added Filament that the whole program is completely different??! You can have the EXACT SAME INTERFACE that you've always used, right down to the open gl preview if you want. Nothing has changed EXCEPT for the addition of Filament, which you can use - OR NOT.

Laurie

You don't even have to update to 4.14. I'm staying on 4.12 for now since the 445.98 nvidia drivers are working perfectly for my 1070/970 and unless a script needs the latest version, I'll be sticking with this until then.

Why does everyone think that just because Daz added Filament that the whole program is completely different??! You can have the EXACT SAME INTERFACE that you've always used, right down to the open gl preview if you want. Nothing has changed EXCEPT for the addition of Filament, which you can use - OR NOT.

Laurie

Using filament the inside of the characters mouth is brightly illuminated.

Is this just me or this a problem with filament? Any solution?

Not sure what the problem is, 4.14 hasn't affected how I use Studio, I'm still a 3dl user and nothing has changed. I am interested in how filament might be useful on my desktop, it's not available on my laptop (integrated graphics with only OpenGL4.0), as not having to do a render to see where shadows lie would speed up my workflow. If you continued to use either 3dl or iray life would shuffle on as though filament were a figment of your imagination.

 

This is the expected bhaviour - see the discussion of the new singleton nodes in the release and highlights threads.

 

What is the point of this downgrade?

The point of this development is:

The singleton nodes are the embodiment of scene level options moved (not copied) to nodes in the scene in order to provide access to those settings outside of the limited context there were previously provided under. Because it is now possible to have a viewport set to the Filament (PBR) DrawStyle, and also have the active renderer set to NVIDIA Iray, both of which have similar settings, it was not intuitive to have to go to Render Settings for the NVIDIA Iray renderer in order to adjust a setting that affected the Filament (PBR) DrawStyle. Similarly, it would not be intuitive to have to set the DrawStyle for the active viewport (of which there can be several) to Filament (PBR) and then access the Draw Setting pane in order adjust setting that affect the NVIDIA Iray renderer. It made more sense to expose the common settings using a familiar paradigm (a node in the scene), introduce the concept of singletons, and present the properties on those nodes in the appropriate panes when/where applicable.

In my opinion it's not a "development" if it takes me more steps to do what I did before.

 

Nevertheless, it is something that was done for a reason.

 

This is the expected bhaviour - see the discussion of the new singleton nodes in the release and highlights threads.

 

What is the point of this downgrade?

The point of this development is:

The singleton nodes are the embodiment of scene level options moved (not copied) to nodes in the scene in order to provide access to those settings outside of the limited context there were previously provided under. Because it is now possible to have a viewport set to the Filament (PBR) DrawStyle, and also have the active renderer set to NVIDIA Iray, both of which have similar settings, it was not intuitive to have to go to Render Settings for the NVIDIA Iray renderer in order to adjust a setting that affected the Filament (PBR) DrawStyle. Similarly, it would not be intuitive to have to set the DrawStyle for the active viewport (of which there can be several) to Filament (PBR) and then access the Draw Setting pane in order adjust setting that affect the NVIDIA Iray renderer. It made more sense to expose the common settings using a familiar paradigm (a node in the scene), introduce the concept of singletons, and present the properties on those nodes in the appropriate panes when/where applicable.

In my opinion it's not a "development" if it takes me more steps to do what I did before.

So I'm trying to play around with Filament. I've followed the tutorial video, but when I hit render, DAZ Studio just hangs and I have to kill the process through Task Manager. System specs: Windows 10, Ryzen 2700 8-core processor, Radeon RX 580 graphics, 64 GB RAM, 1 TB SSD. What am I doing wrong?

Just to be clear, since I'm not seeing filament as one of the options in the viewport right now, Filament Render is not compatible with Mac OS yet? 

And if not, can someone from Daz update the website to reflect that anywhere?? I'm happy I haven't purchased any filament items because I wanted to test its limits with what I have first.

It's in the release notes for 4.14 that Filament is currently Windows Only (Even tho Filament its self works on both Windows & MacOS,  Daz has only intergrated the windows version)

Ah ok, I was wondering where this info was, because when I go to the filament page on the daz store and search either "Mac" or "Windows" nothing comes up. Wish they were more clear here! I'm not even sure how to find the release notes for any versions of Daz Studio lol. Hope it gets implemented in the Mac version soon as it seems very useful to Mac users especially since we don't have Cuda support for iray etc!

 

This is the expected bhaviour - see the discussion of the new singleton nodes in the release and highlights threads.

 

What is the point of this downgrade?

The point of this development is:

The singleton nodes are the embodiment of scene level options moved (not copied) to nodes in the scene in order to provide access to those settings outside of the limited context there were previously provided under. Because it is now possible to have a viewport set to the Filament (PBR) DrawStyle, and also have the active renderer set to NVIDIA Iray, both of which have similar settings, it was not intuitive to have to go to Render Settings for the NVIDIA Iray renderer in order to adjust a setting that affected the Filament (PBR) DrawStyle. Similarly, it would not be intuitive to have to set the DrawStyle for the active viewport (of which there can be several) to Filament (PBR) and then access the Draw Setting pane in order adjust setting that affect the NVIDIA Iray renderer. It made more sense to expose the common settings using a familiar paradigm (a node in the scene), introduce the concept of singletons, and present the properties on those nodes in the appropriate panes when/where applicable.

Just to be clear, since I'm not seeing filament as one of the options in the viewport right now, Filament Render is not compatible with Mac OS yet? 

And if not, can someone from Daz update the website to reflect that anywhere?? I'm happy I haven't purchased any filament items because I wanted to test its limits with what I have first.

It's in the release notes for 4.14 that Filament is currently Windows Only (Even tho Filament its self works on both Windows & MacOS,  Daz has only intergrated the windows version)

Just to be clear, since I'm not seeing filament as one of the options in the viewport right now, Filament Render is not compatible with Mac OS yet? 

And if not, can someone from Daz update the website to reflect that anywhere?? I'm happy I haven't purchased any filament items because I wanted to test its limits with what I have first.

a HUGE one .. I think I noticed it in your building scene as I missed the shadows on the other left plant

 they looking into it already so gonna be fixed with upcoming releases .

What happening in your box scene is that only half of the shadow is created and the rest of the light is passing through the object , all lights source passing light through objects in Filament if there is no shadow active , and as in our case, only half shadow .

Your scene renders the same way on RTX 2060.

 

Oh, so now it is making some sense - BUG!

 

Great! That should be an improvement that is noticeable.

a HUGE one .. I think I noticed it in your building scene as I missed the shadows on the other left plant

 they looking into it already so gonna be fixed with upcoming releases .

What happening in your box scene is that only half of the shadow is created and the rest of the light is passing through the object , all lights source passing light through objects in Filament if there is no shadow active , and as in our case, only half shadow .

Your scene renders the same way on RTX 2060.

 

Oh, so now it is making some sense - BUG!

Since I installed the new daz-studio version, with the filament preview mode.... I'm having lots of problems in the tavern

Preview is way too bright, renders are extremely dark.

smoke items don¡t look well in preview, but is not a big deal.

I worked to separate different parts of the inn in different groups to hide in an easier (for me) way. I don't know if the problem is my file, or anyone using this product out of the box is experimenting any problem too...

thanks!

Filament makes shadows optional, so you are probably getting external environment light streaming in. On the other hand, Filament doesn't (currently) do emissives in DS. It will take some experimentation to get a reasonable match on lighting, and even then it is going to be far from exact.

What happening in your box scene is that only half of the shadow is created and the rest of the light is passing through the object , all lights source passing light through objects in Filament if there is no shadow active , and as in our case, only half shadow .

Your scene renders the same way on RTX 2060.

 

Oh, so now it is making some sense - BUG!

What happening in your box scene is that only half of the shadow is created and the rest of the light is passing through the object , all lights source passing light through objects in Filament if there is no shadow active , and as in our case, only half shadow .

Your scene renders the same way on RTX 2060.

Nvidia RTX 2080 Super, Nvidia driver 456.51. Win 10 64GB RAM. 

Was rendering Iray sucessfully yesterday. Today I get an unusual message and some odd lines in the log.

The message is "Unable to Render. Renderer already in use. The view port is in Texture Shaded for this. Note that the Nvida Iray Viewport renders fine.

The log shows a lenghty series of messages tlike the following:

"2020-11-20 13:59:53.168 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: HTTP/1.1 400 Bad Request

2020-11-20 13:59:53.168 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Date: Fri, 20 Nov 2020 19:59:53 GMT

2020-11-20 13:59:53.190 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Server: Apache

2020-11-20 13:59:53.194 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Vary: Accept-Encoding

2020-11-20 13:59:53.194 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Content-Length: 226

2020-11-20 13:59:53.194 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Connection: close

2020-11-20 13:59:53.197 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: Content-Type: text/html; charset=iso-8859-1

2020-11-20 13:59:53.197 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: 

2020-11-20 13:59:53.197 WARNING: ..\..\..\..\..\src\sdksource\cloud\dzcloudtasknotifier.cpp(178): Got an unknown command from the persistent connection: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">"

Any ideas? I haven't been experimenting with Filament. Again I have been successfully rendering in Iray with both Beta 4.14.0.08 and Public Release 4.14.0.08. Yes I know they are the same.

The only other change i am aware of is a Windows 10 update this am. I think i rolled that back after seeing this error. It only showed 2 Security and 2 other updates (from 11/20 and 11/19).