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.

Thanks for the reply!

I've been reading and watching some videos since I sent this message and I'll definitely use FDM. After my research, I'm inclined to buy the Ender 3 S1 Pro:

https://www.creality.com/products/creality-ender-3-s1-pro-fdm-3d-printer ;

Do you reckon it would be a good choice? I've decades of experience with IT (all sorts of things), I build my own PCs, etc; but I have zero experience with 3D printers (apart from the videos I've been watching).

wsterdan said:

You can probably eliminate a lot of research by deciding if you want to print with Resin (SLA, usually) or Filament (FDM). 

Resin printing generally has smaller build sizes and more expensive material (with more clean-up and a greater need for a well-ventilated room) while filament (usually PLA, though there's a wide range of filament types you can use beside PLA) is much, much cheaper and normally has larger build sizes.

Resin has a much higher resolution print quality; PLA doesn't print with as high a resolution, but can still be very decent.

It mostly depends on what sort of things you wnat to print, and at what size.

Once you decide on whether you want to use Resin or Filament materials, it will be easier for someone to suggest a printer and material.

Hope that helps a bit,

Walt Sterdan

You can probably eliminate a lot of research by deciding if you want to print with Resin (SLA, usually) or Filament (FDM). 

Resin printing generally has smaller build sizes and more expensive material (with more clean-up and a greater need for a well-ventilated room) while filament (usually PLA, though there's a wide range of filament types you can use beside PLA) is much, much cheaper and normally has larger build sizes.

Resin has a much higher resolution print quality; PLA doesn't print with as high a resolution, but can still be very decent.

It mostly depends on what sort of things you wnat to print, and at what size.

Once you decide on whether you want to use Resin or Filament materials, it will be easier for someone to suggest a printer and material.

Hope that helps a bit,

Walt Sterdan

I have been in Texture Shaded mostly. but it has also happened in Filament and Iray draw modes.I'm wondering if my daz script library (dzscript) is corrupt.

It is interesting that things that seem rather catastrophic, like repeated recursive operations,unhandled error, and stack push/pop mismatch are only WARNING, not error. The only real clue to where this trouble is happening is the [WARNING] :: ..\..\..\..\..\src\sdksource\general\dzscript.cpp(1189), but that doesn't even seem to be a line reference in the Render Doctor script, but maybe some generic script function it calls?????

My log corresponding to the snippet you posted is here:

In that test I tried different geometry (trash bag) to apply the granite prest to and a different lighting HDRI. That made no difference.

After "Pausing at least 5000", mine says "Finished Pausing". Yours starts getting warning messages. I have my viewport in Texture Shaded mode. How about You? I wonder if using Iray Preview or Filament viewport could have an impact.

At this point we don't know if the m1 GPU will be used in the near future, but if it is (but probably won't) it won't be until DAZ Studio 5 is released. We have been told at one point that DAZ Studio 5 uses Metal, but that may just be that it's needed as a back-end to supply the Filament rendering engine to the Mac platform.

-- Walt Sterdan

SofaCitizen said:

I would probably avoid using Daz Central or Connect in that situation - infact if you setup the base library on the external drive properly you won't even have to run DIM after Daz Studio is installed. Once DS is installed, immediately go into the list of base libraries and remove the pre-created ones which will be on C: - you will probably want to manually remove those folders. Then you can add the base library from your external drive and within Content DB Maintenance you can check Process Metadata Queue and Re-import Metadata and this will import everything into Smart Content (after several minutes).

However, even if you fully clean up and uninstall everything before you go home you would have to check the T&Cs to see if that is allowed. It probably would be since you would not be loading paid assets onto your friends computer but it's best to check for sure.

Iray preview does run on non-nvidia cards - albeit slowly. However, I don't know what the minimum spec would be for that, or filament or even just textured preview.

I don't want to screw up my existing DS (which already has multiple issues!) so I'd bring a fresh HD and install probably just what I needed on the new HD or who knows, maybe a fresh install would clear up my current issues. I don't see another way except through DIM but I have issues with DIM when I want to install into different folders (ie; I have a separate G9 folder) it will not show the items (all greyed out) on the folder that was not used in the last download. So if I download G9 items into its folder through DIM then open DS all my other content is greyed out and vice versa. I'm having so many issues with DS I 

I would probably avoid using Daz Central or Connect in that situation - infact if you setup the base library on the external drive properly you won't even have to run DIM after Daz Studio is installed. Once DS is installed, immediately go into the list of base libraries and remove the pre-created ones which will be on C: - you will probably want to manually remove those folders. Then you can add the base library from your external drive and within Content DB Maintenance you can check Process Metadata Queue and Re-import Metadata and this will import everything into Smart Content (after several minutes).

However, even if you fully clean up and uninstall everything before you go home you would have to check the T&Cs to see if that is allowed. It probably would be since you would not be loading paid assets onto your friends computer but it's best to check for sure.

Iray preview does run on non-nvidia cards - albeit slowly. However, I don't know what the minimum spec would be for that, or filament or even just textured preview.

ShelLuser said:

Can you mention some of those limitations?  Considering that Filament is an open source project I fail to see why Daz would use a lite version.

See, the engine itself is already lacking a bit, especially when compared to Iray for example. It was never meant to be a full blown render engine, merely something usable for realtime rendering, which is useful with animations.

This may be a good read:

https://www.daz3d.com/forums/discussion/479476/filament-may-not-be-a-good-choice-for-daz-studio

(edit)

Also interesting to know is that Filament is still being developed and gets constant updates. For example not too long ago Filament was unable to cast shadows, but that has eventually also made it into the engine.

Here's the full feature list. I'm guessing Daz chose to keep the feature set light since it's supposed to be a real time preview. It's a shame because it can produce halfway decent renders.

The interesting thing is that the materials guide provides examples of how to write filament material models (I think that might be what they're calling shaders), but I don't know if Daz's Shader Mixer will accept anything besides RSL/MDL. I'm going to have a look at the DS SDK and see if it has any examples.