Hello all,

I posted the message below to the SDK forum yesterday, but not as many people appear to post and read there. This morning I thought maybe somebody may have a solution using Daz Script and I could replicate that in my plugin code:

https://www.daz3d.com/forums/discussion/466336/calling-the-filament-renderer-in-plugin-code#latest

I understand when in the app to set the viewport draw style to 'Filament (PBR)' and then in the Render Tab to select 'Viewport' and then I can render the active viewport correctly. 

But, in my posted code (see the link above) I am assuming the render manager's getActiveRenderer() method cooresponds to the 'Engine' selection on the Render Tab. If that is not correct, or if you know what options and render choices via script to kick off a Filament render I can port it over to my plugin code.

thanks in advance!

Sending you all the positive karma vibes possible.  Encouraging that you are feeling better.  
I pretty much skipped Genesis 3 / Victoria 7 when they came out.  By the time genesis 8 / v8 came out, I had finally gotten around to experimenting with Misty's presets.  I bought a lot of genesis 8 stuff, and the sales resulted in my getting a big genesis 3 library thrown in when buying genesis 8 bundles.  Similarly, I didn't buy much genesis stuff when it first came out but then ended up with a bunch when I dove in genesis 2.

I think I have only tried 2 or 3 filament renders.  I love the control over lights, etc that we get with Carrara.

well I am using Filament a lot but still doesn't justify me buying into something that won't work in my other preferred softwares.

I pretty much held off genesis 8 until Misty made her preset then bought heaps.

is OK I really need to save and my future a tad dodgy at the moment anyway 

if I turn out to have leukaemia after all the upcoming tests I really am not going to give a lot of funks

(a possibility only at this point so not panicking yet but uneasy all the same)

I actually feel quite healthy BTW, better than I have in years but my bloodwork says differently 

they Xrayed all my bones yesterday 

Unsurprising, as you say.  I am curious how the move toward animation and the Filament renderer is going to coexist with IRay renders for stills.  

Discovering Daz Studio

     an article by Dartanbeck

I've been using (and loving it) Daz Studio for years - but only as an assistant, a plugin of sorts to Carrara and my endeavors there.

As of the release of Daz Studio 4.14 and all that the development team has been pouring into it, I felt that I owed it to them to give it a whirl.

With all of the talk (earlier in this thread) of "Filament" and "New Animation Features", I also owed it to myself to try it out!

My experience has been up and down - of course. That goes with any attempt to try software that's entirely different than what we're used to. On these forums, I've expressed my downs and my downs, and then some more of my downs. I think this is common too, because we know there are answers out there and we're frustrated. So we hope to find answers that will propel us forward once again.

That said, I decided to write something more honest about my overall experience with the software. The full article may be incomplete now, but the words there express a true account of my earliest experience with this amazing software. More to follow.

Discovering Daz Studio - Read the Article

I appreciate any feedback. I haven't even proof read it at the time of this posting, so any and all thoughts are totally welcome! ;)

Hello everyone,

I'm hoping someone has started playing with the Filament renderer from a plugin, or just know the ins and outs of the rendering classes and might spot the obvious for me...

I have a plugin which starts a render with this code:

    DzRenderer* myRenderer = myRenderMgr->getActiveRenderer();
    DzProgress renderProgressPopup("Rendering with " + myRenderer->getName() + " Renderer...");
    bool success = myRenderer->render(myHandler, myCamera, dzApp->getRenderMgr()->getRenderOptions());

The attached picture shows my Rendering Tab, where the Engine selected is '3Delight'. When my plugin runs it correctly says myRenderer's name is 3Delight and the image my plugin outputs in a 3Delight image.

But when I select the Engine as 'Viewport' in order to get it to render with Filament, it gives the name back as 'NVidia Iray' and renders in Iray.

Is the Engine choice in this drop down not what you are selecting with 'getActiveRenderer()'? Or, if yes, is there something else I need to set in order to get Filament to be selected? Also, all my Main Window viewports have 'Filament (PBR)' selected as the user draw style.

thanks in advance for any insight/guidance/help!

it's the same as animated textures, DAZ obviously has the functionality to do it but it needs scripts free and paid to actually do it, likewise vertex deformation, particles, landscape and tree generation, volumetrics, my preferred program Carrara does all that.

DAZ studio, while free, developers have to add basic features available in paid softwares (or difficult to use ones like Blender) and we pay for their work in doing so.

I manually add all my lights for Filament too but there is a script in store for that.

I have little money but am very very time rich so yes each to their own.

Frinkky said:

I'm getting the same issue as 4.14 - opening the program brings up the splash screen, the main program window appears and within a couple of seconds it freezes - no element responds to mouseover or click. hen he program just closes. The last few lines in the log file are:

2021-01-09 13:46:30.153 Creating Script Engine...
2021-01-09 13:46:30.169 WARNING: 3DConnexion Plug-in Error: Could not create Device, CoCreateInstance failed
2021-01-09 13:46:30.169 3D mouse support library could not be loaded.
2021-01-09 13:46:30.170 Creating Main Window...
2021-01-09 13:46:30.171 Creating Viewport Manager...
2021-01-09 13:46:30.213 Successfully created OpenGL viewport for Viewport1.
2021-01-09 13:46:30.303 Successfully created OpenGL viewport for Viewport2.
2021-01-09 13:46:30.362 Successfully created OpenGL viewport for Viewport3.
2021-01-09 13:46:30.419 Successfully created OpenGL viewport for Viewport4.
2021-01-09 13:46:30.526 Creating Action Manager...
2021-01-09 13:46:30.537 Creating Pane Manager...
2021-01-09 13:46:30.706 Successfully created OpenGL viewport for AuxViewportView.
2021-01-09 13:46:31.362 WARNING: QFile::flush: No file engine. Is IODevice open?
2021-01-09 13:46:31.473 WARNING: QMetaObject::connectSlotsByName: No matching signal for on_pslJpegSaveQuality_valueChanged(int)
2021-01-09 13:46:31.478 WARNING: QMetaObject::connectSlotsByName: No matching signal for on_sldAniImageQuality_valueChanged(int)
2021-01-09 13:46:31.484 WARNING: QMetaObject::connectSlotsByName: No matching signal for on_bbnRestartDriver_released()
2021-01-09 13:46:31.564 WARNING: QMetaObject::connectSlotsByName: No matching signal for on_ptbEditNodeGraph_released()
2021-01-09 13:46:33.841 Started in: C:/Program Files/DAZ 3D/DAZStudio4 Public Build
2021-01-09 13:46:33.841 DAZ Studio Started
2021-01-09 13:46:33.842 Creating Pixel Buffer
2021-01-09 13:46:33.867 Pixel buffer - Width: 1024 Height: 1024
2021-01-09 13:46:33.868 Compiling OpenGL Shader...

 

So it seems to be an opengl issue...

I'm running this on a 4790K cpu (iGPU disabled), 32gb ram and a 1070ti. 

Any ideas would be appreciated. As stated above, I've been having this problem since 4.14 beta so presumably Filament related? I won't try a 4.14 or 4.15 main release as that would overwrite my only working version (4.12).

It does work on my laptop, 8750H 16gb + 1070 8gb.

I noticed in Event Viewer that the issue appeared to be with ntdll.dll. I updated Windows 10 to 1909, hoping that would resolve the issue, but alas no:

Faulting application name: DAZStudio.exe, version: 4.15.0.2

Faulting module name: ntdll.dll, version: 10.0.18362.1316

If you want to be compatible with any existing shader (3Delight, Iray Uber, any shader mixer shader, any existing mapped shader etc, etc), then you have to limit to 90, 180, 270. It comes from the fact that new images are obtained using LIE rotations above original images (which are made transparent for layer 0), and that LIE rotations are limited to these angles. (Then images are saved as images and replace the LIE)

I've been developping for a while another product (for now called "Xtreme Reshade for Iray Uber"), which will be limited to Iray Uber and Iray Renders, BUT where you will have TONS of possibilities (not only unlimited rotations, but much more potential than you can imagine!). The drawbacks being that you cannot preview result in viewport (forced to be in render or NVIDIA IRay preview), and that of course (well I did not test but this is very likely) it will not be compatible with Filament.  This should come this year. This will be shader specific and render engine specific.

On the contrary, this Shader Rotator is limited to multiples of 90 degrees rotations but completely compatible with any render engine and any (mapped) shader!

Are the transparency issues in Filament resolved in 4.15? Before it acted similar to how OpenGL treated opacity.

Totte said:

wsterdan said:

While I can wait patiently for DAZ to update Studio to run on mX chips and under Big Sur, I would prefer that they get Filament working sooner rather than later, myself. Knowing that I needed to do rendering while physically moving myself away from my work computer I grabbed a MacBook Air and since DAZ wouldn't work under an m1 chip and Big Sur for months, I purchased a 2020-March model instead. It works fine for the type of Toon animation I'm working on, but having installed a Windows 10 VM Fusion partition to test Filament, I found a 1080p animation that took 4 hours to render in 3Delight took 11 minutes using Filamant.

