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
like this
Gotcha!
I figured out this much: the crash happens if I change anything in render settings after there is something in the scene. So I can adjust render settings THEN put something in the scene and it's fine, although still have the double windown at first save. The moment I touch render settings crash is guaranteed at next save.
I'm getting the same errors message after trying to render in Iray on my 2008 MacPro in El Capitan. Last version of DS rendered fine in Iray. In the new version even 3Delight wasn't working at first but now, for some unknown reason, it started working again. Still, I rely on Iray rendering and that is NOT working after the update.I'm very upset and wish I could revert to the last version of DS.
That is sorry due to the Apple-nVidia feud, nVidia has decided to not support Apple with GPU renderd anymore in Iray.
Thanks for your response but, no, I'm not talking about NVIDIA GPU rendering. In the last version of Daz Studio I wasn't doing GPU rendering, I was doing CPU rendering. Worked until the latest update.
That's strange.
Can it be an Intel Core 2 Duo issue?
Does it always crash or was it a particular scene?
I've done a handful renders using the lastest and no crashes in Iray, Xeon CPUs though, MacPro
I'm not Dkal, but I'm the one with the ancient Intel Core 2 Duo iMac having the same issue. Dkal has a MacPro, so I doubt it's running a Core 2 Duo. ;) I'm totally unable to render in Iray now for any scene - it just runs for a couple of seconds and then spits out a transparent or black render. It was working fine up until the last update. Is anyone else running CPU renders having the same issue? Could it be an issue with older Macs? I opened a ticket last week, but no response yet. I wish I could just roll back to the last version. :(
Have any other Mac users seen a problem where hitting command-R to start a render produces a spurious 'Renderer already in use' dialogue box? This is in the recent Beta versions, and presumably the new release versions. I have seen this on both my iMac and my fairly pristine Macbook Pro that I sometimes use as a canary-in-the-coalmine system. But I have filed a help ticket, and they sort of don't seem to believe me, which makes me wonder if I have set some obscure option or something.
Yes, every time I hit command-R I get a "Renderer already in use" dialog box. Then I hit Okay and the image renders anyway (in 3Delight, but it doesn't render in Iray. Just a blank image instead). If I select Render from the Render menu then I don't get an "in use" warning. Others have reported the same issue. It happens in both the last public beta and the final release.
I'm on an old Mac Pro: Here are the specs: Mac Pro: (Early 2008); Processor: 2 x 2.8 Ghz Quad-Core Intel Xeon; Memory: 14 GB 800 MHz DDR2 FB-DIMM; Graphics: ATI Radeon HD 5770 1024 MB; ATI Version: 2.1 ATI-.1.42.15
Iray renders yield a "blank" image as if there was nothing in the scene. I get the same logfile warnings as katiew does. Sometimes DS will crash immediately after rendering the blank image. DS always crashes if I switch the viewport display to NVIDIA Iray mode. 3Delight rendering works now although it didn't the first day I installed the update. Weird. I rely upon Iray rendering though and wish I could just revert to the last version of DS. It worked flawlessly.
There needs to be a large red warning to mac users with nvidea cards do not updat to latest DAZ unless you want your graphics card useless!! Time to find a new 3d program any recommendations? Or work arounds? Unfortunately have been using daz since it's started seems to have been a waste of money and time
Yep, I get that also. Then, I tried Selecting Render from the Menu. It started rendering with the flawed dialogue box. Haven't tried a 3Delight render.
But, more annoying are the crashes when I try to save a file. Usually, I'll do this multiple times when I'm developing a pose. So, I get multiple crashes. If I try to cut down on the number of times I save the scene, I risk having DS just suddenly crash on me, and then everything I've done since the last save is lost. At least, if it crashes when I try to save, the saving is accomplished very quickly.
Maybe DS should have a "Save every _____ " option, and the user could specify how often.
I really think what's needed is a translation of Open GL and Open CL to Metal. Isn't that possible? I don't really understand what CUDA is. Is it owned by Nvidia? If so, then maybe it would be illegal to translate CUDA to Metal. But, if DS is rendering in Open GL and Open CL for people like myself, who are not using Nvidia Graphics cards, then isn't it both legal and possible to translate the Open GL and Open CL to Metal?
I also use Poser, though not as frequently as DS nowadays. If a translation were accomplished, would it work with Poser as well as DS? Or, would the translation be specific to only one app? In any case, I would really like to have Open GL and CL translated into Metal. I would think the person who would do this could make some money on it. Can't Apple do this, and why doesn't Apple do this?
OpenGL rendering is not an option, 3Delight or Iray, OpenGL is only for extreme draft render (what you see in the viewport)
CUDA is nVidias GPU compute system, which Iray is based on for GPU rendering. Metal ports would be needed to be done for OpenCL (for simulations, including all plugins using OpenCL, like Fluidos I & II, and OpenGL for the viewport.
Each program needs to be translated as long as there is no bridge released between OpenGL and Metal, but bridges has a downside, they often eat performance.
Thanks for the explanations, Totte. So it would be legal to translate, then. The translation might eat performance some, but it would probably be faster than just using Open GL and CL on the Mac. The CPU and GPU cards will probably continue to improve and get faster, also, I imagine.
And, even the Windows users are having some problems with the Nvidia GPUs. It seems they have to upgrade to a newer, more expensive version of an Nvidia card if they want to use the latest versions of DAZ Studio. Some are pretty upset with that. So, translation to Metal would free Mac users from wondering and worrying what Nvidia is going to do next. All in all, that may be a good thing.
With Apple pushing Metal, will Open GL and CL still exist in future OS versions? They seem to be there in Catalina and in the Graphics cards (at least in some of them) Apple is selling with the Mac Pro 2019.
No, the only cards that no longer work with Iray are Fermi cards, which are 9 years old at this point. I have one, so I can't use it for Iray in DS4.11 or 4.12. For those with less ancient cards, they just need to update drivers.
I'm so upset with myself for not backing up the installer for 4.12.0.86, the last general release version of DS. It worked. Now I have no way to go back and I'm stuck with a version of DS that does not do Iray renders. Through the years, I've spent SO much money on products for DS and now I'm wondering if all is lost, I'll never render again in Iray, and all I spent is now wasted money. This is a major disappointment!
Let's see what I can dig out, hang on....
Nope - doesn't look like the old installers will be available again.
You could contact Customer Services, asking for the 4.12.0.86 installer and explain why. No guarantee though.
https://helpdaz.zendesk.com/hc/en-us/requests/new
Make sure you ask for the matching version plugins as well.
Same. Still no response to my support ticket, either. I'd be happy if I could just roll back to an earlier version. :(
I don't understand. I'm using the latest 16" MacBook Pro with Catalina & Daz 4.12.0.86 and I only render in Iray. I have no problems. The problem that I do have is that I can no longer choose to use the GPU.
If you have a fast and big nVidia card, render with CPU only is 30 times slower than with GPU,
In another thread, D.Master says he does not render in DAZ Studio; he renders in Marmoset: https://marmoset.co/toolbag/
Is Marsoset faster, or what? Are nVidia cards needed? What about DAZ Scenes, and shaders?
Just seeking information.
Site says:
Well, that's good news. So, the Apple Graphics Cards should work.
In another thread > https://www.daz3d.com/forums/discussion/comment/5611876#Comment_5611876
D.Master comments about exporting from DAZ Studio and importing into Marsoset.
I'd still like more linformation on Marsoset. You have to pay for it, of course, but it doesn't seem overly steep in price: $189.00, and it does say "Perpetual License," and it does say "free point release updates," though I guess you'd have to pay when the next full version is released.
Maybe, for Mac users, this would be worth looking into.
As part of his comment, D.Master does write, "[I]t is real time rendering. Daz will move on to this about next year or so. if not they will fall behind."
DAZ almost has that already on Windows with the RTX 20xx cards, I doubt that DAZ will spend the money needed to get this using some other technology on macOS, sad but true, Apple did make a lot of users uphappy when they decided to stop nVidia from developing drivers for MacOS 10.14 and beyond.
I've been looking everywhere trying to answer this, so sorry if it's been mentioned before. But with my MBP (2014 Retina, i7 Quad 2.3, GeForce GT 750M) with Bootcamp and Daz for Windows can I use iRay rendering with the NVidia card?
Next question, if I were to upgrade to a new MBP and did the same Bootcamp and Daz for Windows would I be able to use a NVidia card with an eGPU?
Doing very basic scenes sometimes with nothing other than a character and Daz crashes when trying to work with lighting and iRay previews.
I'm also have problems with getting the CMS to work, Tried both Release & Beta with no luck, Also tried using your fix but that didn't help either
This is what the error log gives me
LOG: database system was interrupted; last known up at 2020-05-12 10:07:24 BST
LOG: unexpected pageaddr 5/96DCA000 in log segment 0000000100000005000000AC, offset 14458880
LOG: invalid primary checkpoint record
LOG: unexpected pageaddr 5/96D76000 in log segment 0000000100000005000000AC, offset 14114816
LOG: invalid secondary checkpoint record
PANIC: could not locate a valid checkpoint record
LOG: startup process (PID 2088) was terminated by signal 6: Abort trap
LOG: aborting startup due to startup process failure
OS: MacOS 10.15.4 Catalina