Nice!

Why isn't there a hint in the log-file?
For every small problem there are warnings and error hints in it (i. e. iRay, shaders, etc.), but no remark on disabling filament.

Install of newer driver on my system not possible.

bytescapes said:

Artini said:

If Daz Studio will run natively on Apple M1 or higher CPUs, than I will be considering getting Apple computer (first time in my life).

Just to see rendering on Apple M1 GPU is worth to wait for...

 You might not see dramatic rendering improvements on M1 (although I'd bet the interface will be a bit zippier).

Apple and Nvidia have fallen out, so you won't find any Nvidia GPUs in future Macs, or even OS support for the Nvidia GPUs found in older Macs. So for Iray renders, you'll be forced to fall back on CPU rendering.

When Iray uses the CPU to render, it seems to create some of the code it needs to do the render 'on the fly'. The code is designed to run on processors using the x86 architecture (i.e. Intel and AMD chips).

To run x86 code on Apple Silicon such as the M1, the code has to be translated into instructions that the Apple chip can execute. Wherever possible, Apple pre-translates the code when the application is first installed. But because the Iray rendering code is generated dynamically when you start the render, they can't do that. Instead, Apple's Rosetta 2 translation engine has to translate it all then and there. I'm simplifying a bit, but the upshot is that Apple has to do a bunch of work to get the rendering code into a form that their chips can work with. That work takes time and the end result is that everything they have to do slows down the rendering process (and CPU rendering is already much slower than GPU rendering).

It's possible that the Apple chips (the M1, and its likely successors the M1X and M2) have so much power to spare that they can do all this extra work and still beat the performance of the old Intel chips. But I think it's more likely that rendering on Apple Silicon will work out a little slower than rendering on an Intel or AMD CPU, and certainly slower than rendering on an Nvidia GPU. Another factor is that the Apple M1 systems we've seen so far have limited memory -- 8GB or 16GB -- which will make things still slower when handling larger scenes.

Note that this all applies to Iray renders. I don't know if 3Delight will be optimized for Apple Silicon, but I think that Octane already has been, and I believe that Filament could be. And Blender has an Apple Silicon version, although I don't know if their renderers have yet been optimized for Apple chips. So anything other than Iray could eventually enjoy some remarkable speed-ups on Apple Silicon (especially if the renderer can make use of Apple's own GPUs rather than the CPU). But Iray probably won't.

I may be very wrong about this, but this is how things stand now, as I understand them.

You have not made a tests with Apple M1 hardware, apparently.

From my own experiments I see 5 to 50 times speed increase in 3D graphics applications on MacBook Pro 13 inches with Apple M1 hardware

while comparing with older Macs, even with Nvidia graphics card.

I know, that iray does not support Apple M1 natively yet, but hopefully Apple will find another solution.

Right now I am amazed by Apple M1 performance and believe me I have started my journey with the computers

like mainframes that were using paper tape as a program and data input, Timex TS1000 with 8 bit CPU and 2 KB RAM

and continue with all possible hardware including the latest ones.

I have a 4GB nVidia GTX 1650 I was given just before the 3000 series RTX released and it runs out of VRAM quite easily though it tends to do that when I switch to Filament rather than when using iRay. It has run out for a few iRay scenes though. 

At those high prices and scant availability why not go for all of the 3000 series RTX cards and just buy the very first 1 within $100 of MSRP? Especially if you are one prone to buyer's regret. 

Let's start by saying that this is a very great tool. With this tool one can easily access multiple functions of a scene using your tab system to move among the various modules without returning to the Daz Studio interface. It is a good tool for teaching users certain fundamentials of scene and lighting. With the inclusion of Filament as a render option, do you intend to update the EJ Easy Pro Render Suite to support a Filament options?

Andreaswb said:

Hi PerttIA,

No idea what you want to find in the log what helpdesk didn't see.

The Filament related dll is listed and only warnings related to iray due to non-existence of GPU.
The PC is a normal i5 and - as already stated: Win7 pro x64, 8GB

And thank you, but I know how to do it here. First had to eliminate personal data.

Andy

There is no such thing as "Normal i5", all the PC's are a collection of components and there is an infinite number of combinations of what the PC is built out of.

But, yes I did find the reason inside your logfile;

2021-06-30 22:57:52.579 OpenGL features for current hardware:
2021-06-30 22:57:52.579 	OpenGL provider: Intel
2021-06-30 22:57:52.579 	OpenGL renderer: Intel(R) HD Graphics 2500
2021-06-30 22:57:52.579 	OpenGL version: 4.0.0

https://www.daz3d.com/forums/discussion/comment/6200861/#Comment_6200861

Real-Time Rendering

• Added a real-time physically based rendering option to the DrawStyle Options menu in viewports
  • Filament (PBR) - Implements the Filament renderer as a DrawStyle
  • Requires: Windows (currently), 64-bit, OpenGL > 4.1

bytescapes said:

Artini said:

If Daz Studio will run natively on Apple M1 or higher CPUs, than I will be considering getting Apple computer (first time in my life).

Just to see rendering on Apple M1 GPU is worth to wait for...

 You might not see dramatic rendering improvements on M1 (although I'd bet the interface will be a bit zippier).

Apple and Nvidia have fallen out, so you won't find any Nvidia GPUs in future Macs, or even OS support for the Nvidia GPUs found in older Macs. So for Iray renders, you'll be forced to fall back on CPU rendering.

When Iray uses the CPU to render, it seems to create some of the code it needs to do the render 'on the fly'. The code is designed to run on processors using the x86 architecture (i.e. Intel and AMD chips).

To run x86 code on Apple Silicon such as the M1, the code has to be translated into instructions that the Apple chip can execute. Wherever possible, Apple pre-translates the code when the application is first installed. But because the Iray rendering code is generated dynamically when you start the render, they can't do that. Instead, Apple's Rosetta 2 translation engine has to translate it all then and there. I'm simplifying a bit, but the upshot is that Apple has to do a bunch of work to get the rendering code into a form that their chips can work with. That work takes time and the end result is that everything they have to do slows down the rendering process (and CPU rendering is already much slower than GPU rendering).

It's possible that the Apple chips (the M1, and its likely successors the M1X and M2) have so much power to spare that they can do all this extra work and still beat the performance of the old Intel chips. But I think it's more likely that rendering on Apple Silicon will work out a little slower than rendering on an Intel or AMD CPU, and certainly slower than rendering on an Nvidia GPU. Another factor is that the Apple M1 systems we've seen so far have limited memory -- 8GB or 16GB -- which will make things still slower when handling larger scenes.

Note that this all applies to Iray renders. I don't know if 3Delight will be optimized for Apple Silicon, but I think that Octane already has been, and I believe that Filament could be. And Blender has an Apple Silicon version, although I don't know if their renderers have yet been optimized for Apple chips. So anything other than Iray could eventually enjoy some remarkable speed-ups on Apple Silicon (especially if the renderer can make use of Apple's own GPUs rather than the CPU). But Iray probably won't.

I may be very wrong about this, but this is how things stand now, as I understand them.

This is an extremely well-written and worded post. Consider this my 'upvote'. 

Artini said:

If Daz Studio will run natively on Apple M1 or higher CPUs, than I will be considering getting Apple computer (first time in my life).

Just to see rendering on Apple M1 GPU is worth to wait for...

 You might not see dramatic rendering improvements on M1 (although I'd bet the interface will be a bit zippier).

Apple and Nvidia have fallen out, so you won't find any Nvidia GPUs in future Macs, or even OS support for the Nvidia GPUs found in older Macs. So for Iray renders, you'll be forced to fall back on CPU rendering.

When Iray uses the CPU to render, it seems to create some of the code it needs to do the render 'on the fly'. The code is designed to run on processors using the x86 architecture (i.e. Intel and AMD chips).

To run x86 code on Apple Silicon such as the M1, the code has to be translated into instructions that the Apple chip can execute. Wherever possible, Apple pre-translates the code when the application is first installed. But because the Iray rendering code is generated dynamically when you start the render, they can't do that. Instead, Apple's Rosetta 2 translation engine has to translate it all then and there. I'm simplifying a bit, but the upshot is that Apple has to do a bunch of work to get the rendering code into a form that their chips can work with. That work takes time and the end result is that everything they have to do slows down the rendering process (and CPU rendering is already much slower than GPU rendering).

It's possible that the Apple chips (the M1, and its likely successors the M1X and M2) have so much power to spare that they can do all this extra work and still beat the performance of the old Intel chips. But I think it's more likely that rendering on Apple Silicon will work out a little slower than rendering on an Intel or AMD CPU, and certainly slower than rendering on an Nvidia GPU. Another factor is that the Apple M1 systems we've seen so far have limited memory -- 8GB or 16GB -- which will make things still slower when handling larger scenes.

Note that this all applies to Iray renders. I don't know if 3Delight will be optimized for Apple Silicon, but I think that Octane already has been, and I believe that Filament could be. And Blender has an Apple Silicon version, although I don't know if their renderers have yet been optimized for Apple chips. So anything other than Iray could eventually enjoy some remarkable speed-ups on Apple Silicon (especially if the renderer can make use of Apple's own GPUs rather than the CPU). But Iray probably won't.

I may be very wrong about this, but this is how things stand now, as I understand them.

Hi PerttIA,

No idea what you want to find in the log what helpdesk didn't see.

The Filament related dll is listed and only warnings related to iray due to non-existence of GPU.
The PC is a normal i5 and - as already stated: Win7 pro x64, 8GB

And thank you, but I know how to do it here. First had to eliminate personal data.

Andy

doubledeviant said:

DAZ_Rawb said:

- Anyone who has Daz Studio 4 in their account will be able to keep it. You'll be able to continue to download and use it for the foreseeable future.

That's appreciated. The current (and only) general release of 4.15 is six months old and lacks significant fixes included in the current beta (for memory leaks, etc). Can the 4.15.0.14 beta be promoted to general status, please, so we have a proper manual installation for a stable 4.15?

I'm interested in Studio v5 of course, but in the meantime I'd like to try 4.15 for Filament and Genesis 8.1, but the lack of an up-to-date 4.15 has put me off (and cost Daz the sale of several products that would have otherwise interested me).

I would second this.  We need a solid and stable 4.15 release before moving to 5.

 

Hello Don,

x86 is a type of Intel chip that were in Macs until recently.  Apple now has their M1 processer chip, and they are moving the Apple platform back to their own chip.

Filament is a "lighter-weight" PBR(Physically-Based Renderer) rendering engine.  I really haven't looked into it much, as I mostly use Iray.

Qt libraries are a set of "building blocks" and compiler used to build applications in C++.  DAZ Studio is built in C++, and thus needs a way to compile all the different functions and subroutines into one cohesive program.  Qt is one such platform to compile C++ for both PC, MAC, and I also believe Linux as well.

I am not a super-techy. What is x86, a Mac reference? And, What is Filament and Qt libraries.

Good to hear DS5 will run on Macs.

- Major Update will be Daz Studio release running for Macs, no other major features in the Pre-Beta.

- All Plugins and some scripts will be broken. The SDK won't be available with this first release, but will be following it up at a later date. Some other less used features won't work at launch, but will be coming online throughout the year.
- This release will work on at least x86 Macs (with both Filament and Iray). We are still investigating if this initial early-access release will run either natively or through emulation on M1 macs, but M1 support will come during the continued development of Daz Studio 5

This is exactly what us Mac users have been wanting. Thanks!

DAZ_Rawb said:

- Anyone who has Daz Studio 4 in their account will be able to keep it. You'll be able to continue to download and use it for the foreseeable future.

That's appreciated. The current (and only) general release of 4.15 is six months old and lacks significant fixes included in the current beta (for memory leaks, etc). Can the 4.15.0.14 beta be promoted to general status, please, so we have a proper manual installation for a stable 4.15?
I'm interested in Studio v5 of course, but in the meantime I'd like to try 4.15 for Filament and Genesis 8.1, but the lack of an up-to-date 4.15 has put me off (and cost Daz the sale of several products that would have otherwise interested me).

Mustakettu85 said:

DAZ_Rawb said:

Hi everyone. Drum roll please...

Details of the upcoming Daz Studio 5 early-access Pre-Beta:
....Filament and Iray...

Could you please share if the built-in 3Delight version is going to be eventually updated to the final RSL build of 12.5.8 (from 2017, not 2015 as the build currently bundled)?

DAZ_Rawb said:

- Anyone who has Daz Studio 4 in their account will be able to keep it. You'll be able to continue to download and use it for the foreseeable future.

Time to back up installers in case one plans to live beyond "foreseeable", I see.

I pretty sure you can still download daz studio 3 and 2 so I see limited reason to doubt that.

DAZ_Rawb said:

Hi everyone. Drum roll please...

Details of the upcoming Daz Studio 5 early-access Pre-Beta:
....Filament and Iray...

Could you please share if the built-in 3Delight version is going to be eventually updated to the final RSL build of 12.5.8 (from 2017, not 2015 as the build currently bundled)?

DAZ_Rawb said:

- Anyone who has Daz Studio 4 in their account will be able to keep it. You'll be able to continue to download and use it for the foreseeable future.

Time to back up installers in case one plans to live beyond "foreseeable", I see.

DAZ_Rawb said:

Hi everyone. Drum roll please...

As Director of Technology for Daz 3D, I wanted to give you some big news.  The Daz Studio team has been hard at work on a massive foundation change for Daz Studio that will be released as Daz Studio 5! Our project has been the #1 priority for the team for quite some time now, and it's almost done. Since we know how important getting a Mac version of Daz Studio is to all of you, we are switching up our release plans (from our normal releases) to get you a look at the upcoming Daz Studio 5 as soon as possible.

Details of the upcoming Daz Studio 5 early-access Pre-Beta:
- Release timing for this early-access preview is coming soon, at the very end of this month (July) or sometime next month (August).
- This will be a pre-beta release. Normally we wait until the software is completely finished before releasing it.
- Major Update will be Daz Studio release running for Macs, no other major features in the Pre-Beta.
- All Plugins and some scripts will be broken. The SDK won't be available with this first release, but will be following it up at a later date. Some other less used features won't work at launch, but will be coming online throughout the year.
- This release will work on at least x86 Macs (with both Filament and Iray). We are still investigating if this initial early-access release will run either natively or through emulation on M1 macs, but M1 support will come during the continued development of Daz Studio 5.
- It will install into a new location, so you can run it along your current Daz Studio (release/beta) without problems.

As for the final Daz Studio 5 release:
- The timeline for this is to have it out near the very end of this year.
- Features and enhancements will be rolling in through the rest of the year.
- Anyone who has Daz Studio 4 in their account will be able to keep it. You'll be able to continue to download and use it for the foreseeable future.

I hope everyone is just as excited about Daz Studio 5 as we are.

DAZ_Rawb, could you please have DAZ prepare a list of all the DAZ products (scripts/plug-ins), with their product ID, that will not be compatible with DS5 (even if they might be updated at some undetermined future date)? This should be something that can be completed in the beta phase since the compatibility issues are due to QT4 vs QT5 and not bug free DS5.

Petra said:

So other than that it will work on a Mac with Iray and filament, there is nothing new for PC Daz Studio Users?

Initially, no - overhauling the framework has to come first, I would suspect even for the Windows version without the Mac issue, but Rawb ddi clearly say that actual new features would follow.

So other than that it will work on a Mac with Iray and filament, there is nothing new for PC Daz Studio Users?

 

Hi everyone. Drum roll please...

As Director of Technology for Daz 3D, I wanted to give you some big news.  The Daz Studio team has been hard at work on a massive foundation change for Daz Studio that will be released as Daz Studio 5! Our project has been the #1 priority for the team for quite some time now, and it's almost done. Since we know how important getting a Mac version of Daz Studio is to all of you, we are switching up our release plans (from our normal releases) to get you a look at the upcoming Daz Studio 5 as soon as possible.

Details of the upcoming Daz Studio 5 early-access Pre-Beta:
- Release timing for this early-access preview is coming soon, at the very end of this month (July) or sometime next month (August).
- This will be a pre-beta release. Normally we wait until the software is completely finished before releasing it.
- Major Update will be Daz Studio release running for Macs, no other major features in the Pre-Beta.
- All Plugins and some scripts will be broken. The SDK won't be available with this first release, but will be following it up at a later date. Some other less used features won't work at launch, but will be coming online throughout the year.
- This release will work on at least x86 Macs (with both Filament and Iray). We are still investigating if this initial early-access release will run either natively or through emulation on M1 macs, but M1 support will come during the continued development of Daz Studio 5.
- It will install into a new location, so you can run it along your current Daz Studio (release/beta) without problems.

As for the final Daz Studio 5 release:
- The timeline for this is to have it out near the very end of this year.
- Features and enhancements will be rolling in through the rest of the year.
- Anyone who has Daz Studio 4 in their account will be able to keep it. You'll be able to continue to download and use it for the foreseeable future.

I hope everyone is just as excited about Daz Studio 5 as we are.

Hi,

related to my Filament problem I opened a trouble ticket.
Now I got the question whether I have crashes trying to "login".

I'm really irritated: Is it necessary to use "Connect" for Filament usage?

What if I'm not connected to the WWW ??