Torquinox said:

kyoto kid said:

Torquinox said:

Sevrin said:

Nothing Daz has done or said suggests that 3DL will see a renaissance.  While additional render engines are a possibility, they likely won't get any more support than Octane or Filamant do.

Daz is an asset store, and Daz Studio is their loss leader.  Daz won't ask its vendors to support multiple render engines, and most customers won't want to pay a premium for non-Iray materials.

You're probably right. Filament seems forgotten. There are still a lot of options and enhancements available to fans of 3DL, and I don't think converting to 3DL from Iray is all that onerous. There are converters available and one can use the uber shader to span the gap. Some of those options will perish in the transition to DS5. Some are already gone from the store. Even so, Daz has said the final version of DS4 will remain available to current DS4 customers. And some of us may choose to continue using older versions of DS. There are still a surprising number of people in that category, I think.

...then there's Wowie's AweShader system which as been producing some very remarkable rsults.  

I consider that one of the available options, yes. Very cool, though a bit slower and more render-intensive than I like. The PW shaders are another, though some components have disappeared from the store. I was trying to avoid making a list, though that might be a good idea...

...part of the reason I'm going with a 12 core 3.7GHz  Ryzen and 64 GB of memory (upgradable to 128) on my planned upgrade.  

Torquinox said:

vrba79 said:

What is the actual purpose of Filament anyway?

I could be wrong, but I think it was supposed to be a really fast real-time renderer like Blender's Eevee. I don't think it reached its potential, though.

My understanding is that Filament was designed for use as a real-time physically based rendering engine for Android mobile devices. I believe it was originally a side project by a few people at Google.

It's being used in DS as an alternative option for viewport previews (as opposed to a full blown render engine meant for final renders).

- Greg

vrba79 said:

What is the actual purpose of Filament anyway?

I could be wrong, but I think it was supposed to be a really fast real-time renderer like Blender's Eevee. I don't think it reached its potential, though.

What is the actual purpose of Filament anyway?

kyoto kid said:

Torquinox said:

Sevrin said:

Nothing Daz has done or said suggests that 3DL will see a renaissance.  While additional render engines are a possibility, they likely won't get any more support than Octane or Filamant do.

Daz is an asset store, and Daz Studio is their loss leader.  Daz won't ask its vendors to support multiple render engines, and most customers won't want to pay a premium for non-Iray materials.

You're probably right. Filament seems forgotten. There are still a lot of options and enhancements available to fans of 3DL, and I don't think converting to 3DL from Iray is all that onerous. There are converters available and one can use the uber shader to span the gap. Some of those options will perish in the transition to DS5. Some are already gone from the store. Even so, Daz has said the final version of DS4 will remain available to current DS4 customers. And some of us may choose to continue using older versions of DS. There are still a surprising number of people in that category, I think.

...then there's Wowie's AweShader system which as been producing some very remarkable rsults.  

I consider that one of the available options, yes. Very cool, though a bit slower and more render-intensive than I like. The PW shaders are another, though some components have disappeared from the store. I was trying to avoid making a list, though that might be a good idea...

Torquinox said:

Sevrin said:

Nothing Daz has done or said suggests that 3DL will see a renaissance.  While additional render engines are a possibility, they likely won't get any more support than Octane or Filamant do.

Daz is an asset store, and Daz Studio is their loss leader.  Daz won't ask its vendors to support multiple render engines, and most customers won't want to pay a premium for non-Iray materials.

You're probably right. Filament seems forgotten. There are still a lot of options and enhancements available to fans of 3DL, and I don't think converting to 3DL from Iray is all that onerous. There are converters available and one can use the uber shader to span the gap. Some of those options will perish in the transition to DS5. Some are already gone from the store. Even so, Daz has said the final version of DS4 will remain available to current DS4 customers. And some of us may choose to continue using older versions of DS. There are still a surprising number of people in that category, I think.

...then there's Wowie's AweShader system which as been producing some very remarkable rsults.  

Sevrin said:

Nothing Daz has done or said suggests that 3DL will see a renaissance.  While additional render engines are a possibility, they likely won't get any more support than Octane or Filamant do.

