Some settings for G8 Skin shader on filament using iRay parameters, and settings for default HDR scene, no distant lights used  use it if you are lost on filament or want to improve my settings, welcome!

the skin texture is from CO Ichigo and Ichigo Hair for Genesis 8 Female(s)

Filament Draw Options, for this you will need to uncheck "limits" on any parameter, well if you want this PS2 Resident Evil shader of course 

the value is 10357.34 on Environment Intensity Scale

Skin looks very nice under the lighting conditions.Thanks for sharing.

Have you had a chance to test out the new Filament renderer?  It is supposed to be a super time saver for animations, but at the cost of certain lighting and surface options,  and a few other details.  Am curious of your thoughts about the trade-offs.  

It would make even more sense if they were in the Camera Pane

Cameras have their own settings, fStop there controls Depth of Field and if we ever get motion blur I imagien there is likely to be a shutter speed control on the camera for that.

yes,  I agree, 'Exposure', 'Shutter Speed', 'F/Stop', 'ISO' are all Camera settings. I can understand they apply to all cameras but there's no reason they couldn't apply to each camera separately. I also realise that not everyone using Daz will have used a manual Camera though so I suppose that doesn't matter. I don't mind. As long as I know where they are.  I do like the new Filament for setting up scenes though. It is really helpful. 

I was saying that the exposure settings do not behave like real-worl settings in that they have no effect beyond exposure - increasing ISO does not increase noise, adjusting fStop theer does not affect DoF, adjusting spped does not affect motion blur. They are purely exposure settings, while the only one that currently has its other effect (fStop) has a second setting on the camera for that.

I know, they're a waste of time. 

The only thing that matters in the Tone Mapping properties so far as overall exposure is concerned is EV; as @AbnerK says all the other stuff is just a confusing waste of time; it confuses those of us who have used an amateur camera and it is meaningless garbage for everyone else.  With Filament the tone-mapping entry disappears from the render settings pane "because" filament doesn't do any tone mapping, yet it still responds to the EV setting, so if you use Filament to render (by setting the Render Settings/Advanced tab engine setting to "Viewport") it is impossible to adjust the exposure of the render in the render settings tab; instead you have to go to the Parameters of the Tone Mapping node, which curiously reveals all the poo that does absolutely nothing as well as the EV which you need.

I've filed a bug ("ticket") on the fact that the EV setting is not per-camera and that I can't change the EV as I move the camera in an animation.

Something has also happened to the progressive render settings; it looks like the latest release is managing, somehow, to set them back to the default, which results in my renders completing unexpectedly.  Another mystery to solve; progressive render settings are for certain scene specific.

when you say 'progressive render settings, are you talking about the 'Progress' settings? Mine always return to 2 hour limit if Daz crashes. If that's what you mean, you can change them during and after a render finishes. You'll then get the option to 'Resume'. Took me ages to find that out. If not then I must be missing something useful. :) 

It would make even more sense if they were in the Camera Pane

Cameras have their own settings, fStop there controls Depth of Field and if we ever get motion blur I imagien there is likely to be a shutter speed control on the camera for that.

yes,  I agree, 'Exposure', 'Shutter Speed', 'F/Stop', 'ISO' are all Camera settings. I can understand they apply to all cameras but there's no reason they couldn't apply to each camera separately. I also realise that not everyone using Daz will have used a manual Camera though so I suppose that doesn't matter. I don't mind. As long as I know where they are.  I do like the new Filament for setting up scenes though. It is really helpful. 

I was saying that the exposure settings do not behave like real-worl settings in that they have no effect beyond exposure - increasing ISO does not increase noise, adjusting fStop theer does not affect DoF, adjusting spped does not affect motion blur. They are purely exposure settings, while the only one that currently has its other effect (fStop) has a second setting on the camera for that.

I know, they're a waste of time. 

The only thing that matters in the Tone Mapping properties so far as overall exposure is concerned is EV; as @AbnerK says all the other stuff is just a confusing waste of time; it confuses those of us who have used an amateur camera and it is meaningless garbage for everyone else.  With Filament the tone-mapping entry disappears from the render settings pane "because" filament doesn't do any tone mapping, yet it still responds to the EV setting, so if you use Filament to render (by setting the Render Settings/Advanced tab engine setting to "Viewport") it is impossible to adjust the exposure of the render in the render settings tab; instead you have to go to the Parameters of the Tone Mapping node, which curiously reveals all the poo that does absolutely nothing as well as the EV which you need.

I've filed a bug ("ticket") on the fact that the EV setting is not per-camera and that I can't change the EV as I move the camera in an animation.

Something has also happened to the progressive render settings; it looks like the latest release is managing, somehow, to set them back to the default, which results in my renders completing unexpectedly.  Another mystery to solve; progressive render settings are for certain scene specific.

Hello. I have been watching the official daz studio videos on filament. i have one problem, under create, the Physically based draw mode(PBR) option is not available. from the video it seems you need 3 draw/node to be created right?

