Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
You need to install the beta 4.15.0.26 or up. Check Beta in DIM and if you havent added the beta to your products do it in the store.
it was not the beta, hence the problem .... anybody looking to install the beta, it can be found via your product library, where you tell it to be downloaded to DIOM ... then you can install it fromn there.
4.15.02 is the latest release version (=not beta)
Have you 'bought' the beta?
https://www.daz3d.com/daz-studio-beta
Hi Everyone, this long-time lurker needs some help! I'm usually pretty good about figuring out stuff like this, but I'm really stumped this time. I've got a 2020 M1 Mac Mini and have been eagerly awaiting this release. However, I can't get it working- I keep running into all kinds of error messages.
I've installed the latest version of Install Manager. That seems ok, but when I try to open Daz 4.15.02, I keep getting the error: "You do not have permission to open the application 'DAZStudio.app'" (same issue mcorr was having). So I "purchased" the beta release in the store, but that isn't showing up in DIM. I tried restarting DIM, but beta still not showing up there, and there's no way to download it manually.
I've also tried downloading the beta through my product library in the Daz store. But when I click on the green "download now" button next to "Daz Studio
IM00012000-04_DAZStudio415PublicBuildMac64bit.zip" it opens a dialogue in Install Manager: "Would you like to save the existing filter?" That also seems to be a dead end.
What am I doing wrong? Can someone who's got this working walk me through it like I'm a 5-year-old? :-D
Thanks for any help you can provide!
RK
If you have the Public Build in your order history it should show in Install maanger - click the Download Filters button and make sure Public Builds are checked. 4.15.0.2 is the Geenral reelase, and isn't Big Sur compatible - the Public Build is currently 4.15.0.28, though there have been frequent updates so that may well change soon.
The prompt about saving the existing filter may just mean you had something entered in the box at top-right, so it was asking if you wanted to keep that before applying the filter to show the Public Build from the Product Library click.
It's running, but w/out nvidia there is no denoiser, nor filament ....plus the render is so S L O W .....
On the plus side, pbr is working and 8.1. renders, but it#s not an industrial type render, just a preview like render given the limitations mentioned (to say nothing of what would happen with larger files .... uselessI imagine).
Daz 5 needs to be finished to get native support, not Rosetta emulation (at least the render would speed up).
Presently,this is only a temp solution, not not one for any serious work on a macmini m1, like mine.
DS is running only in name, not as we a would hope/expect.
Iray would need to be rewritten with native M1 code by nVidia, Daz has no cotnrol over that (or over 3Delight).
>>Iray would need to be rewritten with native M1 code by nVidia, Daz has no cotnrol over that (or over 3Delight).
There are already more than one graphics device choices in Daz. A native M1 Metal selection (Most likely through a library layer such as Vulcan) would not require assistance from NVidia. The port is up and working great for me. Except for the normal copying the libraries and missing some textures (not unusual), it's been very stable. Darn, now I have to put an M2 Mac mini on the Christmas list.
You forget one small but damn important thing here, materials.
You cannot just simply take materials for one render engine and feed them to another render engine and think it will come out nice. If you have tried Octane or LuxRender with DAZ Studio scenes you know the huge amount of mateiral tweaking involved to even get a decent render.
So it's not just to throw in another render engine and think evernyone's happier.
I am fully aware of that. As I said, "at least the render would speed up."
One other thing, since installing 4.15 on my mac mini, on top ofall the otherl limitations, almost every time I want to use (click on) the color picker (to change the color of a surface), DS crashes. This has happened on people, as well as props. Has anybody found a solution to that, or is that another limitation that must be accepted?
Vulkan would be the wise move.
This should probably be reported to Daz via a support ticket, though it may be worth hanging fire to see if others see the same thing.
If rendering in Metal does become an option, think of the opportunity for a skilled Mac coder to come up with a product that transfers materials from iRay to Metal. Sure, it wouldn't be perfect, but then perhkaps another product could come along that would allow the shaders to be tweaked. In any case, this could be a real boon for some DAZ vendors.
I've reported it after In read this thread. The crash is consitent on my M1Mini with macOS 11, happens the second time you call up the colorpicker with a crash in objc_msgSend (sending selector SetBackgroundColor to an object) which is an indications some object was released and therefore objc_msgSend crashes. As the crash do not happen on my macPro running 10.4.6 it is either macOS 11 or the M1 that is doing things differently.
Another problem with the file system, I keep getting errors finding textures in the runtime directory, garnering a popup. Looks to me like their routime does a forced lower case to work with Windows, but the Mac uses upper and lower case. Perhaps someone at DAZ can get Apple to look over their routines that access UNIX file systems, there is something broken.
The name of the directory is: /users/Shared/DAZ 3D/My DAZ 3D Library/Runtime/Textures/Jepe/JP BH Project 78
--------
The following files could not be found:
runtime/textures/jepe/jp bh project 78/jpbh78-arms01.jpg
runtime/textures/jepe/jp bh project 78/jpbh78-gens01.jpg
runtime/textures/jepe/jp bh project 78/jpbh78-legsg.jpg
runtime/textures/jepe/jp bh project 78/jpbh78-torsog-05b.jpg
They're trying to address the materials problem with USD. Let's hope that they do, and also that Daz Studio eventually supports it.
How did you format your drive? What filesystem are you using?
On Windows, file systems are case insensitive, but on macOS you can format either with case sensitive (unix style, if you will use lots of unix/linux stuff) or case insensitive. If you format case sensitive you will get errors like that, so, don't. And not specifically to DAZ Studio but a lot of different things will break.
It's a choice you make, linux compatible or old macOS/Windows compatible. Usually you shouldn't use case sensitive unless you really need to compile and run older unix things that rely on that.
this is very good news.
Will this version be compatible with older mac 10.13.6?
Will you re-enable GPU rendering with Nvidia cards (NVIDIA GeForce GTX TITAN X) on these older macs, as we are penalized on rendering times since it no longer works on macs.
Will there be a more functional interface especially with the use of Wacom tablets, it's not great ?
I've never understood anything about keyboard shortcuts, so I'd like to improve the settings in the preferences.
I have been using C4D for over 20 years and I find daz studio very obscure in terms of use.
Thanks
So back to Daz 5tudio...
Any chance that daz will release the keys to the HD kingdom for Daz5?
From what we've been told I don't see any reason it wouldn't be.
That's not something Daz has any control of, they don't develop Iray.
Yes it does!
nVidia decided to cut out macOS from HW renders in Iray as part of the Apple-nVidia grudge, nothing DAZ can do anything about.
Yes, I know the problem and they piss me off
Thanks guys
Nvidea is moving ahead with Iray and that means older GPU architectures are no longer supported. It is just as tough on Windows users with older systems.
I am somewhat filled with dread at the concept of Studio 5. So many plug-ins that I rely on are for DS3 and DS4. I am trying so hard to procure an OS 10.15 mac, but it is looking like I will be forced into big sur or building a PC.
But then again, I switched back to Studio 4.8 because iray makes better renders in that version by a massive degree. So since we can't halt the furthering of time or bad decisions in software, I would like to make one little request:
Legacy iray renderer support in DS5. When you go to the render options drop down, it would have each of the iray renderers used so far. That way I could use DS5, select the DS4.8 engine, and have things look good.
...yeah as of sometime last year (in a post from Nov. 10th, 2020 on the release notes for 4.15), it was mentioned that "smaller" Maxwell GPUs had already been moved to "depreciated" status. Prices better come down on the 3060.before my Titan-X becomes obsolete.
@ Kjartan: ...I render in 4.10 even though I build my scenes in 4.12 as in that release, a new version of Iray was included that was optimised for the new RTX cards which put older ones at a disadvantage in speed as OptiX is permanently set to "On" for pre RTX GPUs.
You've made comments like this numerous times, and I don't understand why, since you're already choosing to stay several versions of DS behind. The deprecation (not "depreciation") of older cards is only an issue with newer versions of Iray, so if you don't upgrade past 4.10, your card will never be obsolete.
...if a new version of Daz either introduces some features I've been waiting for and/or fixes some long running annoying bugs (without introducing new ones) I'd update.
The first part was just informing any who was not aware (not everyone reads the release notes) . The second part of my response was to Kjartan who has done the same, to let him/her know he/she is not the only one doing so.
My reluctance to move to 4.15 is primarily due to the number of comments I've seen regarding bugs, some that seem fairly serious. Don't need the extra frustration.
YES, that's a very good idea, I'd like that too and it wouldn't cost daz anything.
I'm on mac 10.15 and I use daz 4.15 with Genesis 8.1 and I have no problem but the rendering is too long with the CPU and yet I have 24 virtual cores, fortunately.
I wouldn't go back to a pc for anything in the world.