Vueiy said:

Richard Haseltine said:

You need a newer version of Daz Studio for dForce Hair (as opposed to dForce cloth used for hair).

I had the newest version (w/ Filament), but rolled it back b/c suddenly all my iray stuff didn't work.  I thought I rolled it back to the update just before Filament, but it's possible I went further back.  By any chance do you (or anyone else for that matter) know which version is most updated before Filament?

If Iray stopped working entirely it could simply be the driver, which could be fixed by updating tio a newer one, although it could also be that your mdoel of nVidia GPU is no longer supported. Either way CPU rendering should still work. I can't recall the exact version that introduced dForce hair, but I think it was 4.12.x.x

Richard Haseltine said:

You need a newer version of Daz Studio for dForce Hair (as opposed to dForce cloth used for hair).

I had the newest version (w/ Filament), but rolled it back b/c suddenly all my iray stuff didn't work.  I thought I rolled it back to the update just before Filament, but it's possible I went further back.  By any chance do you (or anyone else for that matter) know which version is most updated before Filament?

Upon testing further, this issue seems to be similar to what was discussed for other G8F figures here (https://www.daz3d.com/forums/discussion/450151/character-skin-seams), the seams on the figure disappear in IRay render but persist in UE4 and when viewed in Daz via Filament. While I can play around with mip-maps and bump as discussed in the linked forum thread, I'm not sure how I can replicate that on UE4 end. 

onix said:

It is a mystery how you escaped that but it seems to be a pretty common problem. and I have it as well which prevents me from using filament entirely

Hardly a mystery. You seem to be overlooking a very important issue here: the engines don't work side by side at the same time at all. They don't have to.

The moment you start rendering then the main viewport (basically every option within Daz Studio) becomes inaccessible because the program is busy rendering the image, you can't use other options anymore when the rendering process is active. This automatically implies that the viewport process also stops running no matter what engine you've been using (filliament, the commonly used texture shaded renders and even the wire renders) implying that whatever resources it has been using now gets freed in favor for the main render engine. All you're left with at that point is an image shown in the viewport but that doesn't require any resources, just like you don't need a render engine to display the image you generated with rendering.

The engines don't work side by side at the same time at all, they're simply taking turns so to speak.

As for the complexity of my scene... 5 actors ranging from Genesis 1 (2x), Genesis 3 (1x) and Genesis 8 (2x) either using a rather static backdrop as well as within a mansion I recently purchased. I'd say that's decently complex.

ShelLuser said:

onix said:

but Daz totally failed in that task because you cannot use filament and iRay at the same time (maybe it could work if you have 2 GPU cards or an absurd amount of VRAM)

I don't know how you came up with that idea but that doesn't seem right at all. I'm using a GeForce RTX 2060 with 6Gb of video memory and 16Gb of computer memory total and I have absolutely no problem at all with using Filliament as engine in the viewport while also using iRay as the main render engine. 

It is a mystery how you escaped that but it seems to be a pretty common problem. and I have it as well which prevents me from using filament entirely

my suspicion why you did not face it so far is that you are probably rendering very simple scenes with very small VRAM requirements although it is also prety strange how you can fit anything decent into 6GB especially if you use windows 10

onix said:

but Daz totally failed in that task because you cannot use filament and iRay at the same time (maybe it could work if you have 2 GPU cards or an absurd amount of VRAM)

I don't know how you came up with that idea but that doesn't seem right at all. I'm using a GeForce RTX 2060 with 6Gb of video memory and 16Gb of computer memory total and I have absolutely no problem at all with using Filliament as engine in the viewport while also using iRay as the main render engine. 

pity someone cannot compile us some shaders at least

https://google.github.io/filament/Materials.html#compilingmaterials/shadervalidation

As I understand Filament was supposed to be an alternative to OpenGL preview because it is fast and maybe even faster and relatively accurate.

but Daz totally failed in that task because you cannot use filament and iRay at the same time (maybe it could work if you have 2 GPU cards or an absurd amount of VRAM)

 Even attempt to switch between those engines will likely cause a crash so you have to be extra careful to switch into OpenGL first.

I suspect that any other complex rendering engines may have similar problems because they use a Huge amount of VRAM and thus cannot work together with Iray and this is why they are quite useless for preview.

As I read the description of WickedEngine it is not rendering engine at all but rather a game engine(with lots of stuff like a physic simulator), so it is unclear how it would even fit here  and how much tinkering it requires to make things work

In theory, it could be capable of replacing entire DAZ software. 

The filament is not that bad either but Daz implementation lacks a lot of important functions for some unknown reason and this severely limits its use for final renders.

wolf359 said:

Comparisions between render engines is not technically valid unless you compare ALL features.
Render speed  is important
but ultimately meaningless
if the engine lacks the features you need (See Filament).

If you compare the animated filmaking features of cycles or EEVEE
to Iray... it is no contest...none.
Go ahead, invest in a pair of NVIDIA 3090's and render at any frame rate you desire.

You will never acheive a truly cinematic film look without MOTION BLUR, DEPTH OF FEILD/BOKEH
and the VOLUMETRIC LIGHTING EFFECTS that IRay does not offer .

17 seconds per frame @ 24 FPS
1920x1080, Blender EEVEE on CPU

 

 

very impressive Wolf. :)