You don't need to create it; on the scene window in the sometimes-very-difficult-to-see rendering mode option (to the left of the camera/view drop-down) it is at the bottom.

If you set the render mode in the render settings pane/Advanced tab to "viewport" and the viewport is in Filament(PBR) mode then the render will using Filament; it's somewhat weird.

I didn't watch the video of course ;-)

 the video was quite informational. the were some hidden features u need to to tick to bring some stuffs on/ my scene created to filament mode/draw nodes, i guess yeah somehow sometimes it automatically creates

What is your operating system? Are you using the 32 or 64 bit version of DS?

64 bit daz.... i think the name have changed from pbr to filament something....

Hello. I have been watching the official daz studio videos on filament. i have one problem, under create, the Physically based draw mode(PBR) option is not available. from the video it seems you need 3 draw/node to be created right?

You don't need to create it; on the scene window in the sometimes-very-difficult-to-see rendering mode option (to the left of the camera/view drop-down) it is at the bottom.

If you set the render mode in the render settings pane/Advanced tab to "viewport" and the viewport is in Filament(PBR) mode then the render will using Filament; it's somewhat weird.

I didn't watch the video of course ;-)

Hello. I have been watching the official daz studio videos on filament. i have one problem, under create, the Physically based draw mode(PBR) option is not available. from the video it seems you need 3 draw/node to be created right?

It would make even more sense if they were in the Camera Pane

Cameras have their own settings, fStop there controls Depth of Field and if we ever get motion blur I imagien there is likely to be a shutter speed control on the camera for that.

yes,  I agree, 'Exposure', 'Shutter Speed', 'F/Stop', 'ISO' are all Camera settings. I can understand they apply to all cameras but there's no reason they couldn't apply to each camera separately. I also realise that not everyone using Daz will have used a manual Camera though so I suppose that doesn't matter. I don't mind. As long as I know where they are.  I do like the new Filament for setting up scenes though. It is really helpful. 

I was saying that the exposure settings do not behave like real-worl settings in that they have no effect beyond exposure - increasing ISO does not increase noise, adjusting fStop theer does not affect DoF, adjusting spped does not affect motion blur. They are purely exposure settings, while the only one that currently has its other effect (fStop) has a second setting on the camera for that.

I know, they're a waste of time. 

This is very very niche but Filament and Iray compositing is really helpful so far. I hoped I'd be able to use it kind of like a paint filter for environments without having to work around algorithm weirdness, and it is in fact good for that! I want to experiment with some of the other viewport drawstyles to see if I can add more texture or create lineart effects. 

I hope some of you might find it helpful. :) Of course, feel free to tweak it and make changes to suit your own personal tastes and preferences.

Please let me know if I packed it up correctly and if it works ok. :)

It works great, thank you so much for sharing! :D 

 

Oh good! I'm glad it's helpful! :) And your composite render looks fantastic - very cool idea! I'll have to experiment with some compost renders as well. I like the effect!

So I stumbled across this over in the Filament thread, and thought it might be of interest to USC fans.  The new Viewport render option renders out a lot more than you see in the texture-shaded viewport.  Y'all may know about this already, but it was a revelation to me.

Iray Render

Texture-shaded Viewport

Viewport render - Texture-shaded

Filament Viewport Render - Garbage, but anyway

Viewport renders are instant, so I thought it might be a nice way to preview general placement without having to switch to Iray.

It looks like Texture Shaded viewport render doesn't respect the Visible in Viewport attribute the way Filament viewport render does. Bug?

Feature!

Inconsistent!

I submitted a help request about the inconsistency. I don't know which behavior is "correct". It is a Viewport  engine Render, so which flag should be controlling the content of the result - Visible in Viewport or Visible in Render?

It would make even more sense if they were in the Camera Pane

Cameras have their own settings, fStop there controls Depth of Field and if we ever get motion blur I imagien there is likely to be a shutter speed control on the camera for that.

yes,  I agree, 'Exposure', 'Shutter Speed', 'F/Stop', 'ISO' are all Camera settings. I can understand they apply to all cameras but there's no reason they couldn't apply to each camera separately. I also realise that not everyone using Daz will have used a manual Camera though so I suppose that doesn't matter. I don't mind. As long as I know where they are.  I do like the new Filament for setting up scenes though. It is really helpful. 

I was saying that the exposure settings do not behave like real-worl settings in that they have no effect beyond exposure - increasing ISO does not increase noise, adjusting fStop theer does not affect DoF, adjusting spped does not affect motion blur. They are purely exposure settings, while the only one that currently has its other effect (fStop) has a second setting on the camera for that.

It would make even more sense if they were in the Camera Pane

Cameras have their own settings, fStop there controls Depth of Field and if we ever get motion blur I imagien there is likely to be a shutter speed control on the camera for that.

