Which version of DS are you using? DS 4.x doesn't have filament on Mac, only the DS2025 alpha does.

Hi All,

I'm running on an iMac Pro Intel machine. Does the 'Filament' feature work with the intel Macs? I don't have it as an option in my viewport and can't find where I might turn it on in the menus.

Thx.

neilroy1965 said:

I would recommend that people do NOT use the STUDIO drivers!  The Game Ready drivers are more up to date and have fixed issues which cause Windows to crash, where as, for some strange reason, the Studio drivers have not been updated.

Otherwise, it would be nice if there was a way I would submit my bug reports, my crash reports generated by Daz, otherwise, what in [Heaven's name] is the sense of testing an alpha?!

Studio driivers should be more robust in genreal, the game ready drivers get updated more often because new games need support but as a result they are generally less well tested and more prone to stability issues - but the key phrase is "in general".

Your crash appears to be in Filament

vangelrise said:

Mi preoccupa anche la potenza necessaria del pc e/o RAM + scheda video. 

Basta impostare tutto per raggiungere il giusto compromesso. Io renderizzo con 3Delight e in genere ogni fotogramma prende al massimo un minuto (in scenari parecchio affollati, con parecchi effetti di trasparenza, luci e ombre, minimo due chilomtri quadrati di scenario full 3D, mai billboard) e quando sono costretto ad usare IRay in genere impiego lo stesso tempo con delle impostazioni ben calibrate e stesse scene complesse.

Facevo tutto questo già anni fa con un Ryzen 7 1700x e una GTX 745 OEM HP. Ora che ho un Ryzen 9 5900x e una RTX 3060 TI è tutto ancora più fluido.

Non è necessario chissà quale hardware se non ti fermi alle impstazioni di default (strapesantissime) e cerchi le giuste regolazioni.

Per assurdo, impostando IRay per essere più veloce nei render scompaiono quasi del tutto i fireflies e la "granulità". Resta comunque un motore poco affidabile, basta spostarsi un pò dal centro e non funziona più nulla.

Altrimenti c'è sempre Filament, stanno venendo fuori un sacco di prodotti per creare di tutto. In tre secondi renderizza qualsiasi scena con una GPU dei punti del supermercato.

Richard Haseltine said:

nonesuch00 said:

Richard Haseltine said:

nonesuch00 said:

Richard Haseltine said:

nonesuch00 said:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)

I am getting a crach on the latest Alpha. 

AMD Ryzen 7 5700G

96GB RAM

PNY GeForce 4070 12GB

2 TB m.2 nvme PCIe Gen 3 System Disk.

2TB external USB m.2 nvme Gen3 DAZ Content Library Disk

Thanks.

What were you doing at that point? Can you get it to happen consistently?

It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.

How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in 

%appdata%/daz 3d/Studio6 Public Build/

will have the information.

I didn't alter the defaults in the Alpha 6 or the layout file.

I have two paths, with only one file each for Studio6:

a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat

b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat

They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.

%appdata% is C:/users/you/appdata/roaming/, not Program Data - if you paste the path I gave above into a file browser address bar it will take you to the right folder, but the %appdata% is not a folder name in itself.

 

I'm not sure what was going on before but I bought some Outlet Store products today and so needed to install them, once I went to the Install tab in DIM the DAZ Studio Alpha 6 Jun 25 and plugins were on still in the Install Tab listed so I went again and installed them (again, I think) and now it works. So I'm not even sure what was crashing because if it was the prior Alpha version, then that had been already working prior to all the crashing I reported here. Anyway, it works. Sorry for the inconvenience.

nonesuch00 said:

Richard Haseltine said:

nonesuch00 said:

Richard Haseltine said:

nonesuch00 said:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)

I am getting a crach on the latest Alpha. 

AMD Ryzen 7 5700G

96GB RAM

PNY GeForce 4070 12GB

2 TB m.2 nvme PCIe Gen 3 System Disk.

