Strictly speaking it is a Dawstyle, rather than a full render engine. This will affect how some of the Visible In options work, and to produce an image you need to have the Filament Drawstyle ative and set the Render Engine to Viewport rather than being abole to seelct Filament directly.

With the Filatoon shaders, I've come to appreciate Filament a lot, having an older computer. 

Note there are now some store items that include both Iray & Filatoon/Filament presets (a rarity) plus others where the base product is one or the other but has an add-on for the other render engine.

LaraRebooted said:

For those, like me, who have just been using the Nvidia Iray renderer this whole time, is it safe to assume that nothing will be changing for us regardless of which products we've purchased in the past?

Nothing will change if you're doing all your renders in Iray or Filament/Filatoon.

Can someone please explain what this is for and what it does?  I've been gone for a bit and have no idea what this does.

I don't see many renders of the freebies here, so here's one I made for my author social media. The Christmas wreath from earlier this month and the candle from one of the last year's sets, both rendered in Filament (with an awesome Easy Filatoon to make it, well, easy).

Happy Holidays, everyone!

vrba79 said:

This begs the question: How will Daz3D help out users who can't realistically do much Iray? Some artists use 3Delight, because they don't have a GPU that can cut the mustard, and Filament has some pretty glaring deficiencies when it comes to things like strand hair and transparencies.

Daz is helping out b6yb making sure people are aware that they need to back up their installers - which they have been doing for some time. There is nothing else they can do.

This begs the question: How will Daz3D help out users who can't realistically do much Iray? Some artists use 3Delight, because they don't have a GPU that can cut the mustard, and Filament has some pretty glaring deficiencies when it comes to things like strand hair and transparencies.

I feel for people without a good Nvidia card, but at least with Filament you can tame Iray materials to kinda work right with it. It's better than nothing.

If you got a crash with 2025 Alpha when opening the scene file, DS log won't help. You should check dump files from crash dialogue.

What's the draw style in 2025 Alpha ?  If it's Filament, try setting to Texture Shaded before opening the scene file.

Not without using the Iray DrawStyle, or maybe Filament. The basic drawstyles don't implement al the features of the Iray materials, though DS 2025 has increased what they do.

Yes, and Filament. 

Sorry, I was unclear - When I am working on scenes, switching between Iray and Filament seems to keep the scene decently lit but when I switch to Texture Shaded, it becomes too dark. I have to toggle Preview Lights (Ctrl+L) so the scene would be lit similarly as the other viewport modes. It seems like a bug to me but wanted to be sure I was not seeing some odd behavior or if it was something I did.

Also, will there be documentation on what surface settings will be able to be previewed in Filament and Texture shaded (i.e. displacement, opacity, normals, etc...)?

And will shadows be something available in Texture Shaded?

cain-x said:

The Universal Viewport mode is interesting but will there be parity in lighting/exposure when it comes to changing modes between Iray, Filament, and Texture Shaded? 

I am not sure what you are asking. If you mean, will Iay and Filament be item overrides with Universal mode then no - they don't work like other Drawstyles and so cannot be mixed in a single draw.

The Universal Viewport mode is interesting but will there be parity in lighting/exposure when it comes to changing modes between Iray, Filament, and Texture Shaded? 

Yeah, I actually just bought it about 20 minutes ago and already did a fast conversion of a road scene to Filament. Took me all of 10 minutes to convert everything. This will be really great for Filament use, granted I need to work on the lighting a bit, but all the materials are converted.

Yes, the supplied scenes use a lot of instancing, but is surprisingly light on the memory load. The templates with grass (2 of the 4)  use thousands of grass patch instances, but, again, surprisingly light on the memory. Everything shows, but you can't see all of them at the same time (360 degree environment). The Filament view looks off, so some tweaking will be needed.

Does Magix 101 "SkyRay Worlds - Complete World Builder set" use lots of instancing?

I'm using Filament now and too many instances are a problem. Does this set use geometry for everything or is there lots of instancing involved? I can't even see the readme file, I keep getting 503 service unavailable errors trying to access the readme: http://docs.daz3d.com/doku.php/public/read_me/index/92800/start

Anyone own this and can you see everything when in Filament viewport mode? This is the easiet way to tell me if it will work.

I've been fighting with a custom object for a while, trying to get it to work right... I finally have it 95% sorted, just 2 things to complete.

1: Apply the bone system so I can move the main surface anywhere I like (not first time, shouldn't be hard)

2: Make the 4 sides of the pyramid (whose base is the main surface) only visible from inside. Which is proving to be a challenge.
So essentially, it needs to be that no matter what angle you stand viewing this pyramid, you can see its base and the farther sides, while the nearer ones are invisible. In *any* other application, I would just make the material 1-sided, no bother. In fact, most of the time, materials are 1-sided unless you specifically make them otherwise.
Can I find a way to do this in Daz? No. Also couldn't find anything about it in tutorials. Any help would be much appreciated. (Ideally, this would be to work in the Filament engine, but the material doesn't have to be Filament)

Issue: HDRI larger than 8k crash DAZ Alpha.
I give up. I have the exact same issue on two completely different computers:
AMD Desktop with 5070ti Win 10
MSI intel gamer laptop 4070 8Gb VRAM Win 11

It crashes during the HDRI file loading process as far as I can tell:
       > A tiny grey "Please wait" window with a progression bar appears (Too fast for a screenshot), then DAZ stops respondin
       > The log file does not show the expected "Loaded image: XXXXXXXX.exr"  - it just stops at one of the typical "IRAY:RENDER ::   1.0   IRAY   rend info : Received update to 00045.20 iterations after 726.759 ms." 
- Same issue with EXR and HDRI, 16k or 24k
- Same issue with Gamer and Studio Nvidia drivers
- No particular settings in the DAZ preferences, default only. No effect when changing the quality settings.
- No matter if the scene has objects or is completely empty, it crashes as soon as I load the image file.
- The rendering mode has no effect, filament, iray or else
- Changed the screen scaling back to default 100% with original screen resolution. No difference. 
- Tried with many different domes of course, mostly from Polyhaven.
- The perf monitor in the Task Manager does not show anything special, I have plenty of RAM, VRAM and CPU/GPU availability when it happens.
- Of course, no problem whatsoever with DAZ 4.24. Fast and easy, loading the HDRI is no issue. 
- It did work a couple of times only in the last few months when troubleshooting the issue, and I have no idea why.
I am stumped, very few people have this issue as far as I can see and I can´t figure out what´s so special AND in common in my two very different computers. Both Windows are regular, legal licence and up to date. 

I have had this issue with every version of the alpha build, which I have been using for almost a year. It is not a massive constraint - I just render the 16k+ on DAZ 4.24 on the gamer laptop and then apply it as a background. But it really buggers me. I´m not used to fail at troubleshooting ^^'
 

inquire said:

is there any chance that version 4.24 of DS will be made to run natively on an Apple M Chip? The benefit of this would be that if there are scripts that will not work in the new alpha version of DS, a Macintosh user could use the script in version 4.24 of DS, and then save the scene, and reopen it in the new alpha version, and of course, later in the new full version of DS?
Otherwise, when Apple Drops Rosetta 2, Which is probably going to happen in about another year, then all the scripts that will not work in the new version of DS, will not be available to a McIntosh user.

No, they won't be able to make 4.24 Apple Silicon Native, it uses an older version of Qt that doesn't support Metal, to the best of my knowledge. It's the reason we couldn't have Filament prior to the Alpha.