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).

Eyekonography said:

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. 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?

jbowler said:

WendyLuvsCatz said:

oh BTW on the issue I am only having because I am using Filament (and presumably HDR files others are not using) the very same scene the HDR I added shows in iray, if I save the scene using Filament adds the ruins one back even after using purge or clear undo stack, iray still shows the correct one.

It is working for me however there is a LONG delay before the update when using 16k HDRIs from hdrihaven.  The change to the dome seems to be happening in the background; I can load a new HDRI then go back to the filament render and pan the view a few times, maybe 10s, before the new dome displays.  This is on an system with 64GByte of DRAM and a fast processor (a couple of years old now).

What's happening in the parameters tab?  I.e. select the "Environment Options" node in the scene, go to Parameters and however over the picture of the dome in the "Environment Map" setting?  I see the new HDRI appear there when I load it (from Browse... on that setting), then after 10s or so the Filament view updates.  It's comparable to the time to show the Environment Parameters pane the first time; I assume DAZ is loading the HDRI into memory in both cases.

It is true that the HDRI scaling issue has been fixed in the beta; in the original versions (and I think, still, the general release but I haven't checked) the Filament display would show the HDRI at completely the wrong scale, as though it had calculated the angle to display from the focal length incorrectly.

what you describe is happening with most other HDR images but those particular ones are the problem it seems DTSS-Substance-#.HDR

I actually think they are meant to be textures but I have all my HDR files copied to one folder for ease of access

https://www.daz3d.com/strange-substances-pack-2

they render fine with iray but Filament just won't accept them at all, they show in the parameter thumbnail

I want them for scifi effects

Most times in poorly lit renders, or dark or shiny hair, or whatever, I have spots all over the place. I'm getting tired of going into Photoshop to correct the problems. Any ideas what's going on?

I included crops of two pics, the left side in filament, the right side in iray. What are those white spots?

Freightliner Fox said:

Won't happen unless the sun freezes over:

• Change the Carrara file format to reduce save times and reduce saved scene sizes (300 Mb isn't uncommon right now).
• Fix Genesis / Genesis 2 support in Carrara. It's really hit or miss right now with clothing and such.

Probably won't happen:

• Add Cycles as a native rendering option to Studio without having to export to Blender. Cycles is faster than Iray and supports more GPUs.

Might happen:

• Fix the DSON importer so it works in Poser 12.
• +1 on the gryphon suggestion. A good gryphon character to go along with Dragon 3 would be great.
• Fix the broken G4 character support in the latest updates to Studio.
• Fix the long-standing disappearing mouse pointer problem.

Probably will happen:

• +1 on improvements to Filament so it properly supports transparency, spotlights, and glow.
• Fix existing bugs in Filament (textures sometimes render in completely the wrong color, for example, My black DAZ horse 2 came out in neon green)

 

Genesis 9, if only to cut over from my Genesis 8 library. There's only so much more I can tack onto Genesis 8 right now.

Please, gods no. Focus on creating some decent non-human characters and leave Genesis alone for awhile. Fun fact: There is more content available for Victoria 4 than there is for any version of Genesis other than Genesis 8. Why? Because for a long time, Daz was pumping out new generations of Genesis faster than the PAs could produce content for them. And pretty much any time a new version of Genesis comes out, the PAs move on to support the latest figure and stop creating content for the older ones. This makes Genesis a money pit for users.

...yeah was disappointed in the 2 year rollover for the Genesis figure since it was first introduced. I barely got everything together I needed for character design with G3 and suddenly there was G8.  Just couldn't see dumping 100s more into a new Genesis base particularly given the "improvements" were few the investment I had in G3.  G8 may be backwards compatible with regards hair and clothing content (and you still need conversion scripts to make them fit more accurately), but not morphs, character expansions, poses, and other utilities that needed to be specially developed for it. 

WendyLuvsCatz said:

oh BTW on the issue I am only having because I am using Filament (and presumably HDR files others are not using) the very same scene the HDR I added shows in iray, if I save the scene using Filament adds the ruins one back even after using purge or clear undo stack, iray still shows the correct one.

It is working for me however there is a LONG delay before the update when using 16k HDRIs from hdrihaven.  The change to the dome seems to be happening in the background; I can load a new HDRI then go back to the filament render and pan the view a few times, maybe 10s, before the new dome displays.  This is on an system with 64GByte of DRAM and a fast processor (a couple of years old now).

What's happening in the parameters tab?  I.e. select the "Environment Options" node in the scene, go to Parameters and however over the picture of the dome in the "Environment Map" setting?  I see the new HDRI appear there when I load it (from Browse... on that setting), then after 10s or so the Filament view updates.  It's comparable to the time to show the Environment Parameters pane the first time; I assume DAZ is loading the HDRI into memory in both cases.

It is true that the HDRI scaling issue has been fixed in the beta; in the original versions (and I think, still, the general release but I haven't checked) the Filament display would show the HDRI at completely the wrong scale, as though it had calculated the angle to display from the focal length incorrectly.

kgrosser said:

As per the othewr thread:

RiverSoftArt said:

 

Filament is certainly faster than Iray in the viewport.  I haven't figured out a good way to convert to filament and then use Iray.  There are just so many scene changes.

could working in a filament converted scene, save out the characters as subset and then load into an iray environment scene work? Anyway I'm going to try this and see how much different it actually is.

I guess so?  You would need to NOT change the materials and only use the lighting options of the product.

As per the othewr thread:

RiverSoftArt said:

 

Filament is certainly faster than Iray in the viewport.  I haven't figured out a good way to convert to filament and then use Iray.  There are just so many scene changes.

could working in a filament converted scene, save out the characters as subset and then load into an iray environment scene work? Anyway I'm going to try this and see how much different it actually is.

kgrosser said:

RiverSoftArt said:

 If you have "Convert JCMs" checked, there can be a LOT of morphs that get converted.  If you post the log, I can tell you.

Actually it is a LOT ;) How long can it take? Will try again with a clear log and see where I get. Thanks for your exceptional help - and products! Looking forward to your Filament converter, will that speed up the viewport, too? What i would fancy was viewport close to iray but stil render out in iray, but I guess this would require separate scenes subsets and a topic for that other thread...

Filament is certainly faster than Iray in the viewport.  I haven't figured out a good way to convert to filament and then use Iray.  There are just so many scene changes.

Won't happen unless the sun freezes over:

• Change the Carrara file format to reduce save times and reduce saved scene sizes (300 Mb isn't uncommon right now).
• Fix Genesis / Genesis 2 support in Carrara. It's really hit or miss right now with clothing and such.

Probably won't happen:

• Add Cycles as a native rendering option to Studio without having to export to Blender. Cycles is faster than Iray and supports more GPUs.

Might happen:

• Fix the DSON importer so it works in Poser 12.
• +1 on the gryphon suggestion. A good gryphon character to go along with Dragon 3 would be great.
• Fix the broken G4 character support in the latest updates to Studio.
• Fix the long-standing disappearing mouse pointer problem.

Probably will happen:

• +1 on improvements to Filament so it properly supports transparency, spotlights, and glow.
• Fix existing bugs in Filament (textures sometimes render in completely the wrong color, for example, My black DAZ horse 2 came out in neon green)

Genesis 9, if only to cut over from my Genesis 8 library. There's only so much more I can tack onto Genesis 8 right now.

Please, gods no. Focus on creating some decent non-human characters and leave Genesis alone for awhile. Fun fact: There is more content available for Victoria 4 than there is for any version of Genesis other than Genesis 8. Why? Because for a long time, Daz was pumping out new generations of Genesis faster than the PAs could produce content for them. And pretty much any time a new version of Genesis comes out, the PAs move on to support the latest figure and stop creating content for the older ones. This makes Genesis a money pit for users.

RiverSoftArt said:

 If you have "Convert JCMs" checked, there can be a LOT of morphs that get converted.  If you post the log, I can tell you.

Actually it is a LOT ;) How long can it take? Will try again with a clear log and see where I get. Thanks for your exceptional help - and products! Looking forward to your Filament converter, will that speed up the viewport, too? What i would fancy was viewport close to iray but stil render out in iray, but I guess this would require separate scenes subsets and a topic for that other thread...

cain-x said:

Loading video into the backdrop and/or plane would be AMAZING - truly a dream come true. I know there are scripts but having this natively work would be wonderful.

 

DAZ studio is in fact the only 3D software I own that won't do this.

I do use Casual's TexAnim script and it works with Filament too for textures (not tried the background)

it is odd they just cannot integrate the functionality even with their Qt4 build since the maths functions exist 

in Carrara, Poser and iClone (and even once Blender)I have even used animated image based lighting (usually animated cloud loops)

D|S is at least 10 years behind the times here.

These are some great wishes. Most of them achieveable with some outside 3D apps but one can totally dream :)

+1 on Filament and getting all the plumbing done. Even in the short term, I'd settle for fixing the transparency issues. This is a good step forward for animators.

More female shoe kits would be nice too.

Loading video into the backdrop and/or plane would be AMAZING - truly a dream come true. I know there are scripts but having this natively work would be wonderful.

Gemini Queen said:

Nevermind, I figured out how to do it, it just looks like a continuous stream of water now, instead of looking like an actual shower. I'm just silly. I'll need to go buy some water shaders for showers I guess. (Does the store even have that?) Thanks so much though! 

 The shower water in Home One Bathroom's shower comes with an opacity map that needs to be loaded into the Cutout Opacity slot in Iray (I'm guessing that's what you're using -- the map will be preloaded when you bring the shower into the scene. If you're using Filament, i have absolutely no idea what you'll need to do.).

