Mark_e593e0a5 said:

PerttiA said:

aaráribel caađo said:

PerttiA said:

One part of the problem is that supporting BigSur will break the old plug-ins for both platforms (Win+Mac), some for which the developer that is supposed to "push the button" is not amongst the living anymore, will cease to function for good.

Is any of that core functionality? It would be weird if Daz didn't have the code for anything part of the core functionality, except where they licensed it from an entity that woudn't depend on the health of a single person (like 3delight and Iray). On the other hand, Daz is a fairly small business, and small businesses don't always have the budgets for "optimal" solutions. 

As the BigSur support breaks the old plug-ins for ALL users, for some that consider those plug-ins essential, they may as well be considered core functions.

Yes, plugins are an issue. That's why I have not yet upgraded my main Mac to DAZ 4.14. I am currently testing if the plugins I use still function, using a stripped down DAZ Studio on a virtual machine. Since Filament is not yet supported on Macs anyway, staying with 4.12 is not a big issue, I suppose.

Its a sad thing that some developers are no longer with us. But I am a bit shocked that DAZ does not have access to the sources. My company usually has to deposit source code we develop for our customer projects. Since it contains our intellectual property, we deposit that code with an escrow agent. 

The plug ins don't belong to Daz, so they could not claim any right to them - and trying to maintain another person's code, on top of their own, would probably not be a practical option..

PerttiA said:

aaráribel caađo said:

PerttiA said:

One part of the problem is that supporting BigSur will break the old plug-ins for both platforms (Win+Mac), some for which the developer that is supposed to "push the button" is not amongst the living anymore, will cease to function for good.

Is any of that core functionality? It would be weird if Daz didn't have the code for anything part of the core functionality, except where they licensed it from an entity that woudn't depend on the health of a single person (like 3delight and Iray). On the other hand, Daz is a fairly small business, and small businesses don't always have the budgets for "optimal" solutions. 

As the BigSur support breaks the old plug-ins for ALL users, for some that consider those plug-ins essential, they may as well be considered core functions.

Yes, plugins are an issue. That's why I have not yet upgraded my main Mac to DAZ 4.14. I am currently testing if the plugins I use still function, using a stripped down DAZ Studio on a virtual machine. Since Filament is not yet supported on Macs anyway, staying with 4.12 is not a big issue, I suppose.

Its a sad thing that some developers are no longer with us. But I am a bit shocked that DAZ does not have access to the sources. My company usually has to deposit source code we develop for our customer projects. Since it contains our intellectual property, we deposit that code with an escrow agent. 

I think it was Sickleyield who provided some products for precisely that purpose.

Filament renders look a bit too flat and unconvincing for my uses.

Do opacity maps not work in Filament? I have a custom map (which works in Iray) applied to my character's face and her entire face renders at 50% opacity. 

Mapper said:

Experiencing the "Shut down Bug" Moves from active App to Back ground and has to be killed in the Task Manager manually... Yes I've waited, infact went downtown grabbed some grub, got back and it was still in the task manager... Yes I'm lazy I want a one clk kill...LOL

As to filiment trying to figure out the Glowing white textures almost like mega glossy Looks great in Iray...

I had the same issue.  I had to reinstall Daz from the Daz Central program, and it solved that problem.  However, I now can't get the dang tonemapper. environment, or filament draw nodes to work. 

I followed the instructions on how to use the new filament render engine in a tutorial (that I can no longer find) and it worked great.  However after I installed a couple of new figures, the environment node completely stopped working.  I can get a half way decent flat render, but NO SHADOWS now, and neither the environment node, the tonemapping node, nor the filament draw node make any difference at all.  I can move the sliders all day long and NOTHING happens.  STILL NO SHADOWS. 

Dazzleme said:

Just installed a 3090 today..working with Daz 4.12 (dont want to go to filament yet) and I can confirm that even with the latest Nvidia studio drivers (or game ready)  456.71 daz will render NOTHING in Iray preview or Render mode..I have tested my gpu ad nauseum today for hours, the card is working fine and all systems check out well, its definitely Daz..two days ago I could render splendidly with my 1080TI, quite quickly even but wanted the new card for gaming and especially to use the higher Vram to render more complex scenes in daz..as even the 11 vram is a limiting cap with the 1080ti, so..nothing to do but wait until Daz figures this out, anyone else had ANY Luck with the 3080/3090 series cards? Im not trying to whine, Im grateful to have the card as I built a new system in November and just today got my hands on the new card.

Please try to render something simple e.g. a figure and attach the log.

Just installed a 3090 today..working with Daz 4.12 (dont want to go to filament yet) and I can confirm that even with the latest Nvidia studio drivers (or game ready)  456.71 daz will render NOTHING in Iray preview or Render mode..I have tested my gpu ad nauseum today for hours, the card is working fine and all systems check out well, its definitely Daz..two days ago I could render splendidly with my 1080TI, quite quickly even but wanted the new card for gaming and especially to use the higher Vram to render more complex scenes in daz..as even the 11 vram is a limiting cap with the 1080ti, so..nothing to do but wait until Daz figures this out, anyone else had ANY Luck with the 3080/3090 series cards? Im not trying to whine, Im grateful to have the card as I built a new system in November and just today got my hands on the new card.

Quote

Just installed a 3090 today..working with Daz 4.12 (dont want to go to filament yet) and I can confirm that even with the latest Nvidia studio drivers (or game ready)  456.71 daz will render NOTHING in Iray preview or Render mode..I have tested my gpu ad nauseum today for hours, the card is working fine and all systems check out well, its definitely Daz..two days ago I could render splendidly with my 1080TI, quite quickly even but wanted the new card for gaming and especially to use the higher Vram to render more complex scenes in daz..as even the 11 vram is a limiting cap with the 1080ti, so..nothing to do but wait until Daz figures this out, anyone else had ANY Luck with the 3080/3090 series cards? Im not trying to whine, Im grateful to have the card as I built a new system in November and just today got my hands on the new card.

I just installed my 3090 today..Asus Tuf 3090 OC....and found..with 4.12 I cant render in iray at all..spend half a day benchmarking and testing my new GPU, I can confirm the issue is NOT My GPU..it appears to not work with 4.12 still, and I really dont want to impliment 4.14 filament yet...so..any thoughts? Can someone really confirm that it DOES work with 4.14, as opposed to it "seems to be working?" Thanks...I love the gpu..its very very fast...and in gaming looks great..Daz is a hobby..and I can wait for the support...but hope it comes sooner than later with 30 series now on the way to becoming mainstream.

P.S.  I cant do render previews either

for iRay: Normal maps

for Filament: Bump maps

to avoid: getting both sliders at 1.0 or 100%

eliminate: Displacement maps (if any)

Not gonna lie; I've come to really like Filament for the most part. The ability to effectively use a lot of Iray textures and so on without that horrific Iray rendering time is a blessing, believe me.

That being said, I have to feel that there have to be ways of working around it's biggest limitations; namely, the lack of emissive lighting and casting shadows. Maybe it's just me, but I feel like that there has to be some kind of way around those limitations. And I hope that someone comes up with something.

I think Filament has potential to become a monster engine....the negative comments are understandable, but they don't help the developers to push it to new heights. The thing I've liked so far apart from the render speed, is the ability to use iray PBS shaders by first converting them to 3delight.  With lighting, most Iray lights -None HDRI will work and a few. I mean a few 3delight works. The thing I would request the developers to work on are shadows..a plane that catches shadows when using HDRis. I tried using IBL master control- ground panel, but no luck. 

Thanks for this great engine!!

Very nice scene , and as you said surface need to be adjusted not only for Filament , but looks very nice ! 

magaremoto said:

quick comparison between the 3 engines; filament is very quickly (around 5 secs) but many shaders need to be adjusted as pointed out by Mec4d

So, has the Iray (Not using GPU) issue been around this whole while - in previous versions?