Daz is an asset store, and Daz Studio is their loss leader.  Daz won't ask its vendors to support multiple render engines, and most customers won't want to pay a premium for non-Iray materials.

You're probably right. Filament seems forgotten. There are still a lot of options and enhancements available to fans of 3DL, and I don't think converting to 3DL from Iray is all that onerous. There are converters available and one can use the uber shader to span the gap. Some of those options will perish in the transition to DS5. Some are already gone from the store. Even so, Daz has said the final version of DS4 will remain available to current DS4 customers. And some of us may choose to continue using older versions of DS. There are still a surprising number of people in that category, I think.

Blakmoon said:

I had the same issue, it was after I tested the DrawStyle "NVIDIA Iray", clicked the little icone beside and clicked on the scne :everything then went white when I choose back the DraStyle "Filament".

I found the solution in this thread : Horrendous overexposure problem - Daz 3D Forums

The problem comes from some render settings : in Editor tab select "Tone Mapping" and check "Exposure value" = if the value is white it has been changed, try to reset it (for me the default value is 13).

It corrected the issue for me.

Hello, first of all thank you, you gave me the right hint to solve the problem. But i think you just thought it was "Tone Mapping" related. It was not quite like that, since i had the "Exposure Value" on default (13) already and the issue still occured. But you mentioned the "Draw Style" in "Draw Settings". This was set on "Filament". So i switched it from "Filament" to "Texture Shaded" and the figure immediately loaded up correctly in real time.

There are more options in this tab like "Cartoon Shaded", "Wire Texture Shaded", "Solid Bounding Box" (which shapes the figure in boxes) and so on. All of these options change the figure in the viewport very differently, and the option "Filament" just increase the exposure of the figure. So my conclusion is that must be the root of this problem.

WendyLuvsCatz said:

no, spherical lens doesn't work 

the environment map eventually changes hovering over the parameter thumbnail helps egg it along

Interesting - thanks for the tidbit. Never tried that method before. However, I have a scripted method to get animated Environment Map but it does not work in Filament. It does work in Iray. It is annoying... 

An odd thing I still run into is that the Environment Map does not change from the default.

In Iray, it does change - just not in Filament. Is this still an issue?

Also with Shadows, it only works with SpotLights - does it work with all lights now (even from enviroment (dome only))?

Thinking about it I remember one other way I managed to crash the computer itself with Daz: Trying to render a scene in Iray that has a Filament Node in it.  Takes the machine right out.  Offhand it is likely to be a video card issue one way or another if it isn't heat.

Is it a prebuilt?  Check and make sure that your XMP profile is enabled for your RAM settings in BIOS, and also make sure that ReBar is enabled.

Video card won't affect the responsiveness of the app.  At the point you're just in poking around, loading figures in Filament or Texture Draw mode, etc, your GPU is doing absolutely nothing other than displaying the image on the screen.  This will be your CPU and RAM that will be working while you're doing your setup work, transferring data in and out of memory and to and from the hard drive for loading.  If it's delays and sluggish clicking on menu items, or rotating a model even in a simple scene, I'd suspect that your CPU and RAM are working overtime.  If their speeds are throttled, you'll have some issues.

Opensuse+wine seems to be working well and was very easy to get up and going.

All I had to do was install wine-staging, then use it to install DIM.

DIM installed everything else.

Once DS was installed I told it where my libraries were and I was back up and running in no time.

Filament viewport, Smart Content, dforce, autofit, UI sliders and viewport gizmo, veiwport iray preview, everything I've tried works.

Except for GPU iray rendering.

I guess I shouldn't be to upset.

The mac users get neither Filament nor GPU for iray.

Right now, I'm just out the GPU iray rendering.

edit: DIM won't let me save my password. The 'remember me' box isn't selectable.

