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.
 

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.

 

Been away from Studio for a while and catching up on things--one of which is the (relatively) new Filatoon shaders and the Filament renderer.  I have read and compiled as much information as possible on using Filatoon (casting shadows appears to be more tricky than IRay).  I have reproduced all the information below that I have compiled from various sources including this forum (I take no credit for any of this knowledge--I have no knowledge).  Even taking into account everything below, I still can't get a damn spotlight to cast shadows.  I can cast shadows with a distant light and adjust the intensity in various ways with no issues, but cannot get drop shadows to work with anything else.  If you were to hook me up to a lie detector test as to how closely I think I followed the process below, I would pass, but I have to be missing something and I don't know what it is and it's driving me nuts.

Here's what I have compiled and tried to follow to get cast shadows with a Spotlight (is any of this incorrect?):

Open a Scene and add the Basic FilaToon Environment, which spawns a Distant Light and Filament Draw Options.  Be sure to change Distant Light Shadow Type from None (default) to Raytrace.

1. Enabling and Controlling Shadow Casting:

• Shadow Caster: Ensure that the surface of the object you want to cast a shadow has the "Cast Shadows" setting enabled in the FilaToon Shader options.
• Shadow Receiver: Similarly, confirm that the surface receiving the shadow has "Receive Shadows" activated.
• Tweak Shader Settings: Within the shader settings, explore options like "Shadow Smooth" and "MatCap" to refine the appearance of your shadows. 

2. Light Source Configuration:

• Only one Distant Light works at a time.  Filament only "reads" one distant light (whichever one is highest up on the list in the Scene Tab) and if it's set to "Shadows >> None" it can override shadows cast by other lights.
• Point lights do not cast shadows.
• Spotlights can cast shadows, but you have to enable the Shadow Type you want in your light source settings.
  • Make sure to increase Ray Length to 100 (unless you are trying to do something fancy).
  • Also in Light/Shadow Type, switch to Raytrace (unless, again, you intentionally do not want shadows cast by the light).

Spotlight geometry does not do anything to the light or shadow. The only way to adjust spotlights is brightness and angle. (If you want a point light that casts shadows, use a spotlight with the angle increased to 180). If you light your subject with a spotlight and not the distant light, you will get the dark shadows.

If you are using distant light, keep in mind what parts of the scene might be blocking it. You can either hide those elements or go into the surfaces and set Cast Shadows to Off.

You may also want to adjust the Ambient in the scene to something darker to make the lighting look more contrasted.

3. Filament Draw Options:

• On Filament Draw Options, filter menu for Shadow. Up the Shadow Map size to 4096 or more (I find the default 1024 usually creates blocky shadows). Shadow Cascades bumped to 4 often helps, if you have a lot of stuff going on.
• Tone Mapping and Color Grading: Experiment with settings related to shadows within the Filament Draw Options, as well as Tone Mapping and Color Grading, to achieve the desired visual style.
• Experimentation: Combine different settings and lighting arrangements to discover the shadows that best suit your artistic vision. 

4. Additional Considerations:

• Light Rig Setup: Consider using specific lighting setups, like spotlights, and adjusting their ray length to influence shadow behavior.
• LUT Shaders: Applying FilaToon LUT shaders can contribute to smoother shadows and highlights.
• Filatoon Options: On the surface tab for your character's skin you'll see Filatoon options added after you add the shader. You can play with the Filatoon options the shader added [marked in purple] which do all kinds of things like add rim lights and increase the shadow strength as well as making the shadows hard or soft.
• Lower the intensity of the Distant Light so it does not wash out the Spotlight Shadows.
• You may need to play with the environment weight on items to control shadow darkness.

I'm trying to get a noir shadow look, if it helps.  Any suggestions to keep me from banging my head against the wall will be appreciated.  

Richard Haseltine said:

Actually you don't need that - and if you just purchased (within the last 30 days) you should ask for a refund - uber Point is included in the default resources package that is part of Daz Studio, if you have installed that you should already have it (though it is still a 3Delight light that will not do anything special in iray or Filament).

thank you sir  

Actually you don't need that - and if you just purchased (within the last 30 days) you should ask for a refund - uber Point is included in the default resources package that is part of Daz Studio, if you have installed that you should already have it (though it is still a 3Delight light that will not do anything special in iray or Filament).

I did a lowlight render yesterday on my MacMini Pro M4 of Tiili and CJ Eska 9 and it took three hours approximately. That was fine, I had other things to do during that time. And the render came out great.

If I wanted to get a quick render I could render it on my Windows 11 laptop, but I would have had to wait an hour for a cumulative update to chugged its way. By the time it was done, my spine decided I was over sitting in a computer chair for the day.

If I want super quick, I can open the file in the Alpha on the Mac and render it in seconds in Filament and not get the effect I wanted.

Don't ask me why...at the moment everything goes right! I really don't know what's happened, switch on and now Filament works as It should do. I really didn't any change on settings and whatever. It's like It was a kind of joke  thanks for support!!!

The DSON Cache does not store the product details, they are metadata in the database http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/tech_articles/metadata/start

Where you launch the Edito metadata dialogue from is a matter of taste - for example, if you have 3Delight and iray (or Filament) materials and want to set their content type it can be easier to launch the dialogue from the specific sub-folder for those materials, then you can just seelct everything and assign it to the right type - otherwise you have to carefully go through the file list in the dialogue making sure you seelct all and only then ones to be given a specific type.

What happens if you adjust the Environment Intensity setting (in the Environment Settings node)? Iray and Filament are not entirely consistent there.

My Daz studio version is the last one (4.24) and I've got an NVIDIA GeForce RTX 4050. With Filament the scene is completely dark. The strange thing is that all the character details are in. It's kind they're hide somehow. Everything is under-intensified, but they exist. Just into Filament you aren't able to see them. If you switch into iRay everything goes out. Also my graphic driver is the last one. I really don't know what's happened 

Hi. After updating Windows I opened Daz and immediately noticed something strange. I didn't see the usual grid at the bottom. The panel lights up but everything is dark. If I load a figure in Filament I can't see anything. Everything has a black/transparent background. If I switch to iRay everything appears rendered normally. For my convenience I have always used Filament because it doesn't weigh down and is easy to move. Now however if I want to see my work I have to go to iRay. How can I go back to viewing everything only using Filament? Is there any tool to add? Help :):):)