What  I would suggest is loading the shower, selecting the shower water surface in the Surfaces tab (Just called "Water", I think), find the particular water shader you want to use, then hold down the Ctrl key and double click the shader preset. You'll then see a popup menu that asks whether you want to replace or ignore the maps; select "ignore". That will result in the shower water looking more like a shower and less like a solid cone of water. (The trans map is at Runtime\Textures\Maclean\home one\h41showerT.jpg if that helps.)

Top of my wishlist for DAZ Studio: dForce with the following improvements:

1. The ability to pull, drag, re-position cloth during the simulation (as is possible with Marvelous Designer, Blender Cloth Sim and VWD).

2. Faster simulation - it is just painfully slow compared to other cloth sims.

Apart from dForce, a more comprehensive implementation of Filament would be nice so that hair and skin look more realistic. 

oh BTW on the issue I am only having because I am using Filament (and presumably HDR files others are not using) the very same scene the HDR I added shows in iray, if I save the scene using Filament adds the ruins one back even after using purge or clear undo stack, iray still shows the correct one.

cannot find the Filament thread but it is a DAZ studio issue and I am using the beta

so

Filament apparently is limited in how much of a filename it reads for the environment dome

if I use any with the same first word it doesn't replace it

none of Dimension theory's domes with the same prefix as the default ruins will show up as it defaults back to that