2TB external USB m.2 nvme Gen3 DAZ Content Library Disk

Thanks.

What were you doing at that point? Can you get it to happen consistently?

It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.

How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in 

%appdata%/daz 3d/Studio6 Public Build/

will have the information.

I didn't alter the defaults in the Alpha 6 or the layout file.

I have two paths, with only one file each for Studio6:

a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat

b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat

They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.

%appdata% is C:/users/you/appdata/roaming/, not Program Data - if you paste the path I gave above into a file browser address bar it will take you to the right folder, but the %appdata% is not a folder name in itself.

3deedlin said:

WendyLuvsCatz said:

it is very basic as a video editor but totally free and has the ability to render 8K videos or more among other things other free editors don't do.

I use that frequently for 360 panoramic videos 

many swear by Blender for rendering in Eevee but it's not intuitive for me at all

even getting it to use my card and render in it a challenge 

it will readily enough in preview but setting an image series going it keeps defaulting to Blender Render which on a Ryzen3 is useless 

I think it's because I use both my 2080Ti AND onboard Vega graphics for my monitors 

and since the latter is my main monitor it defaults to it

many of my other softwares use both which is awesome 

and that actually includes DAZ studio for Dforce and Filament 

(obviously not iray as Nvidia only)

I am sure this is obvious, but did you enable it to use both or GPU in preferences?

yes but it seems to do it's own thing

I believe it is monitor related though and not the only program that will do that

iClone 6 uses the graphics of whichever monitor it's on too

my unusual setup causes issues sometimes but I cannot plug a second monitor into my 2080Ti display ports as it just won't work, fault with the card which was given to me I think because my 980Ti could run 4 monitors and I never had these issues  

I had to enable the iGPU in the BIOs and it's not something that's recommended 

some Ai programs won't work because of it too as don't see a CUDA engine

it took me 3 different builds of Automatic 1111 to find one that saw my card (and happily works on either monitor) yet weirdly the Forge version works fine too

when it does work it works well as I have the extra non CUDA graphics for other tasks

I also can totally crash my GPU and still have a working monitor to save my work which has proven a lifesaver at times

DAZ studio likes it, I get more rendering power without the monitor poaching some,

WendyLuvsCatz said:

it is very basic as a video editor but totally free and has the ability to render 8K videos or more among other things other free editors don't do.

I use that frequently for 360 panoramic videos 

many swear by Blender for rendering in Eevee but it's not intuitive for me at all

even getting it to use my card and render in it a challenge 

it will readily enough in preview but setting an image series going it keeps defaulting to Blender Render which on a Ryzen3 is useless 

I think it's because I use both my 2080Ti AND onboard Vega graphics for my monitors 

and since the latter is my main monitor it defaults to it

many of my other softwares use both which is awesome 

and that actually includes DAZ studio for Dforce and Filament 

(obviously not iray as Nvidia only)

I am sure this is obvious, but did you enable it to use both or GPU in preferences?

Richard Haseltine said:

nonesuch00 said:

Richard Haseltine said:

nonesuch00 said:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)

I am getting a crach on the latest Alpha. 

AMD Ryzen 7 5700G

96GB RAM

PNY GeForce 4070 12GB

2 TB m.2 nvme PCIe Gen 3 System Disk.

2TB external USB m.2 nvme Gen3 DAZ Content Library Disk

Thanks.

What were you doing at that point? Can you get it to happen consistently?

It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.

How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in 

%appdata%/daz 3d/Studio6 Public Build/

will have the information.

I didn't alter the defaults in the Alpha 6 or the layout file.

I have two paths, with only one file each for Studio6:

a) C:\ProgramData\DAZ 3D\Studio6\dazstudio.dat

b) C:\ProgramData\DAZ 3D\Studio6 Public Build\dazstudio.dat

They are in binary and I don't have a hex editor installed, but those are the only two files in those directories.

it is very basic as a video editor but totally free and has the ability to render 8K videos or more among other things other free editors don't do.