I seemed to be able to reduce the fireflies in the hair when rendering in a full surrounding scene, but then Iray kicks my GPU out of the equation - my little render is still running from last night. 

I guess I'll have to either render a solo character to alpha, or just not use Studio? I don't like these options. It was just starting to get fun - finally.

I love Iray! Filament just doesn't do it for me. The whole transparency thing... yeah... no.

The timeline seems much better than it was before, but I never really knew that I had to change the View mode? So weird. But now that I'm set to Advanced View, it loads that way - unless that's just because I loaded a saved scene.

As for the crazy translate/scale/rotate tool widgets being so drastically horrifying to use, I'm learning that many users I see doing tutorials are actually doing it the way I used to do it in Poser - using sliders instead of direct manipulation. That works for me, albeit kinda strange for such an advanced software.

Truly - Daz Studio is some Sweet Machinery!!!

Kudos to the devs making this thing what it's been becoming. It takes a lot of genius work to get something this powerful in so many ways!

Back to the Iray issue, My Ryzen 7 is no slouch when it comes to rendering some pretty intense, heavy scenes in Carrara. Even with Rosie 5 with four separate layers of dynamic hair (shader-based - heavy on render resources), simulated clothing, reflection, refraction, SSS and transparency, along with volumetrics and lots of geometry (Urban Sprawl plus a whole lot of extra products added throughout to make it Cyberpunk, vehicles in motion with volumetric lighting, etc., etc.,) I'm still coming in at less thn five minutes per frame.

With Iray kicking my GTX out of the equation, renders slowed to a massive crawl with nothing more than a character with dForce hair, simple clothing and a very lightweight (but really cool!) scene. 

I'm certainly not opposed to rendering the character alone to Alpha, and then the scene separately, but I'd still have to render the scene in Carrara, wouldn't I? Most scenes are heavier than what I'm experiencing in this issue: Character and light scene combined. I mean... is it always like this? If so, maybe I should consider quartering the textures of all environments? Damn, that's a lot of dicking around.

Thoughts?

Paintbox said:

ALLIEKATBLUE said:

Could someone explain the steps in doing a render in filament

1) Go to the right hand corner of your viewport in 4.14 and choose the icon next to the camera selection, and from the drop down choose filament PBR

2) Profit

Step 3: If you want it to render outside the viewport so you can make it bigger or save it or whatever: Under Render Settings there is a dropdown named 'Engine'.  Select 'Viewport'.  Now when you do a render it will render to whatever you selected in step 1 above, in this cas filament. Now when you push the render button you get a filament render.

ALLIEKATBLUE said:

Could someone explain the steps in doing a render in filament

1) Go to the right hand corner of your viewport in 4.14 and choose the icon next to the camera selection, and from the drop down choose filament PBR

2) Profit

Oh yeah, it's iray, don't mess with the filament lol.

Sevrin said:

nonesuch00 said:

onix said:

Looks like this filament introduced a lot of new crashes into Daz.

  Most of them happen when you try o switch rendering engines, and typically attempt to use iray and filament at the same time will  need badly so if you are trying to do final rendering or want to use iRay viewport preview you can have a filament running or open at the same time 

although it is quite strange that filament manages to run faster than opengl for some reason

The advanced openGL is slower to render on my PC than an iRay render.

I am getting my Filament crashes just switching from whatever viewstyle in the ViewPort to Filament. It also doesn't matter what I have the actual renderer set to either: 'Viewport', iRay. 3DL, switching to Filament in the Viewport crashes DAZ Studio PB 4.14.1.22

This isn't universal.  I've no issues switching to the Filament draw-style in the latest public build, at least with the simple scenes I've tried it with.  My DS is pretty vanilla, though.  No Octane, or anything.

That's the whole idea. there are no problems with simple scenes 

Fine... So this is live in store! Hurray!!!

As a reminder, the main difference with version 1.1 is that 1.2 handles filament Viewport in the viewport drawstyle options, and accepts the fact that sometimes (if you never launched IRay in your scene for example) you have no environment or no tone mapper.