I moved my libraries to a network drive also, and had the same issue with it not finding sincludefileedit.  The fix is that you need to map the network drive, and use the mapping in your content library path.  Scripts will not find that data folder from an unmapped network drive.  It probably isn't just Turbo Loader, and there may be some DAZ program functions themselves that don't work right if that isn't fixed.  In particular it also cleared up an issue I was having with Filament where adding an HDRI map turned the scene black and didn't add any lights.

Bottom line is if you use a network drive for a library, it needs to be mapped to a drive letter and you need to set that mapping in the content manager.

Padone said:

From your picture it seems the UHD 770 doesn't have an option for dedicated gpu memory and it only has shared memory. A quick search on google didn't provide any useful information. I never used intel graphics so I can't tell, usually you can change the dedicated memory for apus in the bios.

May be Wendy can help better since she has intel.

not really 

mine just works

it's also a Win7 machine 

the graphics are not great iClone 6 struggles on it for example so I think it might be another factor involved 

the also is a limit as to how much you can have in your scene, big ones have crashed my intel driver as has dforce sims if they explode

Ultrascatter will crash it if too many instances 

Ultrascenery always will crash it as incompatible 

collapsed instances crash filament 

even on my Win10 with the 2080Ti

sometimes strandbased hair vanishes during animations 

test it by moving one back

it could be Filament reads files differently as it certainly takes up to a minute to load a different HDR for me if it's not on my C drive (depending on which of my 5 it's on)

also has to be 2:1 WH ratio

Tried changing the draw settings, no help.  Also tried using perspective view.

If I put one figure in the scene it is completely dark and renders complately dark.  If I add lights the background stays black but I can see the figure.

If I switch over to IRAY the HDRI shows up and lights the scene even with the drawstyle of Filament (PBR). 

The only change I made was to move all the libraries to the network drive for all three machines so they could share the same libraries.  There may be something to do with that but if IRAY can see the HDRI I don't know why Filament can't, particularly when it used to.

If I remove the HDRI and go with DAZ delault "None" map it works correctly, the HDRI lights up the Filament scene.

Something has to have changed, I just can't figure out what, and I almost always use HDRI with Filament, it's loads easier than setting up a bunch of point lights and since I am doing comics with it it makes it really quick to make pictures for them.

Are you using a cam? Sometimes I have to go to the Perspective view when using a cam or lights in the scene filament would be so dark you can't see anything.  

If anybody is using Filament and didn't just run into this problem could you let me know"?  I'm trying to figure out if it is something I did or a bug.  If I switch over to IRAY, the HDRI works.  In Filament it doesn't.  Up until about a week ago it did.

The only HDRI that works is the default one, as soon as a map is loaded the scene goes dark.  Any HDRI, including loading sets bought here.

Padone said:

@Richard I believe you are confused, we're talking about the filament viewport here not iray. The default shadow type is none so you need to change it to something to get shadows.

I was thinking Filament was being used as a semi-preview for Iray rendering.

@Soreata From your specs I see the apu ram is 128 MB that can't possibly work. You need to change it to at least 1 GB, I don't know if you have options in the driver settings or you need to go to bios. My ryzen apu gets 2 GB from the system memory, but I guess intel is more limited.

@Richard I believe you are confused, we're talking about the filament viewport here not iray. The default shadow type is none so you need to change it to something to get shadows.

@Soreata From your specs I see the apu ram is 128 MB that can't possibly work. You need to change it to at least 1 GB, I don't know if you have options in the driver settings or you need to go to bios. My ryzen apu gets 2 GB from the system memory, but I guess intel is more limited.

Richard Haseltine said:

Intel GPUs can be less than super, so this may just be a limitation. But as I said, you should not be using the shadow type options with Filament or Iray anyway - do please report your issues, but then leave the control alone.

I have always needed to

there is the 8 light shadow limitation too 

Richard Haseltine said:

Intel GPUs can be less than super, so this may just be a limitation. But as I said, you should not be using the shadow type options with Filament or Iray anyway - do please report your issues, but then leave the control alone.