you right about the limitations of iray. even though you can cheat with fog panes to make volumetric's in iray it not a true volume atmosphere. there is not partical system , Iray does not produce motion blur but you can fake it pretty good in post work its still a work around . Though if you want to render in 3dl in daz you can get volumetrics and motions blur and 3dl is not t bad for animation either but it a lot slower than iray and filament results just does not  look right to me.

we work with what we got i guess.

the viepwort is blank while select filament mode in 4.15 beta. please help.my gpu 1070 and opengl 4.6,CPU Ryder 1700x

Comparisions between render engines is not technically valid unless you compare ALL features.
Render speed  is important
but ultimately meaningless
if the engine lacks the features you need (See Filament).

If you compare the animated filmaking features of cycles or EEVEE
to Iray... it is no contest...none.
Go ahead, invest in a pair of NVIDIA 3090's and render at any frame rate you desire.

You will never acheive a truly cinematic film look without MOTION BLUR, DEPTH OF FEILD/BOKEH
and the VOLUMETRIC LIGHTING EFFECTS that IRay does not offer .

17 seconds per frame @ 24 FPS
1920x1080, Blender EEVEE on CPU

Paintbox said:

stephenschoon said:

Robinson said:

As a dev myself, one of the key considerations would be support.  You don't want to be left in the lurch.  So the older and more established it is the better.  Personally don't know anything about Filament or Wicked Engine but Filament is Google isn't it? 

There's a long list of things Google have started which have quietly disappeared later...

There is a whole loooong list here : https://killedbygoogle.com/

That's a looooong list... I guess you can't monetise everything....

Define "movie"

How long??- Short film or feature length

rendered in Iray? or Filament, or 3Delight?

Any speaking Characters and if so what methods for lipsynch??
32 bit mimic basic( requiring install of 32 bit daz studio)

Anilip2 ? $90+ USD
mimic live? $60 USD( no support for pre recorded audio)
Face mojo? $100+ USD ( Apple luxury brand Iphone 10 X or higher required)
and G8 only

Voice work??
hiring human actors?? 
soliciting volunteers?

Computer based solutions( amazon whatever)

stephenschoon said:

Robinson said:

As a dev myself, one of the key considerations would be support.  You don't want to be left in the lurch.  So the older and more established it is the better.  Personally don't know anything about Filament or Wicked Engine but Filament is Google isn't it? 

There's a long list of things Google have started which have quietly disappeared later...

Yes but there's also a long list of things Google have started and continued on with.  They just start a lot of things.

stephenschoon said:

Robinson said:

As a dev myself, one of the key considerations would be support.  You don't want to be left in the lurch.  So the older and more established it is the better.  Personally don't know anything about Filament or Wicked Engine but Filament is Google isn't it? 

There's a long list of things Google have started which have quietly disappeared later...

There is a whole loooong list here : https://killedbygoogle.com/

Robinson said:

As a dev myself, one of the key considerations would be support.  You don't want to be left in the lurch.  So the older and more established it is the better.  Personally don't know anything about Filament or Wicked Engine but Filament is Google isn't it? 

There's a long list of things Google have started which have quietly disappeared later...

As a dev myself, one of the key considerations would be support.  You don't want to be left in the lurch.  So the older and more established it is the better.  Personally don't know anything about Filament or Wicked Engine but Filament is Google isn't it? 

Per creare uno specchio in 3Delight ti basta aumentare la Reflection Strength e portare in basso Ambient color (verso il nero) e il gioco è fatto.

Per Filament devi aspettare shader specifici, il motore è stato implementato da poco.

Salve a tutti, ho una domanda riguardante Filament . Volevo creare uno specchio.

Usando shader 3Delight o Iray non funzionano.

Invece usando shader PBR  nel riflesso vedo il cielo  con le nuvole e il sole (domus), ma non l'oggetto posto davanti ad esso.

C'é un modo per avere un riflesso reale o bisogna attendere shader specifici per Filament ?

Allego rendering di prova Filament e Iray

FSL Realistic Hair Shaders for Iray and Filament

Didn't see a thread for this so popping one here.

https://www.daz3d.com/fsl-realistic-hair-shaders-for-iray-and-filament

First up - it's awesome and does wonders for old hair (and adds loads of options for new hair too).

Second: By way of a PSA: If applying to older (3DL shader) hairs,DS was hanging for me (waited minutes upon minutes before I quit). Converting to Iray Uber first (mere milliseconds) THEN applying FSL Hair shader (mere split-seconds) works just fine :) Could be just me but figured I'd mention it in case anyone else was having trouble.

Sadly no time for a render just yet, but I wanted to stop by to give it 2 thumbs up :)