Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.Daz 3D is part of
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
The installer only installs to the General Release
Using the latest BETA 4.12.2.60, with an RTX 3090 Zotac Trinity... when I open DAZ the program makes use of the GPU without any scene being loaded, just because it's open.
As the GPU is in use, nothing can be Iray previewed or rendered... it starts to render and after a few iterations (~60) it jumps to CPU, in the log there seems to be some error referring to the memory, although evidently, with 24GB, and the scene being used, the problem cannot be lack of memory.
It's curious because I left it one night rendering a 300 frames animation, the program rendered 158 and then stopped, from then on I couldn't render more, not even a single frame.
I tried to install different versions of the driver, with the same result.
I've located the file that causes the use of the GPU just by opening the program, it's the file "optix_prime.1.dll" that is inside the folder "\libs\iray"... if I rename it the program doesn't use the GPU anymore when it opens, but it doesn't detect it either.
Is it necessary to install some additional component besides the drivers? (CUDA? Optix?... so I understand this is included in the drivers, right?)
Any possible solution?
Thanks in advance!
As I have exactly the same problem: Texture based preview for all three viewports (perspective - top - individual). Just crashed. Last log lines:
2020-11-02 12:39:52.672 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(353): Iray [WARNING] - DISPLA:GEOMETRY :: 1.0 DISPLA geo warn : Object DS_shape_369_163: displacement shader returned values up to 0.982745, clipped to max displace 0.1
2020-11-02 12:39:52.723 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Auto instancing compression ratio 0.94 (Full instancing compression ratio 1.00)
2020-11-02 12:39:52.723 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Importing geometry for motion time 0
2020-11-02 12:39:53.098 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Geometry import (19 triangle objects with 748k triangles, 0 fiber objects with 0 fibers (0 segments), 4532 triangle instances yielding 23416k triangles, 0 fiber instances yielding 0 segments) took 0.376s
2020-11-02 12:39:53.104 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating materials.
2020-11-02 12:39:53.352 Iray [INFO] - MATCNV:RENDER :: 1.0 MATCNV rend info : found 260 textures, 0 lambdas (0 unique)
2020-11-02 12:39:53.361 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating environment.
2020-11-02 12:39:53.366 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating backplate.
2020-11-02 12:39:53.368 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating lights.
2020-11-02 12:39:53.374 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating object flags.
2020-11-02 12:39:53.382 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating caustic portals.
2020-11-02 12:39:53.382 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Updating decals.
2020-11-02 12:39:53.383 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using iray core convergence estimate.
2020-11-02 12:39:53.383 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Allocating 1-layer frame buffer
2020-11-02 12:39:53.389 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Using interactive scheduling, caustic sampler disabled
2020-11-02 12:39:53.405 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU: using 22 cores for rendering
2020-11-02 12:39:53.405 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing OptiX for CUDA device 0
2020-11-02 12:39:53.583 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Initializing OptiX for CUDA device 1
2020-11-02 12:39:53.695 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering with 3 device(s):
2020-11-02 12:39:53.701 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 0 (TITAN RTX)
2020-11-02 12:39:53.701 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CUDA device 1 (TITAN RTX)
2020-11-02 12:39:53.701 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : CPU
2020-11-02 12:39:53.701 Iray [INFO] - IRAY:RENDER :: 1.0 IRAY rend info : Rendering...
2020-11-02 12:39:53.701 Iray [INFO] - IRAY:RENDER :: 1.2 IRAY rend progr: CUDA device 0 (TITAN RTX): Processing scene...
2020-11-02 12:39:53.706 Iray [INFO] - IRAY:RENDER :: 1.8 IRAY rend progr: CUDA device 1 (TITAN RTX): Processing scene...
2020-11-02 12:39:53.706 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend progr: CPU: Processing scene...
2020-11-02 12:39:53.707 Iray [INFO] - IRAY:RENDER :: 1.19 IRAY rend info : Initializing Embree
2020-11-02 12:39:53.743 Iray [VERBOSE] - IRAY:RENDER :: 1.24 IRAY rend stat : Geometry memory consumption: 26.859 MiB (device 1), 0.000 B (host)
2020-11-02 12:39:53.746 Iray [VERBOSE] - IRAY:RENDER :: 1.20 IRAY rend stat : Geometry memory consumption: 26.859 MiB (device 0), 0.000 B (host)
2020-11-02 12:39:59.514 Iray [INFO] - IRAY:RENDER :: 1.19 IRAY rend info : Importing lights for motion time 0
2020-11-02 12:39:59.515 Iray [INFO] - IRAY:RENDER :: 1.19 IRAY rend info : Initializing light hierarchy.
2020-11-02 12:39:59.515 Iray [INFO] - IRAY:RENDER :: 1.19 IRAY rend info : Light hierarchy initialization took 0.000s
2020-11-02 12:39:59.518 Iray [VERBOSE] - IRAY:RENDER :: 1.19 IRAY rend stat : Native CPU code generated in 0.000s
2020-11-02 12:39:59.587 Iray [INFO] - IRAY:RENDER :: 1.10 IRAY rend info : CPU: Scene processed in 5.881s
I actually cannot find the recommended driver version. Mine is 452.06 (Studio). Could that be the problem?
Minimum driver version is 451.48. Any instances in your scene?
Thanks for your reply.
I just updated to 456.71 (Studio) and everything is back to normal. What I noticed, though, is that the Top View viewport in in my scene was set to NVidia view mode, not texture based. Anyway, seems to be working now. Thanks!
Hi, I just updated the beta version to 4.12.2.60 and now I have lost Iray preview and rendering. Ahh! When I select preview, the progress bar is moving, but nothing is displayed. When I select render, I get a blank render in seconds. The released version 4.12.1.118 works fine for both proview and render. Is this a known bug?
Do you use your GPU for Iray? If so, how old are your drivers? The beta needs newer drivers than general release.
Hmmm, looks like my driver is pretty old - 441.12. I'll update and see if that fixes it. Hope it doesn't break anything else.
Yeah! Installed 456.71 Studio driver and now Iray is working. Thanks!
Getting the latest nVidia drivers is pretty much a prerequisite for Daz Studio betas. In my experience, Game Ready drivers work fine.
I use TinyNvidiaUpdateChecker to save myself the hassle of signing in to the nVidia Experience app or visiting the website to check versions and download the latest: https://github.com/ElPumpo/TinyNvidiaUpdateChecker/releases
Given the lack of supersuit comprehensive documentation, I might update this post with a full step by step procedure to install, upgrade and restore Daz Studio betas (including driver updates and such).
Cheers
你们好 能否详细截图解释一下 怎样做的
Mod Edit :- Google translate "Hi, can you please take a detailed screenshot to explain how to do it"
右键单击例如一个脚本，并选择创建自定义动作
Send a bug report about section plane and a way to reproduce it 100% on 15/10, and still no answer yet.
Alright it's a beta indeed but still :/
...it works in the beta release I've been using (4.12.0.47)
Just tried out the new public release, and I have to agree with the others who've posted about the brightness differences between Filament and Iray. I mean, the difference isn't minor, it's like +4 exposure value.
Changing the value to render for every render isn't really a feasible option.
When DAZ release 4.14 ??
Adding more information and tests regarding this problem (and related to Iray planes): https://www.daz3d.com/forums/discussion/comment/6162761/#Comment_6162761
Daz beta v4.12.2.60 and Nvidia RTX 3090 (although I think it is the same with 1080Ti).
The scene I have ready is rendered well without using Iray planes (in particular, Iray interior Camera), but obviously much slower. If I use the Iray plans the program finishes giving an error in CUDA, stopping the rendering before finishing it completely, and leaving the GPU unusable (it's necessary to restart DAZ to be able to use it again).
Tests I've done:
New scene loading only Genesis 2 Female: it works well both without Iray planes and with them (using Iray interior camera).
New scene loading only Genesis 3 Female: it works well without Iray planes, BUT it fails when using Iray interior camera (it shows the same behavior as the scene mentioned first; BTW, it contains 3xGenesis 3 characters).
Taking into account the above I've made the following test:
Load the first scene that gave me problems (scenario + 3xGenesis 3 characters) and remove the 3 Genesis 3 characters; the result: IT WORKS WELL
Then the problem to be located in using Iray planes along with Genesis 3 characters (NOTE: I haven't tried with G8, it will be the following, and I haven't tried to discern whether the problem is located only with G3F or also affects G3M, although I guess it will be both).
Here are some of the error messages:
Can anyone confirm that, indeed, the problem is in using Iray plans with G3 (or G8) characters? Thanks!
UPDATE: Confirmed, also fails when using Iray planes together with G8F
Set the ISO scale to 0.56 value under Filament options node and you have the same in both , tested with over 20 Real HDRI Environment maps
I've read through a lot of this thread and don't really understand if many are having the exact issue I'm having but...
I have a 3080 but can't seem to render with it when gen8 females are in the scene? I go to my log, it says there's roughly 1mb of memory available to use with my 3080, so when it tries to allocate the memory in the scene to a rendering device (my graphics card), it fails, and won't render. This is weird because the 3080 has 10GB VRAM.
Is there some way to patchwork workaround fix this? It's quite frustrating.
You do have the latest NVIDIA driver installed?
Indeed I do. I've used both the latest Studio and Game Ready driver to no avail. I went from 4.12.2.53(or 54) and had no issues - to 4.12.2.60 and here we are. I'm assuming reverting back to 4.12.2.53 is possible, if that's what I'd need to do, but I really hope there's a fix or workaround to temporarily solve this issue until the next beta update.
What is the exact version number of the driver?
Well, I've tried both the Studio and Game Ready drivers, so I'll provide both.
Studio driver: 456.71.
Game Ready driver: 457.09.
Those should certainly work. I missed originally that this was Genesis 8 females specifically - other content works? If this true even of the base Genesis 8 Female? Under Mesh Resolution in the Parameters pane what is the Render SubD Level set to?
Alright, I've figured it out, though I don't really know why it works. Posting it here for others in case they're having weird, somewhat-related issues.
For me, it was about setting my Instancing Optimization from Speed to Auto. Normally the only time I fiddled with this was to remove the much-known bug related to black rings around various genesis characters' eyes.
For some reason, my 3080 was running/rendering really slow when I had the Optimization turned to Speed. The second I switched to Auto everything fixed itself.
Don't know why it worked but here we are.
Edit: Hmm, as I wrote this and tried a few more renders the more I think I haven't fully solved it yet. There's still something going on, I guess I have to keep investigating.
Doesn't really work for me, but I tend to play with environment intensity and tone mapping settings a lot, for exterior shots changing environment intensity scale helps (of course).
Fwiw here's a (fairly) comprehensive explanation I put together back in February of both what causes that eye phenomenon (commonly known as "Shadow Acne") as well as why playing with the Instancing Optimization setting in DS has an effect on it:
ETA: The Iray Programmer's Manual Now has a slightly better explanation of all this which imo is worth repeating here:
When instancing mode is set to “on”, “auto” or “user”, the scene is automatically shifted in space. This increases the precision and accuracy of rendering computations and reduces precision artifacts that originate from self-intersection. To disable this behavior, set bool instancing_shift_camera to “false”.
It is also possible to force an update of the scene shifting by calling the API method IScene::set_dirty at the beginning of a frame with a flag value that marks the instance transforms as dirty. This is recommended if the camera was moved a long distance (like when rendering new frames of an animation, or the user interactively changing it over time), as there is no automatic update of the shifting in order to avoid unexpected stutter through scene updates when moving the camera.
Imo if DS developers could find a place to implement this new "set_dirty" method as - say - an independent menu command somewhere (called something like "eye fix" or "Update Render Plane") they'd be doing a lot of users a favor.
Yes that is correct, interior lighting need different approaches
@raydant , reading the developer's manual makes me sad. I want all of those amazing things in Daz, like being able to save when rendering, ahahahaha. ;.; but, thank you for this, because now I understand iray and iray settings a lot better. :)