Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
yeah the not being. able to cancel in animation is a drawback I encountered
I don't set many iterations and do an initial single render before committing to a series
sorry no ghost lights etc, is pretty much unusable for indoor scenes with sets
as I said works with a HDRi, I usually render the surroundings as a 360 first a small lighting exr, for my animations I composite stuff in Hitfilm anyway so single png image series of figures with a separate set background my normal workflow as my PC cannot load multiple Genesis+ figures dressed anyway.
WETA workshop breakdowns show they do this with real footage and rendered as backgrounds so it's good enough for me.
Ok, but they are working on the next Public Build already for a very long time ...
I'm not sure what you point is there.
The duration between builds as far as I recall, has always varied wildly; sometimes days, and other times months.
If anything I'd think a longer gap between releases meant Daz thought the current version was functioning well, though I'm sure there are actually many factors at play.
Well, I studied it and it's meaningless twaddle. I have absolutely no idea what that's all about. I want to launch two instances, render iray in one and work in the other. Perhaps an explanation in terms of how people actually use software rather than technical description of what the developer has done would be more useful to me.
Did you actually download and run the provided script at the bottom of that post?
Yes. I have no idea what the options mean. Why would I want an "instance name"? Why would I want to "clean on launch"? Why would I want to "copy app settings"? Why would I want to "clean on exit"? I don't have to do this kind of thing with any other piece of software I use that opens multiple windows. Can you imagine if Microsoft Word did something like that?
There are plenty applications which only allows a single instance, e.g. Photoshop. Microsoft Word isn't as complex as DAZ Studio. The whole purpose of using that script to create instances is to have a stable environment. The meanings of the various options are explained in that post.
Instance name - to distinguish it from other instances
Clean on launch, clean on exit - wipe settings and data for this instance
Copy App Settings - you can choose to copy the settings from another DS version/instance, otherwise you will get a default set up.
I love the instance stuff, it's working flawlessly
I'm already thinking of a 3rd monitor connected to my PC and yeah, you've guessed it, I'll also try a 3rd instance..
In my humble opinion, launching another instance is like launching a console help command with an argument, to specify the domain help function will look for.
No arguments might default to default app, specifying an instance name allows us to buy another ticket with another place for the same ride...
It is well known I might be totally wrong, it is safer to skip my blurbs.
Does this version solve the problem with some older poser products crashing DS such as the Plushies?
Are you referring to the ones which were on RDNA?
Yes I was, but its to do with things that have ''embedded IK chains'' they crash 4.12.0.85. Just wondered if that was fixed in this version
When you say crash, when does it happen, e.g. loading a Plushie character?
The issue with some legacy IK chanins was fixed http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log#4_12_1_16
And now there is a new version 4.12.1.109 (See first post in thread)
Thank you
When trying to use Iray preview, 4.12.1.109 beta instantly crashes on nvoptix.dll (latest driver 445.87) on Windows 7 with i9 7940X Skylake-X CPU - is Nvidia forcing use of AVX-512 with Iray now on those CPUs? If so, then Iray became useless on Win7...
Going from DS 4.12.1.076 to 4.12.1.109 Iray has moved from using Embree version 2.8 to 3.6 as the underlying graphics API for CPU rendering. And as of version 2.15.0, Embree on both Windows and Linux is said to be bulit using AVX-512 support. So I suspect you may be correct.
All my Windows systems are W10 right now (and happily so - I'm a huge fan of W10) so I can't test this for myself. But someone else with a W7 machine might wanna check as well to make sure - it could also just be a fluke implementation bug.
Hi Everyone,
I am new to the world of Daz3d, but the cms is not working and i am not sure how i can get the install manager and daz studio sink. I have a Mac with the newest update:catalina?
BTW i have already tried to uninstall and then reinstall and that did nothing. would it be possible that the system is not compatible with my mac software?
The new post ssim is predicting pretty nice, altough I expect it to stop rendering when guessed iteration is reached. However, it just continues until max iteration count (5000) is reached. Is this how this thing supposed to work?
According to the change log of Version 4.12.1.97 DAZ implementet Google Filament as an optional draw style.
I‘ve never heard about it but a quick search showed that it‘s an open source real time renderer.
So i was very excited that we finally seem get an equivalent to Blender‘s Eevee for Daz Studio.
Now that the new beta is released i can't find anything about that feature inside DS.
Has it been taken out for further investigation before release or am i missing anything here?
Any information about that topic would be much appreciated.
It has been removed for the time being. See the last entry in the Change Log.
Oh I totally missed that entry.
Thank you very much Doc!
Still seeing a spurious 'renderer already in use' message when striking CMD-R to render on Mac (but not Windows). Clicking on the Render icon in the toolbar does not do this. Also, on High Sierra (at least), canceling an Iray render will sometimes lead to a crash when the Close Window button in the rendering window is clicked. This does not always happen, and I have not, so far, been able to reproduce this in Catalina.
"Support for a new fiber primitive in order to support hair, fur and other geometries based on curves without tessellation. A new example has been added."
From the NVIDIA highlights.
Where could we check this new thing?
So after several months of waiting for Daz 3D to get Daz Studio 4.12.whatever to work right, I just spent the last two hours reading about all the added features, disabling of multiple instances, all while not being able to fix the CPU fall back problem. Wow. Here's an idea; look at what you changed from 4.11 to 4.12 and sift through that code, because I have absolutely no problems, and there was another person here, Outrider 42, who had no problems, until you started introducing things without proper testing.
From what I can see, those whom have problems, either have Daz 4.12 and/or Windows 10. Currently, i'm running Windows 7 Ultimate, Daz 4.11 and have enough hard resources to run up to 10 instances of Daz while 5 of them are rendering out simultaneous 600 DPI images off one Titan. I did upgrade to daz 4.12 beta.. and way back in the beginning i couldn't save a file worth a damn. I immediately uninstalled Daz 4.12 and went back to 4.11, hoping, for over a year now, that Daz 4.12 would get fixed. Nope, seems the developers are only adding problems while taking out useful features.
At this Rate, I'll never be able to upgrade to 4.12 with all the bad decisions being made. So push aside the bean counter people, and focus on the main issues plaguing Daz 4.12; the CPU fall back issue. Leave the instances thing alone (you never had a problem with it before until just recently as Outrider42 pointed out- and i'm one who runs multiple sessions each day (with renderings to boot- [and to really blow your mind, I've run multiple computers off a singular daz library that was shared on the network...hows that for pushing the limits; again with no problems] without failure or fault here), and add in a siingular feature that I'm finding others have too- duplicate formulas. A simple 'ignore warning' toggle switch and everything will be fine- since we can't exactly control what or when vendors update their stuff (I've had to fix things myself because of a screwup). I mean, if you can eliminate multiple instances with a singular toggle switch that takes like two lines of code (someone actually stated this in the other thread), then an 'ignore warning' toggle switch will be roughly the same size fix.
Beceause I mean, seriously, 46 pages of beta discussions, the most prevelant being CPU fallback. I say again; what did you change and examine that code. Nvidia drivers were being released justs as quickly with 4.11 as they are with 4.12- and those that stayed on 4.11 have NO ISSUES.
Not every feature listed in the Iray change log is implemented in DS, yet, but if they haven't been scrubbed from the log it probably means they're implementation is planned. I am told that hair features are certainly intended to be implemented, and that the implementation should be fairly simple for end-users (possibly via a new shader with slightly different properties for soem aspects).
Hello, I noticed that bar which was showing the progress of mesh smoother disappeard in the latest version ( Yellow bar in bottom right corner). I don't know if it's a bug or there is a button to reshow this bar/pane. Does anybody know how to fix this issue?
Instancing is somethign Daz can do, and it wasn't primarily about resources but about clean coexistance from my understanding. A lot of the CPU drop-back issues are in the way Iray works, and Daz was precisely zero control of that (they can, and do, report issues to nVidia) - Daz has doen some work on the aspects that they do cotnrol, which should have improved the experience for animators when the first frame would render n CPU and the second dropped to CPU, but - particularly for non-RTX cards - the newer versions of Iray are passing more code to the GPU and so reducing the memory available for scene data.