I'd like to be able to work with Filament on my iMac. I don't mind running tests on the Window partition, but I don't want to do the set up and the conversions-to-filament there.

I'd be willing to pay for a Mac-bases rendering feature or plug-in for Mac, and as it's open source and designed for mobile (including iOS) I think we might see m1 support from Filemant before any other rendering engine options.

-- Walt Sterdan

Back to square one, Filament on macOS require Qt 5 and depend on other things that require Qt 5 on macOS, so you need to wait for that too. 

Ah, thanks for the info! I didn't realize that Filament itself required QT 5 on the Mac regardless of DAZ Studio. I appreciate your response.

-- Walt Sterdan 

My older Win7 without a graphics card, but I be a Filament rendering in my bed!

your setup looks very comfy too 

and faster than mine even on the Win10 in my lounge, hence the need for sleep

wsterdan said:

While I can wait patiently for DAZ to update Studio to run on mX chips and under Big Sur, I would prefer that they get Filament working sooner rather than later, myself. Knowing that I needed to do rendering while physically moving myself away from my work computer I grabbed a MacBook Air and since DAZ wouldn't work under an m1 chip and Big Sur for months, I purchased a 2020-March model instead. It works fine for the type of Toon animation I'm working on, but having installed a Windows 10 VM Fusion partition to test Filament, I found a 1080p animation that took 4 hours to render in 3Delight took 11 minutes using Filamant.

I'd like to be able to work with Filament on my iMac. I don't mind running tests on the Window partition, but I don't want to do the set up and the conversions-to-filament there.

I'd be willing to pay for a Mac-bases rendering feature or plug-in for Mac, and as it's open source and designed for mobile (including iOS) I think we might see m1 support from Filemant before any other rendering engine options.

-- Walt Sterdan

Back to square one, Filament on macOS require Qt 5 and depend on other things that require Qt 5 on macOS, so you need to wait for that too. 

While I can wait patiently for DAZ to update Studio to run on mX chips and under Big Sur, I would prefer that they get Filament working sooner rather than later, myself. Knowing that I needed to do rendering while physically moving myself away from my work computer I grabbed a MacBook Air and since DAZ wouldn't work under an m1 chip and Big Sur for months, I purchased a 2020-March model instead. It works fine for the type of Toon animation I'm working on, but having installed a Windows 10 VM Fusion partition to test Filament, I found a 1080p animation that took 4 hours to render in 3Delight took 11 minutes using Filamant.

I'd like to be able to work with Filament on my iMac. I don't mind running tests on the Window partition, but I don't want to do the set up and the conversions-to-filament there.

I'd be willing to pay for a Mac-bases rendering feature or plug-in for Mac, and as it's open source and designed for mobile (including iOS) I think we might see m1 support from Filemant before any other rendering engine options.

-- Walt Sterdan

Mark_e593e0a5 said:

Miss Bad Wolf said:

WendyLuvsCatz said:

Miss Bad Wolf said:

What is filament?

since Google not giving you an answer (or forum search though I understand that one)

https://www.daz3d.com/filament-information-page 

https://www.merriam-webster.com/dictionary/filament I did a web search but was not getting the answers I wanted.

Interesting, as Filament is actually a Google project: https://google.github.io/filament/

 

I was using bing not google for some reason. 

Miss Bad Wolf said:

WendyLuvsCatz said:

Miss Bad Wolf said:

What is filament?

since Google not giving you an answer (or forum search though I understand that one)

https://www.daz3d.com/filament-information-page 

https://www.merriam-webster.com/dictionary/filament I did a web search but was not getting the answers I wanted.

Interesting, as Filament is actually a Google project: https://google.github.io/filament/

WendyLuvsCatz said:

Miss Bad Wolf said:

What is filament?

since Google not giving you an answer (or forum search though I understand that one)

https://www.daz3d.com/filament-information-page 

https://www.merriam-webster.com/dictionary/filament I did a web search but was not getting the answers I wanted.

Miss Bad Wolf said:

What is filament?

since Google not giving you an answer (or forum search though I understand that one)

https://www.daz3d.com/filament-information-page 

What is filament?

FntsyArt said:

Another set of examples. This time camera #1 from Triple Moon Cottage. I was very careful to keep light levels the same between the two examples here. As before I set lighting levels in Filament Draw instead of in the tool. First is a straight RSSY conversion.

The second is a RSSY conversion, but with the base shader turned off.

There are still some problems in the 2nd image, but I think it is evident it is far superior to the first. The problems that remain (such as overly reflective stone work, and lack of color in the potions are Filament problems, not problems with the convertor.

They look beautiful!  Thank you for sharing your images.