Yes, I did so! I need shadows for my renders to make them more realistic, you know... 

I don't know why I'm having this problem.

Intel GPUs can be less than super, so this may just be a limitation. But as I said, you should not be using the shadow type options with Filament or Iray anyway - do please report your issues, but then leave the control alone.

Here are some pics with my specs, guys!

So, all good until I set a shadow type for my spotlight when the viewport is on filament...

What's even stranger, if there is no object in the scene to calculate the shadows, there will be no problem with the light having a shadow type.

Hmm, I have reinstalled the latest UHD graphics driver and restart my computer...

Okay, now daz studio doesn't respond anymore when switching to filament when a spotlight has a deep shadow map or software

So, i have a simple scene 1 figure, 1 spotlight and when i hit the filament its all good... until i select a shadow type for my spotlight...

As I mentioned before, I don't have a gpu. Only the 13700k with the integrated gpu

I can confirm that it is needed to switch between smooth shaded and filament to force filament to update the lights settings. This is a bug.

But I have no crashes here switching the shadow types. Using the ryzen apu. So probably updating drivers will fix it for you.

if using Filament as your renderer try adding and editing stuff especially lights in textured mode then switch back or it won't always update 

this also could be why it crashes

The sahdow type applies only to 3Delight anyway, if you are rendering in Iray (which is when Filament makes most sense) then you should not see the option unless you have Show Hidden Properties enabled. Still, it shouldn't crash so please report this as a possible bug if you are using the current version of Daz Studio via a support ticket.

Hello! I have a problem with the filament render. Daz Studio crashes every time I select a shadow type for my spotlight.

It doesn't crush when I have a directional light with any type of shadow, but when I select deep map shadow or raytraced, on my spotlight, it crushes.

I need help because I don't know what to do. please! Thank you!

My pc has 32gb ram and 13700k cpu. No GPU for the moment, just the intel UHD770 from the cpu.

It happens within the 4.16.03 version as well.

my sole issue with Dforce strandbased hair being PA only is the fact I cannot do out of the box things with it like I do with Carrara.

I rarely even simulate Carrara fur on creatures and DForce cloth hairs IMO are superior to Strandbased hairs anyway, I really only buy SB Dforce hair iif on sale mostly for Filament or if fur for a critter but I prefer rigged fibermesh hair if I can get it, which sadly nobody does anymore.

What I do want to do is use it for interactive grass on terrains any terrain which one cannot do

you can either buy the few flat options or a specific terrain with Dforce curve grass if it's produced

Carrara I can paint my grass where I like on anything 

and yes, I do just use Carrara but it's also a shame not everything I want to use it with will work in Carrara either as DAZ no longer supports it,

The fact is I buy a damned lot of DAZ content but DForce strandbased hair is not finding its way generally into my cart so whatever strategy is behind making it PA only is not working as far as selling it to me, the fact it exists just annoys me because I cannot use the technology how I would like in my renders.

and Oso3D I don't buy your critters for the hair, you could sell them bald and I would still buy them 

I'm having this issue on multiple machines and it just started.  HDRI environments no longer light up the scene, it is totally black, even from saved files.  If I remove the HDRI map and use "none" the scene lights up with the default map.  If I switch over to IRAY the scene lights up.  It will not under Filament.  Is anybody else running into this, and do you know how to fix it?

It doesn't work for any HDRI file, as soon as one is loaded the scene goes black unless you use point lights

WendyLuvsCatz said:

OMG 16K, I live in Australia and that's actually more than my yearly income! (early retirement living on Superannuation)

main thing you need is a good Nvidia graphics card, more VRAM the better otherwise there is always Filament Render

(I have a Ryzen3 BTW which is very entry level, and I do animations, I do have an RTX2080Ti though a gift and 32GB of RAM)

How is daz working especially in viewport, when real-time rendering for posing and stuff with your specs? Could you share your specs please for comparison? Ty!!