I have yet to try Filament but I gotta ask, can it do spherical rendering at all? It would be nice to have another option for doing rendering for VR (though with a little tweaking I've discovered the interactive mode for iray works surprisingly well)

Saxa -- SD said:

barbult said:

In DS 4.21.1.26 Public Build, the timeline animation will only play while I move the cursor around in the Viewport pane. In DS 4.21.1.05 General Release, it plays fine.

For ref, re: DS 4.21.1.26 beta (win10-Nvidia 527.37)
Just tested (1) made new anim (2) then from save, another anim made in 4.16.1.43.
Test both in (3) filament view (4) texture-shade.  
All worked normally.  

Your vid was helpful. Never seem that issue yet. Issue looks annoying.

Thank you very much for testing. I created a different animation today, and it worked OK. However I reloaded my "bad" scene, and the same problem occurred. Maybe there is something strange about that scene or the keyframes in it. If you have time, will you check this scene? I have attached it. Thanks.

Edit: Here is an interesting observation. The different animation I tried today that worked, used Michael 9. The one that consistently won't play uses Genesis 9 Dev Load character. I selected the Dev Load G9 in the Scene pane, and loaded Michael 9, and applied it to the character already in the scene. The very same keyframes played just fine with Michael 9 in that same scene. I tried the same scenario (applying other full characters to the Dev Load G9) and all worked fine. I wonder what is "wrong" with the Dev Load character. Is the problem caused by not having all the anatomy parts (eyes, mouth, etc.) ? I tried adding those anatomy parts to G9 Dev Load and the animation works!

I think it is time to submit a help request about this.

Valve (Steam) has already fought that battle and learned the hard way - it's not feasible for companies to develop for Linux if that isn't their target audience. After the demise of the Steam Box, Valve introduced Proton. Now developers can target the platform they already know, Windows/DirectX/Vulkan, and just make sure that it's compatible with Proton. It involves way less development effort and money.

No reasonable person expects Daz3d to make a Linux native version of DS, that would make no sense financially. But it would be much easier to make the current Windows version install and operate more smoothly with Wine (a Windows compatibility layer). It's honestly almost there already, except for a few hitches with DIM, having to take extra steps to get Iray working, PostgreSQL, and GUI mouse issues. Also, filament works fine in DS/Wine, I used it today.

I believe Filament hasn't been availble on the Mac as the recommended back-end for Filament on the Mac is Metal, and Metal wasn't supported by Qt until version 6.

-- Walt Sterdan

barbult said:

In DS 4.21.1.26 Public Build, the timeline animation will only play while I move the cursor around in the Viewport pane. In DS 4.21.1.05 General Release, it plays fine.

For ref, re: DS 4.21.1.26 beta (win10-Nvidia 527.37)
Just tested (1) made new anim (2) then from save, another anim made in 4.16.1.43.
Test both in (3) filament view (4) texture-shade.  
All worked normally.  

Your vid was helpful. Never seem that issue yet. Issue looks annoying.

Mattymanx said:

AllenArt said:

There is still the issue of "what distribution do I make my software for?", though, if it were me, I'd always go with Debian flavors (Ubuntu, etc.).

I think the main foundational distros would be obvious to support if it ever happened.  The real question would be what dependencies would DS in Linux depend on because those are key.  one simple program may be small in size but its dependencies requirements can end up bloating the install size.  Krita is a good example, you cannot install it unless you install the entire KDE desktop suite.

 

But keep in mind the article is about developers, NOT users.  The Linux user base still only makes up 3% of the overall desktop user base world wide.

Indeed. While the Qt Framework used by DAZ is available on Linux as well, some DAZ-owned code may not be easily portable. E.g. as of now, the Filament render engine is only available for Windows systems. It never has been available for macOS, regardless if Intel-based or Apple Silicon. 

Given that the majority of USERS still are working either on Windows or macOS, from a commercial perspective it would most likely not make a lot of sense to split the scarce (and expensive) ressource called "DAZ Developers" to another platform. Btw, some scripts do already have issues with macOS, as the file paths are handled as in a Linux system.

frank0314 said:

Press and hold [Alt] whilst dragging-n-dropping the icon for an asset in one of the asset views onto the viewport. The center of the target will be interpreted as the world origin for the loading of that asset.
 

Try as I may, this does not work on mac (like other things - filament would be nice).  Does anyone know the mac version of this shortcut?  Tried command, option and control to no avail.