or it just has an issue with his strange substances files,they are HDR format

Happy New Year to all Carrara users!

I use other 3D software but frankly I find that Carrara remains very efficient in modeling, texturing and animation !

Of course it is starting to have some lacks compared to the competition but it remains very fun and pleasant to use. Despite the shameful absence of an update from Daz for Carrara 3D, its technical and ergonomic bases make it a software that could still have a future!

Although Daz sovereignly ignores our pleas, I still dream of a Carrara Z (Da ... Z) which would put him back on track for success :-)

What handicaps him horribly are the slowness of the renderings. They are no longer relevant at all. It would be necessary to create a bridge towards Filament or Iray to give it a second wind.

Let's be positive and bet that Daz will come to his senses in 2021 ;-)

Sincerely, Carrara Friends

olivier turbet

www.createo.fr

TheMysteryIsThePoint said:

marble said:

TheMysteryIsThePoint said:

marble said:

Padone said:

@marble As for Diffeo vs Sagan.

Diffeo is primarily designed to import daz assets then animate and render in blender. Then there's support to import daz poses and animations, but this doesn't include dforce simulations. As for geografts and shells they are supported fine, but yes, it requires some manual work to import them. Then diffeo is limited with HD figures, since it supports the HD shape, but not the HD jcms.

Sagan is primarily designed to animate in daz studio then export the animation to blender, and it relies on Diffeo for materials. Sagan correctly bakes both HD figures and dforce simulations, so it is the best choice if you want to animate in daz studio then render in blender with cycles or eevee.

 

Yep, that just about sums up my conclusions perfectly. Either way, there are drawbacks. It is a great pity that Filament is not the DAZ Studio equivalent of Eevee. It is a great pity that the DAZ Studio animation implementation has feet and limbs jerking about instead of staying where they are pinned. Otherwise, I'm getting quite used to working with my old investments in Keymate and Graphmate (I'm not sure that the DAZ versions of those are ready yet). 

I have saved for a new GPU but am waiting for the prices to stabilise and the rumoured RTX 3080ti 20GB to make an appearance. Or, better, a 3070 with 16GB. I can't afford the prices they are demanding right now and I'm not going to pay all that for another 8 or 10GB GPU if there are better options waiting behind the curtain.

@marble Export your zeroed figure as BVH and import it into Blender. Adjust the bone shapes to make eye-balling animation easier, especially the fingers, add IK, and animate it with Blender's tool. Then merge the BVH back onto your figure in DS (don't forget to turn of locks and limits) and export back to Blender with Sagan. Boom.

How clever .. I would not have thought of that. I have never attempted animation in Blender so a bit to learn there but that's a really good option, thanks. I'm not sure what you mean by "adjust the bone shapes" though.

There are options for how Blender displays bones. You can change them so that there is less difference between looking at your armature and looking at the skinned character for when you have close interaction between the character and objects or between characters. BVH, of course, doesn't bring the skin with it. You could, of course, bring in your character's skin as an obj and rig it with default weights, which would give you a decent visual reference, but I find that just looking at the skeleton is usually enough to get an animation looking perfect and the viewport is much more responsive if Blender doesn't have to deform the skin mesh.

Ahh, right. Trouble is that I'm not only animaring bones. I'm trying for some soft-body effects too which involve morphs. For example, I use muscularity morphs quite a lot as well as many of the Zev0 shaping and posing morphs which mostly work on the "fleshy" bits.