I use that frequently for 360 panoramic videos 

many swear by Blender for rendering in Eevee but it's not intuitive for me at all

even getting it to use my card and render in it a challenge 

it will readily enough in preview but setting an image series going it keeps defaulting to Blender Render which on a Ryzen3 is useless 

I think it's because I use both my 2080Ti AND onboard Vega graphics for my monitors 

and since the latter is my main monitor it defaults to it

many of my other softwares use both which is awesome 

and that actually includes DAZ studio for Dforce and Filament 

(obviously not iray as Nvidia only)

nonesuch00 said:

Richard Haseltine said:

nonesuch00 said:

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio6 Public Build\dzcore.dll" at 0033:000000009EC98223, DzStyledTimeAsFramesPropertyWgt::~DzStyledTimeAsFramesPropertyWgt()+19139293 byte(s)

I am getting a crach on the latest Alpha. 

AMD Ryzen 7 5700G

96GB RAM

PNY GeForce 4070 12GB

2 TB m.2 nvme PCIe Gen 3 System Disk.

2TB external USB m.2 nvme Gen3 DAZ Content Library Disk

Thanks.

What were you doing at that point? Can you get it to happen consistently?

It's happens right after the splash screen goes away, before I ever do anything at all. DAZ Studio never gets the editor on screen. It happens every time.

How many Viewports are open, and what Drawstyles are they using? Was Filament being ussed? The saved layout.dsx file, in 

%appdata%/daz 3d/Studio6 Public Build/

will have the information.

memcneil70 said:

As a user without programmer knowledge, but with both 4.24.0.3 Beta and 6.25.17807 Alpha currently installed on my MacMini M4 and my Windows 11 computers I am assured that my scripts on the Beta are not messed with by the Alpha. I am the one who decides which product/script/plugin to attempt to use on the Alpha, not the programs. So far I have only tested three of Code66's scripts just to see if the Alpha will keep them in my Favorites from one update to another. If I need my scripts/plugins, I use my Beta then open the file in the Alpha if necessary. For the Mac it is the ability to use Filament that is the big plus. By contributing to the Alpha thread what you observe will only help improve it. I would help the PAs in testing but I am probably the last person they would want because I stumble around many scripts. But I will support their work fully no matter what form it arrives in. They provide a service I can not do myself.

So far it's the best idea. As Totte said, some scripts are longer to update than others. I just finished the update of three products, which will be linked to a product to come (some features will appear as a linked bonus in the updated products). Some of the scripts took me one hour or a few hours (time to move variables where they should go and to make cross compatible connects). The genitalia transfer script I use in many products took me one week (still not able to have the DoDuplicate working, I had to totally get rid off it) So far I planned to update everything, but if I find a script which sales at 4 copies per year and I see that it should take me one week or more to update, I might give up. But so far, except the script using the duplicates, it's just a "big update" work.. And I keep my fingers crossed..

As a user without programmer knowledge, but with both 4.24.0.3 Beta and 6.25.17807 Alpha currently installed on my MacMini M4 and my Windows 11 computers I am assured that my scripts on the Beta are not messed with by the Alpha. I am the one who decides which product/script/plugin to attempt to use on the Alpha, not the programs. So far I have only tested three of Code66's scripts just to see if the Alpha will keep them in my Favorites from one update to another. If I need my scripts/plugins, I use my Beta then open the file in the Alpha if necessary. For the Mac it is the ability to use Filament that is the big plus. By contributing to the Alpha thread what you observe will only help improve it. I would help the PAs in testing but I am probably the last person they would want because I stumble around many scripts. But I will support their work fully no matter what form it arrives in. They provide a service I can not do myself.

WendyLuvsCatz said:

Some helpful links

OK, thanks.  That first link has a link to a YouTube video that explains the settings changes needed for Filament.  In the comments, some folks are reluctant to switch from Iray.  But options are always good.  