yes,  I agree, 'Exposure', 'Shutter Speed', 'F/Stop', 'ISO' are all Camera settings. I can understand they apply to all cameras but there's no reason they couldn't apply to each camera separately. I also realise that not everyone using Daz will have used a manual Camera though so I suppose that doesn't matter. I don't mind. As long as I know where they are.  I do like the new Filament for setting up scenes though. It is really helpful. 

This is very very niche but Filament and Iray compositing is really helpful so far. I hoped I'd be able to use it kind of like a paint filter for environments without having to work around algorithm weirdness, and it is in fact good for that! I want to experiment with some of the other viewport drawstyles to see if I can add more texture or create lineart effects. 

I hope some of you might find it helpful. :) Of course, feel free to tweak it and make changes to suit your own personal tastes and preferences.

Please let me know if I packed it up correctly and if it works ok. :)

It works great, thank you so much for sharing! :D 

if you need an earlier version and didn't back up the application and plug-in installers then you will need to cotnact suport via a ticket. However, most people do not seem to be having this issue. reportedly one way to purge filament, albeit addessing a diffrent issue, is to set the preview mode to Texture Shaded.

So I stumbled across this over in the Filament thread, and thought it might be of interest to USC fans.  The new Viewport render option renders out a lot more than you see in the texture-shaded viewport.  Y'all may know about this already, but it was a revelation to me.

Iray Render

Texture-shaded Viewport

Viewport render - Texture-shaded

Filament Viewport Render - Garbage, but anyway

Viewport renders are instant, so I thought it might be a nice way to preview general placement without having to switch to Iray.

It looks like Texture Shaded viewport render doesn't respect the Visible in Viewport attribute the way Filament viewport render does. Bug?

Feature!

Force quitting is not a good idea, and certainly shouldn't be done as a matter of course.

I have both the public release, and the beta icons on my desktop. I've found that this problem is almost random in that "sometimes" it does not occur. The symptom of it occuring is when you close Daz and try to open it again, it won't. So I used to go to task manager and kill it and then I could start Daz again. Then, one day I discovered that all I had to do if one won't open is to open the other. So if Daz regular doesn't open because it's running in the background, I open the beta version instead. You can even open the beta and then close it right away and then the regular one will open. It seems to hang sometimes for a very long time, chugging away at who knows what. And by the way, this only started happening when I upgraded from 4.12 tp 4.14, so there is certainly some kind of issue going on here... and I'm using 4.14.0.8 since I only just discovered yesterday that there had been an upgrade. I'm wondering if Filament has anything to do with this? I love playing with it so I'm trying it everytime I fire up Daz.

DS will not, without assigning a different session name, allow two isntances of the same release channel to run - which is why you can't start the General Release while a General Release is closing but can start a Public Build, and vice versa. I doubt that openign and closing the other release channel is actually unsticking anything, since they should be separate in all respects bar access to the CMS, and that is designed for multiple connections.

One thing I've noticed about this new release is that Iray is way faster if you've previously tried a scene with filament. From there on Iray renders right away instead of that long period where it is black and white.

So I stumbled across this over in the Filament thread, and thought it might be of interest to USC fans.  The new Viewport render option renders out a lot more than you see in the texture-shaded viewport.  Y'all may know about this already, but it was a revelation to me.

Iray Render

Texture-shaded Viewport

Viewport render - Texture-shaded

Filament Viewport Render - Garbage, but anyway

Viewport renders are instant, so I thought it might be a nice way to preview general placement without having to switch to Iray.

It looks like Texture Shaded viewport render doesn't respect the Visible in Viewport attribute the way Filament viewport render does. Bug?

Force quitting is not a good idea, and certainly shouldn't be done as a matter of course.

I have both the public release, and the beta icons on my desktop. I've found that this problem is almost random in that "sometimes" it does not occur. The symptom of it occuring is when you close Daz and try to open it again, it won't. So I used to go to task manager and kill it and then I could start Daz again. Then, one day I discovered that all I had to do if one won't open is to open the other. So if Daz regular doesn't open because it's running in the background, I open the beta version instead. You can even open the beta and then close it right away and then the regular one will open. It seems to hang sometimes for a very long time, chugging away at who knows what. And by the way, this only started happening when I upgraded from 4.12 tp 4.14, so there is certainly some kind of issue going on here... and I'm using 4.14.0.8 since I only just discovered yesterday that there had been an upgrade. I'm wondering if Filament has anything to do with this? I love playing with it so I'm trying it everytime I fire up Daz.

One thing I've noticed about this new release is that Iray is way faster if you've previously tried a scene with filament. From there on Iray renders right away instead of that long period where it is black and white.

but, like, we just got a new beta update with 12.9. we got filament with that, right? Why not wait to do all this other stuff until it's fixed? Or, give people a way to rollback? (if there is one, lemme know, because even though I'm on a PC I'm getting less stability than with 12.9)