Some helpful links

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

https://www.daz3d.com/forums/discussion/704931/filatoon-cell-shaded-rendering-with-filament

 

https://www.daz3d.com/forums/discussion/452621/filament-bring-out-the-renders

WendyLuvsCatz said:

well it's a lot easier than it used to be, that's for sure

I too am using DAZ studio a lot now there is iray and Filament precisely because the newer content is made to work in it

back in the Poser days Carrara was the obvious choice, 3Delight was abysmally slow and openGL looked awful 

things have improved drastically 

I still use Carrara as well myself but certainly you should give D|S a try too

if you have a good Nvidia graphics card iray is a no brainer even if you only render characters as png series to add to scenes in post

I myself do that a lot and so does Dartanbeck

Great, many thanks!  I do have a good nVidia card and have done some DS still renders using Iray, very impressive and useful as backgrounds for Carrara animations.  I did a quick search on "Filament Daz Studio" - is it required for reasonably fast DS animations? 

But OK, sounds like a mix of Carrara and DS might be the answer for animations.  Another learning curve ... sigh. 

well it's a lot easier than it used to be, that's for sure

I too am using DAZ studio a lot now there is iray and Filament precisely because the newer content is made to work in it

back in the Poser days Carrara was the obvious choice, 3Delight was abysmally slow and openGL looked awful 

things have improved drastically 

I still use Carrara as well myself but certainly you should give D|S a try too

if you have a good Nvidia graphics card iray is a no brainer even if you only render characters as png series to add to scenes in post

I myself do that a lot and so does Dartanbeck

I just done a test render using my RTX5060TI 16G, and it worked nicely.  

When i use the texture display on the Viewport the characters are unlit, all dark.  So I am using Filament for the time being which works.  The IRAY mode works as well, through it can be a little strange when you change a Canera's "Dimensions" while using that camera, you will see it stretch for a moment, then correct itself.

I'll do more tests with more complex scenes and have crash reports on. 

After digging online and scraping through the DAZ forums for information (specifically those topics dealing with Filament and the use of Filatoon Shaders) I'm fairly certain that with a little elbow grease and the right settings, it's possible to get output renders similiar to the Fortiche Production Studio style of cel shading seen in Netflix's Arcane series (screenshots attached). 

From a technical perspective (if anyone knows) would the Arcane output depend more on the handpainting of the skin textures or something on the Filatoon Shader side (or maybe even a geoshell thing).  I mean, it's probably both, but I think the hand-painted look of the textures when used on the skin probably push it forward more as opposed to just the Filatoon shaders. You can see the light/darkness sharpness painted onto the skin textures especially around the nose and eyes that is consistent with all characters in that animated series.

I know there are a couple of products in the DAZ store that have Filatoon textures that bring render output close to this, but they are for Genesis 9 and I work with G8 mostly, so I was planning on experimenting with my own hand-painted textures for Genesis 8.  Anyone tried to do this yet--any thoughts from anyone with experience with Filatoon?

wsterdan said:

Totte said:

I've found that on macOS, DS  6.25.2025.17807 crashes when you eiher save a render that is rendered to new window, or you try to render to disk, always, consistent, on both Apple Silicon and old x86_64 HW, so there is something weird in that build that wasn't in thre previous. I don't know how it behaves on Windows, but on macOS it's always CPU rendering, which might be a hint for Windows too.

 

For what it's worth, same version of DAZ Studio, MacBook Pro M4Pro, Sequioa 15.3 and I just did a Filament test render of an animation saving it in .mov format. No crash, and I'm still able to open the .mov file in iMovie perfectly, complete with Audio track in place. Still loving the Alpha.

I've been saving test images for the last couple of days without any crashing. 

UPDATE: I just rendered the same scene out in iRay, same result (albeit much slower ):

.mov file saved, then opened in iMovie complete with audio track in place, no crashes.

 

Interesting - I have crashes when rendering, even just add a